Tags give the ability to mark specific points in history as being important
-
0.9.0
Release: 0.9.07624b271 · ·feat(npm-publish): per-registry jobs with registry_uri/token inputs Changes since 0.8.0: - npm-publish: job names now include registry suffix — publish:npm:{nightly,dev,release}:{registry} - npm-publish: nightly (main) and release (tags) are required; dev (branches) is manual/non-blocking - npm-publish: registry_uri (without protocol) + token inputs replace hardcoded GitLab logic - npm-publish: supports multiple registries by including the component multiple times - yamllint: relax brackets rule to allow $[[ ]] syntax in flow sequences -
0.8.0
Release: 0.8.0da7b7a5f · ·fix(container): correct image lifecycle — build pushes slug, SHA only on main - container:build now pushes $CI_COMMIT_REF_SLUG (slug on branches, "main" on default branch) - container:tag:latest copies main→SHA and main→latest on the default-branch pipeline - container:tag:gittag copies SHA→$CI_COMMIT_TAG on tag pipelines - container:tag:branch removed — redundant, build already handles slug push - SHA images now only exist for commits that landed on main Changes since 0.7.0: - fix(container): correct image lifecycle — build pushes slug, SHA only on main
-
0.7.0
Release: 0.7.0ddf430c3 · ·fix(container): correct image tagging lifecycle - container-build: pushes $CI_COMMIT_SHORT_SHA only (no slug) - container-tag: new component with three jobs - container:tag:branch — short SHA → slug, non-default branches - container:tag:latest — short SHA → $CI_DEFAULT_BRANCH + latest, default branch - container:tag:gittag — short SHA → $CI_COMMIT_TAG, any git tag (dots preserved) - copy-image: add --all for multi-arch manifest list support