docs(release): document smartem-frontend pipeline + refresh artefacts dropdown#204
Merged
Merged
Conversation
Add a fourth section to docs/operations/releasing.md covering
smartem-frontend now that the pipeline added in ADR-0019 has
produced its first stable release (0.1.0) alongside RC builds:
- Path filters, artifacts, versioning model (dual file, must
match), tag prefix, and the stable-release tag flow.
- A "Runtime version metadata" note describing the /version
endpoint and where each field is sourced.
- Expand the "Docker" subsection of "Verifying a release" to
cover the new frontend image alongside smartem-decisions.
Update the artefacts dropdown in the devtools webui: the
"frontend" entry is no longer a placeholder ("deployed via
backend container, no standalone bundle published") - now a
real published container image, mirroring the shape used by
the smartem-decisions backend entry (label, description,
docker pull command, GitHub Releases and Docker links).
github-actions
Bot
added
the
documentation
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
Follow-up to the smartem-frontend release pipeline going live (smartem-frontend#90, first stable release
0.1.0produced earlier today alongside0.1.0rc5). This PR propagates references to the new release across smartem-devtools:docs/operations/releasing.md: add a fourth section forsmartem-frontend, mirroring the existing three (decisions / epuplayer / workspace). Covers path filters, artifacts produced, the dual-file versioning rule (apps/smartem/package.jsonandapps/smartem/src/version.tsmust match), the stable-release tag flow, and a short note on the/versionruntime metadata endpoint. Expand the "Docker" subsection under "Verifying a release" to cover the new image alongsidesmartem-decisions.core/artefacts.json: replace the placeholderfrontendentry ("deployed via backend container, no standalone bundle published") with a real one mirroring thebackendshape — label, description,docker pullcommand, and links to GitHub Releases and the GHCR package.What this PR does NOT do
VITE_API_ENDPOINTat build time but the release workflow doesn't set it, so the bundle'sapiUrl()falls back tohttp://localhost:8000at runtime. Worth deciding (relative/api+ nginx reverse proxy in the SPA image, or per-environment build args, or runtime config injection) before writing k8s manifests that point at a backend the bundle can't reach.packages/api/src/version-check.tsintomain.tsx— tracked separately in smartem-frontend#93.Verification
npm run typecheckinwebui/passes after the JSON edit (the entry conforms to the existingArtefactItemtype — same shape asbackend).python3 -c \"json.load(open('core/artefacts.json'))\"parses cleanly.Test plan
docs/operations/releasing.md