Repository navigation
ci(release): release through a release PR, with change notes on both variants - #140
Merged
Merged
Conversation
…nVersion chore(release): 2026.17 The changelog and the release draft took the project version, which carries the API suffix: the draft was tagged `2026.17.262`, and the 252 build looked for a `2026.17.252` section that never exists, so neither upload had change notes. Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.2.2
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
roxblnfk
force-pushed
the
release/2026.17
branch
from
October 22, 2026 05:48
5294a05 to
11c28cd
Compare
docs(claude): describe the release PR and the <year>.<N> version scheme Every push to main rebuilds a "release: <next>" pull request with the bumped pluginVersion and the patched changelog; merging it tags the version and creates the GitHub release that runs release.yml. The next version is always <year>.<N+1>, or <year>.0 in a new year, so nothing needs a human pick. Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
roxblnfk
force-pushed
the
release/2026.17
branch
from
October 22, 2026 05:49
11c28cd to
93dfcc2
Compare
roxblnfk
added a commit
that referenced
this pull request
Oct 22, 2026
…variants (#140) Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
🔍 What was changed
mainrebuildsrelease: <next>fromrelease/nextwith the bumpedpluginVersionand[Unreleased]moved into## [<next>]. Merging it tagsv<next>and creates the GitHub release, which runsrelease.yml. The draft releases and theChangelog updatePR after publishing are gone.<year>.<N+1>, or<year>.0in a new year. ApluginVersionwithout a changelog section yet is released as is, so the first release PR here isrelease: 2026.17.[Unreleased]is empty..252/.262) carry change notes from the bare-version section; until now none were generated.How it works
build.yml, onmainonly, after build / test / Qodana / verify are green.GITHUB_TOKEN, so no checks run on it; it only touchesgradle.propertiesandCHANGELOG.md.Review notes
pluginVersionis bumped to2026.17by hand here once:mainhas no## [2026.16]section (only[2026.16.262]), so without it the job would offer to release2026.16, which the Marketplace already has.2026.16.262by hand.Checklist
getChangelog/patchChangelogsteps of the job run locally (changelog reverted afterwards)2026.17→2026.18,2026.9→2026.10,2026.17→2027.0in 2027patchPluginXmlfor 252 and 262:<change-notes>filled in bothbuildPlugin(262)mainafter merge