Release version 1.2.0

CHANGELOG.md

@@ -6,9 +6,18 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ## [Unreleased]
 
+## [1.2.0] - 2024-01-01
+
 - feat: new option --json to format output as JSON array
-- fix: field formatting is now applied to field 1 even if it's the only
-       one present and with no delimiters around
+- feat: -r can be used when cutting --characters. It replaces
+  the (empty) delimiter between characters with whatever you provided
+- feat: exit early when some combinations of fields cannot be used together
+- feat: updated dependencies. In particular the regex crate which offers new
+  functionalities (word boundary assertions)
+- fix: field formatting is now applied to field 1 even if no delimiters
+  are found (similar to how we print the unformatted field 1)
+- doc: many error messages have been rewritten for better clarity
+- doc: new svg demo in the README
 
 ## [1.1.0] - 2023-12-02
 

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "tuc"
 description = "When cut doesn't cut it"
-version = "1.1.0"
+version = "1.2.0"
 authors = ["Riccardo Attilio Galli <[email protected]>"]
 edition = "2018"
 homepage = "https://github.com/riquito/tuc"

README.md

@@ -32,7 +32,7 @@ No time to install it? Play with a webassembly version online, the [tuc playgrou
 ## Help
 
 ```
-tuc 1.1.0
+tuc 1.2.0
 Cut text (or bytes) where a delimiter matches, then keep the desired parts.
 
 The data is read from standard input.

doc/tuc.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "tuc" "1" "Dec 02, 2023" "Tuc 1.1.0" "Tuc Manual"
+.TH "tuc" "1" "Jan 01, 2024" "Tuc 1.2.0" "Tuc Manual"
 .hy
 .SH NAME
 .PP

doc/tuc.1.md

@@ -1,6 +1,6 @@
-% tuc(1) Tuc 1.1.0 | Tuc Manual
+% tuc(1) Tuc 1.2.0 | Tuc Manual
 %
-% Dec 02, 2023
+% Jan 01, 2024
 
 NAME
 ====