Skip to content

Decide Every Code R2 release publication model #412

Description

@shiny-code-bot

Finish Line

Every Code has a documented release-ownership decision for whether and how to publish owned binaries, release metadata, channel aliases, and installer lookup data to R2-compatible storage.

Current Status

Completed on July 22, 2026 via PR #417, merged to main as 32cda0a41292dfa89ba86033460b1de172d13047. The semantic ledger rejects the OpenAI-owned R2 publisher stack, keeps GitHub Releases and the Codex Lab distribution manifest authoritative, and preserves alternate-source installer behavior as independent future adaptation work. Focused validation, four review lenses, JetBrains inspection, PR checks, and post-merge ci, Codespell, and cargo-deny all passed.

Scope

  • In: artifact ownership, bucket/domain naming, metadata schema, stable/prerelease channels, installer aliases, signing/checksum expectations, rollback, and publication authority.
  • Out: copying OpenAI endpoints, credentials, workflow topology, branding, or release aliases.

Acceptance Criteria

  • Identify the existing Every Code publication authority and artifact contract.
  • Audit upstream R2 storage, metadata-channel, and installer-alias behavior.
  • Confirm whether managed infrastructure authority exists for an R2 publication path.
  • Choose and document the Every Code ownership policy.
  • Record each upstream R2 commit's final semantic-ledger disposition.
  • Preserve independently useful installer behavior as separate future adaptation work.

Relationships

Decisions

  • Decision: Reject direct adoption of upstream commits cc875d61, a148e0b5, and 667b6bba.
  • Canonical publication authority: GitHub Releases produced by .github/workflows/codex-lab-release.yml, with codex-lab-distribution.json and SHA256SUMS as the owned artifact and integrity contract.
  • Ownership boundary: Do not import OpenAI-owned R2 buckets, domains, object paths, credentials, channels, aliases, workflow topology, or branding.
  • Future option: A CDN or object-storage mirror requires a separate Every Code-owned proposal with explicit infrastructure authority, release grammar, provenance/signing, rollback, and installer-fallback contracts.
  • Authority check: Launchplane returned no configured product/runtime context for an R2 publication mutation, so no managed R2 write authority exists for this repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions