Repository navigation
Bring release/1.1 to main at 3771a4b7b for 1.1.1-rc.1 - #1846
Merged
Merged
Conversation
Carries main's tree at 3771a4b onto release/1.1, keeping the release line at 1.1.0: backend-images.env stays at v1.1.0, and package.json, the desktop Cargo version, release-policy.json and desktop/intelligence-cli.json already match main. The next Create release PR run, kind rc and bump patch, moves them to 1.1.1-rc.1. CHANGELOG.md adds one line under OpenBot Desktop for #1845, which landed after the 1.1.1 notes: Retry waits for a back end whose services are still coming up.
davidmckayv
requested review from
MikeRyanDev,
dustywusty,
guidovizoso,
mxmzb,
samjulien and
tylerslaton
as code owners
November 19, 2026 00:52
davidmckayv
added a commit
that referenced
this pull request
Nov 19, 2026
* Release v1.1.0-rc.1 (#1740) * Release v1.1.0-rc.1 * Release policy for v1.1.0-rc.1 Upgrades from v1.0.3 as well as the releases before it, whose databases (0077 to 0088) the server's migrations all reach. It migrates to 0132_bot_task_runs, the last migration its published images apply. The recovery stays a restore of the backup taken before the upgrade. --------- Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> Co-authored-by: David McKay <david@copilotkit.ai> * Bring release/1.1 to main at 9a11f98 for the next 1.1.0 candidate (#1749) Carries main's tree at 9a11f98, keeping the release lines at 1.1.0-rc.1: package.json, the desktop Cargo version, backend-images.env and release-policy.json. * Release v1.1.0-rc.2 (#1754) * Release v1.1.0-rc.2 * Notes for 1.1.0-rc.2 What changed since rc.1, from the code. A first install that stopped at Connecting OpenBot when the home folder is a git repository. The step before a Composio sign-in, and the Desktop hand-back that counts down. The personal edition's install token and API keys. The API refusing a repeated query parameter and a body that isn't JSON. Tasks shown once, Answered directly, a finished long run keeping its answer. Plain words, a conversation keeping its name. App calls with an unknown parameter refused before the ask. Dropdowns on a Bot's computer. Setup's troubleshooting logs. Usage data's release and error reports. --------- Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> Co-authored-by: David McKay <david@copilotkit.ai> * Release v1.1.0 (#1755) Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> * Bring release/1.1 to main at 3771a4b for 1.1.1-rc.1 (#1846) Carries main's tree at 3771a4b onto release/1.1, keeping the release line at 1.1.0: backend-images.env stays at v1.1.0, and package.json, the desktop Cargo version, release-policy.json and desktop/intelligence-cli.json already match main. The next Create release PR run, kind rc and bump patch, moves them to 1.1.1-rc.1. CHANGELOG.md adds one line under OpenBot Desktop for #1845, which landed after the 1.1.1 notes: Retry waits for a back end whose services are still coming up. * Pass CI on a release candidate's version (release/1.1) (#1849) A release branch's tree carries its candidate's version in package.json, such as 1.1.1-rc.1, and two checks added since 1.1.0 had only ever run on 1.1.0. upgrade-legs.ts took only plain vX.Y.Z tags and threw "Not a release tag: v1.1.1-rc.1" on the tree's own version, so the Desktop upgrade job failed on every pull request into a release branch. It now orders tags with Bun.semver.order, so a candidate comes after the release before it and before its own release; the releases it lists are still the stable ones. client-version-gate.test.tsx asserted the release was the literal 1.1.0, which failed on any other version; it now holds RELEASE to this tree's package.json. New upgrade-legs tests fail on main with the same error and pass with the change, and the gate test fails at 1.1.1-rc.1 before the change and passes after. * Release v1.1.1-rc.1 (#1847) * Release v1.1.1-rc.1 * Release policy for v1.1.1-rc.1 Upgrades from v1.1.0 as well as the releases before it, so database.from adds 0132_bot_task_runs, the database v1.1.0 left. It migrates to 0137_ai_connections, the last migration the v1.1.1-rc.1 OpenBot images apply. The five migrations since 0132 are additive and the v1.1.0 server works against them, so it needs no downtime, as the openbot chart's requires-downtime annotation says. The recovery stays a restore of the backup taken before the upgrade, as upgrades from 1.0.x run 1.1.0's migrations too. --------- Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> Co-authored-by: David McKay <david@copilotkit.ai> Co-authored-by: David McKay <davidmckayv@users.noreply.github.com> * Release v1.1.1 (#1853) * Release v1.1.1 * Notes for 1.1.1: the bundle chart on Amazon RDS and other managed PostgreSQL The 1.1.1 OpenBot images carry a bundle chart that installs on a managed PostgreSQL server: its setup Job lends OpenBot's role the provider's extension role only while the migrations run on an empty database and takes it back after, running again after each install and upgrade, and externalDatabase.intelligenceParameters gives Intelligence connection parameters of its own, as it needs on RDS. * Notes for 1.1.1: correct six lines against the code and add what was missing Fixes the gateway /responses wording, the harnesses' Responses API models, the team edition's AI connection, the connection-of-its-own subject, the bundle's object-storage refusal, a bucket in the environment, the chart's embedded browser, and Quit during a Stop on Windows. Adds the quiet group row, the image reporting its own release, the database wait from the image, a CA of your own at start, Helm 4 --wait, signed OCI charts, the internal status port, scripts/start.sh starting the TypeScript engine, sent-file links and wrapped step reasons. --------- Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> Co-authored-by: David McKay <david@copilotkit.ai> * Keep main's own backend-images.env --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: davidmckayv <1574202+davidmckayv@users.noreply.github.com> Co-authored-by: David McKay <david@copilotkit.ai> Co-authored-by: David McKay <davidmckayv@users.noreply.github.com>
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.
Carries main onto release/1.1 for 1.1.1-rc.1, at 3771a4b, the way a later release on a shipped line takes main's changes (docs/releasing.md, Release candidates and betas). The tree is identical to main's except two files. backend-images.env stays at v1.1.0, the release line; package.json, the desktop Cargo version, release-policy.json and desktop/intelligence-cli.json already match main. CHANGELOG.md adds one line under OpenBot Desktop for #1845, which landed after the 1.1.1 notes: Retry waits for a back end whose services are still coming up. The next Create release PR run, kind rc and bump patch, moves the release lines to 1.1.1-rc.1.