fix(paseo-omp): require Paseo 0.9.2 provider fixes - #177
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.
Summary
paseo-omp, including its pinned isolated canary imageWhy
Paseo 0.9.2 contains the plugin-provider request failure, reload cleanup, and daemon shutdown ordering fixes required by the OMP direct provider. The plugin retains its local persistent-session reservation queue; core failure containment does not replace it.
Verification
bun install --frozen-lockfile && npm run typecheck && npm run checknpm test -- --run tests/provider-interrupt.test.ts— 18 passednpm test -- --run tests/server-bundle.test.ts— 3 passednpm test -- --run— 824 passed, 6 skippednpm run test:integration:canary— Paseo 0.9.2 with OMP 18.1.15 passedPASEO_CANARY_OMP_VERSION=18.2.0 npm run test:integration:canary— passed