Made changes mostly to automation to try to get it to work

This commit is contained in:
Alan Bridgeman 2025-06-11 13:03:48 -05:00
parent e89b358067
commit 01e605bb03
2 changed files with 26 additions and 2 deletions

View file

@ -16,7 +16,7 @@ permissions:
jobs:
# Publishes the package to the private NPM registry
publish:
runs-on: self-hosted
runs-on: default
outputs:
build_and_deploy: ${{ steps.version_check.outputs.build_and_deploy }}
steps:
@ -24,6 +24,30 @@ jobs:
with:
fetch-depth: 0
# Set up Node.js
- name: Set up Node.js version
uses: actions/setup-node@v3
with:
# Taken from [Repo README](https://github.com/actions/setup-node#readme)
#
# > Version Spec of the version to use in SemVer notation.
# > It also admits such aliases as lts/*, latest, nightly and canary builds
# > Examples: 12.x, 10.15.1, >=10.15.0, lts/Hydrogen, 16-nightly, latest, node
node-version: 'latest'
# Taken from [Repo README](https://github.com/actions/setup-node#readme)
#
# > Optional registry to set up for auth. Will set the registry in a project level .npmrc and .yarnrc file,
# > and set up auth to read in from env.NODE_AUTH_TOKEN.
# > Default: ''
registry-url: 'https://npm.pkg.bridgemanaccessible.ca'
# Taken from [Repo README](https://github.com/actions/setup-node#readme)
#
# > Optional scope for authenticating against scoped registries.
# > Will fall back to the repository owner when using the GitHub Packages registry (https://npm.pkg.github.com/).
scope: '@BridgemanAccessible'
# Check if this is a "significant" commit that should trigger a new publish
# This is done by checking if the latest git tag matches the version in the `package.json` file
- name: Version Check

View file

@ -1,6 +1,6 @@
{
"name": "@BridgemanAccessible/listmonk-node-client",
"version": "1.0.1",
"version": "1.0.2",
"description": "A Node client library for Listmonk",
"repository": "https://git.bridgemanaccessible.ca/Bridgeman-Accessible/listmonk-nodejs-client.git",
"author": "Bridgeman Accessible<info@bridgemanaccessible.com>",