Skip to content

Commit

Permalink
chore: updates
Browse files Browse the repository at this point in the history
  • Loading branch information
rustygreen committed Feb 8, 2024
1 parent 893da0b commit 9ebe989
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 6 deletions.
7 changes: 4 additions & 3 deletions .github/workflows/publish.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,10 @@ jobs:
with:
fetch-depth: 0

- name: Exit if not on main branch
if: endsWith(github.ref, 'main') == false
run: exit -1
# TODO: Figure this out - @russell.green
# - name: Exit if not on main branch
# if: endsWith(github.ref, 'main') == false
# run: exit -1

- name: Install NodeJS
uses: actions/setup-node@v4
Expand Down
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@ npx nx generate @nx/angular:library --name=UI_LIB_NAME --buildable=true --direct

To generate a new release, use the following steps:

1. Run `npm run nx -- release --skip-publish` locally. This will create a commit with the version and changelog updates, then create a tag for the new version.
2. Push the changes (including the new tag) to the remote repository with `git push && git push --tags`.
3. The publish workflow will automatically trigger and publish the packages to the npm registry.
1. Run `npm run nx -- release --skip-publish` locally. This will create a commit with the version and changelog updates
2. Create a tag for the new version `git tag <tagname>`.
3. Push the changes (including the new tag) to the remote repository with `git push && git push --tags`.
4. The publish workflow will automatically trigger and publish the packages to the npm registry.

0 comments on commit 9ebe989

Please sign in to comment.