-
Notifications
You must be signed in to change notification settings - Fork 16
Use lossless PNG compression to prevent transparency artifacts #4281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
8957c8a to
1b40bda
Compare
9dadcd1 to
9122f26
Compare
|
@ppawlowski can you take a look here? The alternative would be changing https://github.com/FlowFuse/website/blob/main/.github/workflows/calibreapp-image-actions.yml#L27 to 100 for example. See my comment at #4278 (comment) |
Can we try this solution first? Just to follow the KISS principle. |
…rent pngs KISS version of #4281
|
closing in favor of #4300 |

Summary
This PR fixes white border artifacts that appear on transparent PNG images after automated compression.
Fixes #4278
Problem
The
calibreapp/image-actionsworkflow was using lossy PNG compression (80% quality via sharp/libvips), which can introduce white border artifacts at transparency boundaries. This was observed in PR #4273 wheremcp-in-flowfuse.pngdeveloped a white border at the top after automated compression.Timeline
calibreapp/image-actionsdefaultpngQualitywas always 80% (lossy)Solution
Use a hybrid approach:
Additional optimizations
Safety guarantees
GITHUB_TOKENdon't trigger new workflow runsTest plan