ReactUSWDS Version & USWDS Version
N/A
Describe the bug
For quite some time, our packages have not been getting published to GitHub Packages:
https://github.com/orgs/trussworks/packages/npm/package/react-uswds
The workflow responsible for this is here: https://github.com/trussworks/react-uswds/actions/workflows/publish-next.yml
The failed jobs indicate attempts to publish that fail due to ➤ YN0033: No authentication configured for request
The successful jobs just skip the publish step due to YN0000: Registry already knows about version <X.X.X>; skipping.
So this workflow is not publishing at all anymore.
Expected behavior
Merges to main should publish to GitHub packages successfully.
Screenshots
Additional context
Without having found confirmation, it looks like the GITHUB_TOKEN we were using to is no longer valid for publishing. Instead, GitHub says:
GitHub Packages only supports authentication using a personal access token (classic).
At one point, this was working, so I can only assume this was a GitHub security change.
Device and Browser Information (please complete the following information if describing a UI bug)
N/A
ReactUSWDS Version & USWDS Version
N/A
Describe the bug
For quite some time, our packages have not been getting published to GitHub Packages:
https://github.com/orgs/trussworks/packages/npm/package/react-uswds
The workflow responsible for this is here: https://github.com/trussworks/react-uswds/actions/workflows/publish-next.yml
The failed jobs indicate attempts to publish that fail due to
➤ YN0033: No authentication configured for requestThe successful jobs just skip the publish step due to
YN0000: Registry already knows about version <X.X.X>; skipping.So this workflow is not publishing at all anymore.
Expected behavior
Merges to main should publish to GitHub packages successfully.
Screenshots
Additional context
Without having found confirmation, it looks like the
GITHUB_TOKENwe were using to is no longer valid for publishing. Instead, GitHub says:At one point, this was working, so I can only assume this was a GitHub security change.
Device and Browser Information (please complete the following information if describing a UI bug)
N/A