Skip to content

Prepare release 1.8.1 - #164

Closed
jgfoster wants to merge 1 commit into
mainfrom
james/release-1.8.1
Closed

jgfoster wants to merge 1 commit into
mainfrom
james/release-1.8.1

Conversation

@jgfoster

Copy link
Copy Markdown
Member

Prepares release 1.8.1. npm version 1.8.1 bumps package.json and package-lock.json, and [Unreleased] is promoted to ## [1.8.1] - 2026-10-20 with fresh link definitions. If the release goes out on a later day, change the date before merging.

Merge #163 (Grail pin → 172ad87) first. This changelog describes it, and the CI run on this PR's merge commit is where the release's packages come from. #163 doesn't touch CHANGELOG.md, so updating this branch from main won't conflict.

What's in it

Sweep since v1.8.0

Every merged PR was checked:

npm run release:notes 1.8.1 prints the section cleanly, Prettier passes, and no line in the section exceeds 100 columns.

After merge: wait for CI to go green on the merge commit, then dispatch Actions → Release with 1.8.1, dry-run first.

🤖 Generated with Claude Code

Promote [Unreleased] to 1.8.1 and bump the version with npm version.
Add the entry for the Grail pin bump (#163), and say that a 1.8.0
database carries over, since the engine is unchanged at 4.0.0.a5.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jgfoster

Copy link
Copy Markdown
Member Author

Replaced by #166.

@jgfoster jgfoster closed this Oct 20, 2026
@jgfoster
jgfoster deleted the james/release-1.8.1 branch October 20, 2026 21:34
@jgfoster jgfoster mentioned this pull request Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant