chore(deps): update all dependencies by renovate[bot] · Pull Request #199 · rx-ts/react

renovate · 2025-04-01T01:36:43Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@1stg/app-config (source)	`^8.0.1` → `^15.0.0`	devDependencies	major
@1stg/lib-config (source)	`^11.0.1` → `^13.0.0`	devDependencies	major
@changesets/changelog-github (source)	`^0.4.8` → `^1.0.0`	devDependencies	major
@changesets/cli (source)	`^2.26.1` → `^3.0.0`	devDependencies	major
@mdx-js/react (source)	`^2.3.0` → `^3.0.0`	devDependencies	major
@mdx-js/rollup (source)	`^2.3.0` → `^3.0.0`	devDependencies	major
@testing-library/react	`^14.0.0` → `^16.0.0`	devDependencies	major
@types/node (source)	`^18.15.11` → `^24.0.0`	devDependencies	major
@types/react (source)	`^18.0.33` → `^19.0.0`	devDependencies	major
@types/react-dom (source)	`^18.0.11` → `^19.0.0`	devDependencies	major
@types/web	`^0.0.99` → `^0.0.354`	devDependencies	patch
@vitejs/plugin-react-swc (source)	`^3.3.0` → `^4.0.0`	devDependencies	major
@vitest/coverage-istanbul (source)	`^0.30.0` → `^4.0.0`	devDependencies	major
actions/checkout	`v3` → `v7`	action	major
actions/setup-node	`v3` → `v7`	action	major
andresz1/size-limit-action	→ `e7493a7`	action	pinDigest
changesets/action	`v1` → `v2.1.0`	action	major
codecov/codecov-action	`v3` → `v7`	action	major
github/codeql-action	`v2` → `v4`	action	major
jsdom	`^21.1.2` → `^30.0.0`	devDependencies	major
node	`16` → `24`	uses-with	major
pnpm (source)	`8.2.0` → `11.22.0`	packageManager	major
pnpm/action-setup	`v2` → `v6`	action	major
prism-react-renderer	`^1.3.5` → `^2.0.0`	devDependencies	major
react (source)	`^18.2.0` → `^19.0.0`	devDependencies	major
react-dom (source)	`^18.2.0` → `^19.0.0`	devDependencies	major
react-router-dom (source)	`^6.10.0` → `^7.0.0`	devDependencies	major
remark-gfm	`^3.0.1` → `^4.0.0`	devDependencies	major
rimraf	`^4.4.1` → `^6.0.0`	devDependencies	major
size-limit	`^8.2.4` → `^13.0.0`	devDependencies	major
size-limit-preset-node-lib (source)	`^0.2.0` → `^0.4.0`	devDependencies	minor
type-fest	`^3.8.0` → `^5.0.0`	devDependencies	major
typescript (source)	`5.0.4` → `7.0.2`	devDependencies	major
unplugin-auto-import	`^0.15.2` → `^21.0.0`	devDependencies	major

Release Notes

1stG/configs (@1stg/app-config)

`v15.0.0`

Compare Source

Major Changes

#393 3f70b26 Thanks @JounQin! - chore: bump commitlint
#393 3f70b26 Thanks @JounQin! - chore: bump typescript v6

Patch Changes

Updated dependencies [3f70b26, 3f70b26, 3f70b26]:
- @1stg/prettier-config@5.4.0
- @1stg/eslint-config@10.3.0
- @1stg/remark-preset@3.2.0
- @1stg/babel-preset@4.2.0
- @1stg/commitlint-config@6.0.0
- @1stg/tsconfig@4.0.0
- @1stg/nano-staged@0.3.1

`v14.3.0`

Compare Source

Minor Changes

#388 5343736 Thanks @JounQin! - fix: clarify correct engines field due to 1stg/prettier-config

Patch Changes

Updated dependencies [97cedcc, 5343736, 97cedcc]:
- @1stg/nano-staged@0.3.0
- @1stg/prettier-config@5.3.1

`v14.2.0`

Compare Source

Minor Changes

#385 a7ee3ee Thanks @JounQin! - chore(deps): bump related config packages

Patch Changes

Updated dependencies [4c2cbd7, 4c2cbd7, a7ee3ee]:
- @1stg/eslint-config@10.2.0
- @1stg/prettier-config@5.3.0
- @1stg/nano-staged@0.2.1

`v14.1.0`

Compare Source

Minor Changes

#377 ed8b7e5 Thanks @JounQin! - feat: enable eslint-plugin-node-dependencies conditionally

Patch Changes

Updated dependencies [ed8b7e5, ed8b7e5, ed8b7e5]:
- @1stg/babel-preset@4.1.0
- @1stg/commitlint-config@5.1.0
- @1stg/nano-staged@0.2.0
- @1stg/simple-git-hooks@2.1.0
- @1stg/eslint-config@10.1.0
- @1stg/markuplint-config@4.0.7
- @1stg/prettier-config@5.2.1
- @1stg/remark-preset@3.1.2

`v14.0.0`

Compare Source

Major Changes

#371 3cbd4b7 Thanks @JounQin! - feat!: migrate eslint-plugin-unicorn to eslint-plugin-unicorn-x
#372 f6e2755 Thanks @JounQin! - feat!: use n.convertPath setting for hashbang rule

Patch Changes

Updated dependencies [3cbd4b7, f6e2755]:
- @1stg/eslint-config@10.0.0

`v13.1.0`

Compare Source

Minor Changes

#367 94685f7 Thanks @JounQin! - chore(eslint): bump eslint-plugin-unicorn to v59.0.1

Major Changes

#341 8527c5f Thanks @JounQin! - feat(eslint-config)!: mark all framework plugins as optional peer
#342 3945e4f Thanks @JounQin! - feat!: migrate from lint-staged to nano-staged

Patch Changes

Updated dependencies [8527c5f, fb92907, 4a1925b, 3945e4f]:
- @1stg/eslint-config@9.0.0
- @1stg/remark-preset@3.1.0
- @1stg/prettier-config@5.1.0
- @1stg/simple-git-hooks@2.0.0
- @1stg/nano-staged@0.1.0

`v12.0.1`

Compare Source

Patch Changes

#336 fa39ecf Thanks @JounQin! - chore: bump all (dev) deps
Updated dependencies [fa39ecf]:
- @1stg/browserslist-config@2.1.3
- @1stg/common-config@12.0.1
- @1stg/postcss-config@6.0.5

`v12.0.0`

Compare Source

Major Changes

#329 c08b298 Thanks @JounQin! - chore: bump prettier-plugin-pkg with different orders for types related entries

Patch Changes

Updated dependencies [c08b298, c08b298]:
- @1stg/common-config@12.0.0
- @1stg/stylelint-config@6.0.4

`v11.1.2`

Compare Source

Patch Changes

#325 cf9c358 Thanks @JounQin! - fix(eslint-config): enable curly correctly due to config-prettier
Updated dependencies [cf9c358]:
- @1stg/browserslist-config@2.1.2
- @1stg/common-config@11.1.2
- @1stg/postcss-config@6.0.4

`v11.1.1`

Compare Source

Patch Changes

#322 8fc446d Thanks @JounQin! - chore(prettier-config): bump sh plugin
Updated dependencies [8fc446d]:
- @1stg/common-config@11.1.1

`v11.1.0`

Compare Source

Minor Changes

692226d Thanks @JounQin! - chore(eslint-config): bump mdx/prettier/unicorn plugins

Patch Changes

Updated dependencies [692226d]:
- @1stg/common-config@11.1.0

`v11.0.3`

Compare Source

Patch Changes

#309 5dbb419 Thanks @JounQin! - chore(eslint-config): enable destructuring: all for prefer-const

chore: bump all deps
Updated dependencies [5dbb419]:
- @1stg/browserslist-config@2.1.1
- @1stg/common-config@11.0.5
- @1stg/postcss-config@6.0.2
- @1stg/stylelint-config@6.0.2

`v11.0.2`

Compare Source

Patch Changes

3227ee5 Thanks @JounQin! - chore(eslint-config): drop outdated eslint-formatter-friendly
Updated dependencies [3227ee5]:
- @1stg/common-config@11.0.4

`v11.0.1`

Compare Source

Patch Changes

#296 2cc92e1 Thanks @JounQin! - chore(remark-preset): bump major version
Updated dependencies [2cc92e1]:
- @1stg/common-config@11.0.3

`v11.0.0`

Compare Source

Major Changes

#284 db3b78b Thanks @JounQin! - chore: bump all (dev) deps

Patch Changes

Updated dependencies [db3b78b]:
- @1stg/browserslist-config@2.0.1
- @1stg/common-config@11.0.0
- @1stg/stylelint-config@6.0.1

`v10.0.1`

Compare Source

Patch Changes

Updated dependencies [17fe967]:
- @1stg/stylelint-config@6.0.0

`v10.0.0`

Compare Source

Major Changes

#229 6561a5e Thanks @JounQin! - chore: bump all upgradable (dev)Dependencies

Patch Changes

Updated dependencies [6561a5e]:
- @1stg/browserslist-config@2.0.0
- @1stg/common-config@10.0.0
- @1stg/postcss-config@6.0.0

`v9.0.1`

Compare Source

Patch Changes

#220 9268bd0 Thanks @JounQin! - fix(tsconfig): incompatible module option for Node16 and NodeNext
#220 9268bd0 Thanks @JounQin! - fix(eslint): incorrect project setting for ts in md/mdx
Updated dependencies [9268bd0, 9268bd0]:
- @1stg/common-config@9.0.1

`v9.0.0`

Compare Source

Major Changes

93a4ce0 Thanks @JounQin! - chore: bump eslint plugins

Patch Changes

Updated dependencies [93a4ce0]:
- @1stg/common-config@9.0.0

`v8.1.0`

Compare Source

Minor Changes

#191 59681fb Thanks @JounQin! - chore: bump eslint-plugin-jsdoc
#191 59681fb Thanks @JounQin! - chore: bump stylelint-config-standard and stylelint-scss

Patch Changes

Updated dependencies [59681fb, 59681fb]:
- @1stg/common-config@8.1.0
- @1stg/stylelint-config@5.1.0

changesets/changesets (@changesets/changelog-github)

`v1.0.0`

Compare Source

Major Changes

#1482 df424a4 Thanks @Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26
#1482 df424a4 Thanks @Andarist! - From now on this package is going to be published as ES module.

Minor Changes

#2059 070f531 Thanks @jycouet! - Add an opt-in, experimental template option to render changelog lines from tokens ({summary}, {ref}, {pull}, {commit}, {authors}). Default output is unchanged. The token syntax may change in a patch release; pin the version if you rely on it.
#1871 dfefc4e Thanks @mihkeleidast! - Use GITHUB_REPOSITORY as the default repo when no repo option is configured
#1969 2c7c043 Thanks @marcalexiei! - Add a named export that mirrors the current default export

The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes

#2040 88f2abb Thanks @bluwy! - Improve type-check for options object
#2160 162419d Thanks @beeequeue! - Added or modified the files property in the manifest. This should not change any behavior.
#1947 492b0ca Thanks @bluwy! - Use parseEnv instead of dotenv to load the .env file and avoid loading them to process.env
Updated dependencies [5b02e2f, 062530b, 88f2abb, dae394c, dae394c, df424a4, b5e1762, c19b112, 162419d, 4c26f2f, 96b65ee, 813bbf3, df424a4, a0b5326, 492b0ca]:
- @changesets/get-github-info@1.0.0
- @changesets/types@7.0.0

`v0.7.0`

Compare Source

Minor Changes

#1255 94578cf Thanks @Kauhsa! - Added disableThanks option

`v0.6.0`

Compare Source

Minor Changes

#1850 fd0bc2e Thanks @mixelburg! - Linkify issue references in changelog entries.

Patch Changes

#1810 27fd8f4 Thanks @hirasso! - Replace deprecated String.prototype.trimRight with String.prototype.trimEnd
Updated dependencies [d4b8ad8, e462d89]:
- @changesets/get-github-info@0.8.0

`v0.5.2`

Compare Source

Patch Changes

#1783 398b3fe Thanks @mrginglymus! - Respect GITHUB_SERVER_URL environment variable when constructing URLs
Updated dependencies [398b3fe]:
- @changesets/get-github-info@0.7.0

`v0.5.1`

Compare Source

Patch Changes

Updated dependencies [84a4a1b]:
- @changesets/types@6.1.0

`v0.5.0`

Compare Source

Minor Changes

#1185 a971652 Thanks @Andarist! - package.json#exports have been added to limit what (and how) code might be imported from the package.

Patch Changes

Updated dependencies [a971652]:
- @changesets/get-github-info@0.6.0
- @changesets/types@6.0.0

changesets/changesets (@changesets/cli)

`v3.0.0`

Compare Source

Major Changes

#2128 7113c01 Thanks @Andarist! - Renamed the changeset tag command to changeset git-tag.
#2074 3599e47 Thanks @bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.
#1860 92b1c1b Thanks @mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.
#1482 df424a4 Thanks @Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26
#1994 062530b Thanks @bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.
#2190 96b65ee Thanks @bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.
#2145 f5887ff Thanks @Andarist! - Removed Yarn Classic support
#2097 8c88f6a Thanks @Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).
#1879 c76b232 Thanks @beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.
#1655 db46911 Thanks @bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos
#1651 e1df862 Thanks @bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.
#2117 813bbf3 Thanks @bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally
#1961 07278a7 Thanks @beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.
#1482 df424a4 Thanks @Andarist! - From now on this package is going to be published as ES module.
#1652 a0b5326 Thanks @bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.
#2186 3910adf Thanks @Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.
#1879 c76b232 Thanks @beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

This means the CLI flows will have minor changes, but they are largely the same.

This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.
#2090 3aae903 Thanks @beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

This means a peer dependency update is no longer assumed (forced) to be a breaking change.

If the dependent package is not compatible with the peer's new release you should manually add a major changeset describing why and how to migrate.

Minor Changes

#1121 ce2095d Thanks @Sh031224! - Added new --major, --minor, --patch flags to the add command.
#2135 fd7724a Thanks @youdie006! - Allow comma-separated values in array-valued CLI flags: the --major, --minor, and --patch flags of the add command, and the --ignore flag of the version command. For example, --minor pkg-a,pkg-b is now equivalent to --minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.
#2068

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

changeset-bot · 2025-04-01T01:36:47Z

⚠️ No Changeset found

Latest commit: f653823

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-04-01T01:36:49Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
react	Error			Nov 10, 2025 3:06am

coderabbitai · 2025-04-01T01:36:51Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🔍 Trigger a full review

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

socket-security · 2025-04-01T01:37:46Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Critical CVE: When Vitest UI server is listening, arbitrary file can be read and executed CVE: GHSA-5xrq-8626-4rwp When Vitest UI server is listening, arbitrary file can be read and executed (CRITICAL) Affected versions: >= 4.0.0 < 4.1.0; < 3.2.6 Patched version: 3.2.6 From: package.json → `npm/vitest@0.30.1` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/vitest@0.30.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `chrono-node` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/@1stg/app-config@15.0.0` → `npm/@1stg/lib-config@13.0.1` → `npm/chrono-node@2.9.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/chrono-node@2.9.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `data-urls` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/jsdom@30.0.1` → `npm/data-urls@7.0.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/data-urls@7.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `jsdom` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/jsdom@30.0.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/jsdom@30.0.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `yargs` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/@1stg/app-config@15.0.0` → `npm/yargs@17.7.3` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/yargs@17.7.3`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

socket-security · 2026-01-22T05:05:19Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Quality	Maintenance
	vitest@0.30.1
	@1stg/lib-config@13.0.1
	@1stg/app-config@15.0.0
	react-router-dom@7.18.2
	size-limit-preset-node-lib@0.4.0
	undici@5.29.0
	type-coverage@2.30.1
	@react-enhanced/types@0.2.1
	@react-enhanced/shared@0.2.1
	vite@4.5.14
	@types/qrcode@1.5.6
	@changesets/cli@3.0.0
	@types/react-dom@19.2.4
	@react-enhanced/translate@0.1.3
	@react-enhanced/utils@0.2.1
	@react-enhanced/hooks@0.5.0
	todomvc-app-css@2.4.3
	react-router@6.30.4
	@types/react@19.2.18
	lodash-es@4.18.1
	@types/lodash@4.17.25
	github-markdown-css@5.9.0
	@types/node@12.20.55 ⏵ 24.13.3		⁺²
	size-limit@13.0.3
	@vitest/coverage-istanbul@4.1.10
	classnames@2.5.1
	qrcode@1.5.4
	lodash@4.18.1
	rimraf@3.0.2 ⏵ 6.1.3		⁺¹	⁺³³
	remark-gfm@4.0.1
	react@18.2.0 ⏵ 19.2.8	⁺¹
	@mdx-js/rollup@3.1.1
	@mdx-js/react@3.1.1
See 13 more rows in the dashboard

View full report

renovate Bot force-pushed the renovate/all branch from 2d846fe to 07cc62c Compare April 1, 2025 14:26

vercel Bot had a problem deploying to Preview April 1, 2025 14:27 Failure

renovate Bot force-pushed the renovate/all branch from 07cc62c to ba33255 Compare April 5, 2025 02:30

vercel Bot had a problem deploying to Preview April 5, 2025 02:30 Failure

renovate Bot force-pushed the renovate/all branch from ba33255 to ab4ba75 Compare April 6, 2025 10:14

vercel Bot had a problem deploying to Preview April 6, 2025 10:15 Failure

renovate Bot force-pushed the renovate/all branch from ab4ba75 to 654248a Compare April 7, 2025 21:58

vercel Bot had a problem deploying to Preview April 7, 2025 21:59 Failure

renovate Bot force-pushed the renovate/all branch from 654248a to 404c110 Compare April 12, 2025 05:31

vercel Bot had a problem deploying to Preview April 12, 2025 05:31 Failure

renovate Bot force-pushed the renovate/all branch from 404c110 to f2bac18 Compare April 14, 2025 03:39

vercel Bot had a problem deploying to Preview April 14, 2025 03:39 Failure

renovate Bot force-pushed the renovate/all branch from f2bac18 to 752e17e Compare April 14, 2025 12:00

vercel Bot had a problem deploying to Preview April 14, 2025 12:01 Failure

renovate Bot force-pushed the renovate/all branch from 752e17e to ec5e449 Compare April 15, 2025 07:04

vercel Bot had a problem deploying to Preview April 15, 2025 07:04 Failure

renovate Bot force-pushed the renovate/all branch from ec5e449 to 2514f18 Compare April 16, 2025 07:55

vercel Bot had a problem deploying to Preview April 16, 2025 07:56 Failure

renovate Bot force-pushed the renovate/all branch from 2514f18 to 2d091d1 Compare April 18, 2025 05:49

vercel Bot had a problem deploying to Preview April 18, 2025 05:50 Failure

renovate Bot force-pushed the renovate/all branch from 2d091d1 to 328f671 Compare April 19, 2025 06:41

vercel Bot had a problem deploying to Preview April 19, 2025 06:42 Failure

renovate Bot force-pushed the renovate/all branch from 328f671 to 975cc79 Compare April 20, 2025 05:43

vercel Bot had a problem deploying to Preview April 20, 2025 05:43 Failure

renovate Bot force-pushed the renovate/all branch from 975cc79 to 3382b35 Compare April 21, 2025 11:17

vercel Bot had a problem deploying to Preview April 21, 2025 11:17 Failure

renovate Bot force-pushed the renovate/all branch from 068a041 to 55c0a5d Compare May 3, 2025 07:10

vercel Bot had a problem deploying to Preview May 3, 2025 07:10 Failure

renovate Bot force-pushed the renovate/all branch from 55c0a5d to cfd86ff Compare May 4, 2025 07:00

vercel Bot had a problem deploying to Preview May 4, 2025 07:01 Failure

renovate Bot force-pushed the renovate/all branch from cfd86ff to 3b6601d Compare May 6, 2025 07:44

vercel Bot had a problem deploying to Preview May 6, 2025 07:45 Failure

renovate Bot force-pushed the renovate/all branch from 3b6601d to f5881aa Compare May 9, 2025 06:37

vercel Bot had a problem deploying to Preview May 9, 2025 06:38 Failure

renovate Bot force-pushed the renovate/all branch from f5881aa to 66b9cb3 Compare May 13, 2025 17:46

vercel Bot had a problem deploying to Preview May 13, 2025 17:46 Failure

renovate Bot force-pushed the renovate/all branch from 66b9cb3 to b76ac85 Compare May 15, 2025 06:42

vercel Bot had a problem deploying to Preview May 15, 2025 06:42 Failure

renovate Bot force-pushed the renovate/all branch from b76ac85 to 69b4567 Compare May 17, 2025 05:41

vercel Bot had a problem deploying to Preview May 17, 2025 05:42 Failure

renovate Bot force-pushed the renovate/all branch from 69b4567 to e89ebed Compare May 18, 2025 15:23

vercel Bot had a problem deploying to Preview May 18, 2025 15:24 Failure

renovate Bot force-pushed the renovate/all branch from e89ebed to e9ff0c3 Compare May 19, 2025 13:18

vercel Bot had a problem deploying to Preview May 19, 2025 13:19 Failure

renovate Bot force-pushed the renovate/all branch from e9ff0c3 to 88a1b7d Compare May 29, 2025 04:51

vercel Bot had a problem deploying to Preview May 29, 2025 04:51 Failure

renovate Bot force-pushed the renovate/all branch from 88a1b7d to 1bc1683 Compare June 1, 2025 07:46

vercel Bot had a problem deploying to Preview June 1, 2025 07:47 Failure

renovate Bot force-pushed the renovate/all branch from 1bc1683 to dade9af Compare June 5, 2025 03:54

vercel Bot had a problem deploying to Preview June 5, 2025 03:54 Failure

renovate Bot force-pushed the renovate/all branch from dade9af to 7adaf1a Compare June 5, 2025 06:37

vercel Bot had a problem deploying to Preview June 5, 2025 06:37 Failure

renovate Bot force-pushed the renovate/all branch from 7adaf1a to 25e2b1e Compare June 8, 2025 18:13

vercel Bot had a problem deploying to Preview June 8, 2025 18:13 Failure

chore(deps): update all dependencies

f653823

Navigation Menu

Uh oh!

Uh oh!

chore(deps): update all dependencies - #199

chore(deps): update all dependencies#199
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all

renovate Bot commented Apr 1, 2025 •

edited

Loading

Uh oh!

changeset-bot Bot commented Apr 1, 2025 •

edited

Loading

Uh oh!

vercel Bot commented Apr 1, 2025 •

edited

Loading

Uh oh!

coderabbitai Bot commented Apr 1, 2025 •

edited

Loading

Review skipped

Uh oh!

socket-security Bot commented Apr 1, 2025 •

edited

Loading

Uh oh!

socket-security Bot commented Jan 22, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Uh oh!

Conversation

renovate Bot commented Apr 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Major Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Major Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Minor Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Major Changes

Minor Changes

Configuration

Uh oh!

changeset-bot Bot commented Apr 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

vercel Bot commented Apr 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Apr 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

socket-security Bot commented Apr 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Apr 1, 2025 •

edited

Loading

changeset-bot Bot commented Apr 1, 2025 •

edited

Loading

vercel Bot commented Apr 1, 2025 •

edited

Loading

coderabbitai Bot commented Apr 1, 2025 •

edited

Loading

socket-security Bot commented Apr 1, 2025 •

edited

Loading

socket-security Bot commented Jan 22, 2026 •

edited

Loading