Now that jiralint-pulumi is consuming the lib package from this repo via a true npm package (private; Github Package Registry), it would be good to automatically publish that package upon release of this repo (via github action, probably).
This will probably involve:
in the CI github action: publish the npm package. The ambient GITHUB_TOKEN should give you permission to do this. The action at https://github.com/cycjimmy/semantic-release-action looks promising for this. If that action doesn't work, fall back on doingnpm publish manually (https://docs.npmjs.com/cli/v6/commands/npm-publish). Ensure you're publishing to the private Github Package Registry associated with this repo, not the public npm registry
do the above step only for main branch and/or only for release tags
If that doesn't work, we may have to use a machine user and a corresponding PAT:
Now that jiralint-pulumi is consuming the lib package from this repo via a true npm package (private; Github Package Registry), it would be good to automatically publish that package upon release of this repo (via github action, probably).
This will probably involve:
GITHUB_TOKEN
should give you permission to do this. The action at https://github.com/cycjimmy/semantic-release-action looks promising for this. If that action doesn't work, fall back on doingnpm publish
manually (https://docs.npmjs.com/cli/v6/commands/npm-publish). Ensure you're publishing to the private Github Package Registry associated with this repo, not the public npm registryIf that doesn't work, we may have to use a machine user and a corresponding PAT: