5.18.0#920
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
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.
Minor version bump to 5.18.0, created with
npm version minor(commit message and tag name are the bare version per the repo's.npmrctag-version-prefix="").Includes the merged fail-open authorization fix (#919): a security handler returning a multi-key error object such as
{ error, user: null }is now correctly treated as a failed auth.Why this is a PR instead of a direct push + tag
The release was requested as "bump a minor and push the tag."
npm version minorran cleanly and produced the5.18.0commit and annotated tag locally, but this session's credentials cannot push to protected refs — bothgit push origin mainandgit push origin 5.18.0return HTTP 403 (branch/tag protection). Merging this PR lands the bump onmain; the5.18.0tag / GitHub Release then needs to be created by a maintainer (or via the GitHub Releases UI), since the tag push is likewise blocked here.🤖 Generated with Claude Code
https://claude.ai/code/session_012XVCan3Y52cYZ6WghjZwrw
Generated by Claude Code