4.0.1 - #13
Merged
Merged
Conversation
A no-op patch release. The published 4.0.0 tarball carries a README from before the npm badge and the Releasing section were added, and npm renders the package page from the tarball, so the page is 34 lines behind the repository. Publishing 4.0.1 syncs it. The shipped code is byte-identical to 4.0.0 — verified by diffing the published tarball against master — so this also exercises the new release workflow on a change where nothing can regress. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJR2DDBimsijgYgZS3bUS8
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
2 participants
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.
A no-op patch release, to sync the npm package page and to exercise the release workflow from #11 on a change where nothing can regress.
Why
shadowtools@4.0.0was published by hand, before #11 and #12 landed. npm renders a package's page from the README inside the published tarball, so the page is 34 lines behind the repository — missing the npm badge and the whole Releasing section.The code is not behind. I diffed the published tarball against
master:All eight shipped files are byte-identical. Only the README drifted.
Why now
This is the first release to go through
release.yml, and the OIDC handshake is the one part of that workflow that cannot be tested except by running it. A patch whose code cannot change is the best possible thing to find that out on.Changes
package.jsonandpackage-lock.jsonto4.0.1, vianpm version patch --no-git-tag-version. Nothing else.Once merged I'll tag
v4.0.1on the merge commit. Publishing the GitHub Release for that tag triggers the workflow, which checks the tag matchespackage.json, runs the tests throughprepublishOnly, and publishes.Generated by Claude Code