Skip to content

Commit

Permalink
Bump version to v1.5.0 and update changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
hlysine committed Aug 20, 2023
1 parent d947b72 commit 741b2c5
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 1 deletion.
17 changes: 17 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,22 @@ All notable changes to this project will be documented in this file.
The format is loosely based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.5.0] - 2023-08-20

### Added

- Exports for helper types used to compose token types
- Export for the `RegExpToken` interface
- **Custom tokens API** via `defineToken`
- Support for merging nested character groups
- `charRange` and `notCharRange` tokens

### Changed

- `group` no longer wraps expressions with extra layers of non-capture groups if the expression is already grouped
- Fixed incorrect escapes of backslashes and dashes in character groups
- Moved documentation from README to Gitbook for better organization

## [1.4.0] - 2023-08-19

### Added
Expand Down Expand Up @@ -107,3 +123,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
[1.3.3]: https://github.com/hlysine/readable-regexp/releases/tag/v1.3.3
[1.3.4]: https://github.com/hlysine/readable-regexp/releases/tag/v1.3.4
[1.4.0]: https://github.com/hlysine/readable-regexp/releases/tag/v1.4.0
[1.5.0]: https://github.com/hlysine/readable-regexp/releases/tag/v1.5.0
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "readable-regexp",
"version": "1.4.0",
"version": "1.5.0",
"author": "Henry Lin",
"license": "MIT",
"description": "Regular Expressions - quick and concise, readable and composable.",
Expand Down

0 comments on commit 741b2c5

Please sign in to comment.