Fix current-main release gates#23
Merged
Merged
Conversation
deepfates
marked this pull request as ready for review
July 23, 2026 05:55
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.
What
withwithcaseso strict Credo passesVerification
mix verifyin a non-TTY: 608 tests + 3 properties, 56 Mnesia tests, 0 failures; strict Credo cleanmix verifyin a color-capable TTY: same suites and counts, 0 failures; strict Credo cleanRelease lineage
This deliberately does not change the version or create a tag. The published Hex 1.3.3 artifact does not byte/source-match any Git commit; current
mainalso contains post-1.3.3 public API work. Release identity and the next semver are therefore a separate explicit decision.