Skip to content

CLOUDP-279514 Detect and block breaking changes #4064

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 30, 2025
Merged

Conversation

fmenezes
Copy link
Collaborator

@fmenezes fmenezes commented Jul 30, 2025

Proposed changes

Detect and block breaking changes

Jira ticket: CLOUDP-279514

Closes #[issue number]

Checklist

  • I have signed the MongoDB CLA
  • I have added tests that prove my fix is effective or that my feature works
  • I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
  • I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
  • I have updated test/README.md (if an e2e test has been added)
  • I have run make fmt and formatted my code

Further comments

@fmenezes
Copy link
Collaborator Author

Unfortunately, the new action will only work after we merge, given we need the new tool merged to use it in previous SHAs.

@fmenezes fmenezes marked this pull request as ready for review July 30, 2025 11:33
@fmenezes fmenezes requested a review from a team as a code owner July 30, 2025 11:33
set -e
{
echo "JSON<<EOF"
go run tools/cmd/breakvalidator/main.go generate
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's failing, is it expected?

Run set -e
Error: stat tools/cmd/breakvalidator/main.go: no such file or directory
Error: Process completed with exit code 1.
Error: Unable to process file command 'output' successfully.
Error: Invalid value. Matching delimiter not found 'EOF'

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is why I commented

Unfortunately, the new action will only work after we merge, given we need the new tool merged to use it in previous SHAs.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh! it's expected, sorry i missed it! continuing to review

blva
blva previously approved these changes Jul 30, 2025
Copy link
Collaborator

@blva blva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

Coverage Report 📈

Branch Commit Coverage
master 9c7914d 25.8%
CLOUDP-279514 af87119 25.9%
Difference .1%

@fmenezes
Copy link
Collaborator Author

tested in #4065 we see what is wrong on the task details

@fmenezes fmenezes merged commit d165a3f into master Jul 30, 2025
23 of 24 checks passed
@fmenezes fmenezes deleted the CLOUDP-279514 branch July 30, 2025 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants