[ant-release-bot]

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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

cf@1.0.0-beta.24

Minor Changes

• 6b19d0c: Upload every binary multipart field from a file

  Generated multipart commands now add a flag for each format: binary
  form field besides the payload that --file fills. For example,
  cf pages deployments create accepts --worker-js, --routes-json,
  --redirects, --worker-bundle, and
  --functions-filepath-routing-config-json, so a Pages Direct Upload can
  include an advanced-mode _worker.js with --worker-js @./_worker.js.
  These flags accept literal content or @path/to/file, matching other body
  flags 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, --file only reached _headers and the other files
  could 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-file help

  Document how dotenv secrets files passed to cf deploy and cf workers versions create expand $VAR and ${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.

[pkg-pr-new]

npm i https://pkg.pr.new/cf@426

commit: f0a1fbd

[clanky-the-clanker]

✅ Approved — This is a routine Changesets prerelease version bump, and the version, the pre-mode changeset list and the changelog are consistent with each other. No issues found.

_{The decision is advisory: this comment never approves, blocks or requests changes on the pull request.}

---

✅ All checks passed

📋 Code Quality: ✅ LGTM

This pull request only bumps the version and records changesets, and it matches the description:

• packages/cli/package.json moves cf from 1.0.0-beta.23 to 1.0.0-beta.24.
• .changeset/pre.json adds the four changesets this release uses, in alphabetical order:
  • calm-dogs-expand
  • multipart-binary-file-flags
  • update-openapi-e2b8c60b0222
  • update-openapi-fd89c869d0cf
• Those four match the four changelog entries in the description. The OpenAPI release hashes in the changelog match the changeset names.
• Nothing else changes.

---

📝 Documentation: ✅ LGTM

The new packages/cli/CHANGELOG.md entries for 1.0.0-beta.24 match the release notes in the pull request description. They are grouped correctly into Minor and Patch changes.

---

_{Reviewed commit: f0a1fbd8}

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	277.2 ms	3.3 ms	271.4 ms	283.0 ms
base	276.8 ms	3.5 ms	270.9 ms	282.7 ms

Δ (PR vs base): — +0.5 ms (+0.2%)

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.