Skip to content

Release notes and upgrade policy for 1.1.2 - #1894

Open
davidmckayv wants to merge 2 commits into
mainfrom
docs/notes-1.1.2
Open

davidmckayv wants to merge 2 commits into
mainfrom
docs/notes-1.1.2

Conversation

@davidmckayv

Copy link
Copy Markdown
Contributor

What this changes

CHANGELOG.md and release-policy.json only.

The notes

## Unreleased is rebuilt for 1.1.2 from the code, as docs/releasing.md asks before a release. Every change since 1.1.1 was read in its diff, and an entry stays only where the code shows it.

Before upgrading:

  • No migrations, so 1.1.1 upgrades to 1.1.2 with a rolling upgrade, and can go back the same way.
  • Task threads are off unless the server sets OPENBOT_TASK_THREADS=on. Nothing is removed: a Bot keeps what it is set to, and existing task cards still show.

Bots and models:

  • Bots do the work in the conversation. With task threads on, only a Bot set to hand work to agents hands it out.
  • The Agents page has no Hand work to agents switch, and saving it keeps what a Bot is set to.
  • A Bot asks for the app a request needs instead of searching the web around it.

OpenBot Desktop:

  • Approved folders survive a server restart.
  • Install works over an earlier install whose engine is gone.
  • On Windows, setup no longer waits for ever on a machine ssh.

Kubernetes:

  • The opt-in management agent and its openbot-agent chart, whose image is now the release's own.
  • bun scripts/update.ts kubernetes apply accepts a published release.

The policy

release-policy.json is written for v1.1.2:

  • it upgrades from v1.1.1 as well, so database.from adds 0137_ai_connections;
  • it still migrates to 0137_ai_connections, with no downtime.

Checks

The tests that read the changelog or the policy pass locally: 151 across 9 files. Biome is clean on the policy.

Unreleased is rebuilt from every change since 1.1.1, checked in its diff: Before upgrading (no migrations, task threads off unless OPENBOT_TASK_THREADS turns them on), Bots doing the work in the conversation, the Agents page without Hand work to agents, a Bot asking for the app a request needs, approved folders surviving a server restart, Install over an earlier install, the Windows ssh wait, the opt-in management agent and its chart, and update.ts accepting a published release. release-policy.json is written for v1.1.2: it upgrades from v1.1.1 as well, so database.from adds 0137_ai_connections, and it still migrates to 0137_ai_connections with no downtime.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant