Is there an existing issue for this?
Package ecosystem
Gradle
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
What I expected to see: A clean upgrade.
What I saw:
- The updated
./.gradlew has its permissions downgraded from 755 to 644 and our builds fail.
- Additionally, it would also appear that the line endings of the
gradlew.bat file are changed
Native package manager behavior
The "normal" way of upgrading gradle is running ./.gradlew wrapper --gradle-version xxx which takes care of everything. I suspect that some other approach is being used here.
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
Is there an existing issue for this?
Package ecosystem
Gradle
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
What I expected to see: A clean upgrade.
What I saw:
./.gradlewhas its permissions downgraded from 755 to 644 and our builds fail.gradlew.batfile are changedNative package manager behavior
The "normal" way of upgrading gradle is running
./.gradlew wrapper --gradle-version xxxwhich takes care of everything. I suspect that some other approach is being used here.Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response