Repository navigation
chore(main): release 0.5.0 - #28
Merged
ddeltree merged 2 commits intoSep 16, 2026
Merged
Conversation
The mask commit carried no `BREAKING CHANGE:` footer, so release-please filed the curried `set` under Features with no migration note — anyone upgrading from 0.4.0 would have found `set(obj, [path, value])` gone without warning. Amending the commit would mean force-pushing main for no version benefit: a `feat` at 0.x already bumps the minor under this config, so 0.5.0 is correct either way. CLAUDE.md prescribes fixing the entry on the release PR's branch instead, as 0.4.0 also had to be.
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.
Release PR for 0.5.0, generated by release-please and then hand-edited.
Bumps
package.json,package-lock.jsonand.release-please-manifest.json,and adds the
CHANGELOG.mdentry.The generated entry was rewritten by hand: the mask commit carried no
BREAKING CHANGE:footer, so the curriedsethad been filed under Featureswith no migration note. The version is unaffected — a
featat 0.x alreadybumps the minor under this config.
Opened manually because the Release workflow cannot: Settings → Actions →
General → Workflow permissions → "Allow GitHub Actions to create and approve
pull requests" is off, so release-please updates the branch and then fails at
the last step.
Merging this tags
v0.5.0. Publishing stays manual:git pull && npm publish.