Skip to content

Commit

Permalink
feat: GAUD-5048 - Use new release token (#164)
Browse files Browse the repository at this point in the history
  • Loading branch information
svanherk authored Feb 23, 2024
1 parent c51386a commit 212366d
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 10 deletions.
6 changes: 4 additions & 2 deletions .github/workflows/workflow.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ jobs:
timeout-minutes: 2
strategy:
matrix:
node: ['12', '14', '16', '18']
node: ['12', '14', '16', '18', '20']
steps:
- name: Checkout
uses: Brightspace/third-party-actions@actions/checkout
Expand Down Expand Up @@ -41,11 +41,13 @@ jobs:
persist-credentials: false
- name: Setup Node
uses: Brightspace/third-party-actions@actions/setup-node
with:
node-version: 20
- name: Semantic Release
if: github.ref == 'refs/heads/master'
uses: BrightspaceUI/actions/semantic-release@main
with:
DEFAULT_BRANCH: master
GITHUB_TOKEN: ${{ secrets.D2L_GITHUB_TOKEN }}
GITHUB_TOKEN: ${{ secrets.D2L_RELEASE_TOKEN }}
NPM: true
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
12 changes: 4 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,3 @@
[![Build Status](https://api.travis-ci.com/Brightspace/d2l-license-checker.svg?branch=master)](https://travis-ci.com/Brightspace/d2l-license-checker-ci)

# d2l-license-checker

A simple tool to check licenses of all npm dependencies in a project against an approved set of licenses. Can be added to a test suite / CI to get a warning about packages not meeting predefined license requirements. This is basically a wrapper around [`davglass/license-checker`](https://github.com/davglass/license-checker)
Expand Down Expand Up @@ -53,10 +51,8 @@ The configuration file is a simple JSON file with the following optional entries

* `"ignoreUnusedManualOverrides"`: Set it to true if you do not want warnings logged when you have unused manual overrides (`false` by default)

## Contributing
## Versioning and Releasing

This repo is configured to use `semantic-release`. Commits prefixed with `fix:` and `feat:` will trigger patch and minor releases when merged to `main`.

1. Update code.
1. Update version in `package.json`.
1. Commit/merge changes via pull request.
1. Run `Release new version` GitHub action workflow.
1. Travis will automatically publish tagged commits to npmjs.org.
To learn how to create major releases and release from maintenance branches, refer to the [semantic-release GitHub Action](https://github.com/BrightspaceUI/actions/tree/main/semantic-release) documentation.

0 comments on commit 212366d

Please sign in to comment.