chore: release @alchemy_cms/json_api 4.0.0 - #211
Merged
Merged
Conversation
The 4.0.0 changes (TypeScript deserializer, exports map, dropped deprecated filtering) landed as refactor-type commits on the pre-move root path, so release-please's path-scoped scan of javascript/ finds no user-facing commit and skips the release even with a config `release-as`. Force the first release explicitly via a Release-As footer (which touches javascript/ so it is attributed to the package), seed javascript/CHANGELOG.md for release-please to maintain, and drop the now-redundant config option. Release-As: 4.0.0
Refactors carry useful release information, so include them in generated changelogs going forward. Specifying `changelog-sections` replaces release-please's default set, so the full list is spelled out explicitly: feat, fix, perf, refactor, deps and revert are shown; docs, style, chore, test, build and ci stay hidden.
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
1 participant
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.
Fixes the stuck first release. After #209 merged, release-please ran but skipped — its path-scoped scan of
javascript/found onlyrefactor/docs/ci/buildcommits sincepackage-v3.0.1("No user facing commits found - skipping"), and the configrelease-asset the version but didn't override that skip.This forces the first release with a
Release-As: 4.0.0footer on a commit that touchesjavascript/(so it's attributed to the package), which release-please honours by opening a release PR for that exact version. It also seedsjavascript/CHANGELOG.mdand drops the now-redundant configrelease-as(the footer is one-time and needs no later cleanup).Release-As: 4.0.0line stays in the commit message onmain— release-please reads it from the merged commit. A merge commit preserves it verbatim; a squash merge keeps it as long as the footer remains in the squash commit body (it's there by default for this single-commit PR — just don't strip it).After this merges, release-please should open a
4.0.0release PR; merging that tagspackage-v4.0.0and publishes4.0.0via OIDC.