Repository navigation
Version Packages (beta) - #426
Conversation
commit: |
|
✅ Approved — This is a standard Changesets beta release pull request. The version bump, the six consumed changeset ids and the CHANGELOG entries all match each other, and no issues were found. The decision is advisory: this comment never approves, blocks or requests changes on the pull request. ✅ All checks passed📋 Code Quality: ✅ LGTMThis is an automated Changesets release pull request, and its three changed files match each other:
📝 Documentation: ✅ LGTMThe new Reviewed commit: |
|
| mean | stddev | min | max | |
|---|---|---|---|---|
| PR | 188.6 ms | 13.2 ms | 178.1 ms | 232.4 ms |
| base | 183.8 ms | 3.9 ms | 177.7 ms | 192.1 ms |
Δ (PR vs base): ↑ +4.7 ms (+2.6%)
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.
ee6c915 to
74e7c84
Compare
74e7c84 to
6637163
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.24
Minor Changes
014eadd: Delegate development registry resolution to Miniflare
During the cf beta, stop overriding registry paths for
cf devand--local.Miniflare v5 owns the default
<Cloudflare config directory>/dev-registry/v5and the
CLOUDFLARE_DEV_REGISTRY_PATHoverride. cf no longer interpretsCLOUDFLARE_REGISTRY_PATHor translates registry settings for child processes;exported environment variables reach the selected project tooling unchanged.
Wrangler retains its own default registry for compatibility. Set the same
CLOUDFLARE_DEV_REGISTRY_PATHfor cf and compatible Wrangler/Vite processes whenthey need to share development resources.
6b19d0c: Upload every binary multipart field from a file
Generated multipart commands now add a flag for each
format: binaryform field besides the payload that
--filefills. For example,cf pages deployments createaccepts--worker-js,--routes-json,--redirects,--worker-bundle, and--functions-filepath-routing-config-json, so a Pages Direct Upload caninclude an advanced-mode
_worker.jswith--worker-js @./_worker.js.These flags accept literal content or
@path/to/file, matching other bodyflags while preserving uploaded file bytes and filenames. Both forms upload
as file parts; inline content uses the original form field name as its filename.
Before this change,
--fileonly reached_headersand the other filescould not be sent.
16a20a5: Update the generated command surface for Forge OpenAPI release
e2b8c60b0222e9df2db7db83fdbf465f099a5189.ab93021: Update the generated command surface for Forge OpenAPI release
fd89c869d0cfca05d431fa56fdec63ebe96e7c37.2f2745f: Update the generated command surface for Forge OpenAPI release
fdc1aa8a39e2e515f26c2fc6109d7e93050e811c.Patch Changes
2e6c118: Explain dotenv variable expansion in
--secrets-filehelpDocument how dotenv secrets files passed to
cf deployandcf workers versions createexpand$VARand${VAR}using process values and earlier file values. Process values override matching file keys, including explicitly empty values. Only keys declared in the secrets file are uploaded.Explain how to escape literal dollar signs with a backslash (
PASSWORD=pa\$word), or use JSON to preserve values exactly. Only use trusted dotenv secrets files, since references can read and upload any process environment value. JSON secrets files and API bulk-secret commands retain their existing behavior.