Repository navigation
Release 0.13.0 - #111
Merged
Merged
Release 0.13.0#111
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.
Summary
Prepare posthtml-parser 0.13.0 for npm publication, including the changes merged in #109 and #110.
0.13.0 (2026-10-28)and leave a freshUnreleasedsection.The release includes htmlparser2 12, directive/XML/SVG compatibility fixes, simplified native Node.js testing and TypeScript builds, refreshed documentation and maintainer contact information.
Verification
npm cisucceeds.npm publish --dry-run --jsonsucceeds for posthtml-parser@0.13.0, including the realprepublishOnlycheck and package preparation lifecycle.npm audit: 0 vulnerabilities.npm packproduces the expected nine package files, including JavaScript, declarations, source maps, metadata, README and license.Compatibility
This is a breaking 0.x release:
^20.19.0 || >=22.12.0.decodeEntities: true, entities in textarea content are now decoded consistently with other text content.After merging this release PR, tag the tested master commit as
v0.13.0and publish that checkout to npm.