Skip to content

Bump version to 2.3.2-dev#183

Closed
gaborbernat wants to merge 1 commit into
mainfrom
post-release-v2.3.1
Closed

Bump version to 2.3.2-dev#183
gaborbernat wants to merge 1 commit into
mainfrom
post-release-v2.3.1

Conversation

@gaborbernat

Copy link
Copy Markdown
Member

Post-release version bump after v2.3.1 release.

@gaborbernat

Copy link
Copy Markdown
Member Author

Superseded by #184, which bumps to 2.3.2-dev alongside the 261 compatibility cap.

@gaborbernat gaborbernat deleted the post-release-v2.3.1 branch May 29, 2026 04:30
gaborbernat added a commit that referenced this pull request May 29, 2026
The published `2.3.1` ships with an open `untilBuild`, so the JetBrains
Marketplace serves it to IntelliJ Platform `262` (2026.2). There it is
binary incompatible and fails at runtime with `NoSuchMethodError` and
`NoSuchClassError`, because build `262` reshaped several Python SDK
entry points the plugin depends on. The `UvSdkAdditionalData`
constructor now takes `String?` paths instead of `Path?`,
`VirtualEnvSdkFlavor.getInstance()` moved to
`com.intellij.python.venv.sdk.flavors`,
`PythonSdkUtil.isVirtualEnv(String)` is gone, and the uv icons moved to
`com.intellij.python.uv.common.icons`.

Capping `untilBuild` at `261.*` keeps the `2.3.x` line scoped to the
`2026.1` API it was compiled against, so the Marketplace stops offering
it to `2026.2`. 🔒 Full `262` support arrives separately on the `2.4.x`
line, which lets both compatibility ranges live side by side on the
Marketplace.

This also bumps the development version to `2.3.2-dev` and supersedes
the automated post-release bump in #183.
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.

2 participants