Repository navigation
Gate CI on apidiff reporting no incompatible change since v1.4.0. - #24
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A new
apidiffjob checks out the v1.4.0 tag into a worktree, rewrites its module path to the fork's, writes its export data withapidiff -m -w, and compares HEAD withapidiff -m -incompatible: any output fails the job, and the compatible changes are printed for the record. Both steps run in the same job with the same toolchain, so no export file is committed; export data is bound to the Go version that wrote it.ci-oknow requires the job.Verified locally against master: no incompatible change; compatible changes:
(*Tx).NamedQueryContext: added.