feat(release): release-please tagging, version-tagged images, Renovate#623
Merged
Conversation
…ovate Scaffolds the version-pinned model (the production Flux pinning + Keel removal is a separate, sequenced PR — see docs/runbooks/versioned-deploy.md): - release-please (release-type simple) tags vX.Y.Z via .github/workflows/release.yml. - build-and-publish also builds/pushes in-house images tagged with the release version on v*.*.* tag pushes (force-all so every service gets the tag), keeping the existing :sha/:latest behaviour. - renovate.json pins exact versions and groups the ExtraToast shared artifacts. - docs/runbooks/versioned-deploy.md documents deploy = reconcile pinned tag, rollback = git revert, and the Keel-removal sequencing. Authored by a parallel Codex fleet; reviewed manually. Part of #609. Part of #610.
jorisjonkers-dev-agents
Bot
added
enhancement
This was referenced Jun 8, 2026
jorisjonkers-dev-agents Bot
pushed a commit
that referenced
this pull request
Jun 8, 2026
personal-stack stays continuously deployed (Flux + Keel auto-roll), not version-pinned. SemVer + Renovate apply to the consumed sub-packages (extracted libs/tooling, reusable workflows, future API/frontend pair repos — M7/#625). Rewrites VERSIONING.md and adds a model-correction note to README. Reflects the #623 revert (#624) and that Keel is kept. Part of #605.
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.
What changed
Scaffolds the version-pinned release model (M0). The production-risky half — pinning Flux image tags + removing Keel
:latestauto-roll — is intentionally a separate, sequenced PR that must land only after the first versioned images exist (documented in the runbook).release-please-config.json,.release-please-manifest.json@ 0.1.0,.github/workflows/release.yml) — maintains a release PR and tagsvX.Y.Zon merge to main.build-and-publish.yml— onv*.*.*tag push, builds/pushes every in-house image with the SemVer tag (leadingvstripped), force-all so each service gets the version; existing:sha/:latestbehaviour unchanged. Handles the paths-filter base on tag events.renovate.json— exact-pin (rangeStrategy: pin), groupsdev.extratoast.*/@extratoast/*/ExtraToast/github-workflowsinto one platform bump, pins action digests.docs/runbooks/versioned-deploy.md— deploy = reconcile the commit pinning the tag; rollback =git revert; plus the Keel-removal sequencing note.How it was built
Authored by a parallel Codex fleet (4 high-effort runners, isolated worktrees); diffs reviewed manually. The two verifier-flagged tasks (build-and-publish, renovate) were inspected and are correct.
Verification
Pipeline Completemust be green. release-please/build-publish behaviour is exercised on the first tag, not in this PR.Part of #609. Part of #610.