You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an JSON OpenApi spec that I want to bump the version in as part of a build process. The version property is located in the info object of the JSON as dictated by the OpenAPI standard. When I run the command, for example, bump 3.0.0 my-api.json, it results in a message of my-api.json did not need to be updated. Is there a way to tell the bump command where to look for the version? When I played around with it, it seems that bump only finds the version field if it is at the top level. Is there a way to tell where the version is actually located?
The text was updated successfully, but these errors were encountered:
After some experimentation and studying the unit tests, it appears that when bump is used on files other than the pre-defined ones, it will only update if the current version value it finds match the version in the package.json file. Is that a correct understanding?
I have an JSON OpenApi spec that I want to bump the version in as part of a build process. The version property is located in the
info
object of the JSON as dictated by the OpenAPI standard. When I run the command, for example,bump 3.0.0 my-api.json
, it results in a message ofmy-api.json did not need to be updated
. Is there a way to tell the bump command where to look for the version? When I played around with it, it seems that bump only finds the version field if it is at the top level. Is there a way to tell where the version is actually located?The text was updated successfully, but these errors were encountered: