ci(release): drop setup-gradle from the publish job - #53
Merged
Merged
Conversation
It was the last one left in any workflow, and it restored a cache nothing writes: ci.yml removed its own copies, and this one carried cache-read-only: true. The reason ci.yml gave applies here too -- a warm GRADLE_USER_HOME for this project is ~31 GB against a 10 GB per-repository cache ceiling, so the action could never store what it appeared to store. Nothing else is lost: the job runs ./gradlew --no-daemon, which needs no setup from the action, and setup-java still provides the JDK since this job does not run in the CI container. The cost, paid knowingly, is a cold download of the IntelliJ platform artifacts on every release -- a few minutes, a few times a month, against a cache that was not working. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…tup-gradle ci(release): drop setup-gradle from the publish job
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Carries the CI-only change to
mainso the next release runs the correctedrelease.yml.What
Removes the last
gradle/actions/setup-gradlein any workflow —release.yml's publish job. It carriedcache-read-only: true, and afterci.ymldropped its own copies nothing writes that cache, so the step restored an entry no job produces. Same reasonci.ymlrecorded: a warmGRADLE_USER_HOMEhere is ~31 GB against a 10 GB per-repository cache ceiling.actions/setup-javastays — this job does not run in the CI container, so it is what provides the JDK.No publication results from this merge
release.ymlfires on this push, butguardwill seev5.1.1already on the remote for the version inbuild.gradle.ktsand correctly decide it is already released, so the publish job does not run. This merge only positions the corrected workflow for the next release.No plugin code, tests or resources are touched: one file,
.github/workflows/release.yml.🤖 Generated with Claude Code