This repository was archived by the owner on Aug 24, 2026. It is now read-only.
Repository navigation
Release 1.1.0 - #50
Merged
Merged
Conversation
Fold the Unreleased section into 1.1.0 and redate it to 2026-07-28. The changelog page (#49) landed under Unreleased, but its code is in the same tree as the rest of 1.1.0, so tagging with the section split would publish a release whose own changelog says part of it is unreleased. The date moves off 2026-07-27 because #45 through #49 all merged on the 28th. Also record the bundled profile model refresh from #38 and #41, which changed shipped model IDs and was itemized in neither section. site/changelog.html is regenerated from CHANGELOG.md; npm test passes (184 tests, 182 pass, 2 skipped).
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Prepares the 1.1.0 release.
package.jsonandinstall.jsalready carry1.1.0, so this changes only the changelog and its generated page.Folds
Unreleasedinto1.1.0and redates it to 2026-07-28. The changelogpage (#49) landed under
Unreleased, but its code sits in the same tree as therest of 1.1.0. Tagging with the split in place would publish a release whose own
changelog says part of it is unreleased, and the docs site would show a "Latest"
1.1.0 below an "In progress" section describing code inside that release. The
date moves off 2026-07-27 because #45, #46, #47, #48, and #49 all merged on the
28th.
Records the bundled profile model refresh from #38 and #41. Those changed
shipped model IDs, which is user-visible, and were itemized in neither the 1.0.0
nor the 1.1.0 section.
No prose was rewritten: every existing bullet is preserved verbatim, only the
headings moved.
Verification
npm test- 184 tests, 182 pass, 2 skipped, 0 failnode scripts/build-changelog.js --check-site/changelog.htmlmatchesCHANGELOG.mdnpm run check-install- installed prompts in syncnpm run check-profiles- 5 profiles, 0 errors, 0 warnings1.1.0 - Jul 28, 2026, theLatestpill ison 1.1.0, no
Unreleasedsection remainsAfter merge
v1.1.0gets tagged on the merge commit, plus a retroactivev1.0.0atf60ba23so the release has a previous version to compare against. This repohas no tags or GitHub releases yet, so 1.1.0 will be its first published one.
Touches
site/, so merging also triggers a Pages deploy.