Gathering detailed insights and metrics for scratch-semantic-release-config
Gathering detailed insights and metrics for scratch-semantic-release-config
Gathering detailed insights and metrics for scratch-semantic-release-config
Gathering detailed insights and metrics for scratch-semantic-release-config
semantic-release shareable configuration for Scratch
npm install scratch-semantic-release-config
Typescript
Module System
Node Version
NPM Version
18.5
Supply Chain
88
Quality
76.4
Maintenance
100
Vulnerability
92.4
License
JavaScript (95.21%)
Shell (4.79%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
81,410
Last Day
331
Last Week
1,887
Last Month
5,607
Last Year
58,656
BSD-3-Clause License
3 Stars
336 Commits
1 Forks
1 Watchers
12 Branches
Updated on Feb 12, 2025
Latest Version
3.0.0
Package Id
scratch-semantic-release-config@3.0.0
Unpacked Size
8.70 kB
Size
3.35 kB
File Count
4
NPM Version
10.8.2
Node Version
20.18.0
Published on
Nov 25, 2024
Cumulative downloads
Total Downloads
Last Day
44.5%
331
Compared to previous day
Last Week
55.8%
1,887
Compared to previous week
Last Month
39.6%
5,607
Compared to previous month
Last Year
239%
58,656
Compared to previous year
6
1
Remixed from: @jedmao/semantic-release-npm-github-config
This shareable configuration uses the following plugins:
@semantic-release/commit-analyzer
@semantic-release/release-notes-generator
@semantic-release/npm
@semantic-release/github
@semantic-release/git
package.json
.1npm install --save-dev semantic-release scratch-semantic-release-config
The shareable config can be configured in the semantic-release configuration file:
1{ 2 "extends": "scratch-semantic-release-config", 3 "branch": "main" 4}
Ensure that your CI configuration has the following secret environment variables set:
GH_TOKEN
with public_repo
access.NPM_TOKEN
NODE_AUTH_TOKEN
See each plugin documentation for required installation and configuration steps.
If you're configuring a GitHub workflow you might want
to do a test build matrix first and then publish only if those tests succeed across all environments. The following
will do just that, immediately after something is merged into main
.
1name: Node CI 2 3on: 4 push: 5 branches: 6 - main 7 8jobs: 9 test: 10 name: Test on node ${{ matrix.node }} and ${{ matrix.os }} 11 12 runs-on: ${{ matrix.os }} 13 14 strategy: 15 matrix: 16 node: [8, 10, 12] 17 os: 18 - ubuntu-latest 19 - windows-latest 20 - macOS-latest 21 22 steps: 23 - name: Preserve line endings 24 run: git config --global core.autocrlf false 25 - name: Checkout 26 uses: actions/checkout@v1 27 - name: Setup Node 28 uses: actions/setup-node@v1 29 with: 30 node-version: ${{ matrix.node }} 31 - name: Install & test/cover 32 run: npm ci && npm run cover 33 env: 34 CI: true 35 36 release: 37 name: npm publish / GitHub release 38 needs: test 39 runs-on: ubuntu-latest 40 steps: 41 - name: Checkout 42 uses: actions/checkout@v1 43 - name: Setup Node 44 uses: actions/setup-node@v1 45 with: 46 node-version: 12 47 registry-url: https://registry.npmjs.org/ 48 - name: Install 49 env: 50 CI: true 51 run: npm ci 52 - name: Build 53 if: success() 54 run: npm run build 55 - name: Semantic Release 56 if: success() 57 env: 58 GH_TOKEN: ${{ secrets.GH_TOKEN }} 59 NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} 60 NPM_TOKEN: ${{ secrets.NPM_TOKEN }} 61 run: npx semantic-release
No vulnerabilities found.
No security vulnerabilities found.