release: prepare v0.3.0 — version bump, curated changelog, dashboard image in release flow#389
Merged
Conversation
…image in the release flow Implements the approved release process from docs/design/release-strategy.md (#383 D1): - workspace 0.2.1 -> 0.3.0 (internal dependency reqs bumped to match) - CHANGELOG: curated 0.3.0 entry in the new template (Security fixes / Bug fixes / Features / Operational notes + machine-readable upgrade urgency), covering the 228 commits since v0.2.0; fresh Unreleased stub - release.yml: the tag-triggered release now also builds and version-tags the dashboard image (the tenant fleet runs the proxy+dashboard pair; previously only the proxy got :X.Y.Z/:latest on release) The v0.3.0 tag is pushed separately after this merges.
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
First release under the process agreed in docs/design/release-strategy.md (#383, decision D1 approved): everything shipped since v0.2.0 (2026-04-17, 228 commits) gets a real version.
cargo update).Upgrade urgency: recommendedline (the portal's future update banner consumes this). Existing Unreleased content folded in; fresh Unreleased stub with the template headers as the going-forward convention.ghcr.io/techlab-innov/llmtrace-dashboard(:X.Y.Z+:latest). The fleet runs the proxy+dashboard pair, but only the proxy was version-tagged on release; publish-images covers only main-branch pushes. Cache scope mirrors publish-images' dashboard job.Evidence
cargo update --workspaceclean (internal crates → 0.3.0, no external changes)cargo fmt --all --checkcleancargo check -p llmtrace(proxy) clean at 0.3.0After merge (separate, gated step)
Push the
v0.3.0tag → release.yml validates, tests, Trivy-scans, publishes both images, crates, PyPI, binaries, and the GitHub Release. The proposal's:X.Yminor alias is deliberately NOT added yet — keeping the existing version+latest scheme until there's a consumer for it.