agilecustoms/Consistent Release
Secure, repeatable releases to AWS and npm with semantic versioning, self-service releases and multi‑artifact support
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit May 31, 2026
- License
- MIT
Pinned Snippet
uses: agilecustoms/release@339dfe41cd1c8756b27d65c2c8a078d8e3189a8b # v5.3.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| aws-account | AWS account to publish artifacts to. Not needed if there are no artifacts, just git tag | no | — |
| aws-region | AWS region | no | — |
| aws-role | IAM role to assume to publish, e.g., `ci/publisher` | no | — |
| aws-codeartifact-domain | CodeArtifact domain name, e.g., `mycompany` | no | — |
| aws-codeartifact-repository | CodeArtifact repository name, e.g., `maven` | no | maven |
| aws-codeartifact-maven | Two possible values: build and publish. publish - publish maven artifacts to AWS CodeArtifact, build - just access CodeArtifact to update version in pom.xml | no | — |
| aws-ecr | If true, then push docker image to ECR | no | — |
| aws-s3-bucket | Required if uploading to S3 (i.e. s3/ directory exists) | no | — |
| aws-s3-dir | Allows you to specify S3 bucket directory to upload artifacts to. By default, just place in `bucket/{repo-name}/{version}/*` | no | — |
| changelog-file | Changelog file path. Pass empty string to disable changelog generation | no | CHANGELOG.md |
| changelog-title | Title of the changelog file (first line of the file) | no | # Changelog |
| dev-branch-prefix | Allows you to enforce branch prefix for dev-releases; this helps to write auto-disposal rules. Empty string disables enforcement | no | feature/ |
| dev-release | Allows you to create a temporary named release, mainly for dev testing. Implementation is different for all supported artifact types | no | false |
| floating-tags | When the next version to be released is 1.2.4, then also release 1, 1.2, and latest. Not desired for public terraform modules | no | true |
| java-cache | Enabled by default, specify empty string to disable caching | no | maven |
| java-cache-dependency-path | see https://github.com/actions/setup-java "cache-dependency-path" | no | — |
| java-distribution | Java distribution, use Temurin as it is pre-cached in ubuntu-latest | no | temurin |
| java-version | Java version to use | no | 21 |
| npm-publish | If true, then publish package to npmjs.com registry | no | false |
| npm-visibility | Used together with input `npm-publish`. Specifies package visibility: public or private | no | public |
| python-version | Python version. Not in use right now | no | 3.13 |
| pre-publish-script | Shell script that allows you to update version in custom file(s), not only files governed by build tool (pom.xml, package.json, etc) | no | — |
| release-branches | semantic-release "branches" configuration | no | — |
| release-channel | Repeat `.releaserc.json` `channel` behavior when set `version` explicitly | no | — |
| release-gh | If true, then create a GitHub release with the same name as the tag | no | true |
| release-plugins | semantic-release plugins configuration | no | — |
| summary | Text to print in step summary. Can use `${version}` placeholder. Default is `### Released ${version}`. Set empty string to omit summary generation | no | ### Released ${version} |
| tag-format | By default, the tag (version) has format `v1.0.0`. Use `${version}` to remove `v` prefix | no | — |
| update-version-in-manifest | Update version in language-specific manifest files (e.g., pom.xml, package.json, pyproject.toml) | no | true |
| version | Explicit version to use instead of auto-generation | no | — |
| version-bump | Allows you to bump a version without conventional commits | no | — |
Outputs
| name | description |
|---|---|
| version | Newly released version |