[posquit0]

👋 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

• Add aws.codeartifact.configure-credentials for all CodeArtifact endpoint formats (cargo, generic, maven, npm, nuget, pypi, ruby, and swift) using Bash and the existing AWS CLI.
• Require explicit region, domain, repository, and format. The domain owner is optional for same-account access and is passed to AWS only when provided. Default token duration to 0 (the remaining assumed-role session lifetime), with support for explicit durations of 900–43200 seconds.
• Mask the token and export CODEARTIFACT_AUTH_TOKEN and CODEARTIFACT_REPOSITORY_ENDPOINT for subsequent steps only after both API calls succeed. Expose the endpoint as an action output; never expose the token as an action output.
• Document IAM prerequisites, OIDC/role chaining, and package-manager-specific use. Package manager configuration remains with the caller.
• Include locally runnable regression tests with a mocked AWS CLI.

🚨 To Reviewers

Validation: 51 local regression scenarios across five test methods, covering all eight formats and omitted, empty, and explicit domain owners; ShellCheck; GitHub action JSON schema; and git diff --check. The regression suite can be run locally with the README command.

No live AWS API or package publishing test has been performed.

[github-actions]

GitHub Actions Integration

Repository	jactionlint	check-jsonschema (workflows)	check-jsonschema (actions)
tedilabs/github-actions	✅	✅	✅

✅ All 1 passed.