Skip to content

Bump cloudflare-os to a679442 - #22

Merged
Maximo-Guk merged 4 commits into
mainfrom
bump-cloudflare-os-a679442
Oct 20, 2026
Merged

Maximo-Guk merged 4 commits into
mainfrom
bump-cloudflare-os-a679442

Conversation

@Maximo-Guk

@Maximo-Guk Maximo-Guk commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Moves the cloudflare-os pin 8060cd9 → a679442 (15 upstream commits, compare) and bumps cf to its latest release.

Commits

  1. Bump cloudflare-os to a679442: gitlink only. Checked against the update checklist:
    • Catalog: capnweb, typescript, @cloudflare/workers-types, Wrangler and Vitest are unchanged upstream.
    • Gatekeeper contract (cloudflare-os#835, #688): every change is optional or on the Workshop's side. SupportedResource.groupedWith?, GatekeeperVendor.versionTag?() and ResourceConfiguratorHost.getAcceptedResourceUrlPatterns(), which the Workshop implements. The custom Gatekeeper needs no changes.
    • Base configs: no new required vars, bindings or Durable Object migrations for the starter's own Workers. Upstream's deploy service sets the Workshop's new optional CLOUDFLARE_OS_DEPLOYMENT / CF_VERSION_METADATA. With them unset, the "newer release available" notice (#688) stays off.
    • Optional Gatekeepers: Google gains a Workers AI binding for reading Drive PDFs (#843). It carries over with the base config.
    • No new preinstalled Gatekeeper, no renamed paths, and no build-tooling changes that affect buildCommands().
  2. Route optional Gatekeepers' Workers AI through the Workshop's gateway: an optional Gatekeeper with its own ai binding (today that's Google) gets CF_AI_GATEWAY = aiGateway.name, as Web Search already does. It isn't set when aiGateway.enabled: false or the gateway is in another account, and the operator's vars take precedence. Comes with a test and docs.
  3. Bump cf to 1.0.0-beta.19: every command and flag cf-client.ts passes is still in beta.19's help output, and results still print bare, with no API envelope. cf is added to minimumReleaseAgeExclude because beta.19 is less than 24h old.
  4. cf-os 0.1.2: the version for the next npm release, a patch on 0.1.1. Publish from main once this merges.

Testing

  • pnpm lint and pnpm test pass.
  • pnpm cf-os check passes against a filled-in deployment.jsonc with gatekeepers.google selected. The Google Worker gets AI, CF_AI_GATEWAY and BASE_URL.
  • Durable Object migrations: none in this range.

Maximo-Guk and others added 4 commits October 20, 2026 10:32
Moves the pin 8060cd9 -> a679442 (15 upstream commits). Nothing else
in the starter needed to change for it:

- Catalog: capnweb, typescript, workers-types, Wrangler and Vitest are
  unchanged upstream.
- Gatekeeper contract (cloudflare-os#835, #688): SupportedResource
  gains optional groupedWith, GatekeeperVendor an optional versionTag(),
  and ResourceConfiguratorHost, which the Workshop implements,
  getAcceptedResourceUrlPatterns(). The custom Gatekeeper needs none of
  them.
- Base configs: no new vars, bindings or Durable Object migrations for
  the Workers the starter deploys itself. The Workshop's new optional
  CLOUDFLARE_OS_DEPLOYMENT and CF_VERSION_METADATA come from upstream's
  deploy service; unset, the update notice (#688) stays off.
- Optional Gatekeepers: Google gains a Workers AI binding for reading
  Drive PDFs (#843), carried over with its base config.
- No new preinstalled Gatekeeper, no build-tooling or path renames
  affecting buildCommands().

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Google's Gatekeeper converts Drive PDFs with its own Workers AI binding,
through the AI Gateway its CF_AI_GATEWAY names (cloudflare-os#843), or
through none when unset. An optional Gatekeeper with an `ai` binding now
gets aiGateway.name there, as Web Search does, so those calls share the
Workshop's gateway, limits and logs; not with the catalog off or a
gateway in another account, which the binding cannot reach. The
operator's vars still win.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cf 1.0.0-beta.17 -> 1.0.0-beta.19, the latest release. Every command
and flag cf-client.ts passes is still there, and results still print
bare, without the API envelope. cf joins minimumReleaseAgeExclude with
the other first-party packages, so a new beta can be taken the day it
publishes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Maximo-Guk Maximo-Guk changed the title Bump cloudflare-os to a679442 and cf to 1.0.0-beta.19 Bump cloudflare-os to a679442 and cf to 1.0.0-beta.19; cf-os 0.1.2 Oct 20, 2026
@ask-bonk

ask-bonk Bot commented Oct 20, 2026

Copy link
Copy Markdown

LGTM!

github run

@Maximo-Guk Maximo-Guk changed the title Bump cloudflare-os to a679442 and cf to 1.0.0-beta.19; cf-os 0.1.2 Bump cloudflare-os to a679442 Oct 20, 2026
@ask-bonk

ask-bonk Bot commented Oct 20, 2026

Copy link
Copy Markdown

LGTM!

github run

@Maximo-Guk
Maximo-Guk merged commit cbbf13d into main Oct 20, 2026
5 checks passed
@Maximo-Guk
Maximo-Guk deleted the bump-cloudflare-os-a679442 branch October 20, 2026 16:05
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.

2 participants