Skip to content

Commit

Permalink
[ci] release
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored and DylanPiercey committed Mar 15, 2023
1 parent 085451c commit b105718
Show file tree
Hide file tree
Showing 5 changed files with 11 additions and 13 deletions.
5 changes: 0 additions & 5 deletions .changeset/strong-deers-complain.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/tall-moons-enjoy.md

This file was deleted.

8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# htmljs-parser

## 5.4.3

### Patch Changes

- [#161](https://github.com/marko-js/htmljs-parser/pull/161) [`be73442`](https://github.com/marko-js/htmljs-parser/commit/be734429cc67b87a21a6a0c8880da64a3475d03e) Thanks [@DylanPiercey](https://github.com/DylanPiercey)! - Fixes a regression where the parsed text state (used by eg `script`, `style`) was not properly entering back into text for the closing quote on the string.

- [#162](https://github.com/marko-js/htmljs-parser/pull/162) [`085451c`](https://github.com/marko-js/htmljs-parser/commit/085451cc574b56ce6689f2168a9eed1bd0f0b0e6) Thanks [@DylanPiercey](https://github.com/DylanPiercey)! - Always consume next character of expression if terminator was preceded by an operator.

## 5.4.2

### Patch Changes
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "htmljs-parser",
"description": "An HTML parser recognizes content and string placeholders and allows JavaScript expressions as attribute values",
"version": "5.4.2",
"version": "5.4.3",
"devDependencies": {
"@changesets/changelog-github": "^0.4.7",
"@changesets/cli": "^2.25.2",
Expand Down

0 comments on commit b105718

Please sign in to comment.