chore: update version and changelog - #148
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 03:24
86a3cf8 to
ae15d3a
Compare
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
seamless-auth-api@0.7.3
Patch Changes
9c379b0: Drop the orphaned bootstrap secret check from the container entrypoint.
validateEnvs.shstill requiredSEAMLESS_BOOTSTRAP_SECRETwheneverSEAMLESS_BOOTSTRAP_ENABLEDwas
true. Both variables were removed with the admin bootstrap invite flow, so nothing in theruntime reads either one. A deployment that carried the old
SEAMLESS_BOOTSTRAP_ENABLED=trueoverfrom a previous release refused to boot until it supplied a secret that no longer did anything.