Repository navigation
Prepare JavaScript 0.3.2 metadata and release notes - #17
Merged
Merged
Conversation
mikkel
marked this pull request as ready for review
November 9, 2026 04:44
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 JavaScript package metadata for 0.3.2 after the state fixes merged in #16. The official npm registry still publishes 0.3.1, so this is a new unreleased version; no npm publication is included.
Update package.json and both package-lock version fields together. Add release notes for incomplete-completion errors, coordinated cache writes, the persistent .lock/ sidecar, and unchanged v1 cache JSON. Document separate cache files while old npm/Python writers remain. Move the verified published 0.3.1 history under its registry publication date; the actual npm artifact comes from b8b7936, and draft #15 remains NOT FOR MERGE.
Validation: full offline suite 274 passed / 4 live tests skipped, including actual JS/Python cache overlap; types, release guard and diff checks passed; deterministic benchmark 135 file patches / zero silent wrong applies; npm pack dry run identifies version 0.3.2 and 19 packaged files.
The commit and eventual merge must begin with [CF-Pages-Skip]. The GitHub workflow contains validation only and no npm publishing job. Cloudflare production must remain at b8b7936; GitHub CI remains enabled. This draft's exact head must be routed through Ada before merge under the standing workflow.
Related merged fixes: #16, 255BITS/patchling-py#34 and 255BITS/patchling-examples#6.