Skip to content

chore(release): 0.1.0-beta.1 - #19

Merged
onlyexeption merged 1 commit into
mainfrom
release/0.1.0-beta.1
Oct 26, 2026
Merged

onlyexeption merged 1 commit into
mainfrom
release/0.1.0-beta.1

Conversation

@onlyexeption

Copy link
Copy Markdown
Collaborator

No description provided.

@onlyexeption
onlyexeption merged commit d757ccb into main Oct 26, 2026
8 checks passed
@onlyexeption
onlyexeption deleted the release/0.1.0-beta.1 branch October 26, 2026 13:16

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a straightforward release bump from 0.1.0-beta.0 to 0.1.0-beta.1.

What was reviewed:

  • The version strings match across package.json, both package-lock.json version fields and both server.json version fields, as CLAUDE.md requires.
  • Every 0.1.0-beta.0 reference in README.md and server/README.md is now 0.1.0-beta.1. A repo-wide search outside CHANGELOG.md found no 0.1.0-beta.0 strings left.
  • The new CHANGELOG section has the right compare link (0.1.0-beta.0...0.1.0-beta.1). Its data claims match the docs: 5,343 pages fits "5,300+ public types", and the data version is still 26.1.21.
Extended reasoning...

The change touches only version metadata (package.json, package-lock.json, server.json), version strings in the two READMEs, and a new CHANGELOG entry. It has no source, CI or build logic changes and touches no security-sensitive surface. The repo has no CODEOWNERS file, and the timeline shows no reviewer objections. The bug hunt ended with a dry streak and found nothing. The bump is mechanical and consistent across all files, so approval is warranted.

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.

2 participants