Repository navigation
docs(agents): record 0.9.1, the first release through the looped ClawHub step - #46
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
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.
Records the 0.9.0→0.9.1 pair of releases from outside readings only: tag → commit, the publish run and which job/step is the real evidence, npm dist-tag + shasum + unpacked size + attestation bytes, the GitHub release author and timestamp, both ClawHub slugs, and what a fresh temp-prefix install of 0.9.1 prints (the producer name once, and
_FORWARDSwithaudit/help). Plus one merge-path fact:gh pr merge --mergeworked here becausemergeStateStatusreadCLEAN, where earlier releases readBLOCKED— read the field, don't assume either state.Docs only;
node --testis unaffected (nothing reads AGENTS.md — measured by grep, five test files mention it in comments and none open it).