Repository navigation
chore(release): v1.1.4-beta.1 - #2429
Merged
Merged
Conversation
…vider feat: add Atlas Cloud as an LLM provider
- Move Quick Start above Main Features so install steps are not buried - Remove the Ask DeepWiki badge from all three READMEs - Keep sponsor position and order unchanged - Fix stale Skills list, JP Node runtime claim, Bocha naming, and dead links
docs(readme): reorder sections and fix stale claims
…0f-8a65-4bd1-b22e-ec1e52be5470 Add a Parallel Search MCP user-plugin example
* fix(copilot): validate session authentication * fix(copilot): guard account changes
…ation fix(provider): refresh Codex models and errors
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
zerob13
commented
Oct 12, 2026
zerob13
left a comment
Collaborator
Author
There was a problem hiding this comment.
Release check: v1.1.4-beta.1
Mechanical verification passes. This is a clean release PR:
- The branch head (
5e659db57) is identical to currentdev— zero commits and zero diff between them, so this is a straight fast-forward ofmainfrom v1.1.3 to dev, not a cherry-picked or hand-built branch. package.jsonversion is1.1.4-beta.1, matching the PR title.- The 12 commits it carries over
mainare the dev-merged work since v1.1.3: the user-plugin examples (#2425, #2426), the Copilot auth validation fix (#2427), the Codex model/media refresh (#2428), the README refine (#2422), registry refreshes, and the release bump itself. All of the substantive PRs in that set were reviewed on their own PRs; the registry data (providers.json,registry.json) is the usual build-generated upstream drift that rode along with them.
No issues from my side.
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.
Publish DeepChat v1.1.4-beta.1 from
devat5e659db57e269511c8ba69f8e39feb259b3ead75, with bilingual release notes dated 2026-10-12. The release metadata changes onlypackage.jsonandCHANGELOG.md.Changes since v1.1.3
Provider settings
Validation
pnpm run format,pnpm run i18n,pnpm run lint, andpnpm run typecheckpassed.Publication
Use the documented fast-forward release flow after approval. Do not use GitHub's Merge or Update branch buttons.
Wait for all six native package jobs and remote asset verification, review the exact nineteen-asset draft, and publish it as a prerelease. Remove the temporary release branch after publication.