Skip to content

chore: release v0.23.0 #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Codename-11 merged 1 commit into from
Jul 15, 2026
Merged

chore: release v0.23.0 #47

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,22 @@ The dashboard's **What's New** rail reads this file at request time
entries. Keep entries terse — one line per item under each version
date, grouped by `Added` / `Changed` / `Fixed` / `Removed`.

## [2026-07-15] — v0.23.0 · Mission Control agent fleet

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish same-day releases

When this v0.23.0 entry uses the same bracket date as the previous release, users who opened What's New earlier on July 15 will not get the dashboard unseen indicator for this new release: WhatsNewTile derives freshness from only the first dated entry and compares new Date(entry.date) to changelogSeenAt, so any seen timestamp later than midnight on 2026-07-15 makes v0.23.0 look already seen. Use a per-release timestamp/version for freshness, or adjust the seen check before publishing multiple releases on the same date.

Useful? React with 👍 / 👎.


### Added

- **Mission Control now manages the full agent fleet.** Define identities, choose execution runtimes, inspect MCP client readiness and recent work, and bind or unbind workspaces from one global control plane.

### Changed

- **Workspace agent settings are policy-only.** Capacity, capability overrides, routing eligibility, engagement, and approval stay scoped to the workspace while profile and binding lifecycle moves to Mission Control.
- **Instance Administration is governance-only.** Approvals, instance sharing, and force-disable remain at instance scope; authorized administrators manage and safely remove profiles through Mission Control.
- **Legacy Agent Studio links remain valid.** Former profile routes redirect to the new fleet surface, with explicit global, workspace, and instance scope labels.

### Fixed

- **Agent management actions match workspace authority.** Bind, unbind, and MCP client creation are shown and enforced only for workspace owners and administrators, with durable audit events and preserved history.

## [2026-07-15] — v0.22.0 · Connected agent delivery

### Added
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "forge",
"version": "0.22.0",
"version": "0.23.0",
"private": true,
"description": "Forge — a fast, minimalist, keyboard-driven project management platform with pluggable agents.",
"license": "MIT",
Expand Down
Loading