Repository navigation
chore(flatpak): refresh maven-dependencies.json - #525
Merged
Merged
Conversation
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
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.
Automated refresh of
distribution/linux/flatpak/maven-dependencies.json.The
refresh-flatpak-depsworkflow detected drift after a change to apom.xmlonmasterand regenerated the offline Maven manifest used bythe Devel Flatpak build.
Safe to merge once review passes. If the regeneration itself is broken,
the fix belongs in
distribution/linux/flatpak/generate-dependencies.sh.Note: CI does not run automatically on PRs opened by
GITHUB_TOKEN.Close and reopen this PR, or push any commit to its branch, to trigger
the usual
pr-builder/codeql-analysisworkflows. Upgrading this jobto a PAT or GitHub App token would remove that limitation.