Upgrade Lerna to v9 and migrate npm publishing to Trusted Publishing#236
Open
Bhaswati1148 wants to merge 14 commits into
Open
Upgrade Lerna to v9 and migrate npm publishing to Trusted Publishing#236Bhaswati1148 wants to merge 14 commits into
Bhaswati1148 wants to merge 14 commits into
Conversation
…ing with github and npm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR upgrades Lerna from v8 to v9, updates the GitHub Actions build and publish workflows to use Node.js 24.x, and migrates npm package publishing to npm Trusted Publishing.
It also removes the unused UOWS client generator package from the repo, as we now generate the UOWS client in the
user-office-coreitselfMotivation and Context
Our GitHub Actions workflow was unable to publish new package versions to the npm registry due to authentication failures related to the npm access token used by the publishing process. Please check the failed github action here
As part of investigating the issue, we attempted to generate a new npm access token using the STFC service account. During this process, npm recommended migrating to
Trusted Publishers, which uses GitHub's OIDC-based authentication mechanism instead of long-lived or periodically rotated access tokens. This approach provides a more secure and maintainable solution for package publishing.Support for npm Trusted Publishing was introduced in Lerna v9. Since our current version (v8) does not support this publishing mechanism, upgrading Lerna is required to enable OIDC-based authentication and publishing from GitHub Actions.
How Has This Been Tested
The GitHub Actions publishing workflow was executed from the
debug-npm-authbranch after configuring npm Trusted Publishing and upgrading Lerna to v9.The workflow completed successfully and was able to publish version 1.9.1 of the
@user-office-software/duo-message-brokerpackage to the npm registry using OIDC-based authentication.Reference : successful github actions workflow run
Fixes
Changes
Depends on
Tests included/Docs Updated?