We should be using the release strategy specified by https://github.com/actions/toolkit/blob/master/docs/action-versioning.md#recommendations
To get there, we need to:
- Create a
releases/v1 branch and move the v1 tag and future releases there
- Warn that we will deprecate the master branch and that you should attach to
v1 instead. We will support master in a warned but deprecated state for ~1 month.
- Switch the warning to an error on master. Remove
node_modules from the master branch. We will stay in this state for ~1 month.
- Remove the error on master.
During steps 2 and 3, we need to be extra careful to not check the warning/error into the releases branch.
We should be using the release strategy specified by https://github.com/actions/toolkit/blob/master/docs/action-versioning.md#recommendations
To get there, we need to:
releases/v1branch and move thev1tag and future releases therev1instead. We will support master in a warned but deprecated state for ~1 month.node_modulesfrom the master branch. We will stay in this state for ~1 month.During steps 2 and 3, we need to be extra careful to not check the warning/error into the releases branch.