ci: let the deploy workflow publish without moving latest - #140
Merged
Conversation
The deploy workflow hardcoded `mike deploy --push --update-aliases $VERSION latest`, so every publish moved the `latest` alias onto whatever version was dispatched. The site root redirects to `latest/`, which made it impossible to put an alpha, beta or release candidate on docs.romm.app without also making it the page everyone lands on. Add a `set_latest` boolean input, defaulting to true so a normal release run behaves exactly as before. Unchecking it deploys the version on its own, reachable at its own URL and listed in the version dropdown, with `latest` left where it is. The branch treats only an explicit "false" as opt-out, so a dispatch that somehow arrives without the input still aliases `latest`. Co-Authored-By: Claude Opus 5 (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.
What
Adds a
set_latestboolean input to the Build and Deploy Docs workflow. It defaults totrue, so a normal release dispatch behaves exactly as it does today. Unchecking it runsmike deploy --push "$VERSION"with no alias argument.Why
The deploy step hardcoded the alias:
Every publish therefore moved
latestonto whatever version was dispatched. Since the site root redirects tolatest/, there was no way to put a pre-release on docs.romm.app without also making it the page every visitor lands on.With the input unchecked, an alpha deploys to
docs.romm.app/5.3.0-alpha.1/and shows up in the version dropdown, whilelateststays on the current stable release. Publishing the final version later through a normal run moves the alias as usual.Notes
"false"as the opt-out, so a dispatch that somehow arrives without the input still aliaseslatest.trunk check(actionlint, yamllint, prettier, checkov) passes clean on the file.🤖 Generated with Claude Code