Skip to content

fix(release): namespace R2 publication - #291

Merged
Teakowa merged 1 commit into
mainfrom
fix/issue-283-r2-publication
Sep 9, 2026
Merged

fix(release): namespace R2 publication#291
Teakowa merged 1 commit into
mainfrom
fix/issue-283-r2-publication

Conversation

@e54-bot

@e54-bot e54-bot commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

Refs #283

Publisher-side extraction from #285.

  • publish each archive and checksum once at wright/releases/<version>/...
  • advance and verify only wright/latest/version
  • remove root-level and duplicate latest/<artifact> publication

Deliberately excludes installer, fixture, and Windows transport changes; #285 remains the consumer integration PR.

Verification: release workflow YAML parsed; static contract probe confirms namespaced immutable keys and the sole namespaced latest pointer.

Teakowa
Teakowa previously requested changes Sep 9, 2026

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking cutover regression.

aws s3api put-object \
--bucket "${R2_BUCKET}" \
--key latest/version \
--key wright/latest/version \

@Teakowa Teakowa Sep 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correction: do not add install.sh or fixture changes to this publisher-only PR. The independent publisher/consumer split is intentional. The safe cutover should be handled operationally: merge this publisher contract, backfill the currently published Wright release into wright/releases/<version>/... and create wright/latest/version from that verified release without deleting the existing root-level objects, then rerun #285 against the production namespaced endpoint. After #285 lands, future releases can advance only the namespaced contract. No dual-write or installer change is required in #291.

@Teakowa
Teakowa dismissed their stale review September 9, 2026 08:47

The requested installer coupling was incorrect. #291 is intentionally publisher-only; safe cutover will use a one-time production backfill before #285 consumer verification.

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Teakowa
Teakowa merged commit 7d5defa into main Sep 9, 2026
17 checks passed
@Teakowa
Teakowa deleted the fix/issue-283-r2-publication branch September 9, 2026 08:48
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Make Workshop Great Again Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants