ci: deploy bump.sh spec only when there are relevant spec changes #792
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gssbzn
approved these changes
Jun 30, 2025
andreaangiolillo
deleted the
update_foas_release_to_deploy_bump_only_when_needed
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the
.github/workflows/release-spec.ymlfile to improve the logic for determining when API specification changes should trigger a release to Bump.sh. The changes introduce a new check to ensure that only significant modifications to thev2.jsonfile (beyond minor metadata updates) result in a release.Workflow Enhancements:
Check if changes should be deployed to bump.sh, to analyze the number of changed lines in theopenapi/v2.jsonfile. This ensures that minor updates, such as metadata changes, do not trigger a release. ([.github/workflows/release-spec.ymlR160-R175](https://github.com/mongodb/openapi/pull/792/files#diff-aea44faec3c0b85ba535263f9b540a317c4ab32d8a8c221871a5b231fc4468b1R160-R175))outputssection to include a newbump_releaseoutput, which reflects whether significant changes were detected. ([.github/workflows/release-spec.ymlR109](https://github.com/mongodb/openapi/pull/792/files#diff-aea44faec3c0b85ba535263f9b540a317c4ab32d8a8c221871a5b231fc4468b1R109))ifcondition for therelease-bump-shjob to rely on the newbump_releaseoutput instead ofchanges_detected. ([.github/workflows/release-spec.ymlL200-R217](https://github.com/mongodb/openapi/pull/792/files#diff-aea44faec3c0b85ba535263f9b540a317c4ab32d8a8c221871a5b231fc4468b1L200-R217))## Proposed changes