Repository navigation
docs: record verified v7.2.0 publication - #171
Open
flyingrobots wants to merge 1 commit into
Open
flyingrobots wants to merge 1 commit into
flyingrobots wants to merge 1 commit into
Conversation
|
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 1 minute. View limit details
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. |
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.
Closes #169.
docs/releases/latest-publication.jsonnow names v7.2.0: signed tag on3008b4a, npm gitHead3008b4a, integritysha512-vIDYg2zq…, release workflow 42249242979, and the GitHub Release.chore/git-cas-7.2.0). 333 custody andWarptests passed there. A retainedWarpwrite measured 53 loose objects over 100 writes, down from about 301 on 7.1.0. That consumer ran SHA-1 only; the SHA-256 coverage comes from this repo's own native suites.Evidence:
eslint .is clean, and the 76 docs and release-state tests pass in Docker.