Send readers to the tags, which is where the versions are - #39
Merged
Conversation
install.md pointed at the Releases page to pick a version. There are no GitHub Releases in this repository -- release.yml builds the package and pushes it to both registries, and never creates one -- so that page answers "There aren't any releases here" while four tags sit next to it. The sentence beside the link already said where to look: the git tag is the package version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mbakalarski
added a commit
that referenced
this pull request
Aug 6, 2026
The deploy job waits on GitHub's Pages backend and does no work of its own, so nothing here bounds how long it takes. A 10 minute cap killed PR #39's deploy at 10m03s: the change was merged, every check was green, and the published page kept serving the old content with nothing to indicate why. Measured the same day on netclab.github.io, which runs the same shape of workflow: 8m04s, a cancellation at 10m00s, then 9m12s. The successful runs sit just under the cap that killed one, which is how this stays invisible until it is not. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 6, 2026
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.
docs/install.mdtold readers to "pick a version from the Releases page" andlinked there. This repository has no GitHub Releases —
release.ymlbuildsthe package and pushes it to GHCR and Upbound, and never creates one — so that
page answers "There aren't any releases here", while four tags (
v0.4.0,v0.3.0,v0.2.15,v0.2.14) sit next to it.Reported from the published page.
The fix follows what the sentence beside the link already claimed — the git tag
is the package version — so the link now goes to
/tags, and the comment in thesnippet says "the newest tag" rather than naming the Releases page again.
Verified: the tags page returns 200 and lists every published version, and
mkdocs build --strictpasses.Not done here
Creating actual GitHub Releases is the other way to resolve this, and it is a
larger decision rather than a link fix — it would mean backfilling four tags and
adding a step to
release.yml. Worth considering separately, since releasenotes are wanted anyway: the
spec.scopeimmutability hazard and "a raiseddependsOnfloor does not upgrade an installed dependency" are both things aconsumer should meet at upgrade time, and A5's Marketplace listing wants a
release-notes/directory too.🤖 Generated with Claude Code