Skip to content

chore: prepare next development version #252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ruromero merged 1 commit into from
Apr 14, 2026
Merged

chore: prepare next development version #252

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion gradle.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
projectVersion=1.3.0
projectVersion=1.4.0-SNAPSHOT

@qodo-code-review qodo-code-review Bot Apr 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Release zip version mismatch 🐞 Bug ☼ Reliability

With projectVersion now set to 1.4.0-SNAPSHOT, the tag-driven release workflow runs buildPlugin
without passing -PprojectVersion from the tag, so the built plugin version may not match the tag.
This can cause the workflow to fail when uploading the expected tag-named ZIP from
build/distributions.
Agent Prompt 
### Issue description
The release workflow builds the plugin without forcing `projectVersion` to match the git tag, but later uploads an asset whose path/name is derived from the tag.

### Issue Context
`build.gradle.kts` sets `version` from the `projectVersion` Gradle property (from `gradle.properties` unless overridden). After this PR, that value is `*-SNAPSHOT`, which can diverge from the release tag.

### Fix Focus Areas
- /.github/workflows/release.yml[19-24]
- /build.gradle.kts[12-14]

### Suggested change
In `release.yml`, pass `-PprojectVersion=${{ steps.get_version.outputs.VERSION }}` to the `./gradlew buildPlugin` invocation (so the produced plugin/artifact version matches the tag used for the release asset name/path).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

jetBrainsToken=invalid
jetBrainsChannel=stable

Expand Down
Loading