Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt the newly GA npm provenance feature #1812

Closed
adam-wolfe opened this issue Sep 28, 2023 · 2 comments
Closed

Adopt the newly GA npm provenance feature #1812

adam-wolfe opened this issue Sep 28, 2023 · 2 comments
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits

Comments

@adam-wolfe
Copy link
Contributor

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.

@adam-wolfe adam-wolfe added enhancement New feature or request new The issue wasn't triaged yet labels Sep 28, 2023
@github-actions
Copy link

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.

@awharn
Copy link
Member

awharn commented Sep 28, 2023

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.

@zFernand0 zFernand0 added priority-medium Not functioning - next quarter if capacity permits and removed new The issue wasn't triaged yet labels Oct 16, 2023
@t1m0thyj t1m0thyj moved this to Medium Priority in Zowe CLI Squad Dec 26, 2023
@adam-wolfe adam-wolfe closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
@github-project-automation github-project-automation bot moved this from Medium Priority to Closed in Zowe CLI Squad Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Projects
None yet
Development

No branches or pull requests

3 participants