chore(deps): update dependency @changesets/cli to ^2.29.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@changesets/cli (source)	^2.28.1 -> ^2.29.7

---

Release Notes

changesets/changesets (@​changesets/cli)

v2.29.7

Compare Source

Patch Changes

• Updated dependencies [957f24e]:
  • @​changesets/apply-release-plan@​7.0.13

v2.29.6

Compare Source

Patch Changes

• #​1712 a3563b0 Thanks @​benmccann! - Switch to maintained fork of external-editor

v2.29.5

Compare Source

Patch Changes

• #​1693 6352819 Thanks @​Andarist! - Fixed an issue with workspace:^ and workspace:~ dependency ranges not being semantically treated as, respectively, ^CURRENT_VERSION and ~CURRENT_VERSION. This led to dependent packages being, at times, bumped too often when their dependencies with those ranges were bumped.

• Updated dependencies [6352819]:

  • @​changesets/assemble-release-plan@​6.0.9
  • @​changesets/get-release-plan@​4.0.13

v2.29.4

Compare Source

Patch Changes

• #​1668 65d6632 Thanks @​Andarist! - Fixed a crash in pre mode when trying to version private packages when tagging for private package is disabled

• Updated dependencies [65d6632]:

  • @​changesets/assemble-release-plan@​6.0.8
  • @​changesets/get-release-plan@​4.0.12

v2.29.3

Compare Source

Patch Changes

• #​1589 de8bebc Thanks @​remorses, @​vzt7! - Fixed a crash in prerelease mode when a package misses the version field in its package.json

• #​1619 c1e8a78 Thanks @​manucorporat! - Support ../ in publishConfig.directory when publishing packages

• Updated dependencies [de8bebc]:

  • @​changesets/assemble-release-plan@​6.0.7
  • @​changesets/get-release-plan@​4.0.11

v2.29.2

Compare Source

Patch Changes

• #​1636 f73f84a Thanks @​Netail! - Correctly resolve new changesets with since option when the .changeset directory is not directly in the git root

• Updated dependencies [f73f84a]:

  • @​changesets/read@​0.6.5
  • @​changesets/git@​3.0.4
  • @​changesets/get-release-plan@​4.0.10
  • @​changesets/apply-release-plan@​7.0.12

v2.29.1

Compare Source

Patch Changes

• #​1620 b15e629 Thanks @​Netail! - Correctly fetch new changesets with since if the git option diff.relative has been set to true

• Updated dependencies [b15e629]:

  • @​changesets/git@​3.0.3
  • @​changesets/apply-release-plan@​7.0.11
  • @​changesets/read@​0.6.4
  • @​changesets/get-release-plan@​4.0.9

v2.29.0

Compare Source

Minor Changes

• #​1470 29f34a3 Thanks @​JounQin! - Support scoped registries configured using package.json#publishConfig

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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]

⚠️ No Changeset found

Latest commit: 4d0caf3

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

[coderabbitai]

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.

---

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

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	shell-quote@​1.7.2
	node-releases@​2.0.19
	safer-buffer@​2.1.2
	string.prototype.padend@​3.1.2
	set-function-length@​1.2.2
	object.fromentries@​2.0.8
	path-parse@​1.0.7
	object-keys@​1.1.1
	unbox-primitive@​1.1.0
	typed-array-buffer@​1.0.3
	safe-array-concat@​1.1.3
	side-channel@​1.1.0
	typed-array-length@​1.0.7
	object.entries@​1.1.8
	string.prototype.trim@​1.2.10
	string.prototype.matchall@​4.0.12
	typed-array-byte-length@​1.0.3
	typed-array-byte-offset@​1.0.4
	string.prototype.repeat@​1.0.0
	regexp.prototype.flags@​1.5.4
	string.prototype.trimstart@​1.0.8
	string.prototype.includes@​2.0.1
	string.prototype.trimend@​1.0.9
	object-assign@​4.1.1
	set-blocking@​2.0.0
	nice-try@​1.0.5
	strip-final-newline@​3.0.0 ⏵ 2.0.0	+1		-1
	xml-name-validator@​4.0.0
	shebang-command@​2.0.0
	strip-bom@​4.0.0 ⏵ 3.0.0	+1		-10
	simple-git-hooks@​2.11.1
	min-indent@​1.0.1
	shebang-regex@​3.0.0
	nodent-transform@​3.2.9
See 230 more rows in the dashboard

View full report

[socket-security]

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		[email protected] has a Critical CVE. CVE: GHSA-g4rg-993r-mgx7 Improper Neutralization of Special Elements used in a Command in Shell-quote (CRITICAL) Affected versions: >= 1.6.3 < 1.7.3 Patched version: 1.7.3 From: yarn.lock → npm/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: yarn.lock → npm/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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