[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.22

Minor Changes

• a7fa33c: Detect DeepSeek Harness as an AI coding agent.

  Recognize commands run by DeepSeek Harness through its DSH_SHELL environment marker.
  Capture the agent session ID when DSH_SESSION_ID is available.

• 7993e1d: Update the generated command surface for Forge OpenAPI release
  67c5887b849fdde3ac07438146fa92a0010e2f53.

• 5ef0a6d: Update the generated command surface for Forge OpenAPI release
  708fba786988846438caab6d7540f4f5006a2a5f.

• f08f693: Update the generated command surface for Forge OpenAPI release
  cd7e523512a1ee2fb6b5b041daa68661e61c9119.

• 2c4ec34: Update the generated command surface for Forge OpenAPI release
  d04a1ddd718bb1c91f79d3220174e5a16ed1cacd.

• 54b5920: Update the generated command surface for Forge OpenAPI release
  e2386f5f515cf598f7ebdf682f2eeb60f43d9088.

Patch Changes

• a50dd58: Show additional API error messages on stderr

  Include the response envelope's messages entries after errors when a request fails, so validation details such as missing parameter names are visible. Preserve the full envelope for success: false responses returned with a successful HTTP status, and keep successful-response output unchanged.

• a251687: Clarify the banner when using a project's local cf version

  Show local version instead of delegated when a global cf installation runs
  the version installed in the project. This makes the banner easier to understand
  without knowing how delegation works.

• 947d0c9: Show the shell completions tip at most once, and never in CI

  cf now saves that it has shown the tip before it prints it. If cf cannot write
  its state file, the tip no longer appears on every run. CI runners that attach
  a terminal no longer see the tip.

• b31a9ea: Reject D1 migration names that cannot be stored on Windows

  cf d1 migrations create now rejects names containing :, *, ?, ",
  <, >, or |. On NTFS a : wrote the SQL into a hidden alternate data
  stream of an empty file, so the migration was never applied and the next one
  reused its number. The other characters failed with a raw filesystem error.

• 068bde2: Fix cf deploy for Python Workers with vendored packages

  Upload Build Output modules under their manifest paths in cf deploy,
  cf workers versions create and cf previews deploy instead of prefixing them
  with ./. Python Workers use module names as file paths without normalising
  them, and import vendored packages from the python_modules/ directory. With
  the prefix, the vendored workers SDK was not on the import path, so
  from workers import ... failed with No module named 'workers' (10021).

[pkg-pr-new]

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

commit: ef6fba4

[clanky-the-clanker]

✅ Approved — This is a standard Changesets prerelease version bump. The version, the pre-mode changeset list and the changelog entries agree with each other, and there are no findings.

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

---

✅ All checks passed

📋 Code Quality: ✅ LGTM

packages/cli/package.json goes from 1.0.0-beta.21 to 1.0.0-beta.22, which is the expected prerelease increment in pre mode. .changeset/pre.json adds the 11 consumed changeset names, and they match the changelog entries. There are no correctness or consistency problems.

---

📝 Documentation: ✅ LGTM

The new cf@1.0.0-beta.22 entries in packages/cli/CHANGELOG.md match the release notes in the pull request description. They are clear and correctly split into minor and patch changes.

---

_{Reviewed commit: ef6fba40}

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	281.2 ms	5.1 ms	274.5 ms	291.5 ms
base	282.7 ms	4.6 ms	276.2 ms	295.6 ms

Δ (PR vs base): ↓ -1.5 ms (-0.5%)

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.

[auditbenchai]

No actionable comments were generated in this review. 🎉

Merge risk: ⚪ Minimal · up to bde0ea4

This is a standard automated release PR managed by Changesets; risk is limited to publishing the already merged changes to npm.

Merge readiness: 🟡 Ready to merge, with notes

Pre-merge checks: ✅ 9

✅ Passed checks: 9 passed

Check name	Status	Explanation
Merge conflicts	✅	Merges cleanly into main.
CI checks	✅	All 11 passed.
Secrets	✅	No keys, passwords or tokens in the changed code.
Blocking issues	✅	No critical or high-severity issues in the changed lines.
PR size	✅	38 lines changed.
Title check	✅	The title follows standard Changesets convention for beta release PRs.
Description check	✅	The description automatically generated by Changesets clearly details the release version and included changes.
Linked issues check	✅	No issues are linked directly; this is an automated release PR compiling merged changesets.
Out of scope changes check	✅	Only package versioning and changeset metadata files are modified.

📝 Walkthrough

This automated pull request bumps the CLI package version to 1.0.0-beta.22 as part of the Changesets release workflow. It consumes recently merged changesets, including OpenAPI command surface updates, a shell completions tip fix, and a Python worker deployment fix. Merging will trigger an automatic prerelease publication to npm.

File	Changes
.changeset/pre.json	Tracks consumed changesets for the current prerelease cycle.
packages/cli/package.json	Bumps the package version from 1.0.0-beta.21 to 1.0.0-beta.22.

ℹ️ Review info

• Commit: bde0ea4
• Verdict: ✅ Pass
• Findings: none
• Review: local checks plus AI review of the changed lines
• Scope: Reviewed 2/2 files (of 2 total) — 0 from cache, 0 needed no AI review. Found 0 finding(s), 0 potential secret(s).

💬 Reply to any inline comment and Audit Bench Ai will recheck that code and answer in the thread. Mention @auditbench in the conversation to ask about the whole PR.

🛠️ Open the full report and fix with AI

Thanks for using Audit Bench Ai! Free pull request reviews for open source: paste any public PR at auditbenchai.com/scan.

_{Reviewed by Audit Bench Ai · AI code review for security, logic and performance · Review any public PR free}