Skip to content

fix: pin fallback runtime source#17

Merged
jbjardine merged 1 commit into
mainfrom
agent/release-v1.0.5
Jul 9, 2026
Merged

fix: pin fallback runtime source#17
jbjardine merged 1 commit into
mainfrom
agent/release-v1.0.5

Conversation

@jbjardine

Copy link
Copy Markdown
Owner

What changed

  • pin the fallback build reference in .env.example
  • pin the Compose fallback default to the same upstream commit as the runtime Dockerfile
  • strengthen the release regression test so all three references must be immutable and identical
  • document the correction for the next release

Why

This addresses the unresolved P2 review thread from #16. The runtime Dockerfile was pinned, but the packaged environment and Compose defaults still overrode that pin with mutable upstream main during local or GHCR-fallback builds.

Validation

  • public release regression contracts pass
  • resolved Compose configuration contains only da0f365d4a0bcac5371b4962769abc17bfcd8cef
  • generated release tarball contains the same pinned reference in .env.example and docker-compose.git.yml

This PR is intentionally left open until the automated review has completed and any additional feedback has been assessed.

@jbjardine jbjardine merged commit 3be0770 into main Jul 9, 2026
4 checks passed
@jbjardine jbjardine deleted the agent/release-v1.0.5 branch July 9, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant