You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.
Currently, the CLI and Plugins pipelines deploy all of the components to Zowe's Artifactory server, and any updated packages are deployed to NPM from there all at once by a different nightly job. For this feature to be implemented, the pipelines will need to be changed across the repositories to deploy to both Zowe's Artifactory and NPM directly, and the nightly NPM deployment pipeline can be disabled.
Is your feature or enhancement request related to a problem or limitation? Please describe
Our zowe.org releases are signed as part of the release process, but our npm releases are not.
Describe your enhancement idea
See https://github.blog/changelog/2023-09-26-npm-provenance-general-availability/. Is this something that we can use for Zowe CLI, the Node.js Client SDKs, and some of the plug-ins?
Describe alternatives you've considered
This may provide greater assurance of the provenance of our packages on npm.
The text was updated successfully, but these errors were encountered: