chore(deps-dev): bump @changesets/cli from 2.29.8 to 2.30.0

[dependabot]

Bumps @changesets/cli from 2.29.8 to 2.30.0.

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.30.0

Minor Changes

• #1840 057cca2 Thanks @​wotan-allfather! - Add --since flag to add command

  The add command now supports a --since flag that allows you to specify which branch, tag, or git ref to use when detecting changed packages. This is useful for gitflow workflows where you have multiple target branches and the baseBranch config option doesn't cover all use cases.

  Example: changeset add --since=develop

  If not provided, the command falls back to the baseBranch value in your .changeset/config.json.

• #1845 2b4a66a Thanks @​Andarist! - Delegate OTP prompting to the package manager instead of handling it in-process. This allows Changesets to use the package manager's native web auth support.

• #1774 667fe5a Thanks @​bluwy! - Support importing custom commit option ES module. Previously, it used require() which only worked for CJS modules, however now it uses import() which supports both CJS and ES modules.

• #1839 73b1809 Thanks @​leochiu-a! - Add a --message (-m) flag to changeset add (and default changeset) so the changeset summary can be provided from the command line. When --message is present, the summary prompt is skipped while the final confirmation step is kept.

• #1806 0e8e01e Thanks @​luisadame! - Changeset CLI can now be run from the nested directories in the project, where the .changeset directory has to be found in one of the parent directories

Patch Changes

• #1849 9dc3230 Thanks @​Andarist! - Compute the terminal's size lazily to avoid spurious stderr output in non-interactive mode

• #1857 2a73025 Thanks @​mixelburg! - Fix confusing prompt labels when entering changeset summary after external editor fallback

• #1842 6df3a5e Thanks @​RodrigoHamuy! - Allow private packages to depend on skipped packages without requiring them to also be skipped. Private packages are not published to npm, so it is safe for them to have dependencies on ignored or unversioned packages.

• #1776 503fcaa Thanks @​bluwy! - Support absolute paths in changeset status --output <path>

• Updated dependencies [667fe5a, 1772598, b6f4c74, 6df3a5e, 6df3a5e, 27fd8f4]:

  • @​changesets/apply-release-plan@​7.1.0
  • @​changesets/config@​3.1.3
  • @​changesets/get-release-plan@​4.0.15
  • @​changesets/read@​0.6.7

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​changesets/cli since your current version.

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]

❌ Security Audit Results

Status: High or critical vulnerabilities detected

Severity	Count
Critical	0
High	1
Moderate	0
Low	0
Info	0

Total vulnerabilities: 1

⚠️ Action Required: Please review and fix high/critical vulnerabilities before merging.

Remediation Steps

1. Review the audit results: pnpm audit
2. Update vulnerable dependencies: pnpm update
3. For breaking changes, check package changelogs
4. Run tests to ensure compatibility: pnpm test
5. If no fix is available, consider:
   • Finding alternative packages
   • Waiting for upstream fixes
   • Applying workarounds if risk is acceptable

[github-actions]

✅ Quality Metrics Gate

Metric	Value	Status
Score	91.06/100 (+0)	✅
Lint	20w / 0e	⚠️
TypeScript	0 errors	✅
Tests	100% pass rate	✅
Coverage	95.28% avg	✅
Build	OK	✅

Per-package coverage

Package	Coverage
@kaiord/core	97.06%
@kaiord/fit	96.45%
@kaiord/tcx	97.61%
@kaiord/zwo	91.72%
@kaiord/garmin	97.84%
@kaiord/garmin-connect	98.36%
@kaiord/cli	88.1%
@kaiord/mcp	95.08%

Metrics Gate • 2026-03-09T19:32:49.900Z