Repository navigation
Conversation
Delegate provider discovery, connection checks, metadata/defaults, tool support, and inference connection setup to Motoro's tested develop integration revision. Preserve credential-scoped metadata, coordinate cache refreshes, and apply shared discovery limits. Enable CI on develop/main and document the development, hotfix, and deliberate release workflow. Motoro must be released and the integration pin replaced with its tested release tag before ASAREE's production release. Validation: 250 focused local tests; full CI with 1,694 backend tests passing (3 skipped) and 538 frontend tests passing. Existing warn-only mypy, lint, dependency audit, and action deprecation findings are recorded on the PR. Related: EpistasisLab/ASAREE_Issues#63
Require explicit user/maintainer authorization for main merges, including hotfixes, release tags, artifact publication, and production deployment. Preserve CONTRIBUTING.md as the workflow reference and AGENTS.md as the short operational instruction. Validation: documentation scope/link review, git diff --check, and both required GitHub Actions checks passed.
This was referenced Oct 29, 2026
Replace the temporary Motoro develop commit pin with the published v0.14.0 tag, regenerate uv.lock, and verify installed version, requested tag, and resolved release commit in integration tests. Update the workflow documentation to record the released dependency. Validation: 250 focused tests, uv lock --check, scoped Ruff, git diff --check, and both required GitHub Actions checks passed. Existing warn-only type/lint, audit, and runtime warnings remain recorded in PR #29. Manual UI and authorized Azure AI Foundry/OpenRouter live smoke checks remain pending. This change does not authorize main promotion or ASAREE publication/deployment.
Document main as the default released-code branch while retaining develop as the feature/fix integration branch. Require an explicit develop PR base in contributor and agent instructions, and reject feat/* and fix/* PRs aimed at main in the existing required backend CI job. Preserve both explicit branch rulesets and existing merge methods. Validation: seven PR-target scenarios, CI branch-trigger parsing, git diff --check, and both required GitHub Actions checks passed. Release PR #29 remains draft; no main code merge, release tag, publication, or deployment is authorized by this workflow update.
Preserve provider metadata and provenance, distinguish explicit capability overrides, omit unadvertised defaults, invalidate legacy caches, and version sampling snapshots without rewriting publication history.
Document merge commits as the feature and fix PR workflow, preserving original commits and ancestry.
Keep required checks while skipping unrelated suites, preserving branch-target validation and cancellation of superseded PR runs.
Document path-based suite selection and verify required checks on a documentation-only PR.
Sync main into develop after statistics release promotion
fix: show actionable errors when experiment preparation fails
Pin Motoro v0.15.0 release
jay-m-dev
changed the title
jay-m-dev
marked this pull request as ready for review
November 3, 2026 23:24
jay-m-dev
changed the title
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.
Released as ASAREE v0.16.0 at main merge commit
d71cb3e04f0d3229633ade5af27ea54dace9e5f8, following maintainer smoke-test confirmation and explicit release authorization on 2026-11-03. Post-merge main CI passed both required checks. Synchronization PR #42 merged main back into develop at0cb1afa6aa5c0dcf0113c7cacc69033935345685; sync CI passed its dispatcher and correctly skipped suites for an empty tree diff. Production services were not deployed by the agent.The release comparison now includes provider operations delegated to Motoro; credential-scoped metadata discovery and caching; provider-driven sampling metadata, defaults, and immutable execution snapshots; clearer run-preparation validation errors; and selective CI and branch-workflow updates. No ASAREE database migrations are present in the current comparison. Automatic statistics changes already promoted through #38 are not a new feature in this release.
Dependency integration:
v0.15.0resolves tof1e7ea8b47b5d81581ffaf57dc595554dc6b21aa.developas70f82350d7ceb2f61475116b8f13688978e03ccd. It replaces the temporary develop pin, refreshesuv.lock, verifies installed version/tag/commit provenance, and covers the Local-model sampling payload that an older backend rejected.70f82350d7ceb2f61475116b8f13688978e03ccd(backend passed; frontend correctly skipped for the dependency-only integration diff). Release PR CI passed both required backend and frontend checks for the full release comparison at that candidate.Release checks:
/v1base URL, sampling preview, and run confirmation. This is maintainer-reported validation; the agent did not perform browser or live-inference checks.developcandidate70f82350d7ceb2f61475116b8f13688978e03ccdand on the release PR.70f82350d7ceb2f61475116b8f13688978e03ccd: provider operations/caching and credential isolation, sampling metadata and publication compatibility, frontend controls, validation-message preservation, dependency provenance, tests, and CI/workflow changes. No ASAREE schema migration is added; the existing Motoro migration path remains part of upgrades.developon 2026-11-03. Merge this PR using a merge commit. Authorize release tags, publication, and production deployment separately. Synchronizemainback intodevelopthrough a merge-commit PR afterward.Known validation limitations and warnings:
mako==1.4.0dependency.The earlier checklist described Motoro
v0.14.0and a narrower, older comparison. This description reflects the current integration; earlier CI counts are historical evidence, not validation of this release candidate.Current release-candidate warning counts: mypy 640 errors in 52 files (warn-only); frontend lint 15 warnings, zero errors; npm audit 23 vulnerabilities (1 low, 10 moderate, 11 high, 1 critical). These findings are recorded in the release notes; required CI still passed.