Record the bumps that landed between the tier work and the tag - #117
Merged
Conversation
Two GitHub Actions moved by a major version in release.yml, and neither was written down. A grouped minor or patch bump with green CI needs no entry; a major does, and a workflow that ships no API still decides how this project releases. That distinction has been missed on every release so far, which is why the pre-tag reconciliation exists and why it caught this one. The dependency bumps go in the same line. io.qdrant:client moving to 1.18.3 also makes the README's comparison honest: it said the stacks were verified against 1.18.3 while the benchmark resolved 1.15.0.
|
This pull request adds no capability the code did not already have. 1 file read · 983 ms · against |
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.
The pre-tag reconciliation between
git log v2.1.0..HEADand[Unreleased]found what it exists tofind.
Two Dependabot pull requests merged while the release was being prepared. #112 is a grouped minor and
patch bump, which with green CI needs no entry. #111 moved two GitHub Actions by a major version,
actions/attest-build-provenancev3 to v4 andactions/download-artifactv7 to v8, both inrelease.yml, and that does need one. A workflow ships no API and still decides how this projectreleases, which is the reasoning that was missed three times before
2.0.0.One line under
Internalcovers both, with the dependency versions named.A second thing it turned up
io.qdrant:clientwent from 1.15.0 to 1.18.3, and that makes the README honest rather than onlycurrent. The comparison table says the stacks were verified against
io.qdrant:client:1.18.3, and thebenchmark was resolving 1.15.0. The claim and the code now agree, which they did not when the harness
was added.
Nothing else changed.
audit-library.shreports the repository at standard, and this is the last thingbetween here and the
v2.2.0tag.