Drop the 0.3.0 explanation from the 0.3.1 intro, and its dead links - #375
Merged
Conversation
The paragraph explained why the release is numbered 0.3.1 and that 0.3.0 was tagged but never published. Both the tag and its empty draft release are now deleted, so the thing it was explaining no longer exists for a reader to trip over, and the paragraph spent three sentences on repository bookkeeping in the first thing anyone reads about the release. Deleting the tag also left two link definitions pointing at nothing: `[Unreleased]` compared from v0.3.0, and `[0.3.0]` linked a tag page that now 404s and had no heading using it. Unreleased compares from v0.2.6, the last released version, and the 0.3.0 definition is gone. Verified every remaining `releases/tag/` target in the file resolves to a tag that exists on origin: v0.1.0 through v0.2.6, nine of them, all present. check:changelog still reports 8 entries rendering the date CHANGELOG.md declares, and the site builds. Left alone: one line inside a 0.3.1 entry describes Release Drafter proposing v0.2.7 "for a repo already tagged v0.3.0". That narrates a bug that did happen, which is what a changelog is for.
fstubner
added a commit
that referenced
this pull request
Sep 7, 2026
#376) A CHANGELOG.md-only PR (#375) ran four checks instead of seven: the site build and the preview deploy both skipped, because site.yml decides with `grep -qE '^site/'` and the changelog is not under site/. The site renders CHANGELOG.md, so a change that breaks the site build could have merged without CI noticing. #375 was fine only because it was built locally first. Four files outside site/ feed the build: - CHANGELOG.md, imported by pages/changelog.astro with `?raw` - scripts/install.ps1 and scripts/install.sh, served at /install.ps1 and /install.sh by the two route files that read them at build time - apps/netscli-gui/package.json, which site-content/version.ts reads for the version the page displays All three filters now name the same five paths: site.yml's push trigger, the grep in its `changes` job, and site-preview.yml's two. The list is written three times because a workflow `paths:` cannot reference a variable; each copy carries a note pointing at the others. pages.yml only gains a comment. Its push trigger is still deliberately disabled, and the note now says to copy site.yml's list rather than the `['site/**']` it previously suggested, which would have left changes to those four files undeployed. Verified: the regex matches all five inputs and rejects README.md, crates/**, docs/PUBLISHING.md, CHANGELOG.md.bak, package-lock.json, install.ps1.old and notsite/. All three workflows parse, and the parsed `paths:` lists are identical across the three filters.
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.
The intro paragraph explained why the release is numbered 0.3.1 and that 0.3.0 had been tagged but never published. The tag and its empty draft release are now both deleted, so there's nothing left for a reader to trip over — and the paragraph spent three sentences on repository bookkeeping in the first thing anyone reads about the release.
Fallout from the tag deletion
Two link definitions at the bottom of the file pointed at nothing once
v0.3.0was gone:[Unreleased]compare/v0.3.0...HEADcompare/v0.2.6...HEAD[0.3.0]releases/tag/v0.3.0(404, and no heading used it)Verification
Every remaining
releases/tag/target in the file was checked againstgit ls-remote --tags origin— v0.1.0 through v0.2.6, nine tags, all present.check:changelogstill reports 8 entries rendering the dateCHANGELOG.mddeclares, and the site builds.Deliberately left: one line inside a 0.3.1 entry describes Release Drafter proposing v0.2.7 "for a repo already tagged v0.3.0". That narrates a bug that did happen, which is what a changelog is for.