Repository navigation
chore: update bundled runtime pins - #5
Closed
github-actions[bot] wants to merge 22 commits into
Closed
github-actions[bot] wants to merge 22 commits into
github-actions[bot] wants to merge 22 commits into
Conversation
Select the x86_64 artifact by name and extract it directly into the architecture directory used by the signing step. download-artifact v8 extracts a single pattern match into the supplied path rather than adding an artifact-name directory, so the previous settings left validation looking in the wrong directory.
Generate a checksum after the existing Flatpak build and upload both files as one workflow artifact. Keep automatic builder uploads disabled so the bundle and checksum are published together, and skip artifact compression because the bundle is already compressed. Limit this change to GitHub Actions; the Forgejo workflow remains unchanged.
Use the repository token for AppImage updates when GH_TOKEN is not configured and explicitly dispatch downstream workflows after token pushes. Keep PAT-based automatic triggers when a custom token is available. Serialize each updater to avoid overlapping branch writes and refresh the runtime update branch before force-with-lease. Build contributor branches and retain downloadable CI bundles for three days to limit storage use. Document the main default branch required for consistent scheduled updates and publication.
Use REST pull-request lookup and creation against GITHUB_REPOSITORY instead of CLI fork discovery. Keep the base and head owner explicit so the repository-scoped workflow token never needs access to the upstream repository when maintaining a contributor fork.
Disable optional Rust components explicitly when building Git, as validated in the Forgejo build. The runtime updater now proposes Git 2.56, whose default build otherwise needs a Rust toolchain not provided by this manifest. Older Git versions ignore the variable.
Report missing repository inputs instead of exiting silently and reject unresolved descriptor placeholders with an explicit branch. A bare negated command does not trigger errexit, so the old check could let placeholders through. Quote the release commit expression and use option-safe checksum globs to pass actionlint and shellcheck.
Upgrade upload-artifact from v4 to v7 in the build workflow to remove the Node.js 20 deprecation warning. The release and Pages workflows already use v7, and the existing upload inputs remain supported.
Consolidate the focused platform 26.08, GNU make, and Tools extension branches into development main. Match the extension fixture and its documentation to the new platform version. Make the absence check fail explicitly when the fixture command is unexpectedly available, since a negated command does not trigger shell errexit.
Integrate the sandbox branch while retaining newer runtime pins and managed-tool PATH precedence. Keep host command execution and private key directories opt-in instead of enabling them in the manifest, and align the documentation and task handoffs with those safer defaults. Default shell history to persistent app data even when XDG_STATE_HOME is unset. Add an isolated launcher regression check to CI for state paths, tool precedence, and preservation of existing Git config.
Record the focused upstream artifact changes as integrated while retaining main's Node.js 24 upload action and three-day retention. The checksum and bundle upload behaviour is already present.
Record both upstream candidate branches as integrated into main. Retain the already-correct artifact destination, newer dependency pins, additional tool modules, and NO_RUST build flags.
Bring the security revision of the sandbox PR into main. Retain the newer platform, bundled tools, extension paths, and persistent shell state while removing the host-tool PATH entry. Replace directory and host-command override recipes with opt-in SSH-agent guidance. Persist sandbox-local SSH configuration and run the installed boundary check with disposable canaries, a dedicated agent, and a temporary signing key after building the application.
Point the Flatpak remote, app reference, and Pages configuration at the openSUSE-Python GitHub organization.
- Bundle gitea-cli 0.2.0 as `gt` and note it is not Graphite - Verify gh, glab, and gt are executable in /app/bin before export
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.
Updates bundled runtime source pins for the T3 Code Flatpak.
This workflow keeps updates separate from upstream T3 Code AppImage repinning.