Closed chingor13 closed 3 years ago
Two thoughts:
- Let's make sure all the steps you needed to take here are written down and added to the node.js playbook in detail
For most libraries, and newly cut previous major versions, the release-brancher script will make most of these changes automatically.
- I am very worried about our ability to keep these files up to date. Do we expect to ever need to manage these? Or is this a do it once kind of deal?
This branch was problematic because the CI setup changed between 2.x and 3.x. If there are significant changes to a repository's CI setup between versions, it's not so easy to automatically create these backport branches.
Warning: This pull request is touching the following templated files:
.kokoro
files are templated and should be updated insynthtool
.kokoro
files are templated and should be updated insynthtool
.github/workflows/ci.yaml
(GitHub Actions) should be updated insynthtool