Repository navigation
chore: prepare 3.4.0 release - #1928
Conversation
renkun-ken
left a comment
There was a problem hiding this comment.
The version bump and compatibility requirement look consistent. I have two suggestions for the release notes below.
The first Windows CI attempt failed in test:prepare-jgd with permission denied while reading startup.status; a retry is in progress. Please confirm the Windows check passes before tagging, since the release workflow also requires verification.
renkun-ken
left a comment
There was a problem hiding this comment.
The updated notes address both of my earlier suggestions, including the 3.2.2 backport comparison. The version checks and all six CI checks pass on this revision.
One follow-up for release reliability: Windows failed twice in test:prepare-jgd while reading startup.status with permission denied before passing on the third attempt; the first Linux attempt also failed the terminal readiness timeout test before passing on retry. These tests are unchanged by this PR, but the tag-triggered release runs verification again, so it would be useful to track the intermittent failures separately.
|
Thanks for the review. |
Prepare the 3.4.0 stable release by setting both the extension and bundled
sessversions to 3.4.0. Finalize the changelog under3.4.0 - 2026-11-09, covering the VS Code minimum version, managed jgd/rstudioapi installation, and a brief summary of user-visible performance and reliability improvements.Record the published 3.2.2 hotfix release separately and compare 3.4.0 with v3.2.2. Note that the comparison still includes #1911 because 3.2.2 was released from a backport branch.
Reviewed the 3.2.0 release preparation PRs (#1869, #1873, #1875). No lockfile changes are needed.