Release v1.0.0 - #12
Merged
Merged
Conversation
The code-scanning fix removed the found findings from this test's failure message, but left a closure that rustfmt formats differently, so the formatting check failed on main. The message now names the expected rule and file, which carry no secret material.
…ainer Registry Running the Release workflow by hand without a tag now builds every file from the selected branch as a trial and keeps them as downloads of the run, without publishing anything, so a release can be checked before it is tagged. Every job builds the same ref: the full tag reference, or the trial's exact commit. Each release also pushes ghcr.io/sanskarin/repodna for linux/amd64 and linux/arm64, tagged with the version, the minor and major versions, and latest. The image is Alpine Linux with Git and the release's static repodna binary; it trusts mounted repositories so that history analysis works on checkouts owned by another user, keeps its storage in /tmp/repodna so it also runs with --user, and carries the license files. The workflow tests the amd64 image on the checkout before it pushes.
…rsion The release notes copied the changelog's link definitions, which follow the last section, and listed the downloads with a <version> placeholder. They now end with the section's own text, and the download names carry the version.
Without a signature that covers the whole bundle, Macs with Apple silicon report the downloaded app as damaged and offer no way to open it. The bundle is now signed ad hoc, so macOS asks for confirmation in Privacy & Security instead, and the release workflow checks the signature before it collects the installers. The installation guide and the desktop page now describe Open Anyway in System Settings, which replaced Control-click Open in macOS 15.
CodeQL read the ref that the version check handed to every job as possibly untrusted code: a job output named ref looks like a pull request's branch, so each step that ran code after the checkout (npm, cargo, and the built binary) was reported as a cache poisoning risk. Every job now checks out refs/tags/<tag>, or for a trial the commit the run started from, which is what the output held; only people who can push tags or start the workflow decide either.
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
1 participant
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.
What this changes
Why
How it was tested
Checklist
cargo fmt --all --check,cargo clippy --workspace --all-targets --locked -- -D warnings, andcargo test --workspace --lockedpassnpm run format:check,npm run typecheck, andnpm testpassdocs/is updated, and user-visible changes are listed under "Unreleased" inCHANGELOG.md