Repository navigation
Use recommended release strategy #11
Description
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/v1branch and move thev1tag and future releases there - Warn that we will deprecate the master branch and that you should attach to
v1instead. We will support master in a warned but deprecated state for ~1 month. - Switch the warning to an error on master. Remove
node_modulesfrom 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.
Metadata
Metadata
Assignees
Labels
No labels
Activity
bryanmacfarlane commentedon Nov 5, 2019
We're not doing this anymore. We're moving toward ncc. See javascript-action PRs from me and talk to Josh
bryanmacfarlane commentedon Nov 5, 2019
At that point it's just code and branches and the branching is up to you.
konradpabjan commentedon Nov 6, 2019
A releases branch,
release/v1has been created to track of a stable release version. Thev1tag has also been adjusted to now point to that branch. In the future if there are big changes thenreleases/v2etc. will be created along with new tags. The master branch will remain functional with the latest and greatest changes changes. After changes in the master branch are validated and confirmed to be working they will be ported over to the releases branch.Node_moduleshave been removed from the master and release branch and we now rely on ncc to create a single js file for release. Since the master branch will continue to function, there is no need for deprecation warnings or error messages. We document that using a reference to the master branch could cause breaking changes in the future so no further action is needed: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsuses🔧 Import sphinx-mounts into the workspace as packages/sphinx-mounts (#…