ci(release): auto-bump pluginVersion after publish#82
Merged
Conversation
After the plugin is published to Marketplace, count nightly tags between the previous release tag and the current one (each nightly represents one code change). Bump the BUILD segment of pluginVersion in gradle.properties by that count and roll the change into the existing post-release PR alongside the changelog patch. Requires fetch-depth: 0 on checkout so the version-bump step can walk tag history.
|
🔌 Plugin artifact ready for testing! Download from Actions artifacts Artifact: |
1 task
lukaszlenart
added a commit
that referenced
this pull request
Apr 28, 2026
Manual application of the post-release version-bump rule (#82) for the already-published v261.19017.1, which predates that automation. BUILD increased by 10 (count of nightly tags between v252.18980.1 and v261.19017.1).
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.
Summary
After the plugin is published to JetBrains Marketplace, automatically bump the
pluginVersioningradle.propertiesso the next release cycle starts from a fresh number.The
BUILDsegment is incremented by the number of nightly tags between the previous release tag and the just-released tag (each nightly = one code change).BRANCHandFIXare preserved.Worked example using
v261.19017.1(just released):v252.18980.1v261.19017.1's ancestry since then: 10pluginVersion:261.19027.1Notes
CHANGELOG.md). One PR per release cycle, with bothCHANGELOG.mdandgradle.propertieschanges — the PR is renamedPost-release ...: changelog + bump to ....fetch-depth: 0added to the checkout so the bump step cangit tag --merged/--no-mergedagainst history.+1so theBUILDalways advances, even if for some reason no nightlies are tagged in a cycle.v261.19017.1(which predates this workflow change).Test plan
Post-releasePR with bothCHANGELOG.mdpatch andgradle.propertiesbump