Skip to content

[UPDATE][udctl][1.0.2] Upgrade udctl 0.162.0 to 0.183.0 - #3918

Merged
Terminus-Gitbot merged 1 commit into
beclab:mainfrom
AIDockerCloud:feature/udctl-v1.0.2
Nov 7, 2026
Merged

Terminus-Gitbot merged 1 commit into
beclab:mainfrom
AIDockerCloud:feature/udctl-v1.0.2

Conversation

@AIDockerCloud

Copy link
Copy Markdown
Contributor

Summary

Upgrade udctl (UnDercontrol) from 0.162.0 to 0.183.0 in the Olares app udctl, chart version 1.0.1 -> 1.0.2.

This is the largest jump of the batch: 22 upstream releases, a long SQLite migration chain, and two CLI breaking changes. Review the upgrade notes below before merging.

Changes (5 files, +17 −5)

File Change
Chart.yaml version: 1.0.1 -> 1.0.2, appVersion: 0.162.0 -> 0.183.0
OlaresManifest.yaml metadata.version -> 1.0.2, spec.versionName -> 0.183.0, append upgrade notes
i18n/en-US + i18n/zh-CN append upgrade notes
values.yaml image.tag: 0.162.0 -> 0.183.0

No template change: the container image comes from {{ .Values.image.repository }}:{{ .Values.image.tag }}; the busybox init-container (1.37.0) is untouched. Chart configuration keys (config.*, olaresEnv) are unchanged.

⚠️ Migration risk

udctl is a single all-in-one container with SQLite storage, and it applies migrations on startup. Every release between 0.162.0 and 0.183.0 carries migrations; 0.183.0 alone runs 00122 to 00125.

  • Back up the SQLite database in the app data volume before upgrading.
  • Update the server before any client — 0.183.0 notes it changes the backend, web app and ud CLI.
  • 0.177.1 exists specifically to fix upgrading old SQLite databases to 0.177.0. So a single jump straight to 0.183.0 is the supported path — do not stop at an intermediate version.

Breaking changes between 0.162 and 0.183

Version Breaking change
0.174.0 CLI: the time block resource is renamed to time slot
0.175.0 CLI breaking changes; agent triggers are retired

Neither affects the chart's configuration surface, but users driving the ud CLI or relying on agent triggers will notice.

What was added along the way (highlights)

  • Conversations with agents, and agents that run on the server (0.178–0.182)
  • A single sidebar you arrange yourself, replacing the topic sidebar (0.181)
  • Slack as a messenger alongside Telegram and Discord; agents that ask a question answerable with a click (0.183)
  • One recycle bin for tasks, agents, skills and files (0.164)
  • Notes on files, batch tagging, tag-at-upload (0.166–0.167)
  • CSV export of transactions, budgets and accounts (0.163)
  • A Photos page (0.162)

Verification

  • docker.io/lintao0o0/undercontrol:0.183.0 exists — confirmed in the registry tag list (162 tags; 0.183.0 is the latest, newer than the 0.182.1 seen in the earlier inventory).
  • Version fields consistent: Chart.yaml:version = metadata.version = 1.0.2; Chart.yaml:appVersion = spec.versionName = image.tag = 0.183.0.
  • upgradeDescription has 7 entries in root / en-US / zh-CN, aligned.
  • git diff --check clean; diff limited to the 5 files above.
  • Single GPG-signed commit on top of upstream/main (9fe20f45), no merge commit.

- chart version 1.0.1 -> 1.0.2; appVersion / versionName / image tag -> 0.183.0
- the template builds its image from .Values.image.repository and .Values.image.tag,
  so values.yaml is the only place the tag lives; the busybox init-container is untouched
- verified docker.io/lintao0o0/undercontrol:0.183.0 exists in the registry (latest is
  0.183.0, newer than the 0.182.1 seen in the earlier inventory)
- this spans 22 upstream releases and a long SQLite migration chain: 0.183.0 alone
  runs 00122 to 00125; 0.177.1 exists specifically to fix upgrading old SQLite
  databases, so a single jump to 0.183.0 is the supported path
- document the two CLI breaking changes (0.174.0 time block -> time slot,
  0.175.0 agent triggers retired) and that the SQLite database should be backed up
  before upgrading and the server updated before clients
- chart configuration keys unchanged
@Terminus-Gitbot

Copy link
Copy Markdown
Collaborator

Check passed, please wait for auto-merge.

@Terminus-Gitbot
Terminus-Gitbot merged commit 0530abb into beclab:main Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants