Merged
Conversation
pascalbreuninger
requested changes
Feb 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds devpod's app metadata so it can be pulled by flathub. This was requested in my PR to flathub to publish our flatpak, currently it is in the flathub repo itself.
A templated flatpak manifest has also been added so that we can automatically update the version and hash of the devpod binary. Once this PR is merged, I can update my flathub PR and once approved, devpod will be available on flathub with it's own git repo. When the repo is available I can submit another PR for the CI to push our manifest to it when we cut a new release to update devpod is flathub.
For more info on flathub releases see
https://docs.flathub.org/docs/for-app-authors/submission#after-submission
https://docs.flathub.org/docs/for-app-authors/maintenance