Repository navigation
chore(release): prepare moly 0.0.5 - #11
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.
Prepare moly 0.0.5 from the current master after the JP 7.0.0 work merged. The reviewed Chinese release notes cover native Luau plugins and scripted companions, hierarchical NPCs and cross-group talks, road/weather editing and scrolling, bulk hammer harvesting, the independent stage, text overlays, open fonts, and the Bevy upgrade.
Align all 24 workspace crates and Cargo.lock, the MCP package and server version, and the example plugins' minimum supported version. Keep an English CHANGELOG section and a curated
release-notes/v0.0.5.md, which the existing release workflow uses for a version tag.Validation: workspace version check, JavaScript syntax, public-source boundary check and whitespace checks passed. The maintainer has accepted the editor and harvest interactions through hands-on use. A manual Release workflow builds the 0.0.5 native and separate stage/game WASM candidate archives; it does not create or publish a GitHub release.
This preparation does not merge the separate community translation service, claim production JP 7 resources are live, or include unmerged gameplay PRs.