fix: use git tag for dev release container image tags#749
Conversation
The release notes template used app_version from pyproject.toml (the stable version) for container pull commands. Dev releases like v0.4.8-dev.4 incorrectly showed :0.4.7 tags instead of :0.4.8-dev.4. Derive the image tag from the git tag (stripping the v prefix) so both stable and dev releases show the correct version in pull commands. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
🧰 Additional context used🧠 Learnings (7)📓 Common learnings📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-15T18:17:43.675ZApplied to files:
📚 Learning: 2026-03-15T12:00:18.113ZApplied to files:
📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-19T11:19:40.044ZApplied to files:
🔇 Additional comments (2)
WalkthroughThis pull request modifies the Docker workflow to streamline the release process. The Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
🤖 I have created a release *beep* *boop* --- ## [0.4.8](v0.4.7...v0.4.8) (2026-03-22) ### Features * add auto_cleanup config and improve update UX ([#741](#741)) ([289638f](289638f)) * add reporting lines, escalation paths, and workflow handoffs to templates ([#745](#745)) ([c374cc9](c374cc9)) * differentiate template operational configs ([#742](#742)) ([9b48345](9b48345)) * diversify personality preset assignments across templates ([#743](#743)) ([15487a5](15487a5)) * improve template metadata -- skill taxonomy, descriptions, tags, and display names ([#752](#752)) ([f333f24](f333f24)) ### Bug Fixes * resolve log analysis findings (Ollama prefix, logging, init) ([#748](#748)) ([8f871a4](8f871a4)) * use git tag for dev release container image tags ([#749](#749)) ([f30d071](f30d071)) * use subordinate_id/supervisor_id in HierarchyResolver ([#751](#751)) ([118235b](118235b)) ### Performance * add long-lived cache headers for content-hashed static assets ([#747](#747)) ([4d350b5](4d350b5)) * use worksteal distribution for pytest-xdist ([#750](#750)) ([b7dd7de](b7dd7de)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Summary
:0.4.7) in container pull commands instead of the dev version (e.g.,:0.4.8-dev.4)VERSIONenv var in docker.yml's "Append container images to release" step usedapp_versionfrompyproject.toml, which always contains the stable versiongithub.ref_name) withvprefix stripped. For stable releases the result is identical; for dev releases it now correctly shows the dev versionNote: The actual Docker images were always tagged correctly -- only the release notes pull commands were wrong.
Test plan
v0.4.7still produces:0.4.7in pull commands (tagv0.4.7->${TAG#v}=0.4.7)v0.4.8-dev.4now produces:0.4.8-dev.4in pull commands (tagv0.4.8-dev.4->${TAG#v}=0.4.8-dev.4)Review coverage
Quick mode (CI-only change, no agents needed).
🤖 Generated with Claude Code