Skip to content
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

Return reason of why proof cant be generated (api change) #2389

Merged

Conversation

rafal-ch
Copy link
Contributor

@rafal-ch rafal-ch commented Oct 24, 2024

⚠️ This should only be merged into the next, planned breaking release ⚠️
⚠️ I'll keep it as draft to avoid accidental merge ⚠️

Linked Issues/PRs

Additional changes related to #1394
Closes: #2367

Description

Initially we wanted these changes, but eventually decided to revert them from the original PR, because even though they are not considered strictly breaking, they change the API.

Checklist

  • Breaking changes are clearly marked as such in the PR description and changelog

Before requesting review

  • I have reviewed the code myself

@rafal-ch rafal-ch added the breaking A breaking api change label Oct 24, 2024
@rafal-ch rafal-ch self-assigned this Oct 24, 2024
@rafal-ch rafal-ch requested a review from a team November 13, 2024 14:41
@rafal-ch rafal-ch marked this pull request as ready for review November 13, 2024 15:31
@rafal-ch rafal-ch enabled auto-merge (squash) November 14, 2024 10:07
@rafal-ch rafal-ch merged commit 1396b5c into master Nov 14, 2024
31 of 32 checks passed
@rafal-ch rafal-ch deleted the 1394_return_reason_of_why_proof_cant_be_generated_api_change branch November 14, 2024 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking A breaking api change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants