chore(flatpak): refresh generated sources - #656
Merged
Merged
Conversation
Regenerated by the monthly Refresh Flatpak sources workflow. Cargo entries follow src-tauri/Cargo.lock; npm entries re-resolve package.json against the registry, so this also bumps transitive frontend deps for the Flathub build.
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
InstaZDLL
approved these changes
Sep 15, 2026
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 monthly refresh of the offline Flatpak source manifests.
cargo-sources.jsonfollowssrc-tauri/Cargo.lockexactly.node-sources.json+package-lock.jsonre-resolvepackage.jsonagainst the npm registry, so this also bumps transitive frontend
dependencies for the Flathub build only — the app itself is
built from
bun.lock, the Flatpak sandbox runsnpm ci --offline.packaging/flatpak/check-sources.pypassed in the generating run,and the commit is signed (created through the Git Data API) so the
required_signaturesrule doesn't block the merge.GITHUB_TOKEN, which by design doesn't start workflowruns — CI has not run on this PR, and the ruleset requires code
scanning to pass. Close and reopen the PR to kick everything off, or
configure the
APP_ID/APP_PRIVATE_KEYsecrets so future runs openthe PR as a GitHub App and CI fires on its own.