chore(release): 1.0.0-beta.12

[jaylfc]

Version bump beta.11 -> beta.12 across the three version files (pyproject.toml, desktop/package.json, tinyagentos/init.py) and the CHANGELOG [Unreleased] section moved into a dated [1.0.0-beta.12] - 2026-06-28 section.

Headline of this cycle: remote agent deploy onto cluster workers (#1467), shared Notes/Lists with agent triggers (#1469), plus the Decisions app, Observatory, agent-native tools, canvas migration, app permissions, and secrets broker from the dev delta.

Per docs/RELEASING.md: merge to dev, then a follow-up dev->master promotion PR, then tag v1.0.0-beta.12 on master.

Summary by CodeRabbit

• Chores
  • Bumped the app/package version to 1.0.0-beta.12 across release metadata.
  • Added a new 1.0.0-beta.12 changelog entry and grouped the latest added items under it.

[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]

Warning

Review limit reached

@jaylfc, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: cc16623b-a4c0-450c-a7be-67ddd3f9baaf

📥 Commits

Reviewing files that changed from the base of the PR and between f28589f and 99e6a3c.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• docs/RELEASING.md

📝 Walkthrough

Walkthrough

Version bumped from 1.0.0-beta.11 to 1.0.0-beta.12 in pyproject.toml, desktop/package.json, and tinyagentos/__init__.py. CHANGELOG.md gains a ## [1.0.0-beta.12] - 2026-06-28 release heading grouping the existing "Added" items.

Changes

Release bump to 1.0.0-beta.12

Layer / File(s)	Summary
Version bump and changelog entry CHANGELOG.md, pyproject.toml, desktop/package.json, tinyagentos/__init__.py	Version field updated to 1.0.0-beta.12 in all three package manifests; changelog gains the beta.12 release heading with its associated "Added" bullet items.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• jaylfc/taOS#601: Performs the same coordinated version bump across the identical set of files.
• jaylfc/taOS#1233: Another coordinated beta release bump touching the same four files.
• jaylfc/taOS#1468: Directly related — populates the beta.12 unreleased changelog section that this PR promotes to a released heading.

Suggested reviewers

• kilo-code-bot

Poem

🐇 Hippity hop, the version goes up,
beta.12 now fills the cup!
A heading in the changelog, neat and bright,
three package files bumped just right.
Another release hops into the light! 🎉

🚥 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 clearly identifies the release bump to 1.0.0-beta.12 and matches the versioning changes.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/beta-12

---

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.}

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (6 files)

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

Previous Review Summary (commit f28589f)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit f28589f)

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)

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

---

_{Reviewed by minimax-m3 · Input: 25.8K · Output: 1.1K · Cached: 144.9K}