Update flatpak dependencies to non-EOL versions #724
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scope
electron-builder defaults to 20.08 version of flatpak runtime and base packages. Those packages are EOL, here is example message from flatpak cli:
I couldn't really find a source of truth for those messages, I suspect it just part of flatpak repository that can report if package is EOL
Implementation
Manually specify versions for both runtime and base package. This will require to manually bump them later on, but it's just 2 lines of code change approximately every 2 years, so I hope that's not an issue =)
Screenshots
How to Test
Try building flatpak package on a linux distro with
npm run publish:flatpak
Emoji Guide
For reviewers: Emojis can be added to comments to call out blocking versus non-blocking feedback.
E.g: Praise, minor suggestions, or clarifying questions that don’t block merging the PR.
E.g: Blocking feedback must be addressed before merging.