Skip to content

Conversation

@ChristosT
Copy link
Contributor

The current ci is failing because #25 updated nodejs version only in the test job but not the release job.

@ChristosT
Copy link
Contributor Author

cc: @jourdain

@jourdain
Copy link
Collaborator

jourdain commented Apr 1, 2025

Should the commit be ci: instead of fix:?

Match the node version in the release job to the one we use in testing
@ChristosT ChristosT force-pushed the update-release-job branch from 9903310 to 90ef4b7 Compare April 1, 2025 15:34
@ChristosT
Copy link
Contributor Author

done.

Just wanted to make sure that a new release will be triggered by the ci.

@jourdain jourdain merged commit b4842da into Kitware:master Apr 1, 2025
6 checks passed
@jourdain
Copy link
Collaborator

jourdain commented Apr 1, 2025

got a CI error

@ChristosT
Copy link
Contributor Author

This is the error

npm error code E403
npm error 403 403 Forbidden - GET https://registry.npmjs.org/decamelize-keys/-/decamelize-keys-1.1.1.tgz
npm error 403 In most cases, you or one of your dependencies are requesting
npm error 403 a package version that is forbidden by your security policy, or
npm error 403 on a server you do not have access to.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-01T15_50_24_776Z-debug-0.log
Error: Process completed with exit code 1.

the above link works now . not sure what went wrong. Should I create a new PR to trigger the CI ?
By the way, I created this because #25 had ci errors but I see now that the other PRs merged cleanly and a new release is out.

@jourdain
Copy link
Collaborator

jourdain commented Apr 1, 2025

not sure, it could be fine. We just need to keep an eye on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants