Skip to content

[Release] [GitHub Action] Update package versions - #570

Merged
DonOmalVindula merged 1 commit into
mainfrom
changeset-release/main
Sep 8, 2026
Merged

[Release] [GitHub Action] Update package versions#570
DonOmalVindula merged 1 commit into
mainfrom
changeset-release/main

Conversation

@asgardeo-github-bot

@asgardeo-github-bot asgardeo-github-bot commented Sep 8, 2026

Copy link
Copy Markdown

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.16

Patch Changes

  • Updated dependencies
    [9a156a9]:
    • @asgardeo/javascript@0.23.6

@asgardeo/express@0.0.87

Patch Changes

  • Updated dependencies []:
    • @asgardeo/node@0.0.88

@asgardeo/i18n@0.4.10

Patch Changes

  • #569
    9a156a9 Thanks
    @DonOmalVindula! - Render a read-only profile for users whose attributes are
    owned by an identity provider.

    Asgardeo rejects attribute updates for accounts provisioned from a social or enterprise connection, so the profile
    used to offer edit controls that always failed with a raw SCIM error.

    • <UserProfile /> accepts editable="auto" in React and Next.js. On Asgardeo it looks up the signed-in user's
      federated associations and, when the account is linked to a connection, renders the profile read-only with a short
      note naming the provider. On WSO2 Identity Server, where the same updates succeed, the profile stays editable.
    • <UserDropdown /> forwards editable to the profile it opens from "Manage profile", so the modal follows the same
      rule as the page.
    • BaseUserProfile accepts a predicate for editable, so applications can decide per user without any lookup, and a
      readOnlyNote to explain why editing is unavailable.
    • A rejected update is now reported in plain words instead of the raw SCIM error, and switches the profile to
      read-only for the rest of the session. The Next.js <UserProfile /> previously ignored update failures entirely.
    • New API getMeFederatedAssociations in @asgardeo/javascript and @asgardeo/react, plus the signup-style texts
      user.profile.readonly.federated and user.profile.update.not.allowed.error in all i18n bundles.

    While auto is resolving, the profile shows a loading state rather than edit controls it may have to take away;
    BaseUserProfile now renders that state whenever isLoading is set, in both inline and popup modes. In popup mode
    the lookup is deferred until the profile is actually opened.

@asgardeo/javascript@0.23.6

Patch Changes

  • #569
    9a156a9 Thanks
    @DonOmalVindula! - Render a read-only profile for users whose attributes are
    owned by an identity provider.

    Asgardeo rejects attribute updates for accounts provisioned from a social or enterprise connection, so the profile
    used to offer edit controls that always failed with a raw SCIM error.

    • <UserProfile /> accepts editable="auto" in React and Next.js. On Asgardeo it looks up the signed-in user's
      federated associations and, when the account is linked to a connection, renders the profile read-only with a short
      note naming the provider. On WSO2 Identity Server, where the same updates succeed, the profile stays editable.
    • <UserDropdown /> forwards editable to the profile it opens from "Manage profile", so the modal follows the same
      rule as the page.
    • BaseUserProfile accepts a predicate for editable, so applications can decide per user without any lookup, and a
      readOnlyNote to explain why editing is unavailable.
    • A rejected update is now reported in plain words instead of the raw SCIM error, and switches the profile to
      read-only for the rest of the session. The Next.js <UserProfile /> previously ignored update failures entirely.
    • New API getMeFederatedAssociations in @asgardeo/javascript and @asgardeo/react, plus the signup-style texts
      user.profile.readonly.federated and user.profile.update.not.allowed.error in all i18n bundles.

    While auto is resolving, the profile shows a loading state rather than edit controls it may have to take away;
    BaseUserProfile now renders that state whenever isLoading is set, in both inline and popup modes. In popup mode
    the lookup is deferred until the profile is actually opened.

  • Updated dependencies
    [9a156a9]:

    • @asgardeo/i18n@0.4.10

@asgardeo/nextjs@0.3.35

Patch Changes

  • #569
    9a156a9 Thanks
    @DonOmalVindula! - Render a read-only profile for users whose attributes are
    owned by an identity provider.

    Asgardeo rejects attribute updates for accounts provisioned from a social or enterprise connection, so the profile
    used to offer edit controls that always failed with a raw SCIM error.

    • <UserProfile /> accepts editable="auto" in React and Next.js. On Asgardeo it looks up the signed-in user's
      federated associations and, when the account is linked to a connection, renders the profile read-only with a short
      note naming the provider. On WSO2 Identity Server, where the same updates succeed, the profile stays editable.
    • <UserDropdown /> forwards editable to the profile it opens from "Manage profile", so the modal follows the same
      rule as the page.
    • BaseUserProfile accepts a predicate for editable, so applications can decide per user without any lookup, and a
      readOnlyNote to explain why editing is unavailable.
    • A rejected update is now reported in plain words instead of the raw SCIM error, and switches the profile to
      read-only for the rest of the session. The Next.js <UserProfile /> previously ignored update failures entirely.
    • New API getMeFederatedAssociations in @asgardeo/javascript and @asgardeo/react, plus the signup-style texts
      user.profile.readonly.federated and user.profile.update.not.allowed.error in all i18n bundles.

    While auto is resolving, the profile shows a loading state rather than edit controls it may have to take away;
    BaseUserProfile now renders that state whenever isLoading is set, in both inline and popup modes. In popup mode
    the lookup is deferred until the profile is actually opened.

  • Updated dependencies
    [9a156a9]:

    • @asgardeo/react@0.25.13
    • @asgardeo/node@0.0.88

@asgardeo/node@0.0.88

Patch Changes

  • Updated dependencies
    [9a156a9]:
    • @asgardeo/javascript@0.23.6

@asgardeo/nuxt@0.2.9

Patch Changes

  • Updated dependencies []:
    • @asgardeo/browser@0.7.16
    • @asgardeo/node@0.0.88
    • @asgardeo/vue@0.4.9

@asgardeo/react@0.25.13

Patch Changes

  • #569
    9a156a9 Thanks
    @DonOmalVindula! - Render a read-only profile for users whose attributes are
    owned by an identity provider.

    Asgardeo rejects attribute updates for accounts provisioned from a social or enterprise connection, so the profile
    used to offer edit controls that always failed with a raw SCIM error.

    • <UserProfile /> accepts editable="auto" in React and Next.js. On Asgardeo it looks up the signed-in user's
      federated associations and, when the account is linked to a connection, renders the profile read-only with a short
      note naming the provider. On WSO2 Identity Server, where the same updates succeed, the profile stays editable.
    • <UserDropdown /> forwards editable to the profile it opens from "Manage profile", so the modal follows the same
      rule as the page.
    • BaseUserProfile accepts a predicate for editable, so applications can decide per user without any lookup, and a
      readOnlyNote to explain why editing is unavailable.
    • A rejected update is now reported in plain words instead of the raw SCIM error, and switches the profile to
      read-only for the rest of the session. The Next.js <UserProfile /> previously ignored update failures entirely.
    • New API getMeFederatedAssociations in @asgardeo/javascript and @asgardeo/react, plus the signup-style texts
      user.profile.readonly.federated and user.profile.update.not.allowed.error in all i18n bundles.

    While auto is resolving, the profile shows a loading state rather than edit controls it may have to take away;
    BaseUserProfile now renders that state whenever isLoading is set, in both inline and popup modes. In popup mode
    the lookup is deferred until the profile is actually opened.

  • Updated dependencies
    [9a156a9]:

    • @asgardeo/i18n@0.4.10
    • @asgardeo/browser@0.7.16

@asgardeo/vue@0.4.9

Patch Changes

  • Updated dependencies
    [9a156a9]:
    • @asgardeo/i18n@0.4.10
    • @asgardeo/browser@0.7.16

Summary by CodeRabbit

  • New Features

    • Added automatic read-only profile support for users whose attributes are managed by an identity provider.
    • Added loading feedback while profile editability is determined.
    • Improved update-error messages and switched affected profiles to read-only for the session.
    • Added federated-association profile support and related translations.
  • Chores

    • Published patch releases across the browser, server, framework, and localization packages.

@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 0efa15f0-465e-4224-8c4f-869d0ba5cb0d

📥 Commits

Reviewing files that changed from the base of the PR and between 49380df and 56fbf44.

📒 Files selected for processing (19)
  • .changeset/readonly-federated-profile.md
  • packages/browser/CHANGELOG.md
  • packages/browser/package.json
  • packages/express/CHANGELOG.md
  • packages/express/package.json
  • packages/i18n/CHANGELOG.md
  • packages/i18n/package.json
  • packages/javascript/CHANGELOG.md
  • packages/javascript/package.json
  • packages/nextjs/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/node/CHANGELOG.md
  • packages/node/package.json
  • packages/nuxt/CHANGELOG.md
  • packages/nuxt/package.json
  • packages/react/CHANGELOG.md
  • packages/react/package.json
  • packages/vue/CHANGELOG.md
  • packages/vue/package.json

📝 Walkthrough

Walkthrough

The pull request updates package versions and changelogs for federated-profile support and related dependency releases across the Asgardeo package set. It also removes the pending changeset file.

Changes

Release metadata propagation

Layer / File(s) Summary
Core package releases
packages/javascript/*, packages/i18n/*, packages/react/*
Versions and changelogs record federated-profile read-only behavior, editable="auto", update handling, federated-association APIs, and localization updates.
Runtime package releases
packages/browser/*, packages/node/*
Package versions and changelogs record updated dependencies on the released core packages.
Framework package releases
packages/nextjs/*, packages/nuxt/*, packages/vue/*, packages/express/*
Framework and server package versions and changelogs record propagated dependency updates and federated-profile support.

Estimated code review effort: 1 (Trivial) | ~5 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch changeset-release/main

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@DonOmalVindula
DonOmalVindula merged commit b7fac26 into main Sep 8, 2026
1 check was pending
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants