Target 1.0.0, add prerelease recipe, seed 1.0.0-beta.1 changelog - #5
Merged
Conversation
✅ Deploy Preview for tihole ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…1 changelog - Set VERSION and the site version to 1.0.0 — the first tihole release is 1.0.0 (cut as betas first), not 0.1.0. - Add `just prerelease` to cut vX.Y.Z-beta.N of the current VERSION, beta number auto-incrementing from existing tags. Mirrors the release recipe (main-only, clean-tree, build/vet/test gate, changelog promotion + site sync) but leaves VERSION untouched so betas lead up to the same final. - Seed the [1.0.0-beta.1] and [1.0.0] changelog sections + footer links and regenerate the site changelog (site lists both).
zackkitzmiller
force-pushed
the
chore/prerelease-tooling
branch
from
July 26, 2026 09:38
1b3ee03 to
84fd34c
Compare
zackkitzmiller
changed the title
zackkitzmiller
added a commit
that referenced
this pull request
Jul 26, 2026
Target 1.0.0, add prerelease recipe, seed 1.0.0-beta.1 changelog
zackkitzmiller
added a commit
that referenced
this pull request
Jul 26, 2026
Target 1.0.0, add prerelease recipe, seed 1.0.0-beta.1 changelog
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.
Summary
Two things: fix the first-release version to 1.0.0 (the initial public release is 1.0.0, cut as betas first — not 0.1.0), and add the missing prerelease tooling.
Changes
VERSIONandsite/src/version.js;CHANGELOG.mdsections renamed to[1.0.0-beta.1]/[1.0.0]with matching footer links; site changelog regenerated (lists both).just prerelease— cutsvX.Y.Z-beta.Nof the currentVERSION, beta number auto-incrementing from existingv<base>-beta.*tags. Mirrorsrelease(main-only guard, clean-tree guard, build/vet/test gate,[Unreleased]promotion, footer links,changelog-sync, commit + tag) but leavesVERSIONuntouched so betas lead up to the same final.[1.0.0-beta.1]section captures its delta over the prepped 1.0.0 notes: thez19rmodule rename and the MIT license.Release flow
just prerelease→ push main +v1.0.0-beta.2→release.ymlbuilds/publishes the prerelease.just release patch|minor|major→ same, for finals.Follow-up (done outside this PR)
The mistakenly-published
v0.1.0-beta.1release+tag (0 downloads) is replaced byv1.0.0-beta.1, cut from main after this merges.