chore: release 4.21.0 #385
Merged
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Release ManagerRelease workflow run: https://github.com/npm/template-oss/actions/runs/7064640037 Release Checklist for v4.21.0
|
github-actions
bot
force-pushed
the
release-please--branches--main
branch
5 times, most recently
from
19c35bb
to
23b06e1
Compare
lukekarrys
added a commit
that referenced
this pull request
Dec 1, 2023
- fix: pin release-please version
There is a tradeoff with our usage of release-please. We are using some
`release-please` classes that we import directly from files like `const
{ ManifestPlugin } = require('release-please/build/src/plugin.js')`. Due
to how load bearing our release process is for us, I think it is best to
always pin to an exact version and use dependabot PRs to review all
`release-please` changes.
- chore: update release please mocks and snapshots
This PR also updates mocks and snapshots. I was not expecting this to
need to be updated but they failed in #385. It's possible that the mock
recording or the usage of these mocks inside release-please is
non-deterministic. I will keep an eye on these tests and refactor in the
future if they turn out to be flaky.
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
23b06e1
to
ec4479e
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
ec4479e
to
f8bb856
Compare
lukekarrys
approved these changes
Dec 1, 2023
|
🤖 Release is at https://github.com/npm/template-oss/releases/tag/v4.21.0 🌻 |
Release Workflow
|
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.
🤖 I have created a release beep boop
4.21.0 (2023-12-01)
Features
2daff23#334 use upstream release-please (feat: use upstream release-please #334) (@lukekarrys)3d76fc4#380 release workflow uses composite actions (feat: release workflow uses composite actions #380) (@lukekarrys)Bug Fixes
fbe355c#388 pin release-please version (fix: pin release-please version #388) (@lukekarrys)4fad5d8#387 make prerelease config switch versioning strategy (fix: make prerelease config switch versioning strategy #387) (@lukekarrys)c892260#386 fallback to default release process of 404 from hosted version (fix: fallback to default release process of 404 from hosted version #386) (@lukekarrys)9b22b83#384 give release integration workflow correct permissions and secrets (fix: give release integration workflow correct permissions and secrets #384) (@lukekarrys)This PR was generated with Release Please. See documentation.