chore: bump version to 0.1.0-alpha.2#10
Merged
Merged
Conversation
Ships this release's onboarding work: self-register (invitation_id + invitation_token) as an alternative to pre-provisioned api_key + identity_id, CF-Access header support, a cross-origin-redirect credential-leak guard, and correct cws-core error-detail extraction (RFC 9457 problem+json).
gavin09527
approved these changes
Jul 20, 2026
gavin09527
left a comment
gavin09527
left a comment
There was a problem hiding this comment.
LGTM — clean version bump 0.1.0-alpha.1 → 0.1.0-alpha.2 (package.json + package-lock.json only, no code/dependency changes; SDK stays ^1.0.1). Ships the merged onboarding work (self-register + CF-Access + redirect guard + RFC 9457 error detail).
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.
Ships this release's onboarding work: self-register (invitation_id + invitation_token) as an alternative to pre-provisioned api_key + identity_id, CF-Access header support, a cross-origin-redirect credential-leak guard, and correct cws-core error-detail extraction (RFC 9457 problem+json).
What
Why
Test plan
npm testpasses locallynpm run buildpasses locallyChecklist
// nosemgrep: <rule-id>suppression is justified inline and approved by the project lead