chore: release 8.3.0 - #220
Merged
Merged
Conversation
Graduate the 8.3.0 alpha line to a stable release. Sets the version in files rather than via a Release-As footer, since this repo allows squash merges only with an empty commit body, which strips footers. Also realigns .release-please-manifest.json, which had drifted to 8.1.0 while package.json was at 8.2.0.
vitaligi
requested changes
Aug 3, 2026
vitaligi
left a comment
Contributor
There was a problem hiding this comment.
please update version in package-lock.json
vitaligi
approved these changes
Aug 3, 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
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.
What
Sets the version to 8.3.0 for the stable release of the
8.3.0alpha line. The code is already onmaster(#219); this only sets the release metadata.package.json8.3.0-alpha.28.3.0.release-please-manifest.json8.3.0-alpha.28.3.0CHANGELOG.md8.3.0-alpha.28.3.0sectionWhy the version is in files, not a
Release-AsfooterThe first attempt (#219) used release-please with a
Release-As: 8.3.0footer. It did not work, and cannot work in this repo as configured:allow_merge_commit: falseandallow_rebase_merge: false— squash is the only merge methodsquash_merge_commit_message: "BLANK"— GitHub writes an empty body on squash, so any commit footer is discardedpull_request) blocks pushing the footer straight tomasterWith no releasable commits and no override, release-please ran on
masterand correctly did nothing. Putting the version in tracked files makes it immune to squashing.Release steps after merge
Squash-merging this is safe — the change lives in the tree, not in commit metadata.
v8.3.0on the resultingmastercommitpublish.yamltakes itselsebranch (prerelease != true) and runsnpm publish --access public, putting 8.3.0 on thelatesttagSide effect: fixes drifted release state
.release-please-manifest.jsonsaid8.1.0whilepackage.jsonsaid8.2.0andv8.2.0was tagged — a leftover from the manual8.2.0bump (#209). All three now agree at8.3.0, so future release-please bumps compute from a correct base.Notes
alpharather thanmaster, because chore: release 8.3.0 #219 was squashed.CHANGELOG.mdstill has no8.2.0section (that release was never recorded, soInstanceType/ MAPCO-9571 is undocumented). Left alone here to keep this PR to one purpose — happy to add it separately.