Repository navigation
changelog: the Unreleased section is v1.7.0, released 2026-10-18 - #50
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
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.
This prepares the release that belluikit/alidade#53 waits for. alidade's main pins caliper to c88a51b, the
KeepWhenAllFailcommit (#49), as a pseudo-version.The version and date are yours. I propose v1.7.0:
EngineOptions.KeepWhenAllFailis new, backward-compatible API, which semver treats as a minor bump. v1.6.3 would also work if you prefer patch releases. The date should be the day you publish.The change does the same as #47 did for v1.6.2: it puts a version heading under
## Unreleased, so the Added and Changed entries become that release's.Once the release is published, I'll bump alidade's
go.modto it and regenerate its notices (alidade#53).