Repository navigation
chore(release): 0.7.0 - #28
Merged
Merged
Conversation
Bump the version to 0.7.0 and add CHANGELOG.md with the 0.7.0 entry (#25, #26, #27). Ship the changelog in the npm package, and make the release workflow fail when CHANGELOG.md has no entry for the tagged version and use that entry as the GitHub Release body. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AK8gZCAMiLzJt6vCjwERPJ
…stration Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AK8gZCAMiLzJt6vCjwERPJ
imbenrabi
marked this pull request as ready for review
October 10, 2026 10:05
This was referenced Oct 10, 2026
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
2 participants
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.
Requested by Ben · project thread
Before: package.json says 0.6.3, there is no changelog, and the GitHub Release body comes only from auto-generated notes.
After: package.json says 0.7.0.
CHANGELOG.mdhas a 0.7.0 entry covering #25, #26 and #27, and it ships in the npm package. The release workflow fails if the tagged version has no changelog entry, and it uses that entry as the GitHub Release body, with the auto-generated notes after it.The version is 0.7.0, not 0.6.4, so that the FMP server's
^0.6.3range doesn't pick up the STATIC-mode change (#27) before the server has been verified against it.How:
npm version 0.7.0 --no-git-tag-version, a newCHANGELOG.md,CHANGELOG.mdadded tofiles, and an "Extract changelog entry" step inrelease.yml.Merge order: #26, then #27, then this PR last. The release tag must point at main HEAD, so it goes on this PR's merge commit. FMP server #108 must merge before the tag is pushed.
Verified locally: typecheck, 326/326 tests, and
npm pack --dry-runincludesCHANGELOG.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01AK8gZCAMiLzJt6vCjwERPJ
Generated by Claude Code