Blender Dev 1.0.0-beta.3

Released: 2026-08-16

Beta 3 completes the V1 runtime-authentication gate and strengthens release readiness across managed installations, IDE compatibility, and contributor validation. Runtime commands, setup messages, and early failure reports now share an authenticated protocol with bounded, validated request handling.

Managed installations now honor post-install archive cleanup, Plugin Verifier covers both declared PyCharm targets, and the project’s Python requirement matches Blender 4.2’s bundled runtime. Repeatable Kotlin formatting and expanded release validation make the remaining V1 risks explicit and reproducible.

Added

• Added persisted ownership metadata that distinguishes user-managed Blender installations from installations managed by the plugin, while treating installations saved by earlier versions as user-managed.
• Added Plugin Verifier coverage for the declared PyCharm 2026.1 and 2026.2 targets.
• Added a V1 release-readiness audit covering release blockers, security risks, stability issues, and validation results.
• Added repeatable Kotlin and Gradle Kotlin formatting through Spotless and ktfmt, with a two-space block indent, 140-column limit, and spotlessCheck validation task.

Changed

• Standardized plugin diagnostics around typed error factories while keeping developer logging separate from user-facing notifications.
• Moved Ruff configuration to .ruff.toml with explicit Python-version, formatting, linting, and vendored-file exclusions.
• Restricted generated Marketplace change notes to the current release section.
• Standardized MessageBundle.properties keys across notifications, run configurations, and UI labels.

Fixed

• Fixed Perform post-install cleanup? so successful managed Blender installations remove their downloaded archives when enabled while preserving archives after failed installations or when cleanup is disabled.
• Fixed generated starter Python scripts so both minimal and example-code projects contain a correctly indented registration call.
• Fixed plugin compatibility metadata to depend on the bundled PythonCore plugin directly, allowing Plugin Verifier to resolve the Python APIs used by the plugin on every declared target.
• Isolated JVM platform tests from unrelated bundled IDE plugins, eliminating environment-dependent fixture shutdown failures.
• Replaced deprecated IntelliJ renderer and Kotlin JVM-default compatibility paths used by the plugin.
• Aligned the root Python requirement with Blender 4.2’s bundled Python baseline by lowering it from 3.14 to 3.11.7.

Security

• Finalized per-launch HMAC-SHA-256 authentication for runtime commands, setup messages, and early bootstrap or dependency failures, with exact-body signing, bounded JSON requests, schema validation, replay and cross-session rejection, distinct HTTP failure responses, and authentication-key cleanup. Localhost traffic remains unencrypted; HMAC provides authenticity and integrity, not confidentiality.

Known Issues

• Managed Blender archives are not yet verified against published checksums before extraction.
• Project-template values are not yet escaped specifically for TOML and Python output formats.
• Runtime actions still target the most recently registered Blender session when multiple sessions are active.
• Several visible cache, stub-path, and logging-path settings are persisted but not yet applied at runtime.
• Replacing an installed Blender API stub package is not transactional if installation of the new package fails.