Skip to content

fix(ci-cd): upgrade lerna to v9 for npm publish - #84

Merged
yeshamavani merged 4 commits into
masterfrom
fix/release
Sep 11, 2026
Merged

fix(ci-cd): upgrade lerna to v9 for npm publish#84
yeshamavani merged 4 commits into
masterfrom
fix/release

Conversation

@piyushsinghgaur1

@piyushsinghgaur1 piyushsinghgaur1 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Problem

The Release workflow run failed at the publish step:

lerna WARN notice Package failed to publish: @sourceloop/user-onboarding-client
lerna ERR! E404 Not found
lerna WARN notice Package failed to publish: @sourceloop/search-element
lerna ERR! E404 Not found
lerna WARN notice Package failed to publish: @sourceloop/user-onboarding-element
lerna ERR! E404 Not found

The builds themselves succeeded; only lerna publish failed.

Change

  • Bump lerna from ^7.3.0 to ^9.0.7
  • Refresh package-lock.json accordingly

Lerna 7 predates npm trusted publishing (OIDC), which the release workflow now
relies on after id-token was added to it.

The release workflow failed publishing with `lerna ERR! E404 Not found`
for the element/client packages. Lerna 7 does not support npm trusted
publishing (OIDC) that the release workflow now relies on, so bump
lerna to ^9.0.7 and refresh the lockfile.

Ref: https://github.com/sourcefuse/arc-ng-components/actions/runs/34460014331/job/102815359958
Bump the release tooling so it stays consistent with the lerna 9 setup:
@commitlint/cli ^19.8.1, @commitlint/config-conventional ^16.2.1 and
commitizen ^4.2.5.

@commitlint/config-lerna-scopes is bumped to ^19.8.1 because v16 declares
a peerOptional on lerna ^3 || ^4, which fails to resolve against lerna 9.
Bump the node pin in the CI and release workflows from 20 to 24 and
move the actions to checkout@v5 / setup-node@v5.

Drop the node_modules cache from the pull request workflow. It only
cached the root node_modules, but the workspace dependencies install
into packages/*/node_modules, so a cache hit skipped npm ci and left the
lib build without @angular/router, shepherd.js and uuid. Cache the npm
download cache via setup-node instead and always run npm ci.
@piyushsinghgaur1 piyushsinghgaur1 self-assigned this Sep 11, 2026
@piyushsinghgaur1 piyushsinghgaur1 added the bug Something isn't working label Sep 11, 2026
@yeshamavani
yeshamavani merged commit 779033a into master Sep 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants