docs: refresh Docker tag guidance + nav release link post-v0.4.0 - #628
Merged
Conversation
The v0.4.0 release shipped on 2026-04-23 / 2026-05-05 (CE / EE) and the short-lived v0.5.0 alignment tag was retired 2026-05-06. README and architecture docs were still pointing at the v0.3 release notes file and the EE multi-replica deployment example used `:dev` as if it were the production default — both worth refreshing now that the floating `:latest` / `:dev` / pinned-semver tag scheme is documented and mechanically correct (`docker-build.yml` PR #625 / `build-ee.yml` PR #171 from earlier today). - README nav: `v0.3 release notes` → `Releases` (links to GitHub releases page, durable across future tags). - `docs/architecture/02-container.md`: append a paragraph explaining the three tag classes (`:latest`, `:0.4.0`/`:0.4`, `:dev`) so the Image column has a meaningful tag-selection story. - `docs/architecture/05-deployment.md`: 2-replica compose example now uses `:latest` (with a comment about the alternatives) instead of `:dev` — `:dev` is the wrong default for a documented production deployment example. No content / behaviour changes. Documentation only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Three small documentation refreshes after this morning's v0.5.0-tag retirement and
:latest-tag fix:<a href="docs/releases/v0.3.0.md">v0.3 release notes</a>with<a href="https://github.com/Compendiq/compendiq-ce/releases">Releases</a>so the link is durable across future tags. The v0.3.0 release-notes file isn't being deleted; it just isn't the default header link anymore.docs/architecture/02-container.md— append a paragraph explaining the three tag classes (:latest,:0.4.0/:0.4,:dev) below the per-container image table, so a reader picking which tag to pin has a meaningful story rather than just an untagged image name.docs/architecture/05-deployment.md— 2-replica EE compose example now uses:latestinstead of:dev(with an inline comment about the alternatives).:devwas the wrong default for a documented production deployment example.Pairs with Compendiq/compendiq-ee#174 (EE README — Registry Tags + Version Compatibility tables refreshed).
Test plan
🤖 Generated with Claude Code