Re-enable semver check #1667
Merged
Re-enable semver check #1667
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
|
Waiting on upstream fix. |
|
☔ The latest upstream changes (presumably #1672) made this pull request unmergeable. Please resolve the merge conflicts. |
JohnTitor
force-pushed
the
reenable-semver
branch
2 times, most recently
from
c56a957 to
3951f64
Compare
JohnTitor
force-pushed
the
reenable-semver
branch
from
3951f64 to
b52e8e0
Compare
|
Should be fixed in latest semververfork release. And we need some CI tweaks included in this, so let's merge. |
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.
Let's see if they work well now...
r? @ghost