Skip to content

chore(deps): pin @cloudflare/forge to the published 0.2.0 npm release - #427

Open
Swimburger wants to merge 1 commit into
cloudflare:mainfrom
Swimburger:feat/forge-npm-release
Open

Swimburger wants to merge 1 commit into
cloudflare:mainfrom
Swimburger:feat/forge-npm-release

Conversation

@Swimburger

Copy link
Copy Markdown
Contributor

Summary

Switches the @cloudflare/forge devDependency from a pkg.pr.new tarball URL off a forge main commit to the versioned npm package @cloudflare/forge@0.2.0, published yesterday with provenance via Trusted Publishing.

  • package.json: "@cloudflare/forge": "0.2.0" in place of the https://pkg.pr.new/cloudflare/forge/@cloudflare/forge@f6720c19… URL.
  • package-lock.json: resolves to registry.npmjs.org/@cloudflare/forge/-/forge-0.2.0.tgz and picks up the six per-platform optionalDependencies (@cloudflare/forge-<os>-<cpu>@0.2.0) that ship the native binary.
  • .github/workflows/forge-tools.yml: reads devDependencies["@cloudflare/forge"] as a plain version string (no more ${pin##*@} SHA extraction) and the PR body now says forge \$FORGE_VERSION`` instead of a 12-char SHA slice.
  • scripts/generate-tools.ts header: "a pkg.pr.new build of a forge commit" → "a published npm release".

Cadence change

The forge-tools cron keeps running every six hours, but the generator version only moves when a new forge@<version> tag is cut (manually, by a release manager), not on every merge to forge's main. The cron still pulls the latest openapi.forge.json release each run, so spec-only changes continue to open regeneration PRs at the same cadence.

Test plan

  • npm ci resolves all seven @cloudflare/forge* tarballs from registry.npmjs.org.
  • node_modules/@cloudflare/forge/bin/forge.cjs --version prints forge 0.2.0.
  • Workflow dry-run (workflow_dispatch) opens the regen PR with forge \0.2.0`` in the body.

🤖 Generated with Claude Code

Switches the devDependency from a pkg.pr.new tarball URL off a forge main
commit to the versioned npm package @cloudflare/forge@0.2.0, published
with provenance via Trusted Publishing. The forge-tools workflow now reads
the version string from package.json directly and surfaces it in the PR
body, and the scripts/generate-tools.ts header describes the dep as a
published npm release. Cadence moves from 'every forge main commit' to
'every tagged forge release'.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Swimburger
Swimburger requested review from a team as code owners November 21, 2026 05:39
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