Release 20.5.0 - #1669
Merged
Merged
Release 20.5.0#1669
Conversation
Date the changelog, and bump the Claude plugin manifest to match. The manifest carries its own version and is consumed from the repository rather than the npm tarball, so nothing keeps it in step with the engine automatically — `release.ts` only ever reads versions. It was still on 20.4.0, which `assertPluginManifestVersion` would have caught only after `npm publish` had already run, leaving the package on npm with no tag and no GitHub release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NGvtaUNATVCVxD2qcbiY4t
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.
Dates the 20.5.0 changelog entry and bumps the Claude plugin manifest to match the engine.
The manifest bump is load-bearing
.claude-plugin/plugin.jsonwas still on20.4.0. It carries its own version and is consumed from the repository rather than the npm tarball, so nothing keeps it in step with the engine —release.tsonly ever reads versions, it never writes them.assertPluginManifestVersionwould have caught the drift, but it runs inside the Create GitHub release step, which comes afternpm publishinpublish.yml. The failure mode was therefore: 20.5.0 lands on npm, then the workflow goes red, leaving the release with no tag and no GitHub release entry.What ships in 20.5.0
Nine commits since
20.4.0— mesh-hostedShaderEffect,GLTFModelplacement, Text gradient fills,Camera.roll, and a batch of 3D-reachability and typings fixes. Full detail in the changelog.After merge
Tag and GitHub release are both created by
release.tsfrom the workflow, so the remaining step is dispatchingpublish.ymlwithpackage=melonjs.🤖 Generated with Claude Code
https://claude.ai/code/session_01NGvtaUNATVCVxD2qcbiY4t