Repository navigation
Record v0.9.5 publication and deployment - #41
Merged
Merged
Conversation
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.
Record the completed v0.9.5 merge, tag, trusted publication, and live Pages verification so the next session does not repeat release preparation. Mark the existing release receipt landed now that PR #40 has merged, and replace the pending release checklist with its evidence.
Validation:
node dist/cli.js ready 0203,node dist/cli.js ci, andgit diff --checkpass. The release tag remains at the verified package commit; this follow-up changes documentation and receipt metadata only.Post-publication verification also passed: installation of
@kylebegeman/ledger@0.9.5in a fresh temporary directory with an empty npm cache exited 0, and its installed CLI returnedledger 0.9.5. Registry provenance matches the tagged commit and release workflow. Both live profiles, the Atom feed, and the index return HTTP 200; the public catalog contains 29 releases through v0.9.5. The initial npm propagation delay resolved.