Repository navigation
Pin Motoro v0.15.0 release - #41
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.
Pin ASAREE to the Motoro
v0.15.0release tag instead of the temporary develop commit, and refresh the lockfile. The installed-release regression now verifies version, tag, and commit provenance. A sampling-preview regression covers the Local model capability fields that previously produced HTTP 422 and a blank run-confirmation warning on an older running backend.Validation: 243 focused tests passed across provider operations, model discovery, connection checks, model configuration, and sampling snapshots; scoped Ruff, lockfile consistency, and diff checks passed. Tests used mocked provider transport and did not run live inference. Existing uv warning: the unchanged
mako==1.4.0dependency is yanked.Targets
developand supplies the release dependency for #29. Updating the running backend, promoting intomain, tagging, and deployment remain separate steps.