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

ci(github): fix Can't generate provenance for new or private package #3667

Open
petermetz opened this issue Dec 2, 2024 · 2 comments
Open
Assignees
Labels
bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved)
Milestone

Comments

@petermetz
Copy link
Contributor

Description

The publish job for nodejs packages failed again because private packages are present in the repository. It doesn't make sense to have private packages because everything is open source with an apache 2.0 licence anyway.

2024-12-02T17-20-58-nodejs-package-publish-crash-private-pkg-vs-provenance.log

Acceptance Criteria

  1. All private packages were marked as public.
@petermetz petermetz added bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved) labels Dec 2, 2024
@petermetz petermetz added this to the v2.2.0 milestone Dec 2, 2024
@petermetz petermetz self-assigned this Dec 2, 2024
@jagpreetsinghsasan
Copy link
Contributor

@adrianbatuto will you like to work on this one?

@adrianbatuto
Copy link
Contributor

@adrianbatuto will you like to work on this one?

Sure @jagpreetsinghsasan. I can work on this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved)
Projects
None yet
Development

No branches or pull requests

3 participants