v2.10.0 (2026-04-10) Deploy Arazzo documents to your MCP server

🆕 Deploy an Arazzo workflow document on your MCP server

✨ The new MCP server deployment command (added in v2.9.12) can now receive Arazzo documents as input.

bump deploy path/to/flower-or-arazzo-document.yml --mcp-server my-mcp-server-id-or-slug --token $BUMP_TOKEN

Via the CLI, you can deploy a new workflow document (in either Flower or Arazzo specification format) on an MCP server.
More information in Readme

Note

This feature is currently in closed beta. Request an early access at hello@bump.sh

🐛 Overlay updating arrays now de-duplicate entries

Thanks to @garciasdos a bug has been fixed when applying an overlay that updates an existing array. It now de-duplicates array entries if the overlay adds an already existing value.

v2.9.12 (2026-02-16) Deploy workflow document on an MCP server

🆕 New feature on deploy: deploy a workflow document on an MCP server

✨ Add new option mcp-server to command deploy

bump deploy path/to/flower-document.yml --mcp-server my-mcp-server-id-or-slug --token $BUMP_TOKEN

Via the CLI, you can deploy a new workflow document on an MCP server.
More information in Readme

Note

This feature is currently in closed beta. Request an early access at hello@bump.sh

Full Changelog: v2.9.11...v2.9.12

v2.9.11 (2026-01-30) Overlay JSON Path compliance with RFC 9535

🐛 The overlay command has a better support of JSON path

Thanks to @atamano's new release of jsonpathly (the node library we use to parse JSON paths), the overlay command now supports JSON path functions described by RFC 9535 and fixes an issue in JSON path filtering. See the list of changes for JSON path here. And big thanks to @jeremyfiel and @jamietanna too for reporting those issues and fixing them all!

Internal

• Use the new API token authentication mechanism instead of basic auth when interacting with the Bump.sh API
• dependencies upgrade

Have fun designing APIs ✨ !

v2.9.10 (2026-01-13) Dependencies update and core signature update

This release has no user facing impact. It contains

• dependencies update
• a change in the code/diff library which now accepts two lists of overlay files if necessary

v2.9.9 (2025-11-27) Partial support OpenAPI 3.2

🆕 Support deployment of OpenAPI 3.2 documents 🎉

OpenAPI 3.2 was published on 19 September 2025 (see documentation), and is now partially supported by Bump.sh

Dependencies upgrade

As usual, we've updated some external JS dependencies.

---

And of course, continue having fun playing with APIs 😊 ✨

v2.9.8 (2025-07-29) Fix overlays during directory deployments

🐛 Overlays with bump deploy directory/

This release is a tiny bug fix to be able to use the --overlay flags during a deployment of a directory.

E.g.

bump deploy --hub my-hub --overlay my-overlay.yml directory/ 

Will deploy all specification files of the format <api_name>-api.[format] inside the directory/ directory while applying the my-overlay.yml overlay on each deployed documentation.

v2.9.7 (2025-07-22) Fix authenticated diffs with overlays

This release is a direct follow-up to the latest 2.9.6 release where the “authenticated diffs” were forgotten in the new possibility to apply overlays to a diff command.

From now on, all diffs support the --overlay flags (both public & authenticated diffs)

v2.9.6 (2025-07-21) Fixes and extended support for overlays

🐛 Two bug fixes around overlays

• The overlay output will not output yaml anchors anymore. Cf #709 for details.
• Using $refs inside an overlay file will now work as expected during a bump deploy my-openapi.yml --overlay my-overlay.yml command. Meaning we now send external refs from the overlay file correctly during deployments. More details inin #722

🆕 New feature on overlays: they can now be applied within the diff command

• The diff command now supports --overlay flag. Aligning with the existing behavior of the bump deploy command, you can now call the bump diff command with overlays. This will apply the given overlay(s) to the previous and next versions being compared. All details in #710

Dependencies upgrade

As usual, we've updated some external JS dependencies.

---

Thanks again Jake for reporting most of the issues fixed by this release!

---

And of course, continue having fun designing APIs 😊 ✨

v2.9.5 (2025-04-10) Deploy previews in your documentation context and a fix

🆕 You can now push a temporary version and create a preview in the context of your documentation

With the bump deploy command, you can now pass a new parameter: --preview. This will have the effect to deploy a “temporary” version which won't be visible by your end users but you'll get a preview of your documentation with the deployed document.

e.g.

bump deploy --doc my-doc --token my-secret-token --preview api-definition-file.json

The returned value will be a URL of the version you pushed, directly available in your context but not accessible from your rendered documentation.

🐛 fixing the overlay command (again!)

There was another case which got broken since the refactoring of 2.9.3: removing all elements of an array would.. not remove all elements and always leave n/2 elements in the array.

This is luckly fixed now and an overlay action like this:

- target: "$.servers.*"
  remove: true

will successfully remove all servers to the openapi document you target with that overlay.

😌 Thanks again Lisa for reporting this!

---

As usual, have fun designing APIs 😊 ✨

v2.9.4 (2025-04-01) Fixing `overlay` command (for root target and array targets) and dependencies update

🐛 Fixing the bump overlay command

Both following overlay targets were broken in the previous 2.9.2 release:

• Targeting the root document (target: '$') to add elements with the update action was broken
• Targeting an array element in your OpenAPI document with an update action was broken

This release fixes both bugs 😌. Thanks a lot @lcawl for reporting this issue 🙏

Upgrades

Dev dependencies upgrade including a high severity vulnerability.

---

As usual, have fun designing APIs 😊 ✨