Upgrade dependencies

README.md

@@ -9,7 +9,7 @@
   <a href="https://bump.sh/users/sign_up">Sign up</a>
 </p>
 
-The Bump.sh CLI is used to interact with your API documentation or hubs hosted on Bump.sh. With any API definition of your choice (from Swagger, OpenAPI or AsyncAPI), it can help you to:
+The Bump.sh CLI is used to interact with your API documentation or hubs hosted on Bump.sh. With any API definition of your choice (from Swagger, OpenAPI, or AsyncAPI), it can help you to:
 
 - Validate an API document before publishing it to your documentation
 - Publish an API document to your Bump.sh documentation or hubs
@@ -32,9 +32,8 @@ Under the hood, it uses the API of [developers.bump.sh](https://developers.bump.
 
 ## Installation
 
-The Bump.sh CLI is a node package currently distributed via NPM. This means you must have the Node v14+ interpreter installed on your computer or CI servers.
-
-_If you are looking to use Bump.sh in a continuous integration environment you might be interested by [our Github Action](https://github.com/marketplace/actions/api-documentation-on-bump)._
+The Bump.sh CLI is a node package currently distributed via NPM. You must have the Node v14+ interpreter installed on your computer or CI servers.
+_If you are looking to use Bump.sh in a continuous integration environment you might be interested in [our GitHub Action](https://github.com/marketplace/actions/bump-sh)._
 
 > You can download a standalone package directly from the latest
 > GitHub release assets if you don’t use Node.
@@ -56,7 +55,7 @@ yarn global add bump-cli
 
 ### Add Bump.sh to your node project
 
-As our CLI is a node package, you can easily embed it into your project by adding the package to your `package.json` file, either with NPM
+As our CLI is a node package, you can easily embed it to your project by adding the package to your `package.json` file, either with NPM
 
 ```sh-session
 npm install --save-dev bump-cli
@@ -74,7 +73,7 @@ You can then use any Bump.sh commands with `npx` (same as `npm exec`)
 npx bump --help
 ```
 
-### How should I do if I'm not using npm ?
+### How should I do if I'm not using npm?
 
 Unfortunately, at the moment we only support the Node environment. However, you can download a standalone package directly from the [latest Github release](https://github.com/bump-sh/cli/releases) assets which you can run as a standalone binary. Or you can push your documentation using [our API](https://developers.bump.sh/) (advanced usage only).
 
@@ -87,7 +86,7 @@ $ bump --help
 The Bump.sh CLI is used to interact with your API documentation hosted on Bump.sh by using the API of developers.bump.sh
 
 VERSION
-  bump-cli/2.8.0 linux-x64 node-v16.19.0
+  bump-cli/2.7.2 linux-x64 node-v16.17.0
 
 USAGE
   $ bump [COMMAND]
@@ -96,7 +95,6 @@ COMMANDS
   deploy   Create a new version of your documentation from the given file or URL.
   diff     Get a comparison diff with your documentation from the given file or URL.
   help     Display help for bump.
-  overlay  Apply an OpenAPI specified overlay to your API definition.
   preview  Create a documentation preview from the given file or URL.
 ```
 
@@ -113,7 +111,6 @@ Head over to your Documentation settings in the “CI deployment” section or y
 * [`bump deploy [FILE]`](#bump-deploy-file)
 * [`bump diff [FILE]`](#bump-diff-file)
 * [`bump preview [FILE]`](#bump-preview-file)
-* [`bump overlay [DEFINITION_FILE] [OVERLAY_FILE]`](#bump-overlay-definition_file-overlay_file)
 
 ### `bump deploy [FILE]`
 
@@ -123,7 +120,7 @@ When you update your API, you also want its documentation to be up to date for y
 bump deploy path/to/api-document.yml --doc my-documentation --token $DOC_TOKEN
 ```
 
-> You can find your own `my-documentation` slug and `$DOC_TOKEN` api key from your [documentation settings](https://bump.sh/docs).
+> You can find your own `my-documentation` slug and `$DOC_TOKEN` API key from your [documentation settings](https://bump.sh/docs).
 {: .info}
 
 You can also deploy a given API document to a different branch of your documentation with the `--branch <branch-name>` parameter. Please note the branch will be created if it doesn’t exist. More details about the branching feature are available on [this dedicated help page](https://docs.bump.sh/help/branching). E.g. deploy the API document to the `staging` branch of the documentation:
@@ -140,7 +137,7 @@ If you already have a hub in your [Bump.sh](https://bump.sh) account, you can au
 bump deploy dir/path/to/apis/ --auto-create --hub my-hub --token $HUB_TOKEN
 ```
 
-> You can find your own `my-hub` slug and `$HUB_TOKEN` api key from your [hub settings](https://bump.sh/hubs).
+> You can find your own `my-hub` slug and `$HUB_TOKEN` API key from your [hub settings](https://bump.sh/hubs).
 {: .info}
 
 Please note, by default, only files named `{slug}-api.[format]` are published. Where `{slug}` is a name for your API and `[format]` is either `yaml` or `json`. Adjust to your file naming convention using the `--filename-pattern <pattern>` option.
@@ -158,7 +155,7 @@ path/to/apis
 └─ README.md
 ```
 
-In order to deploy the 3 services API definition files from this folder (`private-api-users-service.json`, `partner-api-payments-service.yml` and `public-api-contracts-service.yml`), you can execute the following command:
+To deploy the 3 services API definition files from this folder (`private-api-users-service.json`, `partner-api-payments-service.yml` and `public-api-contracts-service.yml`), you can execute the following command:
 
 ```
 bump deploy path/to/apis/ --hub my-hub --filename-pattern '*-api-{slug}-service'
@@ -176,7 +173,7 @@ Please check `bump deploy --help` for more usage details.
 
 ### `bump diff [FILE]`
 
-_If you want to receive automatic `bump diff` results on your Github Pull Requests you might be interested by [our Github Action](https://github.com/marketplace/actions/api-documentation-on-bump#api-diff-on-pull-requests) diff command._
+_If you want to receive automatic `bump diff` results on your Github Pull Requests you might be interested by [our Github Action](https://github.com/marketplace/actions/bump-sh#diff-on-pull-requests-only) diff command._
 
 Please note that by default the command will always exit with a
 successful return code. If you want to use this command in a CI
@@ -244,7 +241,7 @@ bump preview --live --open openapi-definition.json
 ```
 
 - Edit your `openapi-definition.json` file in your favorite text editor
-- Watch the live preview being updated each time you save your file.
+- Watch the live preview is updated each time you save your file.
 
 > You can create as many previews as you like without being authenticated. This is a **free and unlimited service**.
 {: .info}
@@ -253,26 +250,6 @@ _Note: the additional `--open` flag helps to automatically open the preview URL
 
 Please check `bump preview --help` for more usage details
 
-### `bump overlay [DEFINITION_FILE] [OVERLAY_FILE]`
-
-> This feature implements the [OpenAPI Overlay specification](https://github.com/OAI/Overlay-Specification). It is possible to apply an Overlay to any kind of document, be it an OpenAPI or AsyncAPI definition file.
-
-The Overlay specification of OpenAPI makes it possible to modify the content of an API definition file by adding a layer on top of it. That layer helps add, remove, or change some or all of the content of the original definition. 
-
-Technically, the `bump overlay` command will output a modified version of the `[DEFINITION_FILE]` (an OpenAPI or AsyncAPI document) by applying the operations described in the `[OVERLAY_FILE]` Overlay file to the original API document.
-
-To redirect the output of the command to a new file you can run the following:
-
-```shell
-bump overlay api-document.yaml overlay-file.yaml > api-overlayed-document.yaml
-```
-
-_Note: you can also apply the overlay during the [`bump deploy` command]((#bump-deploy-file)) with the new `--overlay` flag:_
-
-```shell
-bump deploy api-document.yaml --doc my-doc --token my-token --overlay overlay-file.yaml 
-```
-
 ## Development
 
 Make sure to have Node.js (At least v14) installed on your machine.
@@ -311,10 +288,6 @@ We currently support [OpenAPI](https://github.com/OAI/OpenAPI-Specification) fro
 
 Bug reports and pull requests are welcome on GitHub at <https://github.com/bump-sh/cli>. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
 
-## Thanks
-
-- [Lorna Mitchel](https://github.com/lornajane/) for [openapi-overlay-js](https://github.com/lornajane/openapi-overlays-js)
-
 ## License
 
 The Bump CLI project is released under the [MIT License](http://opensource.org/licenses/MIT).
@@ -327,6 +300,6 @@ Everyone interacting in the Bump-CLI project codebases, issue trackers, chat roo
 
 This npm package starts at v2.0.0 for two main reasons:
 
-- Our [first version](https://github.com/bump-sh/bump-cli) of the Bump CLI was written in Ruby, starting at v2.0.0, which makes it clear we are working on our second version of the Bump CLI
+- Our [first version](https://github.com/bump-sh/bump-cli) of the Bump CLI was written in Ruby, starting at v2.0.0, makes it clear we are working on our second version of the Bump CLI
 
 - The `bump-cli` package used to be [owned by Rico](https://github.com/rstacruz) which already published v1.x packages. If you are looking for the old npm package please head to [`@rstacruz/bump-cli` package](https://www.npmjs.com/package/@rstacruz/bump-cli). _A big thanks to Rico for transferring the ownership of the `bump-cli` package name!_

bin/dev

@@ -0,0 +1,5 @@
+#!/usr/bin/env -S node --loader ts-node/esm
+
+require('@oclif/command').run()
+.then(require('@oclif/command/flush'))
+.catch(require('@oclif/errors/handle'))

bin/run

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
 
-require('@oclif/command').run()
-.then(require('@oclif/command/flush'))
-.catch(require('@oclif/errors/handle'))
+const oclif = require('@oclif/core');
+
+oclif.run().then(require('@oclif/core/flush')).catch(require('@oclif/core/handle'));

examples/valid/overlay.yaml

@@ -25,10 +25,6 @@ actions:
     description: Remove all other servers so we can add our own.
     remove: true
 
-  - target: '$..[?(@["x-beta"]==true)]'
-    description: Remove all beta operations
-    remove: true
-
   - target: '$.servers'
     description: Pop our server into the empty server array.
     update: