Skip to content

[docs] Update documentation for features from 2026-04-27 #993

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

Closed
danielmeppiel wants to merge 1 commit into from
Closed

[docs] Update documentation for features from 2026-04-27 #993

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
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- Renamed the experimental Cowork target and all user-facing surfaces from `cowork` to `copilot-cowork` for futureproofing (e.g. `apm experimental enable copilot-cowork`, `--target copilot-cowork`, `apm config set copilot-cowork-skills-dir`, `APM_COPILOT_COWORK_SKILLS_DIR`). No behaviour change; the `[0.9.3]` release shipped as `cowork` and this rename landed immediately after. (#926)
Copy link

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

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

This entry says "No behaviour change", but the rename is a user-facing CLI/config breaking change (e.g., --target cowork/apm experimental enable cowork no longer appear to be accepted). Consider rewording to clarify that functionality is unchanged but users must update flags/config/env-var names. Also, using backticked [0.9.3] here reads like a literal link label; using plain 0.9.3/v0.9.3 would be clearer in changelog prose.

Suggested change
- Renamed the experimental Cowork target and all user-facing surfaces from `cowork` to `copilot-cowork` for futureproofing (e.g. `apm experimental enable copilot-cowork`, `--target copilot-cowork`, `apm config set copilot-cowork-skills-dir`, `APM_COPILOT_COWORK_SKILLS_DIR`). No behaviour change; the `[0.9.3]` release shipped as `cowork` and this rename landed immediately after. (#926)
- Renamed the experimental Cowork target and all user-facing surfaces from `cowork` to `copilot-cowork` for futureproofing (e.g. `apm experimental enable copilot-cowork`, `--target copilot-cowork`, `apm config set copilot-cowork-skills-dir`, `APM_COPILOT_COWORK_SKILLS_DIR`). Functionality is unchanged, but users must update CLI flags, config keys, and environment variable names; 0.9.3 shipped as `cowork` and this rename landed immediately after. (#926)

Copilot uses AI. Check for mistakes.

### Fixed

- Docs site auto-deploys again after bot-cut releases by correctly detecting tag-push context in `docs.yml`. (#953)
Expand Down
Loading