Skip to content

chore(deps-dev): bump @changesets/cli from 2.31.1 to 3.0.0 - #55

Merged
abdelkabirouadoukou merged 1 commit into
mainfrom
dependabot/bun/changesets/cli-3.0.0
Aug 16, 2026
Merged

abdelkabirouadoukou merged 1 commit into
mainfrom
dependabot/bun/changesets/cli-3.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 15, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @changesets/cli from 2.31.1 to 3.0.0.

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.0

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.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.0

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.

... (truncated)

Commits
  • f442221 Version Packages (#2235)
  • e3facad Version Packages (next) (#2228)
  • c98af4c Do not bump ignored independent packages when exiting pre mode (#2092)
  • 496ca21 Build(deps-dev): Bump the development-dependencies group with 6 updates (#2225)
  • d1053ac Build(deps): Bump the production-dependencies group across 1 directory with 2...
  • 68ea6ec Fix linked and fixed glob patterns expansion (#2222)
  • c1b6f8c fix missing coloring of name (#2218)
  • a53d1f8 Remove old atlaskit changelogs (#2217)
  • 7bcb2d2 Build(deps-dev): Bump the development-dependencies group across 1 directory w...
  • baa658d Version Packages (next) (#2192)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 15, 2026
@vercel

vercel Bot commented Aug 15, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
thexjs-basic Ready Ready Preview Aug 16, 2026 3:19am
x Ready Ready Preview Aug 16, 2026 3:19am

Bumps [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli) from 2.31.1 to 3.0.0.
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.0/packages/cli)

---
updated-dependencies:
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/bun/changesets/cli-3.0.0 branch from 301b739 to 19f73b2 Compare August 16, 2026 03:18
@abdelkabirouadoukou
abdelkabirouadoukou merged commit 38ed7f0 into main Aug 16, 2026
9 checks passed
@abdelkabirouadoukou
abdelkabirouadoukou deleted the dependabot/bun/changesets/cli-3.0.0 branch August 16, 2026 03:29
abdelkabirouadoukou added a commit that referenced this pull request Aug 20, 2026
* feat(core): request-scoped OpenTelemetry tracing correlation (#79)

@thexjs/core never initializes OpenTelemetry itself — apps opt in by calling setTracer() (or getTracer()) with any tracer whose startSpan(name, { attributes }) matches the OTel surface. Without a configured tracer the layer degrades to synchronous no-ops.

Every request opens an x.http root span carrying the x.requestId attribute plus route/method/status; with no inbound x-request-id, one is minted and shared via traceRequestId() so the log line, the response header and the trace span all agree. Request-scoped phase spans cover the whole pipeline, all correlated by x.requestId: x.api (API routes), x.loader (page loaders + SSR/SSG), x.action (server functions), x.middleware (composed onion + handler), x.ssr, and x.db (both connectSQLite and connectPostgres, wrapping query/run/execute/template-tag calls with db.system, db.operation and a redacted + truncated db.statement). Errors inside any span set ERROR and record an exception.

runWithRequestSpan, tracePhase, tracePhaseSync, dbTraceAttributes, TraceSpan and TracerLike are exported. Mock-tracer tests cover a failing DB call carrying the request id, phase spans, error status propagation and the full createApp request lifecycle.

* fix(core): reject hydration beacons from prefix-matching or opaque origins (#138)

The hydration-mismatch beacon used a prefix match on the canonical origin, so Origin: https://localhost.evil.com passed (not just https://localhost). Exact-match now: the header is parsed via originFromHeader and compared as a full origin string, and a present-but-unparseable header (Origin: null from a sandboxed/opaque origin) is treated as cross-site rather than absent. Regression tests cover the evil-prefix origin and Origin: null.

* fix(core): deterministic routing when dynamic routes tie (#140)

Same-category route ties (e.g. /bar/[b] vs /[a]/foo both matching /bar/foo) were left to the OS's directory-scan order, so a build could serve different pages on different platforms. Ties are now broken segment-by-segment by positional specificity (literal 0 > param 1 > catch-all 2), falling back to a lexical routePath sort — deterministic everywhere and documented in the core README. Regression test with both fixture routes active.

* fix(core): serialize concurrent Postgres migrations with an advisory lock (#131)

runPostgresMigrations now runs inside one client.begin() transaction holding SELECT pg_advisory_xact_lock(MIGRATION_LOCK_KEY), so a second process racing the same migration set can't double-apply or interleave DDL. The applied-tracking read happens under the lock, migrations use savepoints, and a failure rolls back only its own migration while prior successes keep their commit. Concurrency regression test added.

* fix(core): pin image-proxy fetch to the verified public IP to close the DNS-rebinding TOCTOU (#132)

The allow-listed hostname was resolved once for validation but the actual fetch re-resolved it, so the DNS answer for the fetch could differ (a second lookup rebinding to a private address). The target is now resolved a single time: private/reserved literals are rejected, every DNS answer must be public, and the first public IP is pinned into the fetch via the Host header + tls.serverName with redirect: manual. Each redirect hop re-resolves and re-pins before connecting. Tests cover pinning on first fetch and on every hop.

* fix(auth): rate-guess spraying across IPs with separate account and IP buckets (#133)

Brute-force was keyed by (IP, identifier), so rotating source IPs reset the throttle. createBruteForceGuard now maintains two independent buckets — an account bucket (identifier alone) stopping guessing one account from many IPs, and an IP bucket (client IP) stopping one IP spraying many accounts — checked together, failed/reset together, with Retry-After reflecting the longer window. Tests updated and extended for the two-bucket behavior.

* fix(core): generated href() now fills catch-all params instead of dropping them (#134)

A catch-all like /docs/* compiles to a * token with no :slug to substitute, so href('/docs/*', { slug }) only stripped the * and returned '/docs/'. The generated href() now substitutes * segments in param order with the value (segments encoded individually so multi-segment values keep their slashes). New runtime test imports the generated manifest and asserts catch-all, param and static href calls.

* fix(core): Redis rate-limiter reports the real window reset, not a sliding one (#135)

The Redis store returned resetAt = Date.now() + windowMs on every call, so Retry-After kept sliding forward instead of converging on the TTL the EXPIRE enforces. incr() now reads PTTL right after INCR (clamped to >= 0) and derives resetAt from the key's actual remaining life. FakeRedis models PTTL and a regression test verifies a mid-window key reports ~remaining, not the full window; verified it fails against the old implementation.

* fix(core): mask connection-string passwords in log redaction (#136)

redactString already masked bearer/basic credentials and inline Authorization values but not URI userinfo, so postgres://deploy:supersecret@db:5432/app printed the password. Redaction now masks the userinfo password for any scheme (http, postgres, mysql, redis, ...) via a scheme://user:pass@ shape regex, leaving password-less URLs untouched. Regression tests added for the common drivers.

* fix(cli): keep dev server responsive during Tailwind recompiles and exit promptly on SIGTERM (#137, #139)

Dev-mode Tailwind recompilation used an async spawn but awaited it synchronously, stalling request handling until the (potentially multi-second) recompile finished; the watcher path now uses a true async compile so the server stays responsive mid-build. shutdown() awaited server.stop(true) inside the 3s window, so a SIGTERM that arrived with nothing left to drain still waited the full grace period — it now stops immediately and the timer is a hard-cap fallback (unref'd). E2E tests cover both: a fake-slow bunx keeping the dev server under 1s, and prompt SIGTERM exit.

* fix(core): lock bookkeeping-table creation in Postgres migrations (#131)

The _x_migrations table was created via CREATE TABLE IF NOT EXISTS before the advisory lock, so two booting replicas raced that DDL and hit Postgres's simultaneous-create catalog race (pg_type_typname_nsp_index) before serialization kicked in. Moving the table creation inside the locked transaction means the loser instead finds the table the winner committed and proceeds to skip — the advisory lock now guards the entire run.

* fix: finish CodeRabbit review on tracing PR (#141, #79, #131-#140)

- changeset: scope the 'no embedded literals' claim to masked quoted
  strings; note the template-tag path binds values out-of-band (#1)
- cli: serialize Tailwind recompiles so saves coalesce into one follow-up
  run after the active compile exits, instead of stacking overlapping
  processors writing the same output (#8); unit test proves no two
  compiles overlap, verified to fail against the old concurrent spawn
- redact: capture the authorization/auth keyword group so it survives the
  $1 replacement instead of emitting a literal '$1 [REDACTED]' (#9);
  exact-output regression test verified against the old non-capturing regex
- tracing: stop double-recording a throwing handler error on the x.http
  root span (the wrapper's fail() plus runWithRequestSpan's catch) (#11);
  mask quoted SQL string literals to '?' in db.statement (#13) — both
  verified failing against the previous behavior
- redis rate-limit test: FakeRedis PTTL now validates its key argument
  instead of silently modeling a malformed call as a missing key (#15)
- auth: empty-identifier regression test now provably fails against the
  old shared `login:` account key (auth.ts skip logic and brute-force
  namespacing both reverted to confirm); IP-bucket test rewritten so the
  attacker's own successful login must NOT reset the spray counter
  (verified it fails when the success path clears the IP bucket)

* fix(release): bump changesets/action to v2 for changesets CLI v3

changesets/action@v1 detects published packages by parsing the publish
command's stdout for 'New tag:' lines, which @changesets/cli v3 no longer
prints. Since the CLI was bumped to v3.0.0 (#55), npm publishes succeeded
but the action never pushed git tags or created GitHub releases.

v2 reads the CHANGESETS_OUTPUT event file the CLI writes instead and
fails loudly if that output is missing. Rename the custom-script inputs
to their v2 names (version-script, publish-script, pr-title,
commit-message).

This branch was successfully deployed

2 active deployments
Preview – x — 19f73b2e Deployed Aug 16, 2026 by vercel[bot]
Preview – thexjs-basic — 19f73b2e Deployed Aug 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant