Skip to content

fix(ci): stop moving latest on manual republish and pin node base image - #14

Merged
BryanFRD merged 1 commit into
mainfrom
fix/11-latest-tag-pin
Oct 25, 2026
Merged

BryanFRD merged 1 commit into
mainfrom
fix/11-latest-tag-pin

Conversation

@BryanFRD

Copy link
Copy Markdown
Contributor

Only tag :latest when the event is release, so a workflow_dispatch republish of an older tag no longer downgrades it. Pin node:24-alpine to a digest in both Dockerfile stages; Renovate keeps it current.

Closes #11

@ferrfleet-interne ferrfleet-interne Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks correct. On workflow_dispatch the expression yields an empty line, which build-push-action drops from tags, so only the version tag gets pushed. The digest pin is applied to both stages, and renovate.json will keep it current.

Nit: a release: published event also fires for prereleases, so a prerelease mcp-v* tag still moves latest. That behaviour predates this PR. If you want it fixed, add && !github.event.release.prerelease to the condition.

@BryanFRD
BryanFRD merged commit b04106d into main Oct 25, 2026
15 of 16 checks passed
@BryanFRD
BryanFRD deleted the fix/11-latest-tag-pin branch October 25, 2026 10:39
ferrflow Bot added a commit that referenced this pull request Oct 26, 2026
## [10.13.4] - 2026-10-26

### Bug Fixes

- fix(deps): override body-parser to >=2.4.0 for GHSA-27r3-jxmh-p828 (#18)
- fix(ci): stop moving latest on manual republish and pin node base image (#14)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci(mcp-publish): stop moving latest on manual republish of an older tag

1 participant