Skip to content

Back Up Instructions

Jump to bottom
George M. Dias edited this page Mar 8, 2022 · 2 revisions

You may be creating a release of the SAF Action so that it includes the latest SAF CLI node module dependency, includes new updates to the action itself, or both! Check out the following instructions to make sure you include the latest dependencies, any changes you may have committed, and the appropriate tags when making a release.

  1. Ensure you have the most recent commits to the SAF Action locally.

  2. Determine the new SAF Action version.

  3. Update package.json file and node modules. CHOOSE STEP 4 DIRECTIONS:

  4. For updating MINOR or PATCH version change: Create a release tag with annotations by doing the following. The annotation will be displayed in the release notes. (You can view SAF Action tags by writing git tag) Add the new release tag from step 2 (ex tag name full: v1.2.1) with an annotation. This tag name full is the new version of the SAF Action, and is only required to have the same major version number as the SAF CLI, but can have different minor or patch numbers. Ex: git tag -a -m "Using SAF CLI verion v1.0.6" Delete previous major release tag (ex tag name major: v1) by running Ex: git push origin :refs/tags/ Re-add the major release tag (ex tag name major: v1) to reference the latest SAF Action semantic version tag. You can use the same annotation. Notice this includes a force flag: -f. Ex: git tag -f -a -m "Using SAF CLI verion v1.0.6" Push the tags to the remote repository. Branch should be main. git push --atomic origin

  5. For updating MAJOR version change: Create a release tag with annotations by doing the following. The annotation will be displayed in the release notes. (You can view SAF Action tags by writing git tag) Add the new release tag from step 2 (ex tag name full: v1.2.1) with an annotation. This tag name full is the new version of the SAF Action, and is only required to have the same major version number as the SAF CLI, but can have different minor or patch numbers. Ex: git tag -a -m "Using SAF CLI verion v1.0.6" Add the major release tag (ex tagNameMajor: v1) to reference the latest SAF Action semantic version tag. You can use the same annotation. Ex: git tag -f -a -m "Using SAF CLI verion v1.0.6" Push the tags to the remote repository. git push --atomic origin

  6. Release the newly tagged version. Optional Information: Running Dependabot manually to detect latest dependency updates and update node modules

Clone this wiki locally