release: 1.0.0-beta.21

[jaylfc]

Version bump + CHANGELOG for 1.0.0-beta.21. Ships App Runtime M3+M4 plus the beta.20 desktop-wiring fix cluster reported by @mandresve.

App Runtime

• Install-time permission consent dialog (feat(userspace): install-time permission consent UI (App Runtime M3) #1579)
• Container app tier: per-app localhost-bound container + proxy + caps (feat(userspace): container app tier (App Runtime M4) #1580)

beta.20 wiring fixes (@mandresve)

• Store agent-framework install actually enables deploy + prefetches base image + notifies (Store apps appear to install successfully, but no backend installation occurs #1582)
• Model delete hits the backend; installed-state auto-refresh (Deleting a model from the Models dialog only updates the UI; the backend never removes the model #1581, taOS Desktop cannot install models after a fresh installation (downloads complete instantly, models are not available) #1548)
• Providers report true status; rkllama port; toggle render (Providers dialog shows all providers in Error state despite backend services running correctly #1578)
• Settings Logs shows real system logs with live tail (Settings → Logs remains empty even after multiple errors and failed operations #1583)
• Text Editor create works over http; randomUUID guarded class-wide (TextEditor is non-functional: cannot create notes or documents #1584)

Bumps pyproject.toml, desktop/package.json, tinyagentos/init.py, uv.lock, desktop/package-lock.json.

Summary by CodeRabbit

• New Features

  • Added app runtime enhancements for install-time permission consent and a new container app tier with isolated proxy deployment.

• Bug Fixes

  • Resolved issues affecting agent-framework installs, backend model deletion, instant-install state, provider status display, live system logs in Settings, and text editor stability for plain HTTP and related hardened components.

• Chores

  • Updated the app version to 1.0.0-beta.21.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3d939caf-0c71-4733-9707-f5c0f692f4e4

📥 Commits

Reviewing files that changed from the base of the PR and between 1d32f3a and 595427f.

⛔ Files ignored due to path filters (2)

• desktop/package-lock.json is excluded by !**/package-lock.json
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• desktop/package.json
• pyproject.toml
• tinyagentos/__init__.py

---

📝 Walkthrough

Walkthrough

This PR bumps the package version from 1.0.0-beta.20 to 1.0.0-beta.21 in desktop/package.json, pyproject.toml, and tinyagentos/init.py, and adds a corresponding CHANGELOG.md entry documenting App Runtime additions and five fixed issues.

Changes

Release Version Bump

Layer / File(s)	Summary
Version bump and changelog entry desktop/package.json, pyproject.toml, tinyagentos/__init__.py, CHANGELOG.md	Version strings updated to 1.0.0-beta.21 across config/source files, with a new dated CHANGELOG.md entry listing Added and Fixed items.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• jaylfc/taOS#1570: Same pattern of updating version fields and CHANGELOG.md across the same set of files.
• jaylfc/taOS#1550: Same release-only version bump touching the same version fields and changelog.
• jaylfc/taOS#1530: Same release-only update of the same version fields and changelog entry.

Suggested reviewers: kilo-code-bot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the release version bump to 1.0.0-beta.21.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/beta.21

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Version bump from 1.0.0-beta.20 to 1.0.0-beta.21 is applied consistently across all six files (CHANGELOG.md, pyproject.toml, tinyagentos/__init__.py, desktop/package.json, desktop/package-lock.json, uv.lock). The new CHANGELOG entry follows the existing Keep a Changelog format, groups changes under Added/Fixed, attributes fixes to @mandresve with the referenced PR numbers, and the version string in uv.lock (1.0.0b21) correctly reflects the PEP 440 normalization of the 1.0.0-beta.21 semver tag.

Files Reviewed (6 files)

• CHANGELOG.md
• pyproject.toml
• tinyagentos/__init__.py
• desktop/package.json
• desktop/package-lock.json
• uv.lock

---

_{Reviewed by minimax-m3 · Input: 20.2K · Output: 1.1K · Cached: 95.1K}