Repository navigation
build(deps): bump @heyatom/bastion-client to 1.0.0 - #5
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
What
Bump
@heyatom/bastion-clientto^1.0.0.Why
Platform plan 03 W2: client 1.0.0 reads both the Bastion 1.11 response shape and the upcoming 2.0
{ data }envelope, so every consumer must be on it before Bastion 2.0 (W3) ships. No behaviour change for this service, which only uses JWKS verification, the service token provider and/or audit (POST /auth/client,POST /events). No code changes needed; no direct use ofBastionHttp.call/BastionService.call/listMyEvents.Checks
pnpm build: OKpnpm test: 15 suites / 207 tests passedpnpm-lock.yamlresolves@heyatom/bastion-client@1.0.0🤖 Generated with Claude Code