Skip to content

ci(release): release through a release PR, with change notes on both variants - #140

Merged
roxblnfk merged 2 commits into
mainfrom
release/2026.17
Oct 22, 2026
Merged

roxblnfk merged 2 commits into
mainfrom
release/2026.17

Conversation

@roxblnfk

@roxblnfk roxblnfk commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

🔍 What was changed

  • Releases go through a release PR, as in release-please: every push to main rebuilds release: <next> from release/next with the bumped pluginVersion and [Unreleased] moved into ## [<next>]. Merging it tags v<next> and creates the GitHub release, which runs release.yml. The draft releases and the Changelog update PR after publishing are gone.
  • The next version is computed: <year>.<N+1>, or <year>.0 in a new year. A pluginVersion without a changelog section yet is released as is, so the first release PR here is release: 2026.17.
  • No release PR while [Unreleased] is empty.
  • Both Marketplace uploads (.252 / .262) carry change notes from the bare-version section; until now none were generated.

How it works

  • Release PR job runs last in build.yml, on main only, after build / test / Qodana / verify are green.
  • The release PR is opened by GITHUB_TOKEN, so no checks run on it; it only touches gradle.properties and CHANGELOG.md.

Review notes

  • pluginVersion is bumped to 2026.17 by hand here once: main has no ## [2026.16] section (only [2026.16.262]), so without it the job would offer to release 2026.16, which the Marketplace already has.
  • After merge, delete the stale draft 2026.16.262 by hand.

Checklist

  • How was this tested:
    • getChangelog / patchChangelog steps of the job run locally (changelog reverted afterwards)
    • next-version arithmetic: 2026.17→2026.18, 2026.9→2026.10, 2026.17→2027.0 in 2027
    • patchPluginXml for 252 and 262: <change-notes> filled in both
    • buildPlugin (262)
    • the workflow itself — first run on main after merge

…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>
@github-actions

Copy link
Copy Markdown
Contributor

Qodana for JVM

It 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 report

To be able to view the detailed Qodana report, you can either:

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.2.2
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

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 roxblnfk changed the title ci(release): release 2026.17 through CI with change notes on both variants ci(release): release through a release PR, with change notes on both variants Oct 22, 2026
@roxblnfk
roxblnfk merged commit c577965 into main Oct 22, 2026
8 checks passed
@roxblnfk
roxblnfk deleted the release/2026.17 branch October 22, 2026 06:49
roxblnfk added a commit that referenced this pull request Oct 22, 2026
…variants (#140)

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant