chains-project/Maven-Lockfile
This action generates a lockfile for a Maven project.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token | yes | — |
| commit-lockfile | Commit the lockfile to the repository in case the pom.xml or workflow file has updated. If this is false or the pom.xml and workflow.yml files are unchanged the action will verify the current lockfile.json. | no | true |
| commit-message | Commit message for the lockfile | no | chore: update lockfile |
| include-maven-plugins | Include Maven plugins in the lockfile | no | true |
| lockfile-name | Name of the lockfile (default="lockfile.json") | no | lockfile.json |
| workflow-filename | Name of the workflow file | no | Lockfile.yml |
| skip-older-regeneration | Skip lockfile regeneration if the existing lockfile was generated by a newer plugin version than this action. Useful to avoid unnecessary commits after a release. | no | true |
| allow-environmental-validation-failure | Allow environmental validation failures (e.g. Maven version changes between runner image updates) to produce a warning instead of failing the build. Recommended when using GitHub-hosted runners where the Maven version is not pinned. See https://github.com/chains-project/maven-lockfile/issues/1583. | no | true |
Outputs
no outputs