Skip to content

chore(ci): remove the one-off lock-regeneration workflow merged by #441 - #442

Open
hyperpolymath wants to merge 5 commits into
mainfrom
claude/new-session-th4e9w-rm-scratch-wf
Open

hyperpolymath wants to merge 5 commits into
mainfrom
claude/new-session-th4e9w-rm-scratch-wf

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

Summary

hyperpolymath/echidna#441 merged the scratch branch claude/new-session-th4e9w-lockregen into main. 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's actions.lock with a real token, and prints it to the job log. The file triggers only on pushes to the scratch branch, so on main it is dead weight, and its header says "scratch branch only, deleted after use".

Changes

  • Delete .github/workflows/zz-one-off-lock-regen.yml. It has no uses: steps, so actions.lock needs no change.
  • Cargo.toml: the workspace excludes .standards-js/tools/js-runtimes. CodeRabbit's CI-fix commits added this (twice) for the red governance / JS runtimes — environment provisions Bun first job: 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, so cargo install --path refuses 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

  • Tests pass (just test or equivalent): no Rust code changed; cargo metadata --locked resolves the workspace.
  • Code is formatted: no code changed.
  • Linter is clean: a workflow file is removed, none added.
  • No banned language patterns.
  • No unsafe blocks without // SAFETY: comments.
  • No banned functions.
  • SPDX license headers present on all new/modified source files: none added.
  • No secrets, credentials, or .env files included.

As Applicable

  • Repo deed, roadmap, docs, TOPOLOGY, CHANGELOG, dependencies, ABI/FFI: not applicable.

Testing

git ls-files .github/workflows on the branch no longer lists the file; grep -c zz-one-off .github/workflows/actions.lock is 0 on main and on the branch, so the lock gate sees no change. cargo metadata --locked --no-deps succeeds with the exclude in place.

Screenshots

None.


Generated by Claude Code

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
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Warning

Review limit reached

You'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.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 2cb68509-75d3-4f2c-9c7e-ec39d97382ba
📥 Commits

Reviewing files that changed from the base of the PR and between 34a0288 and b935706.

📒 Files selected for processing: 1
  • Cargo.toml

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 95f3718f-8e29-469a-a432-e5d55a6e2480
📥 Commits

Reviewing files that changed from the base of the PR and between 0d0aa0c and 34a0288.

📒 Files selected for processing: 1
  • .github/workflows/zz-one-off-lock-regen.yml
💤 Files with no reviewable changes: 1
  • .github/workflows/zz-one-off-lock-regen.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout: 46
  • GitHub Check: rust-ci / llvm-cov line coverage
  • GitHub Check: rust-ci / Cargo check + clippy + fmt
  • GitHub Check: rust-ci / Cargo audit (security)
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / JS runtimes — pnpm
  • GitHub Check: governance / JS runtimes — bun
  • GitHub Check: governance / JS runtimes — deno
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / JS runtimes — environment provisions Bun first
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: governance / Licence consistency
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / UUID v8 conformance
  • GitHub Check: governance / Actions lockfile verify
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / UUID v7 conformance
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: governance / Exemption ratchet
  • GitHub Check: spark-theatre-gate / SPARK Theatre Gate
  • GitHub Check: scan / gitleaks
  • GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
  • GitHub Check: T1 / chuffed
  • GitHub Check: T1 / cvc5
  • GitHub Check: T1 / minizinc
  • GitHub Check: T1 / vampire
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: T1 / spass
  • GitHub Check: Validate DEED manifests
  • GitHub Check: T1 / glpk
  • GitHub Check: T1 / alt-ergo
  • GitHub Check: T1 / z3
  • GitHub Check: T1 / eprover
  • GitHub Check: T1 Guix manifest check
  • GitHub Check: analyze (actions, none)
  • GitHub Check: Dependency audit
  • GitHub Check: PR (address)
  • GitHub Check: analyze (javascript-typescript, none)
  • GitHub Check: Boot Gate
  • GitHub Check: MVP Smoke
  • GitHub Check: zig-ffi / fmt + test (ffi/zig)
  • GitHub Check: Proof safety regressions
  • GitHub Check: semgrep-cloud-platform/scan
📝 Summary

Summary by CodeRabbit

  • Chores
    • Removed the one-off workflow for regenerating and checking the actions lock file.

The pull request removes a one-off GitHub Actions workflow that regenerated and checked actions.lock for a specified branch. The workflow printed the lock and its SHA-256 but did not write changes back to the repository.

Changes: Lock regeneration workflow

Layer / File(s) Summary
Remove the one-off lock workflow
.github/workflows/zz-one-off-lock-regen.yml
The workflow that cloned the repository, regenerated and checked actions.lock, and printed the lock and its SHA-256 was removed.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 34a02

No actionable risk from removing the one-off workflow is established; the change is mergeable after normal checks.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly and concisely identifies the main change: removal of the one-off lock-regeneration workflow associated with PR #441.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description check Passed The description includes the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It explains the workflow deletion, records validation steps, and addresses the checkli…
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Full details: Description check

Explanation

The description includes the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It explains the workflow deletion, records validation steps, and addresses the checklist items. The stated Cargo.toml change should be reconciled with the reported diff before merge.

✨ Finishing Touches
🛠️ Fix failing CI checks
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

hyperpolymath commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner Author

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 main at 0d0aa0c (the Governance run on main after #441 is red too).

Nothing to port into this PR. I cannot re-run the checks from this session.


Generated by Claude Code

@hyperpolymath
hyperpolymath marked this pull request as ready for review October 19, 2026 21:45
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T21:46:26.053292Z 34a0288 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 19, 2026

Copy link
Copy Markdown

Add Carrot credits or activate Agent usage billing to use Autofix

@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

✅ 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.

Note: Fixing CI failures is a beta feature and may encounter errors. Expect some limitations and changes as we gather feedback and continue to improve it.

⏭️ Checks skipped: 1 · already failing on `main` (not caused by this PR)
  • GitHub Actions: Governance / 0_governance _ Validate Hypatia Baseline.txt

coderabbitai Bot and others added 4 commits October 19, 2026 22:25
…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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants