Repository navigation
Conversation
…ependent authentication
GitHub Actions Integration
✅ All 1 passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👋 Background
Package producers and consumers need CodeArtifact credentials regardless of whether they use uv, Poetry, npm, pnpm, Yarn, Maven, or Gradle. This action provides the shared authentication step after the caller configures AWS credentials.
⚙️ Description
aws.codeartifact.configure-credentialsforpypi,npm, andmavenendpoints using Bash and the existing AWS CLI.0(the remaining assumed-role session lifetime), with support for explicit durations of 900–43200 seconds.CODEARTIFACT_AUTH_TOKENandCODEARTIFACT_REPOSITORY_ENDPOINTfor subsequent steps only after both API calls succeed. Expose the endpoint as an action output; never expose the token as an action output.🚨 To Reviewers
Validation completed locally: 35 regression scenarios across four test methods, ShellCheck, actionlint, GitHub action/workflow JSON schemas, and
git diff --check.CI verifies the actual composite environment/output wiring on Linux amd64 and arm64. No live AWS API or package publishing test has been performed.