-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use upstream release-please #334
Conversation
ba07c1a
to
d9c3a29
Compare
d9c3a29
to
badde39
Compare
badde39
to
ee30e61
Compare
fcb5b54
to
61e2718
Compare
10e669e
to
18c0f93
Compare
083c66d
to
855f4da
Compare
7ffb368
to
47b81fc
Compare
2f5c040
to
ae3e517
Compare
This is multiple commits because it helped me keep track of coverage and testing changes as I iterated. But this can be squashed and merged to a single commit. |
This is ready for review but is built on #380 so that will need to be merged first. |
d2fa78b
to
585bf71
Compare
7ea6750
to
8ec3bec
Compare
8ec3bec
to
6797112
Compare
This has been squashed to a single commit and rebased against main. It is ready for review again. |
gh pr merge <PR-NUMBER> ${R} --rebase | ||
\`\`\` | ||
${block('sh')} | ||
gh pr merge <PR-NUMBER> ${R} --squash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I learned that release-please will work faster if the release PRs are merged with squash instead of rebase.
This more closely aligns the test behavior with how it is actually called. The release.yml workflow always passed in a tag.
@@ -19,7 +19,8 @@ | |||
"postlint": "template-oss-check", | |||
"postinstall": "template-oss-apply", | |||
"test-all": "npm run test -ws -iwr --if-present", | |||
"lint-all": "npm run lint -ws -iwr --if-present" | |||
"lint-all": "npm run lint -ws -iwr --if-present", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these entries were alphabetical
🤖 I have created a release *beep* *boop* --- ## [4.21.0](v4.20.0...v4.21.0) (2023-12-01) ### Features * [`2daff23`](2daff23) [#334](#334) use upstream release-please (#334) (@lukekarrys) * [`3d76fc4`](3d76fc4) [#380](#380) release workflow uses composite actions (#380) (@lukekarrys) ### Bug Fixes * [`fbe355c`](fbe355c) [#388](#388) pin release-please version (#388) (@lukekarrys) * [`4fad5d8`](4fad5d8) [#387](#387) make prerelease config switch versioning strategy (#387) (@lukekarrys) * [`c892260`](c892260) [#386](#386) fallback to default release process of 404 from hosted version (#386) (@lukekarrys) * [`9b22b83`](9b22b83) [#384](#384) give release integration workflow correct permissions and secrets (#384) (@lukekarrys) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This also adds 100% test coverage to
release-please
andrelease-manager
usingnock
.Fixes #177