Note that the Infusion 4 release is used as an example in what follows. If you are using these instructions for another release, remember to substitute the correct version number for occurrences of "4.0".
The steps to tag the source code are:
Set the the version as appropriate, for example:
{ version: "4.0.0" } |
Execute:
# using a fresh clone git clone git@github.com:fluid-project/infusion.git # or using a clean master in your current clone # ensure you are on master git checkout master # ensure no uncommitted changes git status -s # fetch the project-repo's (upstream) changes git fetch upstream # ensure no commits in your local master that aren't in the project-repo git log master ^upstream/master # ensure your master is up-to-date with the project-repo git merge upstream/master |
execute:
# create a package build of infusion npm run build:pkg |
build
directory and a products
directory containing the build artifacts. Either of these can be used for testing, but the zip file in the products directory is what should be used for posting the release.all-tests.html
file in a browser), and ensure that all succeed.Execute:
# create the tag git tag -a v4.0.0 |
Once the tag is tested and verified to be ok:
Execute:
# if working a fresh clone git push origin v4.0.0 # if working in an existing clone git push upstream v4.0.0 |
Modify the version in the node package.json
file for the main project repository to reflect that development is now for the next release version. For example:
{ version: "5.0.0" } |