Repository navigation
Version Packages (beta) - #376
Conversation
commit: |
|
✅ Approved — This is an automated Changesets beta release. The version bump to 1.0.0-beta.21, the 11 new changeset IDs in .changeset/pre.json and the new CHANGELOG entry all agree with each other and with the release notes. No issues found. The decision is advisory: this comment never approves, blocks or requests changes on the pull request. ✅ All checks passed📋 Code Quality: ✅ LGTMThis is the automated Changesets "Version Packages (beta)" pull request, and its three changes agree with each other:
📝 Documentation: ✅ LGTMThe new Reviewed commit: |
|
| mean | stddev | min | max | |
|---|---|---|---|---|
| PR | 170.2 ms | 3.5 ms | 164.5 ms | 177.8 ms |
| base | 168.5 ms | 9.0 ms | 160.5 ms | 203.5 ms |
Δ (PR vs base): ↑ +1.6 ms (+1.0%)
Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.
edf3bb6 to
18d6788
Compare
18d6788 to
fdca40c
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
cf@1.0.0-beta.21
Minor Changes
dcab54d: Move prompts, progress and workflow messages to stderr
Breaking change during the beta: prompts, confirmations and the progress
spinner now render on stderr, so they keep working while stdout is redirected,
as in
cf kv namespaces create > ns.json, and a confirmation that used to failthere now waits for an answer. Some confirmations in
cf deployandcf workers triggers deploystill ask only when stdout is a terminal, and goahead without asking otherwise. Prompts and the spinner need stdin and stderr
to be terminals outside CI, so the spinner no longer swallows piped input, and
Ctrl+C or Esc during the spinner now exits with status 130 instead of 0.
cf init,cf build,cf deploy,cf workers versions createandcf workers triggers deployprint their messages on stderr too, togetherwith the output of the build and install commands cf runs, so scripts that
read those messages from stdout must read stderr instead.
cf previews deployno longer prints upload messages into its JSON output, and
cf devstillgives the dev server the whole terminal.
--quietnow also hides notices and the✓success line, but never warnings,the commands that fix them, or prompts. A declined delete ends with
└ Aborted.,cf initprints its next steps below the closed flow so eachcopies on its own, the first-run notices use clack info lines, and the
dev-server errors use the error frame with each install command on its own
line.
c440926: Record the global
cfversion in telemetry when it delegates to a project-pinnedcfWhen a globally installed
cfhands a command to the copy a project pins, itnow passes its own version to that copy, which adds it to telemetry as
globalCliVersion.cliVersionremains the version of thecfthat runs thecommand, and
delegatedstill marks delegated runs. Older global installs donot pass a version, so the property is omitted for them.
b50a51a: Record sanitised detail about unrecognised commands in usage telemetry
When
cfcannot match the arguments to a command, telemetry now records thekind of failure, the recognised part of the command path, whether that part is
a complete command, and up to three unrecognised words. Only the first word can
be included as written, and only when it is a
cfcommand name in a placewhere a command name was expected; later words and anything else, including
any extra value after a complete command, are replaced by a category such as
<hex>,<domain>, or<path>. Unrecognised flags, including short flags suchas
-x, are counted, never named.Failures inside a group or command keep the
commandvalue they were reportedunder before. Failures at the top level that were previously dropped – a typo
with a suggestion, several unknown words, or only flags with no command – are
now reported as unknown commands.
c761c0e: Update the generated command surface for Forge OpenAPI release
2d3b9ab6825d7087ebe00a4b03c2ff219f08e4b4.af49ab3: Update the generated command surface for Forge OpenAPI release
536d02b4bd5629be5333aea4cf1024680abac1ef.4f7b6b4: Update the generated command surface for Forge OpenAPI release
5de500b2959b09d00972516cac5a6c56aec4878a.9b339a6: Update the generated command surface for Forge OpenAPI release
880ff24a8d487f05651f6dc24f482b9845127c7f.8e51747: Update the generated command surface for Forge OpenAPI release
acc1cbed2ca3136244a31aee12f25fc6164566cc.25ad929: Update the generated command surface for Forge OpenAPI release
fdbc7d9b0fdce613501dd81cb37466fbaf0b7cca.Patch Changes
09c9303: Update dependencies published from the Workers SDK repository:
@cloudflare/autoconfig:0.7.11→0.8.0@cloudflare/build-output-utils:0.9.3→0.9.4@cloudflare/cli-shared-helpers:0.2.7→0.2.8@cloudflare/codemods:0.5.1→0.6.0@cloudflare/config:0.27.0→0.28.0@cloudflare/containers-shared:0.23.1→0.23.2@cloudflare/deploy-helpers:0.22.1→0.23.0@cloudflare/runtime-types:0.1.14→0.1.15@cloudflare/workers-auth:0.14.1→0.15.0@cloudflare/workers-utils:0.47.3→0.48.0miniflare:5.20261019.1-beta→5.20261019.2-betad4a5d17: Skip reading the compliance region from the config file when it is set in the environment
Resolve
CLOUDFLARE_COMPLIANCE_REGIONbefore project settings, matching the existing account ID priority. Commands with bothCLOUDFLARE_ACCOUNT_IDandCLOUDFLARE_COMPLIANCE_REGIONno longer evaluate acloudflare.config.tsfile solely to establish API context.