Repository navigation
chore(deps): pin @cloudflare/forge to the published 0.2.0 npm release - #427
Open
Swimburger wants to merge 1 commit into
Open
Swimburger wants to merge 1 commit into
Swimburger wants to merge 1 commit into
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switches the
@cloudflare/forgedevDependency from a pkg.pr.new tarball URL off a forgemaincommit 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 thehttps://pkg.pr.new/cloudflare/forge/@cloudflare/forge@f6720c19…URL.package-lock.json: resolves toregistry.npmjs.org/@cloudflare/forge/-/forge-0.2.0.tgzand picks up the six per-platformoptionalDependencies(@cloudflare/forge-<os>-<cpu>@0.2.0) that ship the native binary..github/workflows/forge-tools.yml: readsdevDependencies["@cloudflare/forge"]as a plain version string (no more${pin##*@}SHA extraction) and the PR body now saysforge \$FORGE_VERSION`` instead of a 12-char SHA slice.scripts/generate-tools.tsheader: "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'smain. The cron still pulls the latestopenapi.forge.jsonrelease each run, so spec-only changes continue to open regeneration PRs at the same cadence.Test plan
npm ciresolves all seven@cloudflare/forge*tarballs fromregistry.npmjs.org.node_modules/@cloudflare/forge/bin/forge.cjs --versionprintsforge 0.2.0.workflow_dispatch) opens the regen PR withforge \0.2.0`` in the body.🤖 Generated with Claude Code