Skip to content

fix: finish the last unfinished review items (wording, default date file, upgrade docs) - #626

Merged
Brooooooklyn merged 3 commits into
mainfrom
fix/unfinished-tracker-items
Oct 28, 2026
Merged

Brooooooklyn merged 3 commits into
mainfrom
fix/unfinished-tracker-items

Conversation

@Brooooooklyn

Copy link
Copy Markdown
Member

Finishes the last three "unfinished" items in the internal SDK review.

#248  wording      provision errors + comments still said "wrangler" / "4.131"
#274  config       dev/build created a new legacy void.json to pin the date
#1052 docs         platform upgrade order + sandbox token permissions

#274: where the default compatibility date goes

Only when a project has no config file and no date:

                 no void.json, no void.config.ts, no date
                                  │
        ┌─────────────────────────┼───────────────────────────┐
        │                         │                           │
 wrangler.toml exists   framework app, or root       any other project
        │               wrangler.json(c) exists              │
        ▼                         ▼                           ▼
 void.json (unchanged)  root wrangler.jsonc          void.config.ts (date only)
                        (adapter reads it)           + .void-wrangler.jsonc in .gitignore
  • Before: every case got a new void.json. Adding void.config.ts later then failed with "Found both".
  • A date already in void.json is still read, so existing projects don't change.
  • wrangler.toml projects stay on void.json, because void.config.ts would hide the toml's bindings.
  • The .gitignore helper moves from void migrate to cloudflare-config.ts so both paths use it. Its regex is now plain string checks.

#248: wording only

  • 3 provision error messages now name the Cloudflare config and Cloudflare tooling. The CLI used to rewrite "wrangler" before printing; that rewrite stays for real wrangler/cf output.
  • Comments no longer say "wrangler 4.131", and no longer claim Void makes wrangler --env= calls.

#1052: docs

maintenance.md → "Upgrade the platform":

  1. Upgrade the platform before the team updates its CLI, because a newer CLI refuses an older platform.
  2. Sandbox apps need Containers Edit and Cloudchamber Edit on the runtime token. Older tokens may lack them, and an upgrade does not add them.

Verification

  • vp run check, vp lint and vp fmt --check pass.
  • vp run test: 748 files and 15,026 tests pass.

🤖 Generated with Claude Code

Brooooooklyn and others added 3 commits October 28, 2026 10:45
The provisioner and deploy steps run the `cf` CLI, but three provision
errors still said "wrangler" and several comments still described
wrangler 4.131. The CLI output rewrote the word before printing, so
users saw the right text, but the source no longer matched what runs.

The errors now name the Cloudflare config and Cloudflare tooling, and
the comments describe current behaviour without the stale version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….json

When a project had no config file and no date, the first dev server,
build or deploy created a new void.json, a format the docs call legacy.
Adding void.config.ts later then failed with "Found both".

Now the date goes where the project already keeps its config:
- a new project gets a generated void.config.ts with only the date, as
  `void init` writes it, and `.void-wrangler.jsonc` is added to
  .gitignore;
- framework apps (Astro, SvelteKit, Nuxt, Analog) and projects with a
  root wrangler.json(c) get it in the root Wrangler file their adapter
  reads;
- a project with wrangler.toml keeps getting it in void.json, because
  void.config.ts would hide the toml's bindings.

A date already in void.json is still read, so existing projects keep
their date. The .gitignore helper moves from `void migrate` to
cloudflare-config.ts so both paths share it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Operators were not told to upgrade the platform before the team updates
the CLI, although a newer CLI refuses an older platform. They were also
not told that a runtime token from an older setup link lacks the
Containers and Cloudchamber permissions that sandbox apps need, which an
upgrade does not add.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Brooooooklyn

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-28T02:46:14.494538Z dd0cd5f Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://fix-unfinished-tracker-items-void-cloud.voidzero-docs.workers.dev (commit dd0cd5f)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://25d9e570-void-cloud.voidzero-docs.workers.dev dd0cd5f 2026-10-28T02:47:02.533Z Visit the dashboard ↗

@Brooooooklyn
Brooooooklyn merged commit 4f1eaee into main Oct 28, 2026
20 checks passed
@Brooooooklyn
Brooooooklyn deleted the fix/unfinished-tracker-items branch October 28, 2026 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant