feat: add Atlas Cloud provider preset - #925
Open
binyangzhu000-sudo wants to merge 65 commits into
Open
Conversation
Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
|
@binyangzhu000-sudo is attempting to deploy a commit to the luokerenx4's Team Team on Vercel. A member of the Team first needs to authorize it. |
release: promote 0.89.1-beta
release: promote 0.89.2-beta
release: promote 0.89.3-beta
Contributor
云端代理审阅（以 upstream
|
release: 0.89.4-beta
release: 0.90.0-beta
Promote dev to master: 0.90.1
Promote dev to master for 0.90.2
Promote repaired 0.90.2 source to master
…90.2-beta.1 Prepare OpenAlice 0.90.2 beta 1
release: promote desktop upgrade smoke repair
…90.2-stable chore(release): prepare v0.90.2
Promote dev to master for v0.91.0-beta.1
Promote repaired dev to master for v0.91.0-beta.1
…91.0-beta.1 Prepare OpenAlice 0.91.0 beta 1
Promote dev to master for v0.91.0-beta.2
…91.0-beta.2 Prepare v0.91.0-beta.2
Promote dev to master for v0.91.0-beta.3
Prepare v0.91.0-beta.3
Promote dev to master for v0.91.0-beta.4
…91.1-beta.1 chore(release): prepare 0.91.1-beta.1
…91.1 chore(release): prepare 0.91.1 stable
…11-aur-fixture Promote accepted AUR fixture repair for 0.91.1
Promote dev for the 0.92 release
…92.0-beta.1 Prepare 0.92.0-beta.1 release
…92.0 Prepare 0.92.0 stable release
Promote market data and Project CLI improvements for 0.92.1 beta
…21-beta Prepare 0.92.1-beta release
Promote dev for v0.92.1-beta.1
…92.1-beta.1 Prepare v0.92.1-beta.1
Promote Broker Pack fixes for v0.92.1-beta.2
…21-beta2 Prepare v0.92.1-beta.2
…21-stable Prepare v0.92.1 stable
chore: promote dev for v0.93.0 release
…93.0-beta chore: prepare v0.93.0-beta
…93.0-stable chore: prepare v0.93.0
All three conflicts were the same both-sides-added-a-preset shape: upstream added an openrouter entry in the exact rows this branch adds atlas-cloud, in DEFAULT_MODEL_BY_PRESET and in the two matching spec expectations. Both entries are kept everywhere, openrouter first in upstream's position. Checked the auto-merged side too: the atlas-cloud entry in model-semantics.ts survived the merge intact. vitest src/ai-providers -> 42 passed; tsc --noEmit clean.
Author
|
Synced with
Both entries are kept everywhere, I also checked the auto-merged side rather than assuming a clean merge is a correct one: the Verification on the merged branch:
No conflicts remain. |
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
3 participants
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
Verification
pnpm exec vitest run src/ai-providers/preset-catalog.spec.ts src/ai-providers/model-semantics.spec.ts src/workspaces/cli/shim.spec.ts services/uta/src/domain/trading/brokers/presets.spec.ts(80 passed)pnpm exec tsc --noEmitpnpm test: 3828 passed, 9 skipped; two unrelated tests timed out under the full parallel run and passed when rerun in the focused set; the catalog-contract failure found by the full run was fixed before the focused rerungit diff --check