Repository navigation
Bundle Intelligence 0.16.0-rc.5 in the chart and the desktop - #1034
Merged
Merged
Conversation
The Helm chart installs Intelligence 0.16.0-rc.5 instead of rc.4. Chart.lock is regenerated by helm dependency update. The desktop's local Intelligence moves to the same release. The stable Intelligence CLI installs the newest stable chart (0.15.1) and cannot be pinned to a candidate, so the desktop now bundles the CLI preview built from the rc.5 commit with its local chart pinned to 0.16.0-rc.5 (Intelligence's publish-cli.yml, dispatched with local_chart_version=0.16.0-rc.5), in the commit form the desktop build accepts.
davidmckayv
requested review from
MikeRyanDev,
dustywusty,
guidovizoso,
mxmzb,
samjulien and
tylerslaton
as code owners
November 5, 2026 22:36
davidmckayv
added a commit
that referenced
this pull request
Nov 5, 2026
…ngelog rebuild # Conflicts: # CHANGELOG.md
davidmckayv
added a commit
that referenced
this pull request
Nov 5, 2026
#1034 moved the chart's Intelligence dependency to 0.16.0-rc.5 and pinned Desktop's CLI to the copilotkit preview built from Intelligence commit 256cc68, whose default local release is 0.16.0-rc.5 (checked in the published package). The Desktop entry no longer says the installer carries whatever CLI was current.
davidmckayv
added a commit
that referenced
this pull request
Nov 5, 2026
…lease on main (#1001) * Point the 0.3.0 release policy at the last migration, 0075_individual_check_ins The policy was written before the personal edition added 0075_individual_check_ins, so the publish workflow's --validate-policy step would refuse the release before building anything. * Rebuild the changelog from the code before cutting a release Entries added to Unreleased since the last release are claims. The release procedure now starts by checking every change since the last tag in its diff and writing the notes from what the code shows. * Rebuild the 0.3.0 changelog from the code Every change merged since v0.2.0, #998 included, was checked in its diff and in the code as it stands, and Unreleased is written from that rather than from the entries added along the way. Entries the code does not support are dropped, ones it contradicts are rewritten, fixes to things that never shipped are folded into the feature they fixed, and changes nobody described now have entries. The section is about 89,000 characters, well under GitHub's 125,000-character limit for a release body, which the previous section would have crossed. The redaction entry that merged after v0.2.0 but sat under the 0.2.0 heading moves to 0.3.0, and the 0.1.0 Before upgrading count, changed to Eight by a merge, is Six again, matching its list. * Build the release policy test's fixture from the committed policy's migrations The fixture's last migration was written out as 0074_single_user_identity, the value the policy held when the test was added, so moving the policy to 0075_individual_check_ins failed five tests that check something else. The fixture now uses the migrations the committed policy names. * Check the Recorder's release notes in everything written since 0.2.0 The test read only ## Unreleased, which is empty on the release commit once the release workflow promotes it, so the checks that gate the publish would have failed. It also required 1.79.1, which main never pinned: the runtime went from 1.77.0 to 1.83.0. It now reads the notes from ## Unreleased to ## 0.2.0 and requires the runtime version server/package.json pins. * Add the harness conversation fixes to the 0.3.0 changelog, from their diffs Claude Agent SDK, Agno, Google ADK, LangGraph and Mastra Bots now answer from the whole conversation in their role. Checked against v0.2.0 and the code on main: the Antigravity fix is folded into its entry because that harness is new in this release, the components entry no longer says the Claude Agent SDK harness drops the standing role, and the macOS signing fixes change only CI, so they have no entry. * Point the 0.3.0 release policy at the last migration, 0077_channel_opening Main added 0076_model_selection and 0077_channel_opening. Create release PR moves only the policy's version within a release, so the database transition has to be right on main before the first candidate is cut, or publishing refuses it. * Add the changes merged since #1012 to the 0.3.0 changelog, from their diffs The standalone Desktop with local Intelligence, signed installers at fixed links, Intelligence in the Helm chart, the model picker, the always-ask refinements, the question drawer and Strands are checked against v0.2.0 and the code on main. Sections they change are rewritten in place, and links to Admin → Enterprise controls point at the pages that replaced it. * State the Intelligence version the Helm chart bundles: 0.16.0-rc.4 #1033 moved the chart's Intelligence dependency from 0.16.0-rc.3 to 0.16.0-rc.4 (Chart.yaml and Chart.lock); the changelog names it once. * State the Intelligence release the chart and Desktop bundle: 0.16.0-rc.5 #1034 moved the chart's Intelligence dependency to 0.16.0-rc.5 and pinned Desktop's CLI to the copilotkit preview built from Intelligence commit 256cc68, whose default local release is 0.16.0-rc.5 (checked in the published package). The Desktop entry no longer says the installer carries whatever CLI was current.
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.
Moves both places OpenBot gets Intelligence to 0.16.0-rc.5.
Helm chart. The Intelligence dependency moves from 0.16.0-rc.4 to 0.16.0-rc.5 in
Chart.yaml,Chart.lock(regenerated withhelm dependency update), the version named in thevalues.yamlcomment and the changelog's Helm chart entry. The published rc.5 chart differs from rc.4 only in its version, image tags and database schema identity: rc.5 adds Learning's Skill auto-approval, with a migration.Desktop. The desktop runs local Intelligence through the CLI it bundles, and the stable CLI (
latest, 4.33.1) installs the newest stable chart when local setup runs, which is 0.15.1. A stable CLI cannot be pinned to a candidate. Intelligence's documented route for a candidate (docs/runbooks/local-evaluation-candidate.md) is a CLI preview built with the chart pinned. Sopublish-cli.ymlwas dispatched on the rc.5 commit withcli_env=production,local_chart_version=0.16.0-rc.5and a committed CopilotKit template ref (run 42121472563). It publishedhttps://pkg.pr.new/CopilotKit/Intelligence/copilotkit@256cc68(copilotkit4.33.1-pre.256cc68, built from Intelligence 256cc680a, the rc.5 commit).desktop/intelligence-cli.jsonnow names that commit-form URL, and the changelog says the desktop's local Intelligence is 0.16.0-rc.5.How it was tested:
chartjob, with CI's Helm 3.19.0, on all six targets (vanilla, self-hosted, eks, eks-sandbox, gke, aks). All pass. Every rc.5 image the chart renders resolves on ghcr.io, and the chart and Helm promotion tests undertests/pass (71 pass, 6 skipped that need a cluster or a database).desktop-version.ts internal, thencli-bundle.ts darwin arm64.build-version.jsonrecords the CLI ascopilotkit4.33.1-pre.256cc68 from the pkg.pr.new URL, with Node 26.13.0 at its pinned SHA-256. The desktop script tests and the release prepare and candidate check tests pass.login --json --mode openbot, thenlocal setup --defer-model --jsonin a new folder, on Docker Desktop), set up a new local stack.local statusreportedinstalledRelease0.16.0-rc.5, stepready, readinessready(api, gateway and dashboard) and a valid licence. Its deployments carryintelligence-0.16.0-rc.5, and the running app-api, app-frontend, realtime-gateway, db-migrations and postgres-pgvector images match the digests of their 0.16.0-rc.5 tags on ghcr.io. The stack was then removed withlocal delete, leaving no containers, volumes, networks or CLI record behind.The CLI preview is the release candidate's CLI, so this pin should move to a stable CLI version once Intelligence 0.16.0 and a CLI that installs it are released.