[Release] [GitHub Action] Update package versions - #568
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (19)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThis patch records sign-up success handling updates and coordinated patch releases. Release notes describe no-session success messaging, Sign In button support, automatic sign-in messaging, and related dependency version updates. ChangesSign-up behavior release
Dependency release metadata
Priority: ➖ Normal — Impact reflects medium issue severity. Estimated code review effort: 2 (Simple) | ~10 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to This release publishes coordinated patch versions and documents the sign-up completion behavior. Package versions and dependency references are consistent, with no current merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description provides detailed release information and explains the included registration updates. It does not follow the repository template because it omits the Purpose, Related Issues, Related PRs, Checklist, and Security checks sections. Resolution Add all sections from the repository template. Include explicit entries for related issues, related PRs, checklist completion, documentation, tests, secure coding, and secret checks. Preserve the existing release details under Purpose or an equivalent release section.
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
@asgardeo/browser@0.7.15
Patch Changes
@asgardeo/express@0.0.86
Patch Changes
@asgardeo/i18n@0.4.9
Patch Changes
#567
d559499Thanks@DonOmalVindula! - Show a success message and a sign-in button when a
registration completes without signing the user in.
BaseSignUpaccepts asignInUrlprop. When the flow completes and the prop is set, the card keeps showing the"account created" message and renders a Sign In button that takes the user to that URL.
<SignUp />passes the configuredsignInUrlautomatically, and the provider no longer navigates toafterSignUpUrlwhen no session was created (for example after a social sign-up, or a multi-step registration).Previously the user was sent to a protected page and bounced straight to the sign-in form without ever seeing that
the account had been created. A per-component
afterSignUpUrlprop is still honoured.Signing you in…" (new i18n key
signup.success.signing.in) instead of leaving the user wondering what happens next.@asgardeo/javascript@0.23.5
Patch Changes
[
d559499]:@asgardeo/nextjs@0.3.34
Patch Changes
#567
d559499Thanks@DonOmalVindula! - Show a success message and a sign-in button when a
registration completes without signing the user in.
BaseSignUpaccepts asignInUrlprop. When the flow completes and the prop is set, the card keeps showing the"account created" message and renders a Sign In button that takes the user to that URL.
<SignUp />passes the configuredsignInUrlautomatically, and the provider no longer navigates toafterSignUpUrlwhen no session was created (for example after a social sign-up, or a multi-step registration).Previously the user was sent to a protected page and bounced straight to the sign-in form without ever seeing that
the account had been created. A per-component
afterSignUpUrlprop is still honoured.Signing you in…" (new i18n key
signup.success.signing.in) instead of leaving the user wondering what happens next.Updated dependencies
[
d559499]:@asgardeo/node@0.0.87
Patch Changes
@asgardeo/nuxt@0.2.8
Patch Changes
@asgardeo/react@0.25.12
Patch Changes
#567
d559499Thanks@DonOmalVindula! - Show a success message and a sign-in button when a
registration completes without signing the user in.
BaseSignUpaccepts asignInUrlprop. When the flow completes and the prop is set, the card keeps showing the"account created" message and renders a Sign In button that takes the user to that URL.
<SignUp />passes the configuredsignInUrlautomatically, and the provider no longer navigates toafterSignUpUrlwhen no session was created (for example after a social sign-up, or a multi-step registration).Previously the user was sent to a protected page and bounced straight to the sign-in form without ever seeing that
the account had been created. A per-component
afterSignUpUrlprop is still honoured.Signing you in…" (new i18n key
signup.success.signing.in) instead of leaving the user wondering what happens next.Updated dependencies
[
d559499]:@asgardeo/vue@0.4.8
Patch Changes
[
d559499]:Summary by CodeRabbit
Bug Fixes
Documentation