Releases: burnt-labs/github-workflows
Releases · burnt-labs/github-workflows
Release list
v1.4.1
Fixed
cloudflare-version.ymlpreviews of Workers that implement a Durable Object (Containers included) no longer fail on the missing preview URL — Cloudflare never generates one for them. The metadata step falls back to the target URL and sets a newpreview-noteoutput ("no preview URL … version is uploaded at 0% traffic"), whichcloudflare-pr.ymlsurfaces in the sticky PR comment and the step summary. Deploys are unchanged, and a missing Version ID still fails the step.
Changed
- advance internal pins to the v1.4.1 implementation
Validation
pnpm install --frozen-lockfilepnpm run lint, 82 Node tests (including a new regression test for the preview-URL fallback), actionlint with shellcheck
v1.4.0
Added
releasePrefixin npm policies: namespaces the npm flow's release tags (types-v1.2.3) so a repository with more than one release flow keeps independent histories; threaded through version derivation, the conventional commit range, and a tag-namespace guard innpm-release.ymld1Migrationsin deployment policies: D1 migrations apply insidecloudflare-version.ymlimmediately before each deploy — deploy only, never preview, per-target--env, from the deployment working directory's wrangler configuration
Changed
- npm publishes request
--provenanceonly when the source repository is public; the registry refuses provenance from private repositories (E422), which failed every private-repository publish npm-publish.ymlruns its package-scoped steps (version write, name read, publish) in the npm policy'sworkingDirectory, matchingnpm-pr.ymlandnpm-main.yml—npm publishfrom a workspace root packed the root packagenpm-main.ymlstrips the configured release prefix when deriving publishable versions- advance internal pins to the v1.4.0 implementation, which also makes the v1.3.4 conventional-bump metadata script reachable for the first time
Validation
pnpm install --frozen-lockfilepnpm run lint, 79 Node tests, actionlintscripts/policy.bundle.mjsregenerated viapnpm build
v1.3.4
Changed
- right-size TypeScript quality, Cloudflare build/deploy, npm pack, and npm publish jobs on
ubicloud-standard-4 - retain
ubicloud-standard-2for orchestration andubicloud-standard-8for container builds - keep required quality checks on Dependabot pull requests while skipping credentialed Cloudflare previews that cannot receive Actions secrets
- advance nested reusable-workflow pins to the immutable v1.3.4 implementation
Validation
pnpm install --frozen-lockfilepnpm run check(Prettier, 63 Node tests, actionlint)
v1.3.3
Changed
- run all direct reusable-workflow jobs on Ubicloud runners
- use
ubicloud-standard-2for lightweight orchestration andubicloud-standard-8for consumer builds, tests, publishing, and container work - pin nested reusable workflows to the immutable Ubicloud implementation commit
Validation
- enforce approved Ubicloud runner labels in workflow tests and actionlint
- verify policy and quality jobs on live Ubicloud capacity
v1.3.2
Fixed
- pin all Cloudflare entry workflows to the immutable single-token Wrangler message fix
- apply the release-deploy correction consistently to pull request, main, and explicit release paths
v1.3.1
v1.3.0
What's Changed
- [codex] Add generic Phala deployment workflow and harden npm jobs by @2xburnt in #20
- [codex] Add app-scoped Cloudflare workflows by @2xburnt in #21
- [codex] Harden app-scoped release metadata by @2xburnt in #23
- Pin v1.3.0 release metadata by @2xburnt in #24
Full Changelog: v1.2.8...v1.3.0
v1.2.8
Allow same-repository pull requests to run Cloudflare quality and preview jobs when the consumer repository is itself a GitHub fork. External fork pull requests and drafts remain excluded.