Repository navigation
chore(ci): remove the one-off lock-regeneration workflow merged by #441 - #442
hyperpolymath wants to merge 5 commits into
Conversation
zz-one-off-lock-regen.yml was a scratch workflow for a scratch branch: it triggers only on pushes to claude/new-session-th4e9w-lockregen, clones hyperpolymath/panic-attack, and prints a regenerated actions.lock to its log. It was never meant for main and does nothing there. It has no uses: steps, so actions.lock needs no change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 29 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
|
Red checks on this PR that are not this PR's: the diff deletes one workflow file that no job runs, and each of these fails the same way on
Nothing to port into this PR. I cannot re-run the checks from this session. Generated by Claude Code |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Add Carrot credits or activate Agent usage billing to use Autofix |
|
✅ Coding Agent task started: View task and status The task will inspect the CI failures, validate its fix, and commit the fix to this branch automatically.
⏭️ Checks skipped: 1 · already failing on `main` (not caused by this PR)
|
…one entry The two CI-fix commits each added the same `.standards-js/tools/js-runtimes` line with its own comment. One entry, with a note on why it exists and when it can go (the governance pin reaching hyperpolymath/standards#1299, which makes that crate its own workspace root). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
#440 carries the same exclude (its CI-fix commit 78a70c2) and merges first; byte-identical text here means the two land without a conflict. It can go once the governance pin reaches hyperpolymath/standards#1299, which makes that crate its own workspace root. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
Summary
hyperpolymath/echidna#441 merged the scratch branch
claude/new-session-th4e9w-lockregenintomain. That branch existed only to run.github/workflows/zz-one-off-lock-regen.yml, a one-off job that clones hyperpolymath/panic-attack, regenerates that repository'sactions.lockwith a real token, and prints it to the job log. The file triggers only on pushes to the scratch branch, so onmainit is dead weight, and its header says "scratch branch only, deleted after use".Changes
.github/workflows/zz-one-off-lock-regen.yml. It has nouses:steps, soactions.lockneeds no change.Cargo.toml: the workspace excludes.standards-js/tools/js-runtimes. CodeRabbit's CI-fix commits added this (twice) for the redgovernance / JS runtimes — environment provisions Bun firstjob: the governance reusable checks hyperpolymath/standards out inside this tree and builds that crate, and at the pinned standards commit the crate is not its own workspace root, socargo install --pathrefuses it. The source fix is hyperpolymath/standards#1299 (merged); this entry can go once the governance pin reaches it, which is the separate pin-bump PR. The last commit folds the two copies into one documented entry.RSR Quality Checklist
Required
just testor equivalent): no Rust code changed;cargo metadata --lockedresolves the workspace.unsafeblocks without// SAFETY:comments..envfiles included.As Applicable
Testing
git ls-files .github/workflowson the branch no longer lists the file;grep -c zz-one-off .github/workflows/actions.lockis 0 onmainand on the branch, so the lock gate sees no change.cargo metadata --locked --no-depssucceeds with the exclude in place.Screenshots
None.
Generated by Claude Code