Add workflow to generate appstream releases file #93
Conversation
This file contains 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
oskirby
force-pushed
the
appstream-releases-xml
branch
from
5003bb3 to
a20dc46
Compare
|
Is this ready for review? |
|
Yes, I think this is now ready for review. |
5 tasks
mcleinman
approved these changes
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have a need for there to be a hosted XML releases file, conforming to the Appstream Metadata format, which someday might be consumed by Flatpaks and maybe SNAPs. We already serve a similar file in JSON format here using github pages, it's just not in the correct data shape.
This PR attempts to add a new workflow which can generate the file, starting with our current mozillavpn.json file as the source of truth.
For this to take effect, we also need to update the Github Pages configuration to deploy from a workflow rather than uploading static artifacts. The configuration is as follows:
