Use upstream release-please instead of our fork

[lukekarrys]

We forked release-please to get some features it did not have yet, but a quick look at the issues listed in npm/template-oss#177 show that most of those features are now in googleapis/release-please.

In order to be confident in dropping our fork, we should first implement full test coverage for the usage of our fork.

TODO:

• Finish test coverage for release please in template oss feat: use upstream release-please template-oss#334
• Use upstream release please and test
• Make any changes necessary
• Deprecate and archive our fork

[lukekarrys]

Weekly Status

Overall status:

🟢 Normal

Target date

2023-12-08

Accomplishments:

• Refactored template-oss release-please usage to add needed features/fixes. PR is ready for review: feat: release workflow uses composite actions template-oss#380
• Made progress on draft PR using upstream release-please including snapshot testing feat: use upstream release-please template-oss#334
• Filed upstream PRs with release-please to get some necessary bug fixes https://github.com/googleapis/release-please/pulls?q=is%3Apr+author%3Alukekarrys+

Next:

• Finish snapshot and integration testing upstream release-please in feat: use upstream release-please template-oss#334
• Land feat: release workflow uses composite actions template-oss#380 and feat: use upstream release-please template-oss#334

Risks