diff --git a/.gitignore b/.gitignore
index 67a7ad9..d529746 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
sablier.yaml
-./plugins/traefik/e2e/kubeconfig.yaml
\ No newline at end of file
+./plugins/traefik/e2e/kubeconfig.yaml
+node_modules
\ No newline at end of file
diff --git a/node_modules/@babel/code-frame/README.md b/node_modules/@babel/code-frame/README.md
deleted file mode 100644
index 08cacb0..0000000
--- a/node_modules/@babel/code-frame/README.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# @babel/code-frame
-
-> Generate errors that contain a code frame that point to source locations.
-
-See our website [@babel/code-frame](https://babeljs.io/docs/en/babel-code-frame) for more information.
-
-## Install
-
-Using npm:
-
-```sh
-npm install --save-dev @babel/code-frame
-```
-
-or using yarn:
-
-```sh
-yarn add @babel/code-frame --dev
-```
diff --git a/node_modules/@babel/helper-validator-identifier/README.md b/node_modules/@babel/helper-validator-identifier/README.md
deleted file mode 100644
index 4f704c4..0000000
--- a/node_modules/@babel/helper-validator-identifier/README.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# @babel/helper-validator-identifier
-
-> Validate identifier/keywords name
-
-See our website [@babel/helper-validator-identifier](https://babeljs.io/docs/en/babel-helper-validator-identifier) for more information.
-
-## Install
-
-Using npm:
-
-```sh
-npm install --save @babel/helper-validator-identifier
-```
-
-or using yarn:
-
-```sh
-yarn add @babel/helper-validator-identifier
-```
diff --git a/node_modules/@babel/highlight/README.md b/node_modules/@babel/highlight/README.md
deleted file mode 100644
index f8887ad..0000000
--- a/node_modules/@babel/highlight/README.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# @babel/highlight
-
-> Syntax highlight JavaScript strings for output in terminals.
-
-See our website [@babel/highlight](https://babeljs.io/docs/en/babel-highlight) for more information.
-
-## Install
-
-Using npm:
-
-```sh
-npm install --save-dev @babel/highlight
-```
-
-or using yarn:
-
-```sh
-yarn add @babel/highlight --dev
-```
diff --git a/node_modules/@colors/colors/README.md b/node_modules/@colors/colors/README.md
deleted file mode 100644
index e2479ce..0000000
--- a/node_modules/@colors/colors/README.md
+++ /dev/null
@@ -1,219 +0,0 @@
-# @colors/colors ("colors.js")
-[](https://github.com/DABH/colors.js/actions/workflows/ci.yml)
-[](https://www.npmjs.org/package/@colors/colors)
-
-Please check out the [roadmap](ROADMAP.md) for upcoming features and releases. Please open Issues to provide feedback.
-
-## get color and style in your node.js console
-
-
-
-## Installation
-
- npm install @colors/colors
-
-## colors and styles!
-
-### text colors
-
- - black
- - red
- - green
- - yellow
- - blue
- - magenta
- - cyan
- - white
- - gray
- - grey
-
-### bright text colors
-
- - brightRed
- - brightGreen
- - brightYellow
- - brightBlue
- - brightMagenta
- - brightCyan
- - brightWhite
-
-### background colors
-
- - bgBlack
- - bgRed
- - bgGreen
- - bgYellow
- - bgBlue
- - bgMagenta
- - bgCyan
- - bgWhite
- - bgGray
- - bgGrey
-
-### bright background colors
-
- - bgBrightRed
- - bgBrightGreen
- - bgBrightYellow
- - bgBrightBlue
- - bgBrightMagenta
- - bgBrightCyan
- - bgBrightWhite
-
-### styles
-
- - reset
- - bold
- - dim
- - italic
- - underline
- - inverse
- - hidden
- - strikethrough
-
-### extras
-
- - rainbow
- - zebra
- - america
- - trap
- - random
-
-
-## Usage
-
-By popular demand, `@colors/colors` now ships with two types of usages!
-
-The super nifty way
-
-```js
-var colors = require('@colors/colors');
-
-console.log('hello'.green); // outputs green text
-console.log('i like cake and pies'.underline.red); // outputs red underlined text
-console.log('inverse the color'.inverse); // inverses the color
-console.log('OMG Rainbows!'.rainbow); // rainbow
-console.log('Run the trap'.trap); // Drops the bass
-
-```
-
-or a slightly less nifty way which doesn't extend `String.prototype`
-
-```js
-var colors = require('@colors/colors/safe');
-
-console.log(colors.green('hello')); // outputs green text
-console.log(colors.red.underline('i like cake and pies')); // outputs red underlined text
-console.log(colors.inverse('inverse the color')); // inverses the color
-console.log(colors.rainbow('OMG Rainbows!')); // rainbow
-console.log(colors.trap('Run the trap')); // Drops the bass
-
-```
-
-I prefer the first way. Some people seem to be afraid of extending `String.prototype` and prefer the second way.
-
-If you are writing good code you will never have an issue with the first approach. If you really don't want to touch `String.prototype`, the second usage will not touch `String` native object.
-
-## Enabling/Disabling Colors
-
-The package will auto-detect whether your terminal can use colors and enable/disable accordingly. When colors are disabled, the color functions do nothing. You can override this with a command-line flag:
-
-```bash
-node myapp.js --no-color
-node myapp.js --color=false
-
-node myapp.js --color
-node myapp.js --color=true
-node myapp.js --color=always
-
-FORCE_COLOR=1 node myapp.js
-```
-
-Or in code:
-
-```javascript
-var colors = require('@colors/colors');
-colors.enable();
-colors.disable();
-```
-
-## Console.log [string substitution](http://nodejs.org/docs/latest/api/console.html#console_console_log_data)
-
-```js
-var name = 'Beowulf';
-console.log(colors.green('Hello %s'), name);
-// outputs -> 'Hello Beowulf'
-```
-
-## Custom themes
-
-### Using standard API
-
-```js
-
-var colors = require('@colors/colors');
-
-colors.setTheme({
- silly: 'rainbow',
- input: 'grey',
- verbose: 'cyan',
- prompt: 'grey',
- info: 'green',
- data: 'grey',
- help: 'cyan',
- warn: 'yellow',
- debug: 'blue',
- error: 'red'
-});
-
-// outputs red text
-console.log("this is an error".error);
-
-// outputs yellow text
-console.log("this is a warning".warn);
-```
-
-### Using string safe API
-
-```js
-var colors = require('@colors/colors/safe');
-
-// set single property
-var error = colors.red;
-error('this is red');
-
-// set theme
-colors.setTheme({
- silly: 'rainbow',
- input: 'grey',
- verbose: 'cyan',
- prompt: 'grey',
- info: 'green',
- data: 'grey',
- help: 'cyan',
- warn: 'yellow',
- debug: 'blue',
- error: 'red'
-});
-
-// outputs red text
-console.log(colors.error("this is an error"));
-
-// outputs yellow text
-console.log(colors.warn("this is a warning"));
-
-```
-
-### Combining Colors
-
-```javascript
-var colors = require('@colors/colors');
-
-colors.setTheme({
- custom: ['red', 'underline']
-});
-
-console.log('test'.custom);
-```
-
-*Protip: There is a secret undocumented style in `colors`. If you find the style you can summon him.*
diff --git a/node_modules/@nodelib/fs.scandir/README.md b/node_modules/@nodelib/fs.scandir/README.md
deleted file mode 100644
index e0b218b..0000000
--- a/node_modules/@nodelib/fs.scandir/README.md
+++ /dev/null
@@ -1,171 +0,0 @@
-# @nodelib/fs.scandir
-
-> List files and directories inside the specified directory.
-
-## :bulb: Highlights
-
-The package is aimed at obtaining information about entries in the directory.
-
-* :moneybag: Returns useful information: `name`, `path`, `dirent` and `stats` (optional).
-* :gear: On Node.js 10.10+ uses the mechanism without additional calls to determine the entry type. See [`old` and `modern` mode](#old-and-modern-mode).
-* :link: Can safely work with broken symbolic links.
-
-## Install
-
-```console
-npm install @nodelib/fs.scandir
-```
-
-## Usage
-
-```ts
-import * as fsScandir from '@nodelib/fs.scandir';
-
-fsScandir.scandir('path', (error, stats) => { /* … */ });
-```
-
-## API
-
-### .scandir(path, [optionsOrSettings], callback)
-
-Returns an array of plain objects ([`Entry`](#entry)) with information about entry for provided path with standard callback-style.
-
-```ts
-fsScandir.scandir('path', (error, entries) => { /* … */ });
-fsScandir.scandir('path', {}, (error, entries) => { /* … */ });
-fsScandir.scandir('path', new fsScandir.Settings(), (error, entries) => { /* … */ });
-```
-
-### .scandirSync(path, [optionsOrSettings])
-
-Returns an array of plain objects ([`Entry`](#entry)) with information about entry for provided path.
-
-```ts
-const entries = fsScandir.scandirSync('path');
-const entries = fsScandir.scandirSync('path', {});
-const entries = fsScandir.scandirSync(('path', new fsScandir.Settings());
-```
-
-#### path
-
-* Required: `true`
-* Type: `string | Buffer | URL`
-
-A path to a file. If a URL is provided, it must use the `file:` protocol.
-
-#### optionsOrSettings
-
-* Required: `false`
-* Type: `Options | Settings`
-* Default: An instance of `Settings` class
-
-An [`Options`](#options) object or an instance of [`Settings`](#settingsoptions) class.
-
-> :book: When you pass a plain object, an instance of the `Settings` class will be created automatically. If you plan to call the method frequently, use a pre-created instance of the `Settings` class.
-
-### Settings([options])
-
-A class of full settings of the package.
-
-```ts
-const settings = new fsScandir.Settings({ followSymbolicLinks: false });
-
-const entries = fsScandir.scandirSync('path', settings);
-```
-
-## Entry
-
-* `name` — The name of the entry (`unknown.txt`).
-* `path` — The path of the entry relative to call directory (`root/unknown.txt`).
-* `dirent` — An instance of [`fs.Dirent`](./src/types/index.ts) class. On Node.js below 10.10 will be emulated by [`DirentFromStats`](./src/utils/fs.ts) class.
-* `stats` (optional) — An instance of `fs.Stats` class.
-
-For example, the `scandir` call for `tools` directory with one directory inside:
-
-```ts
-{
- dirent: Dirent { name: 'typedoc', /* … */ },
- name: 'typedoc',
- path: 'tools/typedoc'
-}
-```
-
-## Options
-
-### stats
-
-* Type: `boolean`
-* Default: `false`
-
-Adds an instance of `fs.Stats` class to the [`Entry`](#entry).
-
-> :book: Always use `fs.readdir` without the `withFileTypes` option. ??TODO??
-
-### followSymbolicLinks
-
-* Type: `boolean`
-* Default: `false`
-
-Follow symbolic links or not. Call `fs.stat` on symbolic link if `true`.
-
-### `throwErrorOnBrokenSymbolicLink`
-
-* Type: `boolean`
-* Default: `true`
-
-Throw an error when symbolic link is broken if `true` or safely use `lstat` call if `false`.
-
-### `pathSegmentSeparator`
-
-* Type: `string`
-* Default: `path.sep`
-
-By default, this package uses the correct path separator for your OS (`\` on Windows, `/` on Unix-like systems). But you can set this option to any separator character(s) that you want to use instead.
-
-### `fs`
-
-* Type: [`FileSystemAdapter`](./src/adapters/fs.ts)
-* Default: A default FS methods
-
-By default, the built-in Node.js module (`fs`) is used to work with the file system. You can replace any method with your own.
-
-```ts
-interface FileSystemAdapter {
- lstat?: typeof fs.lstat;
- stat?: typeof fs.stat;
- lstatSync?: typeof fs.lstatSync;
- statSync?: typeof fs.statSync;
- readdir?: typeof fs.readdir;
- readdirSync?: typeof fs.readdirSync;
-}
-
-const settings = new fsScandir.Settings({
- fs: { lstat: fakeLstat }
-});
-```
-
-## `old` and `modern` mode
-
-This package has two modes that are used depending on the environment and parameters of use.
-
-### old
-
-* Node.js below `10.10` or when the `stats` option is enabled
-
-When working in the old mode, the directory is read first (`fs.readdir`), then the type of entries is determined (`fs.lstat` and/or `fs.stat` for symbolic links).
-
-### modern
-
-* Node.js 10.10+ and the `stats` option is disabled
-
-In the modern mode, reading the directory (`fs.readdir` with the `withFileTypes` option) is combined with obtaining information about its entries. An additional call for symbolic links (`fs.stat`) is still present.
-
-This mode makes fewer calls to the file system. It's faster.
-
-## Changelog
-
-See the [Releases section of our GitHub project](https://github.com/nodelib/nodelib/releases) for changelog for each release version.
-
-## License
-
-This software is released under the terms of the MIT license.
diff --git a/node_modules/@nodelib/fs.stat/README.md b/node_modules/@nodelib/fs.stat/README.md
deleted file mode 100644
index 686f047..0000000
--- a/node_modules/@nodelib/fs.stat/README.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# @nodelib/fs.stat
-
-> Get the status of a file with some features.
-
-## :bulb: Highlights
-
-Wrapper around standard method `fs.lstat` and `fs.stat` with some features.
-
-* :beginner: Normally follows symbolic link.
-* :gear: Can safely work with broken symbolic link.
-
-## Install
-
-```console
-npm install @nodelib/fs.stat
-```
-
-## Usage
-
-```ts
-import * as fsStat from '@nodelib/fs.stat';
-
-fsStat.stat('path', (error, stats) => { /* … */ });
-```
-
-## API
-
-### .stat(path, [optionsOrSettings], callback)
-
-Returns an instance of `fs.Stats` class for provided path with standard callback-style.
-
-```ts
-fsStat.stat('path', (error, stats) => { /* … */ });
-fsStat.stat('path', {}, (error, stats) => { /* … */ });
-fsStat.stat('path', new fsStat.Settings(), (error, stats) => { /* … */ });
-```
-
-### .statSync(path, [optionsOrSettings])
-
-Returns an instance of `fs.Stats` class for provided path.
-
-```ts
-const stats = fsStat.stat('path');
-const stats = fsStat.stat('path', {});
-const stats = fsStat.stat('path', new fsStat.Settings());
-```
-
-#### path
-
-* Required: `true`
-* Type: `string | Buffer | URL`
-
-A path to a file. If a URL is provided, it must use the `file:` protocol.
-
-#### optionsOrSettings
-
-* Required: `false`
-* Type: `Options | Settings`
-* Default: An instance of `Settings` class
-
-An [`Options`](#options) object or an instance of [`Settings`](#settings) class.
-
-> :book: When you pass a plain object, an instance of the `Settings` class will be created automatically. If you plan to call the method frequently, use a pre-created instance of the `Settings` class.
-
-### Settings([options])
-
-A class of full settings of the package.
-
-```ts
-const settings = new fsStat.Settings({ followSymbolicLink: false });
-
-const stats = fsStat.stat('path', settings);
-```
-
-## Options
-
-### `followSymbolicLink`
-
-* Type: `boolean`
-* Default: `true`
-
-Follow symbolic link or not. Call `fs.stat` on symbolic link if `true`.
-
-### `markSymbolicLink`
-
-* Type: `boolean`
-* Default: `false`
-
-Mark symbolic link by setting the return value of `isSymbolicLink` function to always `true` (even after `fs.stat`).
-
-> :book: Can be used if you want to know what is hidden behind a symbolic link, but still continue to know that it is a symbolic link.
-
-### `throwErrorOnBrokenSymbolicLink`
-
-* Type: `boolean`
-* Default: `true`
-
-Throw an error when symbolic link is broken if `true` or safely return `lstat` call if `false`.
-
-### `fs`
-
-* Type: [`FileSystemAdapter`](./src/adapters/fs.ts)
-* Default: A default FS methods
-
-By default, the built-in Node.js module (`fs`) is used to work with the file system. You can replace any method with your own.
-
-```ts
-interface FileSystemAdapter {
- lstat?: typeof fs.lstat;
- stat?: typeof fs.stat;
- lstatSync?: typeof fs.lstatSync;
- statSync?: typeof fs.statSync;
-}
-
-const settings = new fsStat.Settings({
- fs: { lstat: fakeLstat }
-});
-```
-
-## Changelog
-
-See the [Releases section of our GitHub project](https://github.com/nodelib/nodelib/releases) for changelog for each release version.
-
-## License
-
-This software is released under the terms of the MIT license.
diff --git a/node_modules/@nodelib/fs.walk/README.md b/node_modules/@nodelib/fs.walk/README.md
deleted file mode 100644
index 6ccc08d..0000000
--- a/node_modules/@nodelib/fs.walk/README.md
+++ /dev/null
@@ -1,215 +0,0 @@
-# @nodelib/fs.walk
-
-> A library for efficiently walking a directory recursively.
-
-## :bulb: Highlights
-
-* :moneybag: Returns useful information: `name`, `path`, `dirent` and `stats` (optional).
-* :rocket: On Node.js 10.10+ uses the mechanism without additional calls to determine the entry type for performance reasons. See [`old` and `modern` mode](https://github.com/nodelib/nodelib/blob/master/packages/fs/fs.scandir/README.md#old-and-modern-mode).
-* :gear: Built-in directories/files and error filtering system.
-* :link: Can safely work with broken symbolic links.
-
-## Install
-
-```console
-npm install @nodelib/fs.walk
-```
-
-## Usage
-
-```ts
-import * as fsWalk from '@nodelib/fs.walk';
-
-fsWalk.walk('path', (error, entries) => { /* … */ });
-```
-
-## API
-
-### .walk(path, [optionsOrSettings], callback)
-
-Reads the directory recursively and asynchronously. Requires a callback function.
-
-> :book: If you want to use the Promise API, use `util.promisify`.
-
-```ts
-fsWalk.walk('path', (error, entries) => { /* … */ });
-fsWalk.walk('path', {}, (error, entries) => { /* … */ });
-fsWalk.walk('path', new fsWalk.Settings(), (error, entries) => { /* … */ });
-```
-
-### .walkStream(path, [optionsOrSettings])
-
-Reads the directory recursively and asynchronously. [Readable Stream](https://nodejs.org/dist/latest-v12.x/docs/api/stream.html#stream_readable_streams) is used as a provider.
-
-```ts
-const stream = fsWalk.walkStream('path');
-const stream = fsWalk.walkStream('path', {});
-const stream = fsWalk.walkStream('path', new fsWalk.Settings());
-```
-
-### .walkSync(path, [optionsOrSettings])
-
-Reads the directory recursively and synchronously. Returns an array of entries.
-
-```ts
-const entries = fsWalk.walkSync('path');
-const entries = fsWalk.walkSync('path', {});
-const entries = fsWalk.walkSync('path', new fsWalk.Settings());
-```
-
-#### path
-
-* Required: `true`
-* Type: `string | Buffer | URL`
-
-A path to a file. If a URL is provided, it must use the `file:` protocol.
-
-#### optionsOrSettings
-
-* Required: `false`
-* Type: `Options | Settings`
-* Default: An instance of `Settings` class
-
-An [`Options`](#options) object or an instance of [`Settings`](#settings) class.
-
-> :book: When you pass a plain object, an instance of the `Settings` class will be created automatically. If you plan to call the method frequently, use a pre-created instance of the `Settings` class.
-
-### Settings([options])
-
-A class of full settings of the package.
-
-```ts
-const settings = new fsWalk.Settings({ followSymbolicLinks: true });
-
-const entries = fsWalk.walkSync('path', settings);
-```
-
-## Entry
-
-* `name` — The name of the entry (`unknown.txt`).
-* `path` — The path of the entry relative to call directory (`root/unknown.txt`).
-* `dirent` — An instance of [`fs.Dirent`](./src/types/index.ts) class.
-* [`stats`] — An instance of `fs.Stats` class.
-
-## Options
-
-### basePath
-
-* Type: `string`
-* Default: `undefined`
-
-By default, all paths are built relative to the root path. You can use this option to set custom root path.
-
-In the example below we read the files from the `root` directory, but in the results the root path will be `custom`.
-
-```ts
-fsWalk.walkSync('root'); // → ['root/file.txt']
-fsWalk.walkSync('root', { basePath: 'custom' }); // → ['custom/file.txt']
-```
-
-### concurrency
-
-* Type: `number`
-* Default: `Infinity`
-
-The maximum number of concurrent calls to `fs.readdir`.
-
-> :book: The higher the number, the higher performance and the load on the File System. If you want to read in quiet mode, set the value to `4 * os.cpus().length` (4 is default size of [thread pool work scheduling](http://docs.libuv.org/en/v1.x/threadpool.html#thread-pool-work-scheduling)).
-
-### deepFilter
-
-* Type: [`DeepFilterFunction`](./src/settings.ts)
-* Default: `undefined`
-
-A function that indicates whether the directory will be read deep or not.
-
-```ts
-// Skip all directories that starts with `node_modules`
-const filter: DeepFilterFunction = (entry) => !entry.path.startsWith('node_modules');
-```
-
-### entryFilter
-
-* Type: [`EntryFilterFunction`](./src/settings.ts)
-* Default: `undefined`
-
-A function that indicates whether the entry will be included to results or not.
-
-```ts
-// Exclude all `.js` files from results
-const filter: EntryFilterFunction = (entry) => !entry.name.endsWith('.js');
-```
-
-### errorFilter
-
-* Type: [`ErrorFilterFunction`](./src/settings.ts)
-* Default: `undefined`
-
-A function that allows you to skip errors that occur when reading directories.
-
-For example, you can skip `ENOENT` errors if required:
-
-```ts
-// Skip all ENOENT errors
-const filter: ErrorFilterFunction = (error) => error.code == 'ENOENT';
-```
-
-### stats
-
-* Type: `boolean`
-* Default: `false`
-
-Adds an instance of `fs.Stats` class to the [`Entry`](#entry).
-
-> :book: Always use `fs.readdir` with additional `fs.lstat/fs.stat` calls to determine the entry type.
-
-### followSymbolicLinks
-
-* Type: `boolean`
-* Default: `false`
-
-Follow symbolic links or not. Call `fs.stat` on symbolic link if `true`.
-
-### `throwErrorOnBrokenSymbolicLink`
-
-* Type: `boolean`
-* Default: `true`
-
-Throw an error when symbolic link is broken if `true` or safely return `lstat` call if `false`.
-
-### `pathSegmentSeparator`
-
-* Type: `string`
-* Default: `path.sep`
-
-By default, this package uses the correct path separator for your OS (`\` on Windows, `/` on Unix-like systems). But you can set this option to any separator character(s) that you want to use instead.
-
-### `fs`
-
-* Type: `FileSystemAdapter`
-* Default: A default FS methods
-
-By default, the built-in Node.js module (`fs`) is used to work with the file system. You can replace any method with your own.
-
-```ts
-interface FileSystemAdapter {
- lstat: typeof fs.lstat;
- stat: typeof fs.stat;
- lstatSync: typeof fs.lstatSync;
- statSync: typeof fs.statSync;
- readdir: typeof fs.readdir;
- readdirSync: typeof fs.readdirSync;
-}
-
-const settings = new fsWalk.Settings({
- fs: { lstat: fakeLstat }
-});
-```
-
-## Changelog
-
-See the [Releases section of our GitHub project](https://github.com/nodelib/nodelib/releases) for changelog for each release version.
-
-## License
-
-This software is released under the terms of the MIT license.
diff --git a/node_modules/@octokit/auth-token/README.md b/node_modules/@octokit/auth-token/README.md
deleted file mode 100644
index 2e48b73..0000000
--- a/node_modules/@octokit/auth-token/README.md
+++ /dev/null
@@ -1,285 +0,0 @@
-# auth-token.js
-
-> GitHub API token authentication for browsers and Node.js
-
-[](https://www.npmjs.com/package/@octokit/auth-token)
-[](https://github.com/octokit/auth-token.js/actions?query=workflow%3ATest)
-
-`@octokit/auth-token` is the simplest of [GitHub’s authentication strategies](https://github.com/octokit/auth.js).
-
-It is useful if you want to support multiple authentication strategies, as it’s API is compatible with its sibling packages for [basic](https://github.com/octokit/auth-basic.js), [GitHub App](https://github.com/octokit/auth-app.js) and [OAuth app](https://github.com/octokit/auth.js) authentication.
-
-
-
-- [Usage](#usage)
-- [`createTokenAuth(token) options`](#createtokenauthtoken-options)
-- [`auth()`](#auth)
-- [Authentication object](#authentication-object)
-- [`auth.hook(request, route, options)` or `auth.hook(request, options)`](#authhookrequest-route-options-or-authhookrequest-options)
-- [Find more information](#find-more-information)
- - [Find out what scopes are enabled for oauth tokens](#find-out-what-scopes-are-enabled-for-oauth-tokens)
- - [Find out if token is a personal access token or if it belongs to an OAuth app](#find-out-if-token-is-a-personal-access-token-or-if-it-belongs-to-an-oauth-app)
- - [Find out what permissions are enabled for a repository](#find-out-what-permissions-are-enabled-for-a-repository)
- - [Use token for git operations](#use-token-for-git-operations)
-- [License](#license)
-
-
-
-## Usage
-
-
-
-```js
-const auth = createTokenAuth("ghp_PersonalAccessToken01245678900000000");
-const authentication = await auth();
-// {
-// type: 'token',
-// token: 'ghp_PersonalAccessToken01245678900000000',
-// tokenType: 'oauth'
-// }
-```
-
-## `createTokenAuth(token) options`
-
-The `createTokenAuth` method accepts a single argument of type string, which is the token. The passed token can be one of the following:
-
-- [Personal access token](https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line)
-- [OAuth access token](https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/)
-- [GITHUB_TOKEN provided to GitHub Actions](https://developer.github.com/actions/creating-github-actions/accessing-the-runtime-environment/#environment-variables)
-- Installation access token ([server-to-server](https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation))
-- User authentication for installation ([user-to-server](https://docs.github.com/en/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps))
-
-Examples
-
-```js
-// Personal access token or OAuth access token
-createTokenAuth("ghp_PersonalAccessToken01245678900000000");
-// {
-// type: 'token',
-// token: 'ghp_PersonalAccessToken01245678900000000',
-// tokenType: 'oauth'
-// }
-
-// Installation access token or GitHub Action token
-createTokenAuth("ghs_InstallallationOrActionToken00000000");
-// {
-// type: 'token',
-// token: 'ghs_InstallallationOrActionToken00000000',
-// tokenType: 'installation'
-// }
-
-// Installation access token or GitHub Action token
-createTokenAuth("ghu_InstallationUserToServer000000000000");
-// {
-// type: 'token',
-// token: 'ghu_InstallationUserToServer000000000000',
-// tokenType: 'user-to-server'
-// }
-```
-
-## `auth()`
-
-The `auth()` method has no options. It returns a promise which resolves with the the authentication object.
-
-## Authentication object
-
-
-
-
-
- name
-
-
- type
-
-
- description
-
-
-
-
-
-
- type
-
-
- string
-
-
- "token"
-
-
-
-
- token
-
-
- string
-
-
- The provided token.
-
-
-
-
- tokenType
-
-
- string
-
-
- Can be either "oauth" for personal access tokens and OAuth tokens, "installation" for installation access tokens (includes GITHUB_TOKEN provided to GitHub Actions), "app" for a GitHub App JSON Web Token, or "user-to-server" for a user authentication token through an app installation.
-
-
-
-
-
-## `auth.hook(request, route, options)` or `auth.hook(request, options)`
-
-`auth.hook()` hooks directly into the request life cycle. It authenticates the request using the provided token.
-
-The `request` option is an instance of [`@octokit/request`](https://github.com/octokit/request.js#readme). The `route`/`options` parameters are the same as for the [`request()` method](https://github.com/octokit/request.js#request).
-
-`auth.hook()` can be called directly to send an authenticated request
-
-```js
-const { data: authorizations } = await auth.hook(
- request,
- "GET /authorizations"
-);
-```
-
-Or it can be passed as option to [`request()`](https://github.com/octokit/request.js#request).
-
-```js
-const requestWithAuth = request.defaults({
- request: {
- hook: auth.hook,
- },
-});
-
-const { data: authorizations } = await requestWithAuth("GET /authorizations");
-```
-
-## Find more information
-
-`auth()` does not send any requests, it only transforms the provided token string into an authentication object.
-
-Here is a list of things you can do to retrieve further information
-
-### Find out what scopes are enabled for oauth tokens
-
-Note that this does not work for installations. There is no way to retrieve permissions based on an installation access tokens.
-
-```js
-const TOKEN = "ghp_PersonalAccessToken01245678900000000";
-
-const auth = createTokenAuth(TOKEN);
-const authentication = await auth();
-
-const response = await request("HEAD /");
-const scopes = response.headers["x-oauth-scopes"].split(/,\s+/);
-
-if (scopes.length) {
- console.log(
- `"${TOKEN}" has ${scopes.length} scopes enabled: ${scopes.join(", ")}`
- );
-} else {
- console.log(`"${TOKEN}" has no scopes enabled`);
-}
-```
-
-### Find out if token is a personal access token or if it belongs to an OAuth app
-
-```js
-const TOKEN = "ghp_PersonalAccessToken01245678900000000";
-
-const auth = createTokenAuth(TOKEN);
-const authentication = await auth();
-
-const response = await request("HEAD /");
-const clientId = response.headers["x-oauth-client-id"];
-
-if (clientId) {
- console.log(
- `"${token}" is an OAuth token, its app’s client_id is ${clientId}.`
- );
-} else {
- console.log(`"${token}" is a personal access token`);
-}
-```
-
-### Find out what permissions are enabled for a repository
-
-Note that the `permissions` key is not set when authenticated using an installation access token.
-
-```js
-const TOKEN = "ghp_PersonalAccessToken01245678900000000";
-
-const auth = createTokenAuth(TOKEN);
-const authentication = await auth();
-
-const response = await request("GET /repos/{owner}/{repo}", {
- owner: "octocat",
- repo: "hello-world",
-});
-
-console.log(response.data.permissions);
-// {
-// admin: true,
-// push: true,
-// pull: true
-// }
-```
-
-### Use token for git operations
-
-Both OAuth and installation access tokens can be used for git operations. However, when using with an installation, [the token must be prefixed with `x-access-token`](https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation).
-
-This example is using the [`execa`](https://github.com/sindresorhus/execa) package to run a `git push` command.
-
-```js
-const TOKEN = "ghp_PersonalAccessToken01245678900000000";
-
-const auth = createTokenAuth(TOKEN);
-const { token, tokenType } = await auth();
-const tokenWithPrefix =
- tokenType === "installation" ? `x-access-token:${token}` : token;
-
-const repositoryUrl = `https://${tokenWithPrefix}@github.com/octocat/hello-world.git`;
-
-const { stdout } = await execa("git", ["push", repositoryUrl]);
-console.log(stdout);
-```
-
-## License
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/core/README.md b/node_modules/@octokit/core/README.md
deleted file mode 100644
index 3cc5141..0000000
--- a/node_modules/@octokit/core/README.md
+++ /dev/null
@@ -1,448 +0,0 @@
-# core.js
-
-> Extendable client for GitHub's REST & GraphQL APIs
-
-[](https://www.npmjs.com/package/@octokit/core)
-[](https://github.com/octokit/core.js/actions?query=workflow%3ATest+branch%3Amain)
-
-
-
-- [Usage](#usage)
- - [REST API example](#rest-api-example)
- - [GraphQL example](#graphql-example)
-- [Options](#options)
-- [Defaults](#defaults)
-- [Authentication](#authentication)
-- [Logging](#logging)
-- [Hooks](#hooks)
-- [Plugins](#plugins)
-- [Build your own Octokit with Plugins and Defaults](#build-your-own-octokit-with-plugins-and-defaults)
-- [LICENSE](#license)
-
-
-
-If you need a minimalistic library to utilize GitHub's [REST API](https://developer.github.com/v3/) and [GraphQL API](https://developer.github.com/v4/) which you can extend with plugins as needed, then `@octokit/core` is a great starting point.
-
-If you don't need the Plugin API then using [`@octokit/request`](https://github.com/octokit/request.js/) or [`@octokit/graphql`](https://github.com/octokit/graphql.js/) directly is a good alternative.
-
-## Usage
-
-
-
-When using with GitHub Enterprise Server, set `options.baseUrl` to the root URL of the API. For example, if your GitHub Enterprise Server's hostname is `github.acme-inc.com`, then set `options.baseUrl` to `https://github.acme-inc.com/api/v3`. Example
-
-```js
-const octokit = new Octokit({
- baseUrl: "https://github.acme-inc.com/api/v3",
-});
-```
-
-
-
-
- options.previews
-
-
- Array of Strings
-
-
-
-Some REST API endpoints require preview headers to be set, or enable
-additional features. Preview headers can be set on a per-request basis, e.g.
-
-```js
-octokit.request("POST /repos/{owner}/{repo}/pulls", {
- mediaType: {
- previews: ["shadow-cat"],
- },
- owner,
- repo,
- title: "My pull request",
- base: "main",
- head: "my-feature",
- draft: true,
-});
-```
-
-You can also set previews globally, by setting the `options.previews` option on the constructor. Example:
-
-```js
-const octokit = new Octokit({
- previews: ["shadow-cat"],
-});
-```
-
-
-
-
- options.request
-
-
- Object
-
-
-
-Set a default request timeout (`options.request.timeout`) or an [`http(s).Agent`](https://nodejs.org/api/http.html#http_class_http_agent) e.g. for proxy usage (Node only, `options.request.agent`).
-
-There are more `options.request.*` options, see [`@octokit/request` options](https://github.com/octokit/request.js#request). `options.request` can also be set on a per-request basis.
-
-
-
-
- options.timeZone
-
-
- String
-
-
-
-Sets the `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
-
-```js
-const octokit = new Octokit({
- timeZone: "America/Los_Angeles",
-});
-```
-
-The time zone header will determine the timezone used for generating the timestamp when creating commits. See [GitHub's Timezones documentation](https://developer.github.com/v3/#timezones).
-
-
-
-
- options.userAgent
-
-
- String
-
-
-
-A custom user agent string for your app or library. Example
-
-```js
-const octokit = new Octokit({
- userAgent: "my-app/v1.2.3",
-});
-```
-
-
-
-
-
-## Defaults
-
-You can create a new Octokit class with customized default options.
-
-```js
-const MyOctokit = Octokit.defaults({
- auth: "personal-access-token123",
- baseUrl: "https://github.acme-inc.com/api/v3",
- userAgent: "my-app/v1.2.3",
-});
-const octokit1 = new MyOctokit();
-const octokit2 = new MyOctokit();
-```
-
-If you pass additional options to your new constructor, the options will be merged shallowly.
-
-```js
-const MyOctokit = Octokit.defaults({
- foo: {
- opt1: 1,
- },
-});
-const octokit = new MyOctokit({
- foo: {
- opt2: 1,
- },
-});
-// options will be { foo: { opt2: 1 }}
-```
-
-If you need a deep or conditional merge, you can pass a function instead.
-
-```js
-const MyOctokit = Octokit.defaults((options) => {
- return {
- foo: Object.assign({}, options.foo, { opt1: 1 }),
- };
-});
-const octokit = new MyOctokit({
- foo: { opt2: 1 },
-});
-// options will be { foo: { opt1: 1, opt2: 1 }}
-```
-
-Be careful about mutating the `options` object in the `Octokit.defaults` callback, as it can have unforeseen consequences.
-
-## Authentication
-
-Authentication is optional for some REST API endpoints accessing public data, but is required for GraphQL queries. Using authentication also increases your [API rate limit](https://developer.github.com/v3/#rate-limiting).
-
-By default, Octokit authenticates using the [token authentication strategy](https://github.com/octokit/auth-token.js). Pass in a token using `options.auth`. It can be a personal access token, an OAuth token, an installation access token or a JSON Web Token for GitHub App authentication. The `Authorization` header will be set according to the type of token.
-
-```js
-import { Octokit } from "@octokit/core";
-
-const octokit = new Octokit({
- auth: "mypersonalaccesstoken123",
-});
-
-const { data } = await octokit.request("/user");
-```
-
-To use a different authentication strategy, set `options.authStrategy`. A list of authentication strategies is available at [octokit/authentication-strategies.js](https://github.com/octokit/authentication-strategies.js/#readme).
-
-Example
-
-```js
-import { Octokit } from "@octokit/core";
-import { createAppAuth } from "@octokit/auth-app";
-
-const appOctokit = new Octokit({
- authStrategy: createAppAuth,
- auth: {
- appId: 123,
- privateKey: process.env.PRIVATE_KEY,
- },
-});
-
-const { data } = await appOctokit.request("/app");
-```
-
-The `.auth()` method returned by the current authentication strategy can be accessed at `octokit.auth()`. Example
-
-```js
-const { token } = await appOctokit.auth({
- type: "installation",
- installationId: 123,
-});
-```
-
-## Logging
-
-There are four built-in log methods
-
-1. `octokit.log.debug(message[, additionalInfo])`
-1. `octokit.log.info(message[, additionalInfo])`
-1. `octokit.log.warn(message[, additionalInfo])`
-1. `octokit.log.error(message[, additionalInfo])`
-
-They can be configured using the [`log` client option](client-options). By default, `octokit.log.debug()` and `octokit.log.info()` are no-ops, while the other two call `console.warn()` and `console.error()` respectively.
-
-This is useful if you build reusable [plugins](#plugins).
-
-If you would like to make the log level configurable using an environment variable or external option, we recommend the [console-log-level](https://github.com/watson/console-log-level) package. Example
-
-```js
-const octokit = new Octokit({
- log: require("console-log-level")({ level: "info" }),
-});
-```
-
-## Hooks
-
-You can customize Octokit's request lifecycle with hooks.
-
-```js
-octokit.hook.before("request", async (options) => {
- validate(options);
-});
-octokit.hook.after("request", async (response, options) => {
- console.log(`${options.method} ${options.url}: ${response.status}`);
-});
-octokit.hook.error("request", async (error, options) => {
- if (error.status === 304) {
- return findInCache(error.response.headers.etag);
- }
-
- throw error;
-});
-octokit.hook.wrap("request", async (request, options) => {
- // add logic before, after, catch errors or replace the request altogether
- return request(options);
-});
-```
-
-See [before-after-hook](https://github.com/gr2m/before-after-hook#readme) for more documentation on hooks.
-
-## Plugins
-
-Octokit’s functionality can be extended using plugins. The `Octokit.plugin()` method accepts a plugin (or many) and returns a new constructor.
-
-A plugin is a function which gets two arguments:
-
-1. the current instance
-2. the options passed to the constructor.
-
-In order to extend `octokit`'s API, the plugin must return an object with the new methods.
-
-```js
-// index.js
-const { Octokit } = require("@octokit/core")
-const MyOctokit = Octokit.plugin(
- require("./lib/my-plugin"),
- require("octokit-plugin-example")
-);
-
-const octokit = new MyOctokit({ greeting: "Moin moin" });
-octokit.helloWorld(); // logs "Moin moin, world!"
-octokit.request("GET /"); // logs "GET / - 200 in 123ms"
-
-// lib/my-plugin.js
-module.exports = (octokit, options = { greeting: "Hello" }) => {
- // hook into the request lifecycle
- octokit.hook.wrap("request", async (request, options) => {
- const time = Date.now();
- const response = await request(options);
- console.log(
- `${options.method} ${options.url} – ${response.status} in ${Date.now() -
- time}ms`
- );
- return response;
- });
-
- // add a custom method
- return {
- helloWorld: () => console.log(`${options.greeting}, world!`);
- }
-};
-```
-
-## Build your own Octokit with Plugins and Defaults
-
-You can build your own Octokit class with preset default options and plugins. In fact, this is mostly how the `@octokit/` modules work, such as [`@octokit/action`](https://github.com/octokit/action.js):
-
-```js
-const { Octokit } = require("@octokit/core");
-const MyActionOctokit = Octokit.plugin(
- require("@octokit/plugin-paginate-rest").paginateRest,
- require("@octokit/plugin-throttling").throttling,
- require("@octokit/plugin-retry").retry
-).defaults({
- throttle: {
- onAbuseLimit: (retryAfter, options) => {
- /* ... */
- },
- onRateLimit: (retryAfter, options) => {
- /* ... */
- },
- },
- authStrategy: require("@octokit/auth-action").createActionAuth,
- userAgent: `my-octokit-action/v1.2.3`,
-});
-
-const octokit = new MyActionOctokit();
-const installations = await octokit.paginate("GET /app/installations");
-```
-
-## LICENSE
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/endpoint/README.md b/node_modules/@octokit/endpoint/README.md
deleted file mode 100644
index c7b5232..0000000
--- a/node_modules/@octokit/endpoint/README.md
+++ /dev/null
@@ -1,421 +0,0 @@
-# endpoint.js
-
-> Turns GitHub REST API endpoints into generic request options
-
-[](https://www.npmjs.com/package/@octokit/endpoint)
-[](https://github.com/octokit/endpoint.js/actions/workflows/test.yml?query=branch%3Amain)
-
-`@octokit/endpoint` combines [GitHub REST API routes](https://developer.github.com/v3/) with your parameters and turns them into generic request options that can be used in any request library.
-
-
-
-
-
-- [Usage](#usage)
-- [API](#api)
- - [`endpoint(route, options)` or `endpoint(options)`](#endpointroute-options-or-endpointoptions)
- - [`endpoint.defaults()`](#endpointdefaults)
- - [`endpoint.DEFAULTS`](#endpointdefaults)
- - [`endpoint.merge(route, options)` or `endpoint.merge(options)`](#endpointmergeroute-options-or-endpointmergeoptions)
- - [`endpoint.parse()`](#endpointparse)
-- [Special cases](#special-cases)
- - [The `data` parameter – set request body directly](#the-data-parameter-%E2%80%93-set-request-body-directly)
- - [Set parameters for both the URL/query and the request body](#set-parameters-for-both-the-urlquery-and-the-request-body)
-- [LICENSE](#license)
-
-
-
-## Usage
-
-
-
-Example for [List organization repositories](https://developer.github.com/v3/repos/#list-organization-repositories)
-
-```js
-const requestOptions = endpoint("GET /orgs/{org}/repos", {
- headers: {
- authorization: "token 0000000000000000000000000000000000000001",
- },
- org: "octokit",
- type: "private",
-});
-```
-
-The resulting `requestOptions` looks as follows
-
-```json
-{
- "method": "GET",
- "url": "https://api.github.com/orgs/octokit/repos?type=private",
- "headers": {
- "accept": "application/vnd.github.v3+json",
- "authorization": "token 0000000000000000000000000000000000000001",
- "user-agent": "octokit/endpoint.js v1.2.3"
- }
-}
-```
-
-You can pass `requestOptions` to common request libraries
-
-```js
-const { url, ...options } = requestOptions;
-// using with fetch (https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)
-fetch(url, options);
-// using with request (https://github.com/request/request)
-request(requestOptions);
-// using with got (https://github.com/sindresorhus/got)
-got[options.method](url, options);
-// using with axios
-axios(requestOptions);
-```
-
-## API
-
-### `endpoint(route, options)` or `endpoint(options)`
-
-
-
-
-
- name
-
-
- type
-
-
- description
-
-
-
-
-
-
- route
-
-
- String
-
-
- If set, it has to be a string consisting of URL and the request method, e.g., GET /orgs/{org}. If it’s set to a URL, only the method defaults to GET.
-
-
-
-
- options.method
-
-
- String
-
-
- Required unless route is set. Any supported http verb. Defaults to GET.
-
-
-
-
- options.url
-
-
- String
-
-
- Required unless route is set. A path or full URL which may contain :variable or {variable} placeholders,
- e.g., /orgs/{org}/repos. The url is parsed using url-template.
-
-
-
-
- options.baseUrl
-
-
- String
-
-
- Defaults to https://api.github.com.
-
-
-
-
- options.headers
-
-
- Object
-
-
- Custom headers. Passed headers are merged with defaults:
- headers['user-agent'] defaults to octokit-endpoint.js/1.2.3 (where 1.2.3 is the released version).
- headers['accept'] defaults to application/vnd.github.v3+json.
-
-
-
-
- options.mediaType.format
-
-
- String
-
-
- Media type param, such as raw, diff, or text+json. See Media Types. Setting options.mediaType.format will amend the headers.accept value.
-
-
-
-
- options.mediaType.previews
-
-
- Array of Strings
-
-
- Name of previews, such as mercy, symmetra, or scarlet-witch. See API Previews. If options.mediaType.previews was set as default, the new previews will be merged into the default ones. Setting options.mediaType.previews will amend the headers.accept value. options.mediaType.previews will be merged with an existing array set using .defaults().
-
-
-
-
- options.data
-
-
- Any
-
-
- Set request body directly instead of setting it to JSON based on additional parameters. See "The data parameter" below.
-
-
-
-
- options.request
-
-
- Object
-
-
- Pass custom meta information for the request. The request object will be returned as is.
-
-
-
-
-
-All other options will be passed depending on the `method` and `url` options.
-
-1. If the option key has a placeholder in the `url`, it will be used as the replacement. For example, if the passed options are `{url: '/orgs/{org}/repos', org: 'foo'}` the returned `options.url` is `https://api.github.com/orgs/foo/repos`.
-2. If the `method` is `GET` or `HEAD`, the option is passed as a query parameter.
-3. Otherwise, the parameter is passed in the request body as a JSON key.
-
-**Result**
-
-`endpoint()` is a synchronous method and returns an object with the following keys:
-
-
-
-
-
- key
-
-
- type
-
-
- description
-
-
-
-
-
-
method
-
String
-
The http method. Always lowercase.
-
-
-
url
-
String
-
The url with placeholders replaced with passed parameters.
-
-
-
headers
-
Object
-
All header names are lowercased.
-
-
-
body
-
Any
-
The request body if one is present. Only for PATCH, POST, PUT, DELETE requests.
-
-
-
request
-
Object
-
Request meta option, it will be returned as it was passed into endpoint()
-
-
-
-
-### `endpoint.defaults()`
-
-Override or set default options. Example:
-
-```js
-const request = require("request");
-const myEndpoint = require("@octokit/endpoint").defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
- headers: {
- "user-agent": "myApp/1.2.3",
- authorization: `token 0000000000000000000000000000000000000001`,
- },
- org: "my-project",
- per_page: 100,
-});
-
-request(myEndpoint(`GET /orgs/{org}/repos`));
-```
-
-You can call `.defaults()` again on the returned method, the defaults will cascade.
-
-```js
-const myProjectEndpoint = endpoint.defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
- headers: {
- "user-agent": "myApp/1.2.3",
- },
- org: "my-project",
-});
-const myProjectEndpointWithAuth = myProjectEndpoint.defaults({
- headers: {
- authorization: `token 0000000000000000000000000000000000000001`,
- },
-});
-```
-
-`myProjectEndpointWithAuth` now defaults the `baseUrl`, `headers['user-agent']`,
-`org` and `headers['authorization']` on top of `headers['accept']` that is set
-by the global default.
-
-### `endpoint.DEFAULTS`
-
-The current default options.
-
-```js
-endpoint.DEFAULTS.baseUrl; // https://api.github.com
-const myEndpoint = endpoint.defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
-});
-myEndpoint.DEFAULTS.baseUrl; // https://github-enterprise.acme-inc.com/api/v3
-```
-
-### `endpoint.merge(route, options)` or `endpoint.merge(options)`
-
-Get the defaulted endpoint options, but without parsing them into request options:
-
-```js
-const myProjectEndpoint = endpoint.defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
- headers: {
- "user-agent": "myApp/1.2.3",
- },
- org: "my-project",
-});
-myProjectEndpoint.merge("GET /orgs/{org}/repos", {
- headers: {
- authorization: `token 0000000000000000000000000000000000000001`,
- },
- org: "my-secret-project",
- type: "private",
-});
-
-// {
-// baseUrl: 'https://github-enterprise.acme-inc.com/api/v3',
-// method: 'GET',
-// url: '/orgs/{org}/repos',
-// headers: {
-// accept: 'application/vnd.github.v3+json',
-// authorization: `token 0000000000000000000000000000000000000001`,
-// 'user-agent': 'myApp/1.2.3'
-// },
-// org: 'my-secret-project',
-// type: 'private'
-// }
-```
-
-### `endpoint.parse()`
-
-Stateless method to turn endpoint options into request options. Calling
-`endpoint(options)` is the same as calling `endpoint.parse(endpoint.merge(options))`.
-
-## Special cases
-
-
-
-### The `data` parameter – set request body directly
-
-Some endpoints such as [Render a Markdown document in raw mode](https://developer.github.com/v3/markdown/#render-a-markdown-document-in-raw-mode) don’t have parameters that are sent as request body keys, instead, the request body needs to be set directly. In these cases, set the `data` parameter.
-
-```js
-const options = endpoint("POST /markdown/raw", {
- data: "Hello world github/linguist#1 **cool**, and #1!",
- headers: {
- accept: "text/html;charset=utf-8",
- "content-type": "text/plain",
- },
-});
-
-// options is
-// {
-// method: 'post',
-// url: 'https://api.github.com/markdown/raw',
-// headers: {
-// accept: 'text/html;charset=utf-8',
-// 'content-type': 'text/plain',
-// 'user-agent': userAgent
-// },
-// body: 'Hello world github/linguist#1 **cool**, and #1!'
-// }
-```
-
-### Set parameters for both the URL/query and the request body
-
-There are API endpoints that accept both query parameters as well as a body. In that case, you need to add the query parameters as templates to `options.url`, as defined in the [RFC 6570 URI Template specification](https://tools.ietf.org/html/rfc6570).
-
-Example
-
-```js
-endpoint(
- "POST https://uploads.github.com/repos/octocat/Hello-World/releases/1/assets{?name,label}",
- {
- name: "example.zip",
- label: "short description",
- headers: {
- "content-type": "text/plain",
- "content-length": 14,
- authorization: `token 0000000000000000000000000000000000000001`,
- },
- data: "Hello, world!",
- }
-);
-```
-
-## LICENSE
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/graphql/README.md b/node_modules/@octokit/graphql/README.md
deleted file mode 100644
index aee921a..0000000
--- a/node_modules/@octokit/graphql/README.md
+++ /dev/null
@@ -1,409 +0,0 @@
-# graphql.js
-
-> GitHub GraphQL API client for browsers and Node
-
-[](https://www.npmjs.com/package/@octokit/graphql)
-[](https://github.com/octokit/graphql.js/actions?query=workflow%3ATest+branch%3Amain)
-
-
-
-- [Usage](#usage)
- - [Send a simple query](#send-a-simple-query)
- - [Authentication](#authentication)
- - [Variables](#variables)
- - [Pass query together with headers and variables](#pass-query-together-with-headers-and-variables)
- - [Use with GitHub Enterprise](#use-with-github-enterprise)
- - [Use custom `@octokit/request` instance](#use-custom-octokitrequest-instance)
-- [TypeScript](#typescript)
- - [Additional Types](#additional-types)
-- [Errors](#errors)
-- [Partial responses](#partial-responses)
-- [Writing tests](#writing-tests)
-- [License](#license)
-
-
-
-## Usage
-
-
-
-```js
-const MyOctokit = Octokit.plugin(paginateRest);
-const octokit = new MyOctokit({ auth: "secret123" });
-
-// See https://developer.github.com/v3/issues/#list-issues-for-a-repository
-const issues = await octokit.paginate("GET /repos/{owner}/{repo}/issues", {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
-});
-```
-
-If you want to utilize the pagination methods in another plugin, use `composePaginateRest`.
-
-```js
-function myPlugin(octokit, options) {
- return {
- allStars({owner, repo}) => {
- return composePaginateRest(
- octokit,
- "GET /repos/{owner}/{repo}/stargazers",
- {owner, repo }
- )
- }
- }
-}
-```
-
-## `octokit.paginate()`
-
-The `paginateRest` plugin adds a new `octokit.paginate()` method which accepts the same parameters as [`octokit.request`](https://github.com/octokit/request.js#request). Only "List ..." endpoints such as [List issues for a repository](https://developer.github.com/v3/issues/#list-issues-for-a-repository) are supporting pagination. Their [response includes a Link header](https://developer.github.com/v3/issues/#response-1). For other endpoints, `octokit.paginate()` behaves the same as `octokit.request()`.
-
-The `per_page` parameter is usually defaulting to `30`, and can be set to up to `100`, which helps retrieving a big amount of data without hitting the rate limits too soon.
-
-An optional `mapFunction` can be passed to map each page response to a new value, usually an array with only the data you need. This can help to reduce memory usage, as only the relevant data has to be kept in memory until the pagination is complete.
-
-```js
-const issueTitles = await octokit.paginate(
- "GET /repos/{owner}/{repo}/issues",
- {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
- },
- (response) => response.data.map((issue) => issue.title)
-);
-```
-
-The `mapFunction` gets a 2nd argument `done` which can be called to end the pagination early.
-
-```js
-const issues = await octokit.paginate(
- "GET /repos/{owner}/{repo}/issues",
- {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
- },
- (response, done) => {
- if (response.data.find((issue) => issue.title.includes("something"))) {
- done();
- }
- return response.data;
- }
-);
-```
-
-Alternatively you can pass a `request` method as first argument. This is great when using in combination with [`@octokit/plugin-rest-endpoint-methods`](https://github.com/octokit/plugin-rest-endpoint-methods.js/):
-
-```js
-const issues = await octokit.paginate(octokit.rest.issues.listForRepo, {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
-});
-```
-
-## `octokit.paginate.iterator()`
-
-If your target runtime environments supports async iterators (such as most modern browsers and Node 10+), you can iterate through each response
-
-```js
-const parameters = {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
-};
-for await (const response of octokit.paginate.iterator(
- "GET /repos/{owner}/{repo}/issues",
- parameters
-)) {
- // do whatever you want with each response, break out of the loop, etc.
- const issues = response.data;
- console.log("%d issues found", issues.length);
-}
-```
-
-Alternatively you can pass a `request` method as first argument. This is great when using in combination with [`@octokit/plugin-rest-endpoint-methods`](https://github.com/octokit/plugin-rest-endpoint-methods.js/):
-
-```js
-const parameters = {
- owner: "octocat",
- repo: "hello-world",
- since: "2010-10-01",
- per_page: 100,
-};
-for await (const response of octokit.paginate.iterator(
- octokit.rest.issues.listForRepo,
- parameters
-)) {
- // do whatever you want with each response, break out of the loop, etc.
- const issues = response.data;
- console.log("%d issues found", issues.length);
-}
-```
-
-## `composePaginateRest` and `composePaginateRest.iterator`
-
-The `compose*` methods work just like their `octokit.*` counterparts described above, with the differenct that both methods require an `octokit` instance to be passed as first argument
-
-## How it works
-
-`octokit.paginate()` wraps `octokit.request()`. As long as a `rel="next"` link value is present in the response's `Link` header, it sends another request for that URL, and so on.
-
-Most of GitHub's paginating REST API endpoints return an array, but there are a few exceptions which return an object with a key that includes the items array. For example:
-
-- [Search repositories](https://developer.github.com/v3/search/#example) (key `items`)
-- [List check runs for a specific ref](https://developer.github.com/v3/checks/runs/#response-3) (key: `check_runs`)
-- [List check suites for a specific ref](https://developer.github.com/v3/checks/suites/#response-1) (key: `check_suites`)
-- [List repositories](https://developer.github.com/v3/apps/installations/#list-repositories) for an installation (key: `repositories`)
-- [List installations for a user](https://developer.github.com/v3/apps/installations/#response-1) (key `installations`)
-
-`octokit.paginate()` is working around these inconsistencies so you don't have to worry about it.
-
-If a response is lacking the `Link` header, `octokit.paginate()` still resolves with an array, even if the response returns a single object.
-
-## Types
-
-The plugin also exposes some types and runtime type guards for TypeScript projects.
-
-
-
-### PaginateInterface
-
-An `interface` that declares all the overloads of the `.paginate` method.
-
-### PaginatingEndpoints
-
-An `interface` which describes all API endpoints supported by the plugin. Some overloads of `.paginate()` method and `composePaginateRest()` function depend on `PaginatingEndpoints`, using the `keyof PaginatingEndpoints` as a type for one of its arguments.
-
-```typescript
-import { Octokit } from "@octokit/core";
-import {
- PaginatingEndpoints,
- composePaginateRest,
-} from "@octokit/plugin-paginate-rest";
-
-type DataType = "data" extends keyof T ? T["data"] : unknown;
-
-async function myPaginatePlugin(
- octokit: Octokit,
- endpoint: E,
- parameters?: PaginatingEndpoints[E]["parameters"]
-): Promise> {
- return await composePaginateRest(octokit, endpoint, parameters);
-}
-```
-
-### isPaginatingEndpoint
-
-A type guard, `isPaginatingEndpoint(arg)` returns `true` if `arg` is one of the keys in `PaginatingEndpoints` (is `keyof PaginatingEndpoints`).
-
-```typescript
-import { Octokit } from "@octokit/core";
-import {
- isPaginatingEndpoint,
- composePaginateRest,
-} from "@octokit/plugin-paginate-rest";
-
-async function myPlugin(octokit: Octokit, arg: unknown) {
- if (isPaginatingEndpoint(arg)) {
- return await composePaginateRest(octokit, arg);
- }
- // ...
-}
-```
-
-## Contributing
-
-See [CONTRIBUTING.md](CONTRIBUTING.md)
-
-## License
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/plugin-request-log/README.md b/node_modules/@octokit/plugin-request-log/README.md
deleted file mode 100644
index cbc8f1b..0000000
--- a/node_modules/@octokit/plugin-request-log/README.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# plugin-request-log.js
-
-> Log all requests and request errors
-
-[](https://www.npmjs.com/package/@octokit/plugin-request-log)
-[](https://github.com/octokit/plugin-request-log.js/actions?workflow=Test)
-
-## Usage
-
-
-
-
-Browsers
-
-
-Load `@octokit/plugin-request-log` and [`@octokit/core`](https://github.com/octokit/core.js) (or core-compatible module) directly from [cdn.skypack.dev](https://cdn.skypack.dev)
-
-```html
-
-```
-
-
-
-```js
-const MyOctokit = Octokit.plugin(restEndpointMethods);
-const octokit = new MyOctokit({ auth: "secret123" });
-
-// https://developer.github.com/v3/users/#get-the-authenticated-user
-octokit.rest.users.getAuthenticated();
-```
-
-There is one method for each REST API endpoint documented at [https://developer.github.com/v3](https://developer.github.com/v3). All endpoint methods are documented in the [docs/](docs/) folder, e.g. [docs/users/getAuthenticated.md](docs/users/getAuthenticated.md)
-
-## TypeScript
-
-Parameter and response types for all endpoint methods exported as `{ RestEndpointMethodTypes }`.
-
-Example
-
-```ts
-import { RestEndpointMethodTypes } from "@octokit/plugin-rest-endpoint-methods";
-
-type UpdateLabelParameters =
- RestEndpointMethodTypes["issues"]["updateLabel"]["parameters"];
-type UpdateLabelResponse =
- RestEndpointMethodTypes["issues"]["updateLabel"]["response"];
-```
-
-In order to get types beyond parameters and responses, check out [`@octokit/openapi-types`](https://github.com/octokit/openapi-types.ts/#readme), which is a direct transpilation from GitHub's official OpenAPI specification.
-
-## Contributing
-
-See [CONTRIBUTING.md](CONTRIBUTING.md)
-
-## License
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/request-error/README.md b/node_modules/@octokit/request-error/README.md
deleted file mode 100644
index 343c456..0000000
--- a/node_modules/@octokit/request-error/README.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# http-error.js
-
-> Error class for Octokit request errors
-
-[](https://www.npmjs.com/package/@octokit/request-error)
-[](https://github.com/octokit/request-error.js/actions?query=workflow%3ATest)
-
-## Usage
-
-
-
-### REST API example
-
-```js
-// Following GitHub docs formatting:
-// https://developer.github.com/v3/repos/#list-organization-repositories
-const result = await request("GET /orgs/{org}/repos", {
- headers: {
- authorization: "token 0000000000000000000000000000000000000001",
- },
- org: "octokit",
- type: "private",
-});
-
-console.log(`${result.data.length} repos found.`);
-```
-
-### GraphQL example
-
-For GraphQL request we recommend using [`@octokit/graphql`](https://github.com/octokit/graphql.js#readme)
-
-```js
-const result = await request("POST /graphql", {
- headers: {
- authorization: "token 0000000000000000000000000000000000000001",
- },
- query: `query ($login: String!) {
- organization(login: $login) {
- repositories(privacy: PRIVATE) {
- totalCount
- }
- }
- }`,
- variables: {
- login: "octokit",
- },
-});
-```
-
-### Alternative: pass `method` & `url` as part of options
-
-Alternatively, pass in a method and a url
-
-```js
-const result = await request({
- method: "GET",
- url: "/orgs/{org}/repos",
- headers: {
- authorization: "token 0000000000000000000000000000000000000001",
- },
- org: "octokit",
- type: "private",
-});
-```
-
-## Authentication
-
-The simplest way to authenticate a request is to set the `Authorization` header directly, e.g. to a [personal access token](https://github.com/settings/tokens/).
-
-```js
-const requestWithAuth = request.defaults({
- headers: {
- authorization: "token 0000000000000000000000000000000000000001",
- },
-});
-const result = await requestWithAuth("GET /user");
-```
-
-For more complex authentication strategies such as GitHub Apps or Basic, we recommend the according authentication library exported by [`@octokit/auth`](https://github.com/octokit/auth.js).
-
-```js
-const { createAppAuth } = require("@octokit/auth-app");
-const auth = createAppAuth({
- appId: process.env.APP_ID,
- privateKey: process.env.PRIVATE_KEY,
- installationId: 123,
-});
-const requestWithAuth = request.defaults({
- request: {
- hook: auth.hook,
- },
- mediaType: {
- previews: ["machine-man"],
- },
-});
-
-const { data: app } = await requestWithAuth("GET /app");
-const { data: app } = await requestWithAuth(
- "POST /repos/{owner}/{repo}/issues",
- {
- owner: "octocat",
- repo: "hello-world",
- title: "Hello from the engine room",
- }
-);
-```
-
-## request()
-
-`request(route, options)` or `request(options)`.
-
-**Options**
-
-
-
-
-
- name
-
-
- type
-
-
- description
-
-
-
-
-
- route
-
-
- String
-
-
- **Required**. If route is set it has to be a string consisting of the request method and URL, e.g. GET /orgs/{org}
-
-
-
-
- options.baseUrl
-
-
- String
-
-
- The base URL that route or url will be prefixed with, if they use relative paths. Defaults to https://api.github.com.
-
-
-
- options.headers
-
-
- Object
-
-
- Custom headers. Passed headers are merged with defaults:
- headers['user-agent'] defaults to octokit-rest.js/1.2.3 (where 1.2.3 is the released version).
- headers['accept'] defaults to application/vnd.github.v3+json. Use options.mediaType.{format,previews} to request API previews and custom media types.
-
-
-
-
- options.mediaType.format
-
-
- String
-
-
- Media type param, such as `raw`, `html`, or `full`. See Media Types.
-
-
-
-
- options.mediaType.previews
-
-
- Array of strings
-
-
- Name of previews, such as `mercy`, `symmetra`, or `scarlet-witch`. See API Previews.
-
-
-
-
- options.method
-
-
- String
-
-
- Any supported http verb, case insensitive. Defaults to Get.
-
-
-
-
- options.url
-
-
- String
-
-
- **Required**. A path or full URL which may contain :variable or {variable} placeholders,
- e.g. /orgs/{org}/repos. The url is parsed using url-template.
-
-
-
-
- options.data
-
-
- Any
-
-
- Set request body directly instead of setting it to JSON based on additional parameters. See "The `data` parameter" below.
-
- Node only. Useful for custom proxy, certificate, or dns lookup.
-
-
-
-
- options.request.fetch
-
-
- Function
-
-
- Custom replacement for built-in fetch method. Useful for testing or request hooks.
-
-
-
-
- options.request.hook
-
-
- Function
-
-
- Function with the signature hook(request, endpointOptions), where endpointOptions are the parsed options as returned by endpoint.merge(), and request is request(). This option works great in conjuction with before-after-hook.
-
- Use an AbortController instance to cancel a request. In node you can only cancel streamed requests.
-
-
-
- options.request.log
-
-
- object
-
-
- Used for internal logging. Defaults to console.
-
-
-
-
- options.request.timeout
-
-
- Number
-
-
- Node only. Request/response timeout in ms, it resets on redirect. 0 to disable (OS limit applies). options.request.signal is recommended instead.
-
-
-
-
-All other options except `options.request.*` will be passed depending on the `method` and `url` options.
-
-1. If the option key is a placeholder in the `url`, it will be used as replacement. For example, if the passed options are `{url: '/orgs/{org}/repos', org: 'foo'}` the returned `options.url` is `https://api.github.com/orgs/foo/repos`
-2. If the `method` is `GET` or `HEAD`, the option is passed as query parameter
-3. Otherwise the parameter is passed in the request body as JSON key.
-
-**Result**
-
-`request` returns a promise. If the request was successful, the promise resolves with an object containing 4 keys:
-
-
-
-
-
- key
-
-
- type
-
-
- description
-
-
-
-
-
status
-
Integer
-
Response status status
-
-
-
url
-
String
-
URL of response. If a request results in redirects, this is the final URL. You can send a HEAD request to retrieve it without loading the full response body.
-
-
-
headers
-
Object
-
All response headers
-
-
-
data
-
Any
-
The response body as returned from server. If the response is JSON then it will be parsed into an object
-
-
-
-If an error occurs, the promise is rejected with an `error` object containing 3 keys to help with debugging:
-
-- `error.status` The http response status code
-- `error.request` The request options such as `method`, `url` and `data`
-- `error.response` The http response object with `url`, `headers`, and `data`
-
-If the error is due to an `AbortSignal` being used, the resulting `AbortError` is bubbled up to the caller.
-
-## `request.defaults()`
-
-Override or set default options. Example:
-
-```js
-const myrequest = require("@octokit/request").defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
- headers: {
- "user-agent": "myApp/1.2.3",
- authorization: `token 0000000000000000000000000000000000000001`,
- },
- org: "my-project",
- per_page: 100,
-});
-
-myrequest(`GET /orgs/{org}/repos`);
-```
-
-You can call `.defaults()` again on the returned method, the defaults will cascade.
-
-```js
-const myProjectRequest = request.defaults({
- baseUrl: "https://github-enterprise.acme-inc.com/api/v3",
- headers: {
- "user-agent": "myApp/1.2.3",
- },
- org: "my-project",
-});
-const myProjectRequestWithAuth = myProjectRequest.defaults({
- headers: {
- authorization: `token 0000000000000000000000000000000000000001`,
- },
-});
-```
-
-`myProjectRequest` now defaults the `baseUrl`, `headers['user-agent']`,
-`org` and `headers['authorization']` on top of `headers['accept']` that is set
-by the global default.
-
-## `request.endpoint`
-
-See https://github.com/octokit/endpoint.js. Example
-
-```js
-const options = request.endpoint("GET /orgs/{org}/repos", {
- org: "my-project",
- type: "private",
-});
-
-// {
-// method: 'GET',
-// url: 'https://api.github.com/orgs/my-project/repos?type=private',
-// headers: {
-// accept: 'application/vnd.github.v3+json',
-// authorization: 'token 0000000000000000000000000000000000000001',
-// 'user-agent': 'octokit/endpoint.js v1.2.3'
-// }
-// }
-```
-
-All of the [`@octokit/endpoint`](https://github.com/octokit/endpoint.js) API can be used:
-
-- [`octokitRequest.endpoint()`](#endpoint)
-- [`octokitRequest.endpoint.defaults()`](#endpointdefaults)
-- [`octokitRequest.endpoint.merge()`](#endpointdefaults)
-- [`octokitRequest.endpoint.parse()`](#endpointmerge)
-
-## Special cases
-
-
-
-### The `data` parameter – set request body directly
-
-Some endpoints such as [Render a Markdown document in raw mode](https://developer.github.com/v3/markdown/#render-a-markdown-document-in-raw-mode) don’t have parameters that are sent as request body keys, instead the request body needs to be set directly. In these cases, set the `data` parameter.
-
-```js
-const response = await request("POST /markdown/raw", {
- data: "Hello world github/linguist#1 **cool**, and #1!",
- headers: {
- accept: "text/html;charset=utf-8",
- "content-type": "text/plain",
- },
-});
-
-// Request is sent as
-//
-// {
-// method: 'post',
-// url: 'https://api.github.com/markdown/raw',
-// headers: {
-// accept: 'text/html;charset=utf-8',
-// 'content-type': 'text/plain',
-// 'user-agent': userAgent
-// },
-// body: 'Hello world github/linguist#1 **cool**, and #1!'
-// }
-//
-// not as
-//
-// {
-// ...
-// body: '{"data": "Hello world github/linguist#1 **cool**, and #1!"}'
-// }
-```
-
-### Set parameters for both the URL/query and the request body
-
-There are API endpoints that accept both query parameters as well as a body. In that case you need to add the query parameters as templates to `options.url`, as defined in the [RFC 6570 URI Template specification](https://tools.ietf.org/html/rfc6570).
-
-Example
-
-```js
-request(
- "POST https://uploads.github.com/repos/octocat/Hello-World/releases/1/assets{?name,label}",
- {
- name: "example.zip",
- label: "short description",
- headers: {
- "content-type": "text/plain",
- "content-length": 14,
- authorization: `token 0000000000000000000000000000000000000001`,
- },
- data: "Hello, world!",
- }
-);
-```
-
-## LICENSE
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/rest/README.md b/node_modules/@octokit/rest/README.md
deleted file mode 100644
index 3a46f37..0000000
--- a/node_modules/@octokit/rest/README.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# rest.js
-
-> GitHub REST API client for JavaScript
-
-[](https://www.npmjs.com/package/@octokit/rest)
-[](https://github.com/octokit/rest.js/actions?query=workflow%3ATest+branch%3Amain)
-
-## Usage
-
-
-
-```js
-const octokit = new Octokit();
-
-// Compare: https://docs.github.com/en/rest/reference/repos/#list-organization-repositories
-octokit.rest.repos
- .listForOrg({
- org: "octokit",
- type: "public",
- })
- .then(({ data }) => {
- // handle data
- });
-```
-
-See https://octokit.github.io/rest.js for full documentation.
-
-## Contributing
-
-We would love you to contribute to `@octokit/rest`, pull requests are very welcome! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for more information.
-
-## Credits
-
-`@octokit/rest` was originally created as [`node-github`](https://www.npmjs.com/package/github) in 2012 by Mike de Boer from Cloud9 IDE, Inc. [The original commit](https://github.blog/2020-04-09-from-48k-lines-of-code-to-10-the-story-of-githubs-javascript-sdk/) is from 2010 which predates the npm registry.
-
-It was adopted and renamed by GitHub in 2017. Learn more about its origin on GitHub's blog: [From 48k lines of code to 10—the story of GitHub’s JavaScript SDK](https://github.blog/2020-04-09-from-48k-lines-of-code-to-10-the-story-of-githubs-javascript-sdk/)
-
-## LICENSE
-
-[MIT](LICENSE)
diff --git a/node_modules/@octokit/types/README.md b/node_modules/@octokit/types/README.md
deleted file mode 100644
index c48ce42..0000000
--- a/node_modules/@octokit/types/README.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# types.ts
-
-> Shared TypeScript definitions for Octokit projects
-
-[](https://www.npmjs.com/package/@octokit/types)
-[](https://github.com/octokit/types.ts/actions?workflow=Test)
-
-
-
-- [Usage](#usage)
-- [Examples](#examples)
- - [Get parameter and response data types for a REST API endpoint](#get-parameter-and-response-data-types-for-a-rest-api-endpoint)
- - [Get response types from endpoint methods](#get-response-types-from-endpoint-methods)
-- [Contributing](#contributing)
-- [License](#license)
-
-
-
-## Usage
-
-See all exported types at https://octokit.github.io/types.ts
-
-## Examples
-
-### Get parameter and response data types for a REST API endpoint
-
-```ts
-import { Endpoints } from "@octokit/types";
-
-type listUserReposParameters =
- Endpoints["GET /repos/{owner}/{repo}"]["parameters"];
-type listUserReposResponse = Endpoints["GET /repos/{owner}/{repo}"]["response"];
-
-async function listRepos(
- options: listUserReposParameters
-): listUserReposResponse["data"] {
- // ...
-}
-```
-
-### Get response types from endpoint methods
-
-```ts
-import {
- GetResponseTypeFromEndpointMethod,
- GetResponseDataTypeFromEndpointMethod,
-} from "@octokit/types";
-import { Octokit } from "@octokit/rest";
-
-const octokit = new Octokit();
-type CreateLabelResponseType = GetResponseTypeFromEndpointMethod<
- typeof octokit.issues.createLabel
->;
-type CreateLabelResponseDataType = GetResponseDataTypeFromEndpointMethod<
- typeof octokit.issues.createLabel
->;
-```
-
-## Contributing
-
-See [CONTRIBUTING.md](CONTRIBUTING.md)
-
-## License
-
-[MIT](LICENSE)
diff --git a/node_modules/@pnpm/npm-conf/readme.md b/node_modules/@pnpm/npm-conf/readme.md
deleted file mode 100644
index eb443cf..0000000
--- a/node_modules/@pnpm/npm-conf/readme.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# @pnpm/npm-conf [](https://travis-ci.com/pnpm/npm-conf)
-
-> Get the npm config
-
-
-## Install
-
-```
-$ pnpm add @pnpm/npm-conf
-```
-
-
-## Usage
-
-```js
-const npmConf = require('@pnpm/npm-conf');
-
-const conf = npmConf();
-
-conf.get('prefix')
-//=> //=> /Users/unicorn/.npm-packages
-
-conf.get('registry')
-//=> https://registry.npmjs.org/
-```
-
-To get a list of all available `npm` config options:
-
-```bash
-$ npm config list --long
-```
-
-
-## API
-
-### npmConf()
-
-Returns the `npm` config.
-
-### npmConf.defaults
-
-Returns the default `npm` config.
-
-
-## License
-
-MIT
diff --git a/node_modules/@semantic-release/commit-analyzer/README.md b/node_modules/@semantic-release/commit-analyzer/README.md
deleted file mode 100644
index 0b87281..0000000
--- a/node_modules/@semantic-release/commit-analyzer/README.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# **commit-analyzer**
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to analyze commits with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
-
-[](https://github.com/semantic-release/commit-analyzer/actions?query=workflow%3ATest+branch%3Amaster) [](https://www.npmjs.com/package/@semantic-release/commit-analyzer)
-[](https://www.npmjs.com/package/@semantic-release/commit-analyzer)
-[](https://www.npmjs.com/package/@semantic-release/commit-analyzer)
-
-| Step | Description |
-|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
-| `analyzeCommits` | Determine the type of release by analyzing commits with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog). |
-
-## Install
-
-```bash
-$ npm install @semantic-release/commit-analyzer -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- ["@semantic-release/commit-analyzer", {
- "preset": "angular",
- "releaseRules": [
- {"type": "docs", "scope":"README", "release": "patch"},
- {"type": "refactor", "release": "patch"},
- {"type": "style", "release": "patch"}
- ],
- "parserOpts": {
- "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES"]
- }
- }],
- "@semantic-release/release-notes-generator"
- ]
-}
-```
-
-With this example:
-- the commits that contains `BREAKING CHANGE` or `BREAKING CHANGES` in their body will be considered breaking changes.
-- the commits with a 'docs' `type`, a 'README' `scope` will be associated with a `patch` release
-- the commits with a 'refactor' `type` will be associated with a `patch` release
-- the commits with a 'style' `type` will be associated with a `patch` release
-
-**Note**: Your commits must be formatted **exactly** as specified by the chosen convention. For example the [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines) require the `BREAKING CHANGE` keyword to be followed by a colon (`:`) and to be in the **footer** of the commit message.
-
-## Configuration
-
-### Options
-
-| Option | Description | Default |
-|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
-| `preset` | [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset (possible values: [`angular`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular), [`atom`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-atom), [`codemirror`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-codemirror), [`ember`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-ember), [`eslint`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-eslint), [`express`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-express), [`jquery`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-jquery), [`jshint`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-jshint), [`conventionalcommits`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-conventionalcommits)). | [`angular`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular) |
-| `config` | npm package name of a custom [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset. | - |
-| `parserOpts` | Additional [conventional-commits-parser](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser#conventionalcommitsparseroptions) options that will extends the ones loaded by `preset` or `config`. This is convenient to use a [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset with some customizations without having to create a new module. | - |
-| `releaseRules` | An external module, a path to a module or an `Array` of rules. See [`releaseRules`](#releaserules). | See [`releaseRules`](#releaserules) |
-| `presetConfig` | Additional configuration passed to the [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset. Used for example with [conventional-changelog-conventionalcommits](https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.0.0/README.md). | - |
-
-**Notes**: in order to use a `preset` it must be installed (for example to use the [eslint preset](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-eslint) you must install it with `npm install conventional-changelog-eslint -D`)
-
-**Note**: `config` will be overwritten by the values of `preset`. You should use either `preset` or `config`, but not both.
-
-**Note**: Individual properties of `parserOpts` will override ones loaded with an explicitly set `preset` or `config`. If `preset` or `config` are not set, only the properties set in `parserOpts` will be used.
-
-**Note**: For presets that expects a configuration object, such as [`conventionalcommits`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-conventionalcommits), the `presetConfig` option **must** be set.
-
-#### releaseRules
-
-Release rules are used when deciding if the commits since the last release warrant a new release. If you define custom release rules the [default rules](lib/default-release-rules.js) will be used if nothing matched. Those rules will be matched against the commit objects resulting of [conventional-commits-parser](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser) parsing. Each rule property can be defined as a [glob](https://github.com/micromatch/micromatch#matching-features).
-
-##### Rules definition
-
-This is an `Array` of rule objects. A rule object has a `release` property and 1 or more criteria.
-```json
-{
- "plugins": [
- ["@semantic-release/commit-analyzer", {
- "preset": "angular",
- "releaseRules": [
- {"type": "docs", "scope": "README", "release": "patch"},
- {"type": "refactor", "scope": "core-*", "release": "minor"},
- {"type": "refactor", "release": "patch"},
- {"scope": "no-release", "release": false}
- ]
- }],
- "@semantic-release/release-notes-generator"
- ]
-}
-```
-
-##### Rules matching
-
-Each commit will be compared with each rule and when it matches, the commit will be associated with the release type in the rule's `release` property. If a commit match multiple rules, the highest release type (`major` > `minor` > `patch`) is associated with the commit.
-
-See [release types](lib/default-release-types.js) for the release types hierarchy.
-
-With the previous example:
-- Commits with `type` 'docs' and `scope` 'README' will be associated with a `patch` release.
-- Commits with `type` 'refactor' and `scope` starting with 'core-' (i.e. 'core-ui', 'core-rules', ...) will be associated with a `minor` release.
-- Other commits with `type` 'refactor' (without `scope` or with a `scope` not matching the glob `core-*`) will be associated with a `patch` release.
-- Commits with scope `no-release` will not be associated with a release type.
-
-##### Default rules matching
-
-If a commit doesn't match any rule in `releaseRules` it will be evaluated against the [default release rules](lib/default-release-rules.js).
-
-With the previous example:
-- Commits with a breaking change will be associated with a `major` release.
-- Commits with `type` 'feat' will be associated with a `minor` release.
-- Commits with `type` 'fix' will be associated with a `patch` release.
-- Commits with `type` 'perf' will be associated with a `patch` release.
-- Commits with scope `no-release` will not be associated with a release type even if they have a breaking change or the `type` 'feat', 'fix' or 'perf'.
-
-##### No rules matching
-
-If a commit doesn't match any rules in `releaseRules` or in [default release rules](lib/default-release-rules.js) then no release type will be associated with the commit.
-
-With the previous example:
-- Commits with `type` 'style' will not be associated with a release type.
-- Commits with `type` 'test' will not be associated with a release type.
-- Commits with `type` 'chore' will not be associated with a release type.
-
-##### Multiple commits
-
-If there is multiple commits that match one or more rules, the one with the highest release type will determine the global release type.
-
-Considering the following commits:
-- `docs(README): Add more details to the API docs`
-- `feat(API): Add a new method to the public API`
-
-With the previous example the release type determined by the plugin will be `minor`.
-
-##### Specific commit properties
-
-The properties to set in the rules will depends on the commit style chosen. For example [conventional-changelog-angular](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular) use the commit properties `type`, `scope` and `subject` but [conventional-changelog-eslint](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-eslint) uses `tag` and `message`.
-
-For example with `eslint` preset:
-```json
-{
- "plugins": [
- ["@semantic-release/commit-analyzer", {
- "preset": "eslint",
- "releaseRules": [
- {"tag": "Docs", "message":"*README*", "release": "patch"},
- {"tag": "New", "release": "patch"}
- ]
- }],
- "@semantic-release/release-notes-generator"
- ]
-}
-```
-With this configuration:
-- Commits with `tag` 'Docs', that contains 'README' in their header message will be associated with a `patch` release.
-- Commits with `tag` 'New' will be associated with a `patch` release.
-- Commits with `tag` 'Breaking' will be associated with a `major` release (per [default release rules](lib/default-release-rules.js)).
-- Commits with `tag` 'Fix' will be associated with a `patch` release (per [default release rules](lib/default-release-rules.js)).
-- Commits with `tag` 'Update' will be associated with a `minor` release (per [default release rules](lib/default-release-rules.js)).
-- All other commits will not be associated with a release type.
-
-##### External package / file
-
-`releaseRules` can also reference a module, either by it's `npm` name or path:
-```json
-{
- "plugins": [
- ["@semantic-release/commit-analyzer", {
- "preset": "angular",
- "releaseRules": "./config/release-rules.js"
- }],
- "@semantic-release/release-notes-generator"
- ]
-}
-```
-```js
-// File: config/release-rules.js
-module.exports = [
- {type: 'docs', scope: 'README', release: 'patch'},
- {type: 'refactor', scope: 'core-*', release: 'minor'},
- {type: 'refactor', release: 'patch'},
-];
-```
diff --git a/node_modules/@semantic-release/error/README.md b/node_modules/@semantic-release/error/README.md
deleted file mode 100644
index e098967..0000000
--- a/node_modules/@semantic-release/error/README.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# @semantic-release/error
-
-Error type used by all [semantic-release](https://github.com/semantic-release/semantic-release) packages.
-
-[](https://github.com/semantic-release/error/actions?query=workflow%3ATest+branch%3Amaster)
-
-Errors of type `SemanticReleaseError` or an inherited type will be considered by [semantic-release](https://github.com/semantic-release/semantic-release) as an expected exception case (no release to be done, running on a PR etc..). That indicate to the `semantic-release` process to stop and exit with the `0` success code.
-
-Any other type of error will be considered by [semantic-release](https://github.com/semantic-release/semantic-release) as an unexpected error (i/o issue, code problem etc...). That indicate to the `semantic-release` process to stop, log the error and exit with the `1` failure code.
-
-## Usage
-
-```js
-const SemanticReleaseError = require("@semantic-release/error");
-
-// Default
-throw new SemanticReleaseError();
-
-// With error message
-throw new SemanticReleaseError("An error happened");
-
-// With error message and error code
-throw new SemanticReleaseError("An error happened", "ECODE");
-
-// With error message, error code and details
-throw new SemanticReleaseError("An error happened", "ECODE", "Here is some suggestions to solve this error.");
-
-// With inheritance
-class InheritedError extends SemanticReleaseError {
- constructor(message, code, newProperty, details) {
- super(message);
- Error.captureStackTrace(this, this.constructor);
- this.name = this.constructor.name;
- this.code = code;
- this.details = details;
- this.newProperty = "newProperty";
- }
-}
-
-throw new InheritedError("An error happened", "ECODE", "Here is some suggestions to solve this error.");
-```
diff --git a/node_modules/@semantic-release/exec/README.md b/node_modules/@semantic-release/exec/README.md
deleted file mode 100644
index 12742e8..0000000
--- a/node_modules/@semantic-release/exec/README.md
+++ /dev/null
@@ -1,141 +0,0 @@
-# @semantic-release/exec
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to execute custom shell commands.
-
-[](https://github.com/semantic-release/exec/actions?query=workflow%3ATest+branch%3Amaster) [](https://www.npmjs.com/package/@semantic-release/exec)
-[](https://www.npmjs.com/package/@semantic-release/exec)
-[](https://www.npmjs.com/package/@semantic-release/exec)
-
-| Step | Description |
-|--------------------|---------------------------------------------------------------------------------------------------------|
-| `verifyConditions` | Execute a shell command to verify if the release should happen. |
-| `analyzeCommits` | Execute a shell command to determine the type of release. |
-| `verifyRelease` | Execute a shell command to verifying a release that was determined before and is about to be published. |
-| `generateNotes` | Execute a shell command to generate the release note. |
-| `prepare` | Execute a shell command to prepare the release. |
-| `publish` | Execute a shell command to publish the release. |
-| `success` | Execute a shell command to notify of a new release. |
-| `fail` | Execute a shell command to notify of a failed release. |
-
-## Install
-
-```bash
-$ npm install @semantic-release/exec -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- ["@semantic-release/exec", {
- "verifyConditionsCmd": "./verify.sh",
- "publishCmd": "./publish.sh ${nextRelease.version} ${options.branch} ${commits.length} ${Date.now()}"
- }],
- ]
-}
-```
-
-With this example:
-- the shell command `./verify.sh` will be executed on the [verify conditions step](https://github.com/semantic-release/semantic-release#release-steps)
-- the shell command `./publish.sh 1.0.0 master 3 870668040000` (for the release of version `1.0.0` from branch `master` with `3` commits on `August 4th, 1997 at 2:14 AM`) will be executed on the [publish step](https://github.com/semantic-release/semantic-release#release-steps)
-
-**Note**: it's required to define a plugin for the [analyze commits step](https://github.com/semantic-release/semantic-release#release-steps). If no [analyzeCommitsCmd](#analyzecommitscmd) is defined the plugin [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer) must be defined in the `plugins` list.
-
-## Configuration
-
-### Options
-
-| Options | Description |
-|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `verifyConditionsCmd` | The shell command to execute during the verify condition step. See [verifyConditionsCmd](#verifyconditionscmd). |
-| `analyzeCommitsCmd` | The shell command to execute during the analyze commits step. See [analyzeCommitsCmd](#analyzecommitscmd). |
-| `verifyReleaseCmd` | The shell command to execute during the verify release step. See [verifyReleaseCmd](#verifyreleasecmd). |
-| `generateNotesCmd` | The shell command to execute during the generate notes step. See [generateNotesCmd](#generatenotescmd). |
-| `prepareCmd` | The shell command to execute during the prepare step. See [prepareCmd](#preparecmd). |
-| `addChannelCmd` | The shell command to execute during the add channel step. See [addChannelCmd](#addchannelcmd). |
-| `publishCmd` | The shell command to execute during the publish step. See [publishCmd](#publishcmd). |
-| `successCmd` | The shell command to execute during the success step. See [successCmd](#successcmd). |
-| `failCmd` | The shell command to execute during the fail step. See [failCmd](#failcmd). |
-| `shell` | The shell to use to run the command. See [execa#shell](https://github.com/sindresorhus/execa#shell). |
-| `execCwd` | The path to use as current working directory when executing the shell commands. This path is relative to the path from which **semantic-release** is running. For example if **semantic-release** runs from `/my-project` and `execCwd` is set to `buildScripts` then the shell command will be executed from `/my-project/buildScripts` |
-
-Each shell command is generated with [Lodash template](https://lodash.com/docs#template). All the objects passed to the [semantic-release plugins](https://github.com/semantic-release/semantic-release#plugins) are available as template options.
-
-## verifyConditionsCmd
-
-Execute a shell command to verify if the release should happen.
-
-| Command property | Description |
-|------------------|--------------------------------------------------------------------------|
-| `exit code` | `0` if the verification is successful, or any other exit code otherwise. |
-| `stdout` | Write only the reason for the verification to fail. |
-| `stderr` | Can be used for logging. |
-
-## analyzeCommitsCmd
-
-| Command property | Description |
-|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | Only the release type (`major`, `minor` or `patch` etc..) can be written to `stdout`. If no release has to be done the command must not write to `stdout`. |
-| `stderr` | Can be used for logging. |
-
-## verifyReleaseCmd
-
-| Command property | Description |
-|------------------|--------------------------------------------------------------------------|
-| `exit code` | `0` if the verification is successful, or any other exit code otherwise. |
-| `stdout` | Only the reason for the verification to fail can be written to `stdout`. |
-| `stderr` | Can be used for logging. |
-
-## generateNotesCmd
-
-| Command property | Description |
-|------------------|---------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | Only the release note must be written to `stdout`. |
-| `stderr` | Can be used for logging. |
-
-## prepareCmd
-
-| Command property | Description |
-|------------------|---------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | Can be used for logging. |
-| `stderr` | Can be used for logging. |
-
-## addChannelCmd
-
-| Command property | Description |
-|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | The `release` information can be written to `stdout` as parseable JSON (for example `{"name": "Release name", "url": "http://url/release/1.0.0"}`). If the command write non parseable JSON to `stdout` no `release` information will be returned. |
-| `stderr` | Can be used for logging. |
-
-## publishCmd
-
-| Command property | Description |
-|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | The `release` information can be written to `stdout` as parseable JSON (for example `{"name": "Release name", "url": "http://url/release/1.0.0"}`). If the command write non parseable JSON to `stdout` no `release` information will be returned. |
-| `stderr` | Can be used for logging. |
-
-## successCmd
-
-| Command property | Description |
-|------------------|---------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | Can be used for logging. |
-| `stderr` | Can be used for logging. |
-
-## failCmd
-
-| Command property | Description |
-|------------------|---------------------------------------------------------------------------------------------------------------------|
-| `exit code` | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-| `stdout` | Can be used for logging. |
-| `stderr` | Can be used for logging. |
diff --git a/node_modules/@semantic-release/git/README.md b/node_modules/@semantic-release/git/README.md
deleted file mode 100644
index 2d078ed..0000000
--- a/node_modules/@semantic-release/git/README.md
+++ /dev/null
@@ -1,272 +0,0 @@
-# @semantic-release/git
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to commit release assets to the project's [git](https://git-scm.com/) repository.
-
-[](https://github.com/semantic-release/git/actions?query=workflow%3ATest+branch%3Amaster) [](https://www.npmjs.com/package/@semantic-release/git)
-[](https://www.npmjs.com/package/@semantic-release/git)
-[](https://www.npmjs.com/package/@semantic-release/git)
-
-| Step | Description |
-|--------------------|------------------------------------------------------------------------------------------------------------------------------------|
-| `verifyConditions` | Verify the access to the remote Git repository, the commit [`message`](#message) and the [`assets`](#assets) option configuration. |
-| `prepare` | Create a release commit, including configurable file assets. |
-
-## Install
-
-```bash
-$ npm install @semantic-release/git -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- ["@semantic-release/git", {
- "assets": ["dist/**/*.{js,css}", "docs", "package.json"],
- "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
- }]
- ]
-}
-```
-
-With this example, for each release a release commit will be pushed to the remote Git repository with:
-- a message formatted like `chore(release): [skip ci]\n\n`
-- the `.js` and `.css` files in the `dist` directory, the files in the `docs` directory and the `package.json`
-
-### Merging between semantic-release branches
-
-This plugin will, by default, create commit messages with the keyword `[skip ci]`, so they won't trigger a new unnecessary CI build. If you are using **semantic-release** with [multiple branches](https://github.com/semantic-release/semantic-release/blob/beta/docs/usage/workflow-configuration.md), when merging a branch with a head being a release commit, a CI job will be triggered on the target branch. Depending on the CI service that might create an unexpected behavior as the head of the target branch might be ignored by the build due to the `[skip ci]` keyword.
-
-To avoid any unexpected behavior we recommend to use the [`--no-ff` option](https://git-scm.com/docs/git-merge#Documentation/git-merge.txt---no-ff) when merging branches used by **semantic-release**.
-
-**Note**: This concerns only merges done between two branches configured in the [`branches` option](https://github.com/semantic-release/semantic-release/blob/beta/docs/usage/configuration.md#branches).
-
-## Configuration
-
-### Git authentication
-
-The Git user associated with the [Git credentials](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#authentication) has to be able to push commit to the [release branch](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#branch).
-
-When configuring branches permission on a Git hosting service (e.g. [GitHub protected branches](https://help.github.com/articles/about-protected-branches), [GitLab protected branches](https://docs.gitlab.com/ee/user/project/protected_branches.html) or [Bitbucket branch permissions](https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html)) it might be necessary to create a specific configuration in order to allow the **semantic-release** user to bypass global restrictions. For example on GitHub you can uncheck "Include administrators" and configure **semantic-release** to use an administrator user, so the plugin can push the release commit without requiring [status checks](https://help.github.com/articles/about-required-status-checks) and [pull request reviews](https://help.github.com/articles/about-required-reviews-for-pull-requests).
-
-### Environment variables
-
-| Variable | Description | Default |
-|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
-| `GIT_AUTHOR_NAME` | The author name associated with the release commit. See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing). | @semantic-release-bot. |
-| `GIT_AUTHOR_EMAIL` | The author email associated with the release commit. See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing). | @semantic-release-bot email address. |
-| `GIT_COMMITTER_NAME` | The committer name associated with the release commit. See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing). | @semantic-release-bot. |
-| `GIT_COMMITTER_EMAIL` | The committer email associated with the release commit. See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing). | @semantic-release-bot email address. |
-
-### Options
-
-| Options | Description | Default |
-|-----------|------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
-| `message` | The message for the release commit. See [message](#message). | `chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}` |
-| `assets` | Files to include in the release commit. Set to `false` to disable adding files to the release commit. See [assets](#assets). | `['CHANGELOG.md', 'package.json', 'package-lock.json', 'npm-shrinkwrap.json']` |
-
-#### `message`
-
-The message for the release commit is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
-
-| Parameter | Description |
-|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
-| `branch` | The branch from which the release is done. |
-| `branch.name` | The branch name. |
-| `branch.type` | The [type of branch](https://github.com/semantic-release/semantic-release/blob/beta/docs/usage/workflow-configuration.md#branch-types). |
-| `branch.channel` | The distribution channel on which to publish releases from this branch. |
-| `branch.range` | The range of [semantic versions](https://semver.org) to support on this branch. |
-| `branch.prerelease` | The pre-release detonation to append to [semantic versions](https://semver.org) released from this branch. |
-| `lastRelease` | `Object` with `version`, `gitTag` and `gitHead` of the last release. |
-| `nextRelease` | `Object` with `version`, `gitTag`, `gitHead` and `notes` of the release being done. |
-
-**Note**: It is recommended to include `[skip ci]` in the commit message to not trigger a new build. Some CI service support the `[skip ci]` keyword only in the subject of the message.
-
-##### `message` examples
-
-The `message` `Release <%= nextRelease.version %> - <%= new Date().toLocaleDateString('en-US', {year: 'numeric', month: 'short', day: 'numeric', hour: 'numeric', minute: 'numeric' }) %> [skip ci]\n\n<%= nextRelease.notes %>` will generate the commit message:
-
-> Release v1.0.0 - Oct. 21, 2015 1:24 AM \[skip ci\]
## 1.0.0
### Features * Generate 1.21 gigawatts of electricity ...
-
-#### `assets`
-
-Can be an `Array` or a single entry. Each entry can be either:
-- a [glob](https://github.com/micromatch/micromatch#matching-features)
-- or an `Object` with a `path` property containing a [glob](https://github.com/micromatch/micromatch#matching-features).
-
-Each entry in the `assets` `Array` is globbed individually. A [glob](https://github.com/micromatch/micromatch#matching-features) can be a `String` (`"dist/**/*.js"` or `"dist/mylib.js"`) or an `Array` of `String`s that will be globbed together (`["dist/**", "!**/*.css"]`).
-
-If a directory is configured, all the files under this directory and its children will be included.
-
-**Note**: If a file has a match in `assets` it will be included even if it also has a match in `.gitignore`.
-
-##### `assets` examples
-
-`'dist/*.js'`: include all `js` files in the `dist` directory, but not in its sub-directories.
-
-`'dist/**/*.js'`: include all `js` files in the `dist` directory and its sub-directories.
-
-`[['dist', '!**/*.css']]`: include all files in the `dist` directory and its sub-directories excluding the `css` files.
-
-`[['dist', '!**/*.css'], 'package.json']`: include `package.json` and all files in the `dist` directory and its sub-directories excluding the `css` files.
-
-`[['dist/**/*.{js,css}', '!**/*.min.*']]`: include all `js` and `css` files in the `dist` directory and its sub-directories excluding the minified version.
-
-### Examples
-
-When used with the [@semantic-release/changelog](https://github.com/semantic-release/changelog) or [@semantic-release/npm](https://github.com/semantic-release/npm) plugins:
-- The [@semantic-release/changelog](https://github.com/semantic-release/changelog) plugin must be called first in order to update the changelog file so the `@semantic-release/git` and [@semantic-release/npm](https://github.com/semantic-release/npm) plugins can include it in the release.
-- The [@semantic-release/npm](https://github.com/semantic-release/npm) plugin must be called second in order to update the `package.json` file so the `@semantic-release/git` plugin can include it in the release commit.
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- "@semantic-release/changelog",
- "@semantic-release/npm",
- "@semantic-release/git"
- ],
-}
-```
-
-### GPG signature
-
-Using GPG, you can [sign and verify tags and commits](https://git-scm.com/book/id/v2/Git-Tools-Signing-Your-Work). With GPG keys, the release tags and commits made by Semantic-release are verified and other people can trust that they were really were made by your account.
-
-#### Generate the GPG keys
-
-If you already have a GPG public and private key you can skip this step and go to the [Get the GPG keys ID and the public key content](#get-the-gpg-keys-id-and-the-public-key-content) step.
-
-[Download and install the GPG command line tools](https://www.gnupg.org/download/#binary) for your operating system.
-
-Create a GPG key
-
-```bash
-$ gpg --full-generate-key
-```
-
-At the prompt select the `RSA and RSA` king of key, enter `4096` for the keysize, specify how long the key should be valid, enter yout name, the email associated with your Git hosted account and finally set a long and hard to guess passphrase.
-
-#### Get the GPG keys ID and the public key content
-
-Use the `gpg --list-secret-keys --keyid-format LONG` command to list your GPG keys. From the list, copy the GPG key ID you just created.
-
-```bash
-$ gpg --list-secret-keys --keyid-format LONG
-/Users//.gnupg/pubring.gpg
----------------------------------------
-sec rsa4096/XXXXXXXXXXXXXXXX 2017-12-01 [SC]
-uid
-ssb rsa4096/YYYYYYYYYYYYYYYY 2017-12-01 [E]
-```
-the GPG key ID if 16 character string, on the on the `sec` line, after `rsa4096`. In this example, the GPG key ID is `XXXXXXXXXXXXXXXX`.
-
-Export the public key (replace XXXXXXXXXXXXXXXX with your key ID):
-
-```bash
-$ gpg --armor --export XXXXXXXXXXXXXXXX
-```
-
-Copy your GPG key, beginning with -----BEGIN PGP PUBLIC KEY BLOCK----- and ending with -----END PGP PUBLIC KEY BLOCK-----
-
-#### Add the GPG key to your Git hosted account
-
-##### Add the GPG key to GitHub
-
-In GitHub **Settings**, click on **SSH and GPG keys** in the sidebar, then on the **New GPG Key** button.
-
-Paste the entire GPG key export previously and click the **Add GPG Key** button.
-
-See [Adding a new GPG key to your GitHub account](https://help.github.com/articles/adding-a-new-gpg-key-to-your-github-account/) for more details.
-
-### Use the GPG key to sign commit and tags locally
-
-If you want to use this GPG to also sign the commits and tags you create on your local machine you can follow the instruction at [Git Tools - Signing Your Work](https://git-scm.com/book/id/v2/Git-Tools-Signing-Your-Work)
-This step is optional and unrelated to Semantic-release.
-
-#### Add the GPG keys to your CI environment
-
-Make the public and private GPG key available on the CI environment. Encrypt the keys, commit it to your repository and configure the CI environment to decrypt it.
-
-##### Add the GPG keys to Travis CI
-
-Install the [Travis CLI](https://github.com/travis-ci/travis.rb#installation):
-
-```bash
-$ gem install travis
-```
-
-[Login](https://github.com/travis-ci/travis.rb#login) to Travis with the CLI:
-
-```bash
-$ travis login
-```
-
-Add the following [environment](https://github.com/travis-ci/travis.rb#env) variables to Travis:
-- `GPG_PASSPHRASE` to Travis with the value set during the [GPG keys generation](#generate-the-gpg-keys) step
-- `GPG_KEY_ID` to Travis with the value of your GPG key ID retrieved during the [GPG keys generation](#generate-the-gpg-keys) (replace XXXXXXXXXXXXXXXX with your key ID)
-- `GIT_EMAIL` with the email address you set during the [GPG keys generation](#generate-the-gpg-keys) step
-- `GIT_USERNAME` with the name you set during the [GPG keys generation](#generate-the-gpg-keys) step
-
-```bash
-$ travis env set GPG_PASSPHRASE
-$ travis env set GPG_KEY_ID XXXXXXXXXXXXXXXX
-$ travis env set GIT_EMAIL
-$ travis env set GIT_USERNAME
-```
-
-From your repository root export your public and private GPG keys in the `git_gpg_keys.asc` (replace XXXXXXXXXXXXXXXX with your key ID):
-
-```bash
-$ gpg --export -a XXXXXXXXXXXXXXXX > git_gpg_keys.asc
-$ gpg --export-secret-key -a XXXXXXXXXXXXXXXX >> git_gpg_keys.asc
-```
-
-[Encrypt](https://github.com/travis-ci/travis.rb#encrypt) the `git_gpg_keys.asc` (public and private key) using a symmetric encryption (AES-256), and store the secret in a secure environment variable in the Travis environment:
-
-```bash
-$ travis encrypt-file git_gpg_keys.asc
-```
-The `travis encrypt-file` will encrypt the keys into the `git_gpg_keys.asc.enc` file and output in the console the command to add to your `.travis.yml` file. It should look like `openssl aes-256-cbc -K $encrypted_AAAAAAAAAAAA_key -iv $encrypted_BBBBBBBBBBBB_iv -in git_gpg_keys.asc.enc -out git_gpg_keys.asc -d`.
-
-Copy this command to your `.travis.yml` file in the `before_install` step. Change the output path to write the unencrypted key in `/tmp`: `-out git_gpg_keys.asc` => `/tmp/git_gpg_keys.asc`. This will avoid to commit / modify / delete the unencrypted keys by mistake on the CI. Then add the commands to decrypt the GPG keys and make it available to `git`:
-
-```yaml
-before_install:
- # Decrypt the git_gpg_keys.asc.enc key into /tmp/git_gpg_keys.asc
- - openssl aes-256-cbc -K $encrypted_AAAAAAAAAAAA_key -iv $encrypted_BBBBBBBBBBBB_iv -in git_gpg_keys.asc.enc -out /tmp/git_gpg_keys.asc -d
- # Make sure only the current user can read the keys
- - chmod 600 /tmp/git_gpg_keys.asc
- # Import the gpg key
- - gpg --batch --yes --import /tmp/git_gpg_keys.asc
- # Create a script that pass the passphrase to the gpg CLI called by git
- - echo '/usr/bin/gpg2 --passphrase ${GPG_PASSPHRASE} --batch --no-tty "$@"' > /tmp/gpg-with-passphrase && chmod +x /tmp/gpg-with-passphrase
- # Configure git to use the script that passes the passphrase
- - git config gpg.program "/tmp/gpg-with-passphrase"
- # Configure git to sign the commits and tags
- - git config commit.gpgsign true
- # Configure git to use your GPG key
- - git config --global user.signingkey ${GPG_KEY_ID}
-```
-
-See [Encrypting Files](https://docs.travis-ci.com/user/encrypting-files/) for more details.
-
-Delete the local keys as it won't be used anymore:
-
-```bash
-$ rm git_gpg_keys.asc
-```
-
-Commit the encrypted keys and the `.travis.yml` file to your repository:
-
-```bash
-$ git add git_gpg_keys.asc.enc .travis.yml
-$ git commit -m "ci(travis): Add the encrypted GPG keys"
-$ git push
-```
diff --git a/node_modules/@semantic-release/github/README.md b/node_modules/@semantic-release/github/README.md
deleted file mode 100644
index 3f87d33..0000000
--- a/node_modules/@semantic-release/github/README.md
+++ /dev/null
@@ -1,221 +0,0 @@
-# @semantic-release/github
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a
-[GitHub release](https://help.github.com/articles/about-releases) and comment on released Pull Requests/Issues.
-
-[](https://github.com/semantic-release/github/actions?query=workflow%3ATest+branch%3Amaster)
-
-[](https://www.npmjs.com/package/@semantic-release/github)
-[](https://www.npmjs.com/package/@semantic-release/github)
-[](https://www.npmjs.com/package/@semantic-release/github)
-
-| Step | Description |
-|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `verifyConditions` | Verify the presence and the validity of the authentication (set via [environment variables](#environment-variables)) and the [assets](#assets) option configuration. |
-| `publish` | Publish a [GitHub release](https://help.github.com/articles/about-releases), optionally uploading file assets. |
-| `addChannel` | Update a [GitHub release](https://help.github.com/articles/about-releases)'s `pre-release` field. |
-| `success` | Add a comment to each [GitHub Issue](https://help.github.com/articles/about-issues) or [Pull Request](https://help.github.com/articles/about-pull-requests) resolved by the release and close issues previously open by the `fail` step. |
-| `fail` | Open or update a [GitHub Issue](https://help.github.com/articles/about-issues) with information about the errors that caused the release to fail. |
-
-## Install
-
-```bash
-$ npm install @semantic-release/github -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- ["@semantic-release/github", {
- "assets": [
- {"path": "dist/asset.min.css", "label": "CSS distribution"},
- {"path": "dist/asset.min.js", "label": "JS distribution"}
- ]
- }],
- ]
-}
-```
-
-With this example [GitHub releases](https://help.github.com/articles/about-releases) will be published with the file `dist/asset.min.css` and `dist/asset.min.js`.
-
-## Configuration
-
-### GitHub authentication
-
-The GitHub authentication configuration is **required** and can be set via [environment variables](#environment-variables).
-
-Follow the [Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) documentation to obtain an authentication token. The token has to be made available in your CI environment via the `GH_TOKEN` environment variable. The user associated with the token must have push permission to the repository.
-
-When creating the token, the **minimum required scopes** are:
-
-- [`repo`](https://github.com/settings/tokens/new?scopes=repo) for a private repository
-- [`public_repo`](https://github.com/settings/tokens/new?scopes=public_repo) for a public repository
-
-_Notes on GitHub Actions:_ You can use the default token which is provided in the secret _GITHUB_TOKEN_. However releases done with this token will NOT trigger release events to start other workflows.
-If you have actions that trigger on newly created releases, please use a generated token for that and store it in your repository's secrets (any other name than GITHUB_TOKEN is fine).
-
-When using the _GITHUB_TOKEN_, the **minimum required permissions** are:
-
-- `contents: write` to be able to publish a GitHub release
-- `issues: write` to be able to comment on released issues
-- `pull-requests: write` to be able to comment on released pull requests
-
-### Environment variables
-
-| Variable | Description |
-| -------------------------------------------------- | --------------------------------------------------------- |
-| `GH_TOKEN` or `GITHUB_TOKEN` | **Required.** The token used to authenticate with GitHub. |
-| `GITHUB_API_URL` or `GH_URL` or `GITHUB_URL` | The GitHub Enterprise endpoint. |
-| `GH_PREFIX` or `GITHUB_PREFIX` | The GitHub Enterprise API prefix. |
-
-### Options
-
-| Option | Description | Default |
-|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `githubUrl` | The GitHub Enterprise endpoint. | `GH_URL` or `GITHUB_URL` environment variable. |
-| `githubApiPathPrefix` | The GitHub Enterprise API prefix. | `GH_PREFIX` or `GITHUB_PREFIX` environment variable. |
-| `proxy` | The proxy to use to access the GitHub API. Set to `false` to disable usage of proxy. See [proxy](#proxy). | `HTTP_PROXY` environment variable. |
-| `assets` | An array of files to upload to the release. See [assets](#assets). | - |
-| `successComment` | The comment to add to each issue and pull request resolved by the release. Set to `false` to disable commenting on issues and pull requests. See [successComment](#successcomment). | `:tada: This issue has been resolved in version ${nextRelease.version} :tada:\n\nThe release is available on [GitHub release]()` |
-| `failComment` | The content of the issue created when a release fails. Set to `false` to disable opening an issue when a release fails. See [failComment](#failcomment). | Friendly message with links to **semantic-release** documentation and support, with the list of errors that caused the release to fail. |
-| `failTitle` | The title of the issue created when a release fails. Set to `false` to disable opening an issue when a release fails. | `The automated release is failing 🚨` |
-| `labels` | The [labels](https://help.github.com/articles/about-labels) to add to the issue created when a release fails. Set to `false` to not add any label. | `['semantic-release']` |
-| `assignees` | The [assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users) to add to the issue created when a release fails. | - |
-| `releasedLabels` | The [labels](https://help.github.com/articles/about-labels) to add to each issue and pull request resolved by the release. Set to `false` to not add any label. See [releasedLabels](#releasedlabels). | `['released<%= nextRelease.channel ? \` on @\${nextRelease.channel}\` : "" %>']- |
-| `addReleases` | Will add release links to the GitHub Release. Can be `false`, `"bottom"` or `"top"`. See [addReleases](#addReleases). | `false` |
-
-#### proxy
-
-Can be `false`, a proxy URL or an `Object` with the following properties:
-
-| Property | Description | Default |
-|---------------|----------------------------------------------------------------|--------------------------------------|
-| `host` | **Required.** Proxy host to connect to. | - |
-| `port` | **Required.** Proxy port to connect to. | File name extracted from the `path`. |
-| `secureProxy` | If `true`, then use TLS to connect to the proxy. | `false` |
-| `headers` | Additional HTTP headers to be sent on the HTTP CONNECT method. | - |
-
-See [node-https-proxy-agent](https://github.com/TooTallNate/node-https-proxy-agent#new-httpsproxyagentobject-options) and [node-http-proxy-agent](https://github.com/TooTallNate/node-http-proxy-agent) for additional details.
-
-##### proxy examples
-
-`'http://168.63.76.32:3128'`: use the proxy running on host `168.63.76.32` and port `3128` for each GitHub API request.
-`{host: '168.63.76.32', port: 3128, headers: {Foo: 'bar'}}`: use the proxy running on host `168.63.76.32` and port `3128` for each GitHub API request, setting the `Foo` header value to `bar`.
-
-#### assets
-
-Can be a [glob](https://github.com/isaacs/node-glob#glob-primer) or and `Array` of
-[globs](https://github.com/isaacs/node-glob#glob-primer) and `Object`s with the following properties:
-
-| Property | Description | Default |
-| -------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------ |
-| `path` | **Required.** A [glob](https://github.com/isaacs/node-glob#glob-primer) to identify the files to upload. | - |
-| `name` | The name of the downloadable file on the GitHub release. | File name extracted from the `path`. |
-| `label` | Short description of the file displayed on the GitHub release. | - |
-
-Each entry in the `assets` `Array` is globbed individually. A [glob](https://github.com/isaacs/node-glob#glob-primer)
-can be a `String` (`"dist/**/*.js"` or `"dist/mylib.js"`) or an `Array` of `String`s that will be globbed together
-(`["dist/**", "!**/*.css"]`).
-
-If a directory is configured, all the files under this directory and its children will be included.
-
-The `name` and `label` for each assets are generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
-
-| Parameter | Description |
-|---------------|-------------------------------------------------------------------------------------|
-| `branch` | The branch from which the release is done. |
-| `lastRelease` | `Object` with `version`, `gitTag` and `gitHead` of the last release. |
-| `nextRelease` | `Object` with `version`, `gitTag`, `gitHead` and `notes` of the release being done. |
-| `commits` | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`. |
-
-**Note**: If a file has a match in `assets` it will be included even if it also has a match in `.gitignore`.
-
-##### assets examples
-
-`'dist/*.js'`: include all the `js` files in the `dist` directory, but not in its sub-directories.
-
-`[['dist', '!**/*.css']]`: include all the files in the `dist` directory and its sub-directories excluding the `css`
-files.
-
-`[{path: 'dist/MyLibrary.js', label: 'MyLibrary JS distribution'}, {path: 'dist/MyLibrary.css', label: 'MyLibrary CSS
-distribution'}]`: include the `dist/MyLibrary.js` and `dist/MyLibrary.css` files, and label them `MyLibrary JS
-distribution` and `MyLibrary CSS distribution` in the GitHub release.
-
-`[['dist/**/*.{js,css}', '!**/*.min.*'], {path: 'build/MyLibrary.zip', label: 'MyLibrary'}]`: include all the `js` and
-`css` files in the `dist` directory and its sub-directories excluding the minified version, plus the
-`build/MyLibrary.zip` file and label it `MyLibrary` in the GitHub release.
-
-`[{path: 'dist/MyLibrary.js', name: 'MyLibrary-${nextRelease.gitTag}.js', label: 'MyLibrary JS (${nextRelease.gitTag}) distribution'}]`: include the file `dist/MyLibrary.js` and upload it to the GitHub release with name `MyLibrary-v1.0.0.js` and label `MyLibrary JS (v1.0.0) distribution` which will generate the link:
-
-> `[MyLibrary JS (v1.0.0) distribution](MyLibrary-v1.0.0.js)`
-
-#### successComment
-
-The message for the issue comments is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
-
-| Parameter | Description |
-|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `branch` | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done. |
-| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release. |
-| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done. |
-| `commits` | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`. |
-| `releases` | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`. |
-| `issue` | A [GitHub API pull request object](https://developer.github.com/v3/search/#search-issues) for pull requests related to a commit, or an `Object` with the `number` property for issues resolved via [keywords](https://help.github.com/articles/closing-issues-using-keywords) |
-
-##### successComment example
-
-The `successComment` `This ${issue.pull_request ? 'pull request' : 'issue'} is included in version ${nextRelease.version}` will generate the comment:
-
-> This pull request is included in version 1.0.0
-
-#### failComment
-
-The message for the issue content is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
-
-| Parameter | Description |
-|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `branch` | The branch from which the release had failed. |
-| `errors` | An `Array` of [SemanticReleaseError](https://github.com/semantic-release/error). Each error has the `message`, `code`, `pluginName` and `details` properties. `pluginName` contains the package name of the plugin that threw the error. `details` contains a information about the error formatted in markdown. |
-
-##### failComment example
-
-The `failComment` `This release from branch ${branch.name} had failed due to the following errors:\n- ${errors.map(err => err.message).join('\\n- ')}` will generate the comment:
-
-> This release from branch master had failed due to the following errors:
-> - Error message 1
-> - Error message 2
-
-#### releasedLabels
-
-Each label name is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
-
-| Parameter | Description |
-|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `branch` | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done. |
-| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release. |
-| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done. |
-| `commits` | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`. |
-| `releases` | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`. |
-| `issue` | A [GitHub API pull request object](https://developer.github.com/v3/search/#search-issues) for pull requests related to a commit, or an `Object` with the `number` property for issues resolved via [keywords](https://help.github.com/articles/closing-issues-using-keywords) |
-
-##### releasedLabels example
-
-The `releasedLabels` ```['released<%= nextRelease.channel ? ` on @\${nextRelease.channel}` : "" %> from <%= branch.name %>']``` will generate the label:
-
-> released on @next from branch next
-
-#### addReleases
-
-Add links to other releases to the GitHub release body.
-
-Valid values for this option are `false`, `"top"` or `"bottom"`.
-
-##### addReleases example
-
-See [The introducing PR](https://github.com/semantic-release/github/pull/282) for an example on how it will look.
\ No newline at end of file
diff --git a/node_modules/@semantic-release/npm/README.md b/node_modules/@semantic-release/npm/README.md
deleted file mode 100644
index 1188eaa..0000000
--- a/node_modules/@semantic-release/npm/README.md
+++ /dev/null
@@ -1,130 +0,0 @@
-# @semantic-release/npm
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a [npm](https://www.npmjs.com) package.
-
-[](https://github.com/semantic-release/npm/actions?query=workflow%3ATest+branch%3Amaster) [](https://www.npmjs.com/package/@semantic-release/npm)
-[](https://www.npmjs.com/package/@semantic-release/npm)
-[](https://www.npmjs.com/package/@semantic-release/npm)
-
-| Step | Description |
-|--------------------|-------------|
-| `verifyConditions` | Verify the presence of the `NPM_TOKEN` environment variable, or an `.npmrc` file, and verify the authentication method is valid. |
-| `prepare` | Update the `package.json` version and [create](https://docs.npmjs.com/cli/pack) the npm package tarball. |
-| `addChannel` | [Add a release to a dist-tag](https://docs.npmjs.com/cli/dist-tag). |
-| `publish` | [Publish the npm package](https://docs.npmjs.com/cli/publish) to the registry. |
-
-## Install
-
-```bash
-$ npm install @semantic-release/npm -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- "@semantic-release/npm",
- ]
-}
-```
-
-## Configuration
-
-### Npm registry authentication
-
-The npm authentication configuration is **required** and can be set via [environment variables](#environment-variables).
-
-Both the [token](https://docs.npmjs.com/getting-started/working_with_tokens) and the legacy (`username`, `password` and `email`) authentication are supported. It is recommended to use the [token](https://docs.npmjs.com/getting-started/working_with_tokens) authentication. The legacy authentication is supported as the alternative npm registries [Artifactory](https://www.jfrog.com/open-source/#os-arti) and [npm-registry-couchapp](https://github.com/npm/npm-registry-couchapp) only supports that form of authentication.
-
-**Notes**:
-- Only the `auth-only` [level of npm two-factor authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication#levels-of-authentication) is supported, **semantic-release** will not work with the default `auth-and-writes` level.
-- The presence of an `.npmrc` file will override any specified environment variables.
-
-### Environment variables
-
-| Variable | Description |
-| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `NPM_TOKEN` | Npm token created via [npm token create](https://docs.npmjs.com/getting-started/working_with_tokens#how-to-create-new-tokens) |
-| `NPM_USERNAME` | Npm username created via [npm adduser](https://docs.npmjs.com/cli/adduser) or on [npmjs.com](https://www.npmjs.com) |
-| `NPM_PASSWORD` | Password of the npm user. |
-| `NPM_EMAIL` | Email address associated with the npm user |
-| `NPM_CONFIG_USERCONFIG` | Path to non-default .npmrc file |
-
-Use either `NPM_TOKEN` for token authentication or `NPM_USERNAME`, `NPM_PASSWORD` and `NPM_EMAIL` for legacy authentication
-
-### Options
-
-| Options | Description | Default |
-|--------------|---------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
-| `npmPublish` | Whether to publish the `npm` package to the registry. If `false` the `package.json` version will still be updated. | `false` if the `package.json` [private](https://docs.npmjs.com/files/package.json#private) property is `true`, `true` otherwise. |
-| `pkgRoot` | Directory path to publish. | `.` |
-| `tarballDir` | Directory path in which to write the package tarball. If `false` the tarball is not be kept on the file system. | `false` |
-
-**Note**: The `pkgRoot` directory must contain a `package.json`. The version will be updated only in the `package.json` and `npm-shrinkwrap.json` within the `pkgRoot` directory.
-
-**Note**: If you use a [shareable configuration](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/shareable-configurations.md#shareable-configurations) that defines one of these options you can set it to `false` in your [**semantic-release** configuration](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration) in order to use the default value.
-
-### Npm configuration
-
-The plugin uses the [`npm` CLI](https://github.com/npm/cli) which will read the configuration from [`.npmrc`](https://docs.npmjs.com/files/npmrc). See [`npm config`](https://docs.npmjs.com/misc/config) for the option list.
-
-The [`registry`](https://docs.npmjs.com/misc/registry) can be configured via the npm environment variable `NPM_CONFIG_REGISTRY` and will take precedence over the configuration in `.npmrc`.
-
-The [`registry`](https://docs.npmjs.com/misc/registry) and [`dist-tag`](https://docs.npmjs.com/cli/dist-tag) can be configured in the `package.json` and will take precedence over the configuration in `.npmrc` and `NPM_CONFIG_REGISTRY`:
-```json
-{
- "publishConfig": {
- "registry": "https://registry.npmjs.org/",
- "tag": "latest"
- }
-}
-```
-
-### Examples
-
-The `npmPublish` and `tarballDir` option can be used to skip the publishing to the `npm` registry and instead, release the package tarball with another plugin. For example with the [@semantic-release/github](https://github.com/semantic-release/github) plugin:
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- ["@semantic-release/npm", {
- "npmPublish": false,
- "tarballDir": "dist",
- }],
- ["@semantic-release/github", {
- "assets": "dist/*.tgz"
- }]
- ]
-}
-```
-
-When publishing from a sub-directory with the `pkgRoot` option, the `package.json` and `npm-shrinkwrap.json` updated with the new version can be moved to another directory with a `postversion`. For example with the [@semantic-release/git](https://github.com/semantic-release/git) plugin:
-
-```json
-{
- "plugins": [
- "@semantic-release/commit-analyzer",
- "@semantic-release/release-notes-generator",
- ["@semantic-release/npm", {
- "pkgRoot": "dist",
- }],
- ["@semantic-release/git", {
- "assets": ["package.json", "npm-shrinkwrap.json"]
- }]
- ]
-}
-```
-```json
-{
- "scripts": {
- "postversion": "cp -r package.json .. && cp -r npm-shrinkwrap.json .."
- }
-}
-```
diff --git a/node_modules/@semantic-release/release-notes-generator/README.md b/node_modules/@semantic-release/release-notes-generator/README.md
deleted file mode 100644
index 96c90e7..0000000
--- a/node_modules/@semantic-release/release-notes-generator/README.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# **release-notes-generator**
-
-[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to generate changelog content with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
-
-[](https://github.com/semantic-release/release-notes-generator/actions?query=workflow%3ATest+branch%3Amaster) [](https://www.npmjs.com/package/@semantic-release/release-notes-generator)
-[](https://www.npmjs.com/package/@semantic-release/release-notes-generator)
-
-| Step | Description |
-|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `generateNotes` | Generate release notes for the commits added since the last release with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog). |
-
-## Install
-
-```bash
-$ npm install @semantic-release/release-notes-generator -D
-```
-
-## Usage
-
-The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
-
-```json
-{
- "plugins": [
- ["@semantic-release/commit-analyzer", {
- "preset": "angular",
- "parserOpts": {
- "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"]
- }
- }],
- ["@semantic-release/release-notes-generator", {
- "preset": "angular",
- "parserOpts": {
- "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"]
- },
- "writerOpts": {
- "commitsSort": ["subject", "scope"]
- }
- }]
- ]
-}
-```
-
-With this example:
-- the commits that contains `BREAKING CHANGE`, `BREAKING CHANGES` or `BREAKING` in their body will be considered breaking changes (by default the [angular preset](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular/index.js#L14) checks only for `BREAKING CHANGE` and `BREAKING CHANGES`)
-- the commits will be sorted in the changelog by `subject` then `scope` (by default the [angular preset](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular/index.js#L90) sort the commits in the changelog by `scope` then `subject`)
-
-## Configuration
-
-### Options
-
-| Option | Description | Default |
-|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `preset` | [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset (possible values: [`angular`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular), [`atom`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-atom), [`codemirror`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-codemirror), [`ember`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-ember), [`eslint`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-eslint), [`express`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-express), [`jquery`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-jquery), [`jshint`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-jshint), [`conventionalcommits`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-conventionalcommits)). | [`angular`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular) |
-| `config` | NPM package name of a custom [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset. | - |
-| `parserOpts` | Additional [conventional-commits-parser](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser#conventionalcommitsparseroptions) options that will extends the ones loaded by `preset` or `config`. This is convenient to use a [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset with some customizations without having to create a new module. | - |
-| `writerOpts` | Additional [conventional-commits-writer](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-writer#options) options that will extends the ones loaded by `preset` or `config`. This is convenient to use a [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset with some customizations without having to create a new module. | - |
-| `host` | The host used to generate links to issues and commits. See [conventional-changelog-writer#host](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-writer#host). | The host from the [`repositoryurl` option](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#repositoryurl). |
-| `linkCompare` | Whether to include a link to compare changes since previous release in the release note. | `true` |
-| `linkReferences` | Whether to include a link to issues and commits in the release note. See [conventional-changelog-writer#linkreferences](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-writer#linkreferences). | `true` |
-| `commit` | Keyword used to generate commit links (formatted as `////`). See [conventional-changelog-writer#commit](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-writer#commit). | `commits` for Bitbucket repositories, `commit` otherwise |
-| `issue` | Keyword used to generate issue links (formatted as `////`). See [conventional-changelog-writer#issue](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-writer#issue). | `issue` for Bitbucket repositories, `issues` otherwise |
-| `presetConfig` | Additional configuration passed to the [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) preset. Used for example with [conventional-changelog-conventionalcommits](https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.0.0/README.md). | - |
-
-**Notes**: in order to use a `preset` it must be installed (for example to use the [eslint preset](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-eslint) you must install it with `npm install conventional-changelog-eslint -D`)
-
-**Note**: `config` will be overwritten by the values of `preset`. You should use either `preset` or `config`, but not both.
-
-**Note**: Individual properties of `parserOpts` and `writerOpts` will override ones loaded with an explicitly set `preset` or `config`. If `preset` or `config` are not set, only the properties set in `parserOpts` and `writerOpts` will be used.
-
-**Note**: For presets that expects a configuration object, such as [`conventionalcommits`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-conventionalcommits), the `presetConfig` option **must** be set.
diff --git a/node_modules/@semantic-release/release-notes-generator/node_modules/find-up/readme.md b/node_modules/@semantic-release/release-notes-generator/node_modules/find-up/readme.md
deleted file mode 100644
index d6a21e5..0000000
--- a/node_modules/@semantic-release/release-notes-generator/node_modules/find-up/readme.md
+++ /dev/null
@@ -1,156 +0,0 @@
-# find-up [](https://travis-ci.org/sindresorhus/find-up)
-
-> Find a file or directory by walking up parent directories
-
-
-## Install
-
-```
-$ npm install find-up
-```
-
-
-## Usage
-
-```
-/
-└── Users
- └── sindresorhus
- ├── unicorn.png
- └── foo
- └── bar
- ├── baz
- └── example.js
-```
-
-`example.js`
-
-```js
-const path = require('path');
-const findUp = require('find-up');
-
-(async () => {
- console.log(await findUp('unicorn.png'));
- //=> '/Users/sindresorhus/unicorn.png'
-
- console.log(await findUp(['rainbow.png', 'unicorn.png']));
- //=> '/Users/sindresorhus/unicorn.png'
-
- console.log(await findUp(async directory => {
- const hasUnicorns = await findUp.exists(path.join(directory, 'unicorn.png'));
- return hasUnicorns && directory;
- }, {type: 'directory'}));
- //=> '/Users/sindresorhus'
-})();
-```
-
-
-## API
-
-### findUp(name, options?)
-### findUp(matcher, options?)
-
-Returns a `Promise` for either the path or `undefined` if it couldn't be found.
-
-### findUp([...name], options?)
-
-Returns a `Promise` for either the first path found (by respecting the order of the array) or `undefined` if none could be found.
-
-### findUp.sync(name, options?)
-### findUp.sync(matcher, options?)
-
-Returns a path or `undefined` if it couldn't be found.
-
-### findUp.sync([...name], options?)
-
-Returns the first path found (by respecting the order of the array) or `undefined` if none could be found.
-
-#### name
-
-Type: `string`
-
-Name of the file or directory to find.
-
-#### matcher
-
-Type: `Function`
-
-A function that will be called with each directory until it returns a `string` with the path, which stops the search, or the root directory has been reached and nothing was found. Useful if you want to match files with certain patterns, set of permissions, or other advanced use-cases.
-
-When using async mode, the `matcher` may optionally be an async or promise-returning function that returns the path.
-
-#### options
-
-Type: `object`
-
-##### cwd
-
-Type: `string`
-Default: `process.cwd()`
-
-Directory to start from.
-
-##### type
-
-Type: `string`
-Default: `'file'`
-Values: `'file'` `'directory'`
-
-The type of paths that can match.
-
-##### allowSymlinks
-
-Type: `boolean`
-Default: `true`
-
-Allow symbolic links to match if they point to the chosen path type.
-
-### findUp.exists(path)
-
-Returns a `Promise` of whether the path exists.
-
-### findUp.sync.exists(path)
-
-Returns a `boolean` of whether the path exists.
-
-#### path
-
-Type: `string`
-
-Path to a file or directory.
-
-### findUp.stop
-
-A [`Symbol`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) that can be returned by a `matcher` function to stop the search and cause `findUp` to immediately return `undefined`. Useful as a performance optimization in case the current working directory is deeply nested in the filesystem.
-
-```js
-const path = require('path');
-const findUp = require('find-up');
-
-(async () => {
- await findUp(directory => {
- return path.basename(directory) === 'work' ? findUp.stop : 'logo.png';
- });
-})();
-```
-
-
-## Related
-
-- [find-up-cli](https://github.com/sindresorhus/find-up-cli) - CLI for this module
-- [pkg-up](https://github.com/sindresorhus/pkg-up) - Find the closest package.json file
-- [pkg-dir](https://github.com/sindresorhus/pkg-dir) - Find the root directory of an npm package
-- [resolve-from](https://github.com/sindresorhus/resolve-from) - Resolve the path of a module like `require.resolve()` but from a given path
-
-
----
-
-