Repository navigation
fix(ci): restore the version and mode checks #155 dropped - #165
Merged
Merged
Conversation
5958ac8 (#155) renamed the `checks` job from "actionlint + version surfaces" to "actionlint" and deleted its version-surfaces step in the same edit. .mergify.yml still lists `check-success = actionlint + version surfaces` in the default queue's queue_conditions, so no PR could satisfy it and every PR waited outside the queue. Restore the step (`version-management sync check` from the locked pnpm-release-management release-tools) and the job name, so the required check exists and verifies what its name says. The requirement in .mergify.yml is unchanged.
2 tasks
Contributor
|
@Mergifyio queue |
9 of 10 tasks
✅ Merged into
|
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.
Summary
#155 dropped three verifications from CI; this restores them. The merge queue can see the check it requires again (
actionlint + version surfaces), CI again fails when the Nix-built binary reports a version other thanpackage.json's, and the platform workflow again fails on an unknownmodeinstead of passing having built nothing..mergify.ymlis unchanged.Which case it was
The version-surfaces verification was dropped, not just renamed. Commit 5958ac8 (#155, "fix: check .nix files; stop testing configuration") changed the
checksjob in one edit:name: actionlint + version surfacesbecamename: actionlint.Version surfaces agree (release.jsonc, checked by the locked release toolchain)(version-management sync check) was deleted..mergify.yml, added earlier in 9e44128 (#141), still requirescheck-success = actionlint + version surfaces, so no PR could satisfy it.git log -S'actionlint + version surfaces'shows 5958ac8 as the only commit that removed the string from the workflow, and nothing onmasterrunsversion-management sync checkany more. The step first came from 44e1c87 (#138), which retired the repository-local version gate in favour of this toolchain check.The first commit restores the job name and the step as they were before #155. On
masterthe check passes (sync-versions: ok — 0.3.6 across the manifest and every surface), so restoring it does not turn existing PRs red.Other checks #155 dropped
nixjob, "Smoke the built binary version"): comparescomment-checker --versionfrom the Nix build withclaude-code-comment-checker <package.json version>. It was the binary-identity check 44e1c87 kept when it retiredrun-binary-smoke.ts. Restored with the same command; the rationale for smoking the unwrapped binary (the bwrap wrapper needs--unshare-net, which Actions containers do not permit) moved from a YAML comment into the step name, because this repository's comment checker flags it as redundant.mode(platform.yml, "Reject unknown mode"): without it a typo in a caller'smodeskips everyinputs.mode == ...step and the job goes green having built and staged nothing. fix: check .nix files; stop testing configuration #155's description lists this among the deletions as checking only configuration. It guards a caller-supplied input, so it is restored as it was.Left deleted
The
hook_commands.rschanges in #155 stay as they are:repo_settings_hook_runs_the_readme_hook_commandasserted that two config files hold the same string. It restates the configuration and exercises no behavior.exactly_one(nowfirst) counted the hook entries in config files. Same reason.real_direnv_exits_1_without_running_the_command_when_envrc_is_blocked_or_command_is_missingruns only thedirenvbinary and never the hook script or the checker, so it tests a third party's behavior and fails or passes with no change to this repository. Itsdirenvinstall step inrust-gate.ymlis tooling for that test alone, so it stays deleted too.Unapplied review findings
.mergify.yml:14—merge_conditionsdo not includeactionlint + version surfaces. Intended: the commit and surface checks are judged on the PR, the gate on the queue draft, as insystemfsoftware/systemfsoftware.Residual risk: nothing checks that the check names in
.mergify.ymlmatch the workflow's job names, so another rename would strand the queue the same way.The Mergify rule that stops approvals from queueing PRs on
masteris fixed at its source in the organization's.githubrepository, in its own PR.Testing
nix shell --inputs-from . pnpm-release-management#release-tools -c version-management sync checkexits 0.claude-code-comment-checker 0.3.6, equal to the expected value.rehearsalexits 0,bogusexits 1 with the message.actionlint(locked nixpkgs) exits 0.cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test --all-targetspass locally. Mutation was not run: no classifier change.actionlint + version surfaces,nix flake checkandpackaging / rehearsaljobs on this PR's head.20261111-015121-2650e7a1, status complete, depth focused) on the first commit. The later commits restore deleted lines verbatim and were not separately reviewed.