build(deps): bump @frontegg/react from 7.2.0 to 7.12.18 in /console

[dependabot]

Bumps @frontegg/react from 7.2.0 to 7.12.18.

Release notes

Sourced from @​frontegg/react's releases.

v7.12.18

• FR-22346 - Fixed enable session per tenant data mismatch between user jwt and sdk
• FR-22346 - Fixed enable session per tenant data mismatch between user jwt and sdk

---

[!NOTE] Low Risk Dependency-only bump of Frontegg SDK packages; risk is limited to upstream behavior changes/regressions in auth/session handling introduced by the new versions.

Overview Updates @frontegg/react to depend on @frontegg/js and @frontegg/react-hooks 7.101.0 (from 7.100.0).

Refreshes yarn.lock to pull the 7.101.0 Frontegg dependency chain (@frontegg/types, @frontegg/redux-store, @frontegg/rest-api) with no source code changes in this repo.

Written by Cursor Bugbot for commit 428af0c0ac5ae6afa6c4be281a3dc811657801b4. This will update automatically on new commits. Configure here.

v7.12.17

• FR-23484 - Added an option to render SSO guides outside of admin box

---

[!NOTE] Low Risk Lockfile-only dependency bump with no application code changes; risk is limited to behavior changes introduced by the updated upstream Frontegg packages.

Overview Updates @frontegg/react to depend on @frontegg/js and @frontegg/react-hooks 7.100.0 (from 7.99.0).

Refreshes yarn.lock accordingly, pulling in the 7.100.0 versions of Frontegg transitive packages (@frontegg/types, @frontegg/redux-store, @frontegg/rest-api).

Written by Cursor Bugbot for commit 28f2aa9a6f81391244e8b9928f8cafac3da023c0. This will update automatically on new commits. Configure here.

v7.12.16

• FR-22263 - Fixed publish

---

[!NOTE] Updates Frontegg dependencies to the latest minor release.

• Bumps @frontegg/js and @frontegg/react-hooks from 7.97.0 to 7.99.0 in packages/react/package.json

... (truncated)

Changelog

Sourced from @​frontegg/react's changelog.

7.12.18 (2026-2-16)

• FR-22346 - Fixed enable session per tenant data mismatch between user jwt and sdk
• FR-22346 - Fixed enable session per tenant data mismatch between user jwt and sdk

---

[!NOTE] Low Risk Dependency-only bump of Frontegg SDK packages; risk is limited to upstream behavior changes/regressions in auth/session handling introduced by the new versions.

Overview Updates @frontegg/react to depend on @frontegg/js and @frontegg/react-hooks 7.101.0 (from 7.100.0).

Refreshes yarn.lock to pull the 7.101.0 Frontegg dependency chain (@frontegg/types, @frontegg/redux-store, @frontegg/rest-api) with no source code changes in this repo.

Written by Cursor Bugbot for commit 428af0c0ac5ae6afa6c4be281a3dc811657801b4. This will update automatically on new commits. Configure here.

7.12.17 (2026-2-10)

• FR-23484 - Added an option to render SSO guides outside of admin box

---

[!NOTE] Low Risk Lockfile-only dependency bump with no application code changes; risk is limited to behavior changes introduced by the updated upstream Frontegg packages.

Overview Updates @frontegg/react to depend on @frontegg/js and @frontegg/react-hooks 7.100.0 (from 7.99.0).

Refreshes yarn.lock accordingly, pulling in the 7.100.0 versions of Frontegg transitive packages (@frontegg/types, @frontegg/redux-store, @frontegg/rest-api).

Written by Cursor Bugbot for commit 28f2aa9a6f81391244e8b9928f8cafac3da023c0. This will update automatically on new commits. Configure here.

7.12.16 (2026-1-27)

• FR-22263 - Fixed publish

---

[!NOTE] Updates Frontegg dependencies to the latest minor release.

... (truncated)

Commits

• f47e3b4 chore(release): publish 7.12.18
• 7ccbf62 Merge pull request #1327 from frontegg/upgrade-admin-portal
• 428af0c update admin-portal 7.101.0
• 3903026 chore(release): publish 7.12.17
• b2c9603 Merge pull request #1325 from frontegg/upgrade-admin-portal
• 28f2aa9 update admin-portal 7.100.0
• ea72cda chore(release): publish 7.12.16
• 70d64f9 Merge pull request #1322 from frontegg/upgrade-admin-portal
• 2cb0f6b update admin-portal 7.99.0
• cd79216 chore(release): publish 7.12.15
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).