Release 0.20.18 - #205
Merged
Merged
Release 0.20.18#205
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release 0.20.18 with the three reviewed feedback fixes merged in #201, #203 and #204: preserve source filenames in Canvas downloads, open local chat file references safely in Canvas, and retain saved provider endpoints with atomic, sanitized preparation failures. Provider isolation remains explicitly incomplete in #182.
Versions, release notes, lock metadata and committed frontend assets match. The production frontend build is reproducible, all 334 frontend tests pass, the distributions pass package verification, and focused backend/browser checks cover the changes. The complete Python suite is running locally as additional coverage; its final result will be recorded separately and is not a publication gate under the current development policy. Automatic publication retains package, frontend and runtime qualification; full Python/browser CI remains opt-in.
PR202 remains draft for its owner's user review. Quiet observation work and broader paused investigations are not included. Spark-1 stays on the published-release update path.