Repository navigation
Release v6.2.0 - #56
Merged
Merged
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
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 Scratch for Java 6.2.0 with portable
SaveData<T>and the three-slot Coin Quest demo. Desktop games save JSON in the platform user-data directory; the online IDE uses IndexedDB through the same API. Missing slots use supplied defaults, while malformed data and failed writes report errors and preserve the previous save.The demo uses built-in assets and persists score and sprite positions. The launcher now checks compilation before starting a demo, fixing
ClassNotFoundExceptionwith older compiled classes.The release updates the version, changelog, compatibility artifacts and catalogs. The matching browser metadata is committed to online-ide at 782b9413, with runtime
6.2.0-browser.1. Documentation explicitly loads embedded build 31, which includes SaveData support.Validation: library tests and visual checks passed on the feature commit; generated compatibility/catalog freshness and strict parity checks passed against the release branch; all 416 browser compatibility/catalog tests passed locally; documentation builds with the pinned runtime. The final release-branch checks and embedded release/CDN workflows must succeed before merging.