Repository navigation
v0.15.0
Minor Changes
-
#252
9e4fcecThanks @philibea! - Drop support for Changesets v2 and Node < 22. Bump all@changesets/*dependencies to v3 and@manypkg/get-packagesto v3.Breaking changes:
- Node engine requirement bumped from
>=18.0.0to^22.12 || ^24 || >=26to match Changesets v3 @changesets/*dependencies bumped to v3 versions, which are ESM-only@manypkg/get-packagesbumped to v3, changing thePackagesandPackagetypes (toolis now an object withtypeproperty,rootrenamed torootPackage,Packagenow requiresrelativeDir)
Bug fixes for Changesets v3 compatibility:
- Handle the new
changeset versionexit code 1 when no unreleased changesets exist - Detect published packages via the
CHANGESETS_OUTPUTenv var (NDJSON format) from Changesets v3 - Prevent creating empty release MRs when the version command produces no file changes — fall through to publish instead
- Use
ignoreReturnCode: trueon version and publish commands since v3 may exit non-zero in valid scenarios - Releases for a single-package (root) repository now consistently use a
v<version>tag, matching Changesets v3 output
- Node engine requirement bumped from
-
#220
15840f3Thanks @JounQin! - Refresh dependencies, including several major upgrades:@actions/corev2 → v3 and@actions/execv1 → v3@gitbeaker/restv42 → v43 — request error messages now include only the description contextcommanderv13 → v15 — now ESM-only and requires Node.js ≥ 22.12 (require(esm)); the deprecatedcommander/esm.mjsexport was removeddotenvv16 → v17global-agentv3 → v4p-limitv6 → v7
Minimum supported Node.js raised from
^22.11to^22.12to satisfycommanderv15'srequire(esm)support.This refresh also resolves security advisories in the runtime
qsdependency (via@gitbeaker/rest,qs6.15.3 → 6.16.0) and in the development-onlyvitest/@vitest/mockerandminimatchdependencies.Dev tooling majors were upgraded as well (
eslintv10,typescriptv6 / native preview,vitestv5,size-limitv14,@pkgr/rollupv7,npm-run-all2v9,nano-stagedv1).
New Contributors
Full Changelog: v0.14.0...v0.15.0