Repository navigation
release: 0.1.0 - #51
Merged
Merged
Conversation
added 3 commits
September 26, 2026 19:31
…all checks out the tag
…test counts its packages
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
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.
This is the release branch for 0.1.0, the first release. It bumps the version, adds
CHANGELOG.md, and makes every document that said there was no release true of one.The version
No code changes beyond the version constant. The tag goes on this PR's merge commit, dated 2026-09-26.
Ten places, counted rather than assumed:
"version"in the rootpackage.jsonand in each of the eightpackages/*/package.json, andVERSIONinpackages/core/src/version.ts.packages/core/src/version.test.tsholds them to one number and counts the manifests, so a new package fails it until the count in the test is raised. The publicCLAUDE.mdnow lists those places under "Cutting a release", step 2, where it said they would be listed once the stack existed.The README's install steps check out the release. "Installing" was
git clonethen./install.sh, which installsmain, and after the next commit tomainthat is code no release contains whileclickmonk versionstill prints the last release. It now runsgit checkout v0.1.0first. "Cutting a release" step 2 names that line as one more place to bump, and gives the command that counts it, because the version test cannot see a README.pnpm installrewrote nothing inpnpm-lock.yaml.The changelog
One entry, 0.1.0, with "Added" and "What 0.1.0 does not do". There is no "Fixed" or "Changed" section, because nothing was released before it. "Added" was read against the whole history and every merged PR, #5 through #50. The fonts sentence is #48's, and the notifications line carries #49's rule for a domain verified by hand. The brand assets (#1) and CI changes are not user-facing and have no entry.
The "does not do" list and the README's "What does not work yet" say the same things. Reconciling them added three items to the README's list that only the interface section or "Upgrading" stated before: no time zone setting for the install (#43), no bulk operations (#39), and no published container image. The bulk item says one link and one domain at a time, and the interface section's "one setting at a time" is gone, because settings are saved several at once. The changelog's list gained the report limits, the export that ends the connection, and the IPv6 test coverage that the README already listed. The TLS line says "domains you have verified" rather than "verified with a DNS record", because a domain added with
--verifiedgets a certificate too.Releases are git tags, and there is no published image. The changelog's opening says so. An install builds from the checkout, as
install.shdoes.The documents
README "Status" opens with "0.1.0, the first release. It has not yet carried anyone's production traffic, and the list below of what it does not do is part of the release." The public
CLAUDE.md's "Current status" says "Released as 0.1.0; early."SECURITY.mdgains its supported-versions table: the latest release is supported and nothing older is, with no backports. It shows how to find the version to put in a report. The reporting channels are unchanged.CONTRIBUTING.mdno longer says most of the product is not built. It points at the README's status section for what 0.1.0 does and does not do. Its pointer to "The stack suites" now namesCLAUDE.md, where that section is. It said "above", and the section was never inCONTRIBUTING.md.Verification
pnpm lint,pnpm lint:sh,pnpm typecheckandpnpm buildare clean.pnpm testpasses: 1565 tests in 67 files, and the interface's 592 in 46. The count is 9 manifests at"version": "0.1.0"and 1VERSION = '0.1.0', and nothing at0.0.0in either. The image built from this branch printsclickmonk 0.1.0 (schema version 10)forclickmonk version. The version guard was mutated twice. The first mutation set one package's manifest back to0.0.0, and the second setVERSIONto0.1.1. Each failedversion.test.ts's agreement test, and the file's other two tests passed. That one test covers both cases. The stack and durability suites were not run on this branch because nothing they exercise changed. CI runs them. The IPv6 published-port test, which CI skips, passed in the gate for #50 on a host whose IPv6 addresses are unique-local, and nothing it exercises changed here.