Merging prerelease/2025.03 to main #6558
Closed
Conversation
This file contains 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
v0.1.169 fixes a deadlock when starting reticulate sessions. It would be great to get it included in 2025.03 release. See: posit-dev/ark#728
Update `product.json` to provide the most recent release of each bootstrapped extension we're providing. Otherwise, when users have AutoUpdate enabled, at first launch, Positron will do two back-to-back installs. This was causing issues with our automation that required skipping the Problems tests in #6537 ### QA Notes @:problems
… than the application directory (#6554) @midleman and @testlabauto reported that their tests relying on extensions were failing locally. This is because the bootstrapped extension feature was saving `.version` to the application folder rather than the user's extension folder, causing the bootstrapped extensions to only be installed for the first user that launched the application. Because the tests use a temporary user data directory per run, the extensions would not be installed on subsequent runs. This would've prevented extensions from being installed for multiple users on Workbench as well. We now create, look for, and update `.version` in the user's extension directory rather that the application directory. In the implementation, `storageFilePath` was unnecessarily being declared as a class member so I fixed that as well.
|
E2E Tests 🚀 |
petetronic
changed the title
|
I have another change I'd like to merge from the prerelease branch into main if we're okay to wait for CI on #6552 and bring that change here! |
|
An update that #6552 CI checks are green and it's ready to merge. #6552 is targeted to the |
petetronic
force-pushed
the
prerelease/2025.03
branch
from
b9ab841 to
f7be371
Compare
|
I'm going to close this as I want to resolve the failure I'm seeing first. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Capturing any work done on the prerelease/2025.03 branch to main.
Ignoring the ark bump as main had since moved to v0.1.170.
It looked like QA's changes were duplicated to main already on #6522, so it ended up being a no-op, but probably best to merge the history rather than re-do on main in future.