mirror of
https://github.com/gradle/actions.git
synced 2026-06-11 06:00:40 +00:00
Björn Kautler
a740661292
This PR adds a missing enum value, and makes strings that are actually
delimited lists those lists, so that you for example in the generated
Kotlin bindings can simply do
```kotlin
additionalArguments = listOf(
"--info",
"--stacktrace",
"--show-version"
)
```
instead of needing to do
```kotlin
additionalArguments = listOf(
"--info",
"--stacktrace",
"--show-version"
).joinToString(" ")
```
or writing it all in one line as one string.
This is also how the typings for older versions are in the typing
catalog.
Theoretically, this is a breaking changes as the typings define the API
surface of the action and from the typings bindings are generated. I'll
leave it up to you how you handle it regarding version increase or when
to merge.
The wrapper-validation action
The wrapper-validation action validates the checksums of all Gradle Wrapper JAR files present in the repository and fails if any unknown Gradle Wrapper JAR files are found.
The action should be run in the root of the repository, as it will recursively search for any files named gradle-wrapper.jar.
Note
Starting with v4 the
setup-gradleaction will automatically perform wrapper validation on each execution.If you are using
setup-gradlein your workflows, it is unlikely that you will need to use thewrapper-validationaction.
Example workflow
name: "Validate Gradle Wrapper"
on:
push:
pull_request:
jobs:
validation:
name: "Validation"
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
- uses: gradle/actions/wrapper-validation@v6
See the full action documentation for more advanced usage scenarios.