chore(deps): pin fpm-tune to v1.0.0 (stable) - #132
Merged
Conversation
fpm-tune reached its stable 1.0 release. The runtime autotuner embedded in 3.1.0 was built against a v0.1.0 beta; pin it to v1.0.0 so the released init tracks a frozen API rather than a moving beta. The serve API init embeds is unchanged from beta.25 (1.0 added only serve-side logging and docs), so no code change is needed. Regenerate the SBOM. Adds the CHANGELOG entry for 3.1.1 (this pin plus the release smoke-test fix from #131).
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.
fpm-tune hit stable v1.0.0. The runtime autotuner in 3.1.0 was built against a v0.1.0 beta; this pins the stable 1.0 so the released init tracks a frozen API. The embedded serve API is unchanged from beta.25 (1.0 added only serve-side logging + docs), so no code change. Verified: build, touched-package tests, gofmt, license-check (go-m1cpu exception holds), vulncheck, and the full container e2e all pass on v1.0.0. Adds the CHANGELOG entry for v3.1.1. Cutting v3.1.1 once this is on main.