chore: pin templates to v0.2.3#32
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
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 the pinned
seamless-templatesref fromv0.2.2tov0.2.3in src/core/images.ts.Why
seamless-templatesv0.2.3bumped the bundled Seamless Auth SDK versions in the starter templates (@seamless-auth/reactto^0.4.0for TOTP support, and@seamless-auth/expressto^0.7.0, which pulls in@seamless-auth/core0.7.0). This is the second half of the documented two-step templates-ref dance: the templates release landed first, this pins the CLI to it soseamless initscaffolds the new SDK versions.Conformance CI is unaffected:
verify-conformance.ymlchecks outseamless-templatesat its default branch (emptytemplates-refinput), so it already tracks the change onmain.Verification
npm run buildpasses; the compileddist/core/images.jsreflectsv0.2.3.patchtoseamless-cli) is included.