Our workflows are all failing intermittently due to Unauthorized (401)

[LucasDreyerSanlam]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

We have workflows which pull internal dependencies (Java packages) that are published by other Github projects to Github's Maven central (maven.pkg.github.com)

Our builds work locally (even after deleting the local Maven repo), and fail intermittently in our PR and merge pipelines. Each pipeline repeats the build process several times (e.g. one for unit tests and one for integration tests). Sometimes one passes and the other fails, but given the high failure probability, there's always at least one that fails.

This has been blocking our PR and merge pipelines for almost 24h.

Error from the actions runner:

Error:  	Caused by: The following artifacts could not be resolved: a.b.c:pom:0.0.6 (absent): Could not transfer artifact a.b.c:pom:0.0.6 from/to abc (https://maven.pkg.github.com/a/b): status code: 401, reason phrase: Unauthorized (401)
Error:  

The 401 is misleading, because it's intermittent and our Github API tokens haven't changed. Maybe the runner is internally being given the wrong token, or maybe the Github auth server is broken.

We saw the exact same behaviour two weeks ago during https://www.githubstatus.com/incidents/2fk03fzv6zk0, implying the same problem has reoccured.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[jannikrichter]

Same here, quite frustrating

[stianjensen]

Seeing an increase in this behavior the past 3 days.