actions-marketplace-validations/action-monorepo-version-tags-lifecycle
Generate version tags on a monorepo with multiple components
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| mode | Execution mode can be "product" "component" | yes | — |
| type | Execution type can be "pre-release" "release" "fix" "final" "new-release-branch" | yes | — |
| current-tag | Current tag of a component, e.g. "component-v0.4.0". | no | v0.0.0 |
| current-major | Current major version of the product. | no | 0 |
| component-prefix | Component prefix, e.g. "component1-". | no | — |
| release-branch-prefix | Release branch prefix, e.g. "release/v". | no | — |
| pre-release-name | A pre release name, e.g. "alpha" or "rc" | no | — |
| tag-branch | Branch to create a version tag, e.g. "main" | no | main |
| update-versions-in | String representation of an array of objects with file/property keys. If provided the action will update those files/properties with the version that is being released. | no | false |
| use-tag-in-versions-file | If true, use the tag when updating the versions file. If false use the version instead. | no | false |
| commit-message | The message in the commit for version updates. | no | Update version file [skip-ci] |
| commit-author | The author for the commit in the version updates. | no | Tagger Action |
| commit-author-email | The author email for the commit in the version updates. | no | no-reply-tagger-action@igz.es |
| dry-run | Enable dry run mode, e.g. "true" or "false" | no | false |
Outputs
| name | description |
|---|---|
| tag | The new version tag that was created |
| version | The new version tag that was created |