Repository navigation
ci(release): publish without rerunning the pull request's gates (0.60.4) - #88
Merged
Merged
Conversation
make audit and make install-evals run on every Pull Request (harness.yml). The release job now reads the version, checks the registry, installs the packed tarball into a throwaway repository and publishes; it no longer reruns both gates on the merge commit. The owner chose this knowing main is unprotected, so a merge of two green branches is not re-audited before publish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
The release job no longer reruns
make auditandmake install-evalson the merge commit. Both already run on every Pull Request inharness.yml. The release now reads the version, checks the registry, installs the packed tarball into a throwaway repository, then publishes.Trade-off (owner's choice)
mainis not protected, so a merge of two independently green branches is no longer re-audited before an immutable npm version leaves. The owner chose this ("Just cut it") over making the release wait onharness.ymlor protectingmain.Changes
.github/workflows/release.yml: drop the gitleaks install,make auditandmake install-evalssteps; the header says where the gates run.package.json,.orly/orly.json: 0.60.4.docs/CHANGELOG.md: 0.60.4 entry.Based on
mainatd21a063(#87, 0.60.3, already published).🤖 Generated with Claude Code