[Release] [GitHub Action] Update package versions - #576
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (11)
✨ 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 |
brionmario
approved these changes
Sep 23, 2026
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.
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.17
Patch Changes
#575
83c0597Thanks@janithjay! - Fix SCIM2 responses (
/scim2/Me,/scim2/Schemas, and relatedorganization/profile API calls) not being parsed as JSON.
FetchHttpClientonly treated a response as JSON when itsContent-Typeheader was exactlyapplication/json.Asgardeo's SCIM2 endpoints respond with
Content-Type: application/scim+json, which didn't match, so the responsebody was returned as raw, unparsed text instead of a parsed object. This caused the user profile to render incorrectly
(missing fields, or falling back to a partial ID-token-derived profile) or crash with
TypeError: schemas.forEach is not a function.The content-type check now correctly matches
application/jsonand any subtype ending in+json(e.g.application/scim+json), while still treating non-document JSON formats likeapplication/geo+json-seqas text(since those aren't parseable as a single JSON document).
@asgardeo/nextjs@0.3.36
Patch Changes
@asgardeo/nuxt@0.2.10
Patch Changes
[
83c0597]:@asgardeo/react@0.25.14
Patch Changes
[
83c0597]:@asgardeo/vue@0.4.10
Patch Changes
[
83c0597]:Summary by CodeRabbit
application/scim+json, are now parsed as JSON. This helps profile information render correctly and prevents errors when loading schemas.