chore: bump version to 0.11.0

Author: matteosacchetto

README.md

@@ -11,13 +11,13 @@ Simple Node.js CLI which allows you to create and extract zip/tar files with sup
 Install it locally with
 
 ```bash
-npm i https://github.com/matteosacchetto/node-zip-cli/releases/download/v0.10.1/node-zip-cli-0.10.1.tgz
+npm i https://github.com/matteosacchetto/node-zip-cli/releases/download/v0.11.0/node-zip-cli-0.11.0.tgz
 ```
 
 Or install it globally with
 
 ```bash
-npm i --location=global https://github.com/matteosacchetto/node-zip-cli/releases/download/v0.10.1/node-zip-cli-0.10.1.tgz
+npm i --location=global https://github.com/matteosacchetto/node-zip-cli/releases/download/v0.11.0/node-zip-cli-0.11.0.tgz
 ```
 
 ### Other versions
@@ -210,7 +210,7 @@ Allows you to specify paths that you want to exclude. This option follows the sa
 > For example, providing `*.mjs` will result in the shell replacing it will all the file matching the wildcard, so as the input to the CLI, instead of `"*.mjs"` will be provided the whole list (e.g. "rollup.config.mjs", "test.runner.mjs", ...). Instead, providing `"*.mjs"` will behave as expected, providing as input to the CLI the pattern `"*.mjs"`
 
 > [!NOTE]
-> Up to the current version (0.10.1) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
+> Up to the current version (0.11.0) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
 
 ###### `--allow-git`
 
@@ -348,7 +348,7 @@ Allows you to specify paths that you want to exclude. This option follows the sa
 > For example, providing `*.mjs` will result in the shell replacing it will all the file matching the wildcard, so as the input to the CLI, instead of `"*.mjs"` will be provided the whole list (e.g. "rollup.config.mjs", "test.runner.mjs", ...). Instead, providing `"*.mjs"` will behave as expected, providing as input to the CLI the pattern `"*.mjs"`
 
 > [!NOTE]
-> Up to the current version (0.10.1) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
+> Up to the current version (0.11.0) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
 
 ###### `--allow-git`
 
@@ -449,7 +449,7 @@ Filter the types of entries this command will list
 By default, the three types are included, but you can decide to only list a subset.
 
 > [!NOTE]
-> Up to the current version (0.10.1) symlinks are not listed by default. To list them you need to specify the `-s keep` option.
+> Up to the current version (0.11.0) symlinks are not listed by default. To list them you need to specify the `-s keep` option.
 >
 > Since version (0.10.0) to list them you can just specify the `-s` option
 
@@ -489,7 +489,7 @@ Allows you to specify paths that you want to exclude. This option follows the sa
 > For example, providing `*.mjs` will result in the shell replacing it will all the file matching the wildcard, so as the input to the CLI, instead of `"*.mjs"` will be provided the whole list (e.g. "rollup.config.mjs", "test.runner.mjs", ...). Instead, providing `"*.mjs"` will behave as expected, providing as input to the CLI the pattern `"*.mjs"`
 
 > [!NOTE]
-> Up to the current version (0.10.1) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
+> Up to the current version (0.11.0) the list of paths to ignore which are specified with this options are applied after default ignore paths (like `.git`) BUT before any .gitignore or .zipignore file. This means that paths you specify here could be overridden by the aforementioned files.
 
 ###### `--allow-git`
 
@@ -510,7 +510,7 @@ Simply run this CLI providing to each command all the necessary options.
 This file is meant to be placed in a folder that you plan to zip/tar. It is meant to be used instead of the .gitignore, if the content of the folder is not related to git, or as an extension of the .gitignore, where you can specify additional rules related only to the zip file creation. The .zipignore file follows the same syntax and rules as the traditional .gitignore
 
 > [!NOTE]
-> Up to the current version (0.10.1) the .zipignore builds on top of already existing .gitignore rules, so if you only want to ignore some additional files you **do not need** to copy paste the content of the .gitignore.
+> Up to the current version (0.11.0) the .zipignore builds on top of already existing .gitignore rules, so if you only want to ignore some additional files you **do not need** to copy paste the content of the .gitignore.
 
 > [!NOTE]
 > Since version (0.7.0) the strategy of ignoring everythin (`*`) and then un-ignoring (!) some paths (e.g. `!test`, `!src`, ...) is supported and behaves like in the gitignore specs. Quoting from [gitignore specs](https://git-scm.com/docs/gitignore): *"It is not possible to re-include a file if a parent directory of that file is excluded. Git doesn’t list excluded directories for performance reasons, so any patterns on contained files have no effect, no matter where they are defined. "*.
@@ -524,6 +524,6 @@ This file is meant to be placed in a folder that you plan to zip/tar. It is mean
 
 > [!WARNING]
 > *Current limitations*  
-> Up to the current version (0.10.1) zip/tar and unzip/untar handle files, directories and symlinks.
+> Up to the current version (0.11.0) zip/tar and unzip/untar handle files, directories and symlinks.
 >
 > Since version (0.10.0) symlink support is marked as stable, but requires the user to explicitly enable it for `zip`,`tar` and `find` through the `-s, --symlink` option.

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "node-zip-cli",
-  "version": "0.10.1",
+  "version": "0.11.0",
   "description": "Simple nodejs cli which allows you to create and extract zip/tar files with support for .gitignore files",
   "main": "dist/index.mjs",
   "bin": "dist/index.mjs",