chore: bring release flow into the canonical repo (#1) - #22
Merged
Conversation
Establishes this repo as the single home for cutting releases, per #1. - release.sh: build + regenerate cdn-files/update-info.json with the ZIP's SHA-256 (self-hosted updater rejects a hash mismatch). - cdn-files/plugin-info.json: WordPress 'View details' metadata, version- corrected to 2.1.0 with refreshed feature list + changelog (was stale at 1.3.7 in the monorepo copy). - cdn-files/.gitignore: update-info.json is a per-build artifact (embeds a build-specific hash) — uploaded to the CDN, never committed. - RELEASING.md: documents the full flow incl. the manual wrangler R2 upload. Verified release.sh runs clean in this repo and emits a valid update-info.json. Part of #1.
This was referenced Jul 19, 2026
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
1 participant
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.
Makes this repo the single home for releases (#1 DoD: "releases build from this repo only").
release.sh— runsbuild.sh, then regeneratescdn-files/update-info.jsonwith the built ZIP's SHA-256 (the self-hosted updater rejects a package whose hash doesn't match). Verified it runs clean here and emits valid metadata.cdn-files/plugin-info.json— the WordPress "View details" metadata, version-corrected to 2.1.0 with a refreshed feature list + changelog. The monorepo copy was stale at 1.3.7.cdn-files/.gitignore—update-info.jsonis a per-build artifact (embeds a build-specific hash), uploaded to the CDN, never committed.RELEASING.md— documents version bump →./release.sh→ wrangler R2 upload → tag, and states this repo is canonical.Remaining on #1 (a real release event, needs CDN credentials): upload the next release's ZIP + JSON so the live CDN stops advertising 1.3.7, and add a deprecation pointer to the monorepo copy (separate app-repo PR).
Part of #1.