chore(release): cut 0.10.0#986
Conversation
There was a problem hiding this comment.
Pull request overview
Cuts the v0.10.0 release by updating the Python package version and promoting the changelog entries from Unreleased into a dated 0.10.0 section.
Changes:
- Bump package version in
pyproject.tomlfrom0.9.4to0.10.0. - Promote
CHANGELOG.mdentries into## [0.10.0] - 2026-04-27and update the attributions/descriptions for the shipped PRs.
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Updates the project version to 0.10.0 for the release. |
CHANGELOG.md |
Adds the 0.10.0 release section and moves/edits entries to reflect shipped changes. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 3
| - `pr-description-skill` mermaid guidance hardened: new asset `assets/mermaid-conventions.md` defines diagram-type-by-intent (sequenceDiagram for execution flow with `rect rgb(...)` boxing, flowchart for pipelines/architecture with `classDef new`, stateDiagram-v2 for state machines) and captures GitHub-renderer gotchas that `mmdc` does not always catch (notably: square brackets in flowchart edge labels MUST be quoted -- `|"[label]"|` not `|[label]|`). | ||
| - `pr-description-skill` ships an evals suite (genesis-driven): 18 trigger evals on the val-split ship gate + 3 content scenarios with/without the skill loaded (anchor delta +6 to +11 across refactor / docs-only / dep-bump shapes). Runs deterministically without an LLM API key, so PR-description quality regressions are caught in CI. (#985) | ||
| - `pr-description-skill` mermaid guidance hardened: new asset `assets/mermaid-conventions.md` defines diagram-type-by-intent (sequenceDiagram for execution flow with `rect rgb(...)` boxing, flowchart for pipelines/architecture with `classDef new`, stateDiagram-v2 for state machines) and captures GitHub-renderer gotchas that `mmdc` does not always catch (notably: square brackets in flowchart edge labels MUST be quoted -- `|"[label]"|` not `|[label]|`). (#984) | ||
| - Windows CI no longer crashes on the non-ASCII SKILL.md test fixture (forced UTF-8 read; cp1252 default was raising `UnicodeDecodeError` during test discovery). (#979) |
There was a problem hiding this comment.
The #979 changelog entry says the fix was "forced UTF-8 read", but PR #979's stated fix is pinning UTF-8 write encoding for the non-ASCII fixture (so later reads/validation succeed on Windows cp1252). Please adjust this wording to reflect the actual change.
| - Windows CI no longer crashes on the non-ASCII SKILL.md test fixture (forced UTF-8 read; cp1252 default was raising `UnicodeDecodeError` during test discovery). (#979) | |
| - Windows CI no longer crashes on the non-ASCII `SKILL.md` test fixture (pins UTF-8 write encoding for the fixture so later reads on Windows `cp1252` do not raise `UnicodeDecodeError` during test discovery). (#979) |
|
|
||
| ### Added | ||
|
|
||
| - README "Coming from `npx skills add`?" conversion block: a 30-second migration table for users arriving from the agentskills.io ecosystem, mapping every `npx skills` verb to its `apm` equivalent. (#980) |
There was a problem hiding this comment.
The #980 entry description appears to overclaim what the linked PR did. PR #980 (per its own summary) adds a short "Coming from npx skills add?" block with two apm install examples and a docs link; it does not provide a full verb-by-verb migration table. Please reword this line to match the actual README change so the changelog stays accurate.
| - README "Coming from `npx skills add`?" conversion block: a 30-second migration table for users arriving from the agentskills.io ecosystem, mapping every `npx skills` verb to its `apm` equivalent. (#980) | |
| - README adds a "Coming from `npx skills add`?" block with `apm install` examples and a docs link for users migrating from the agentskills.io ecosystem. (#980) |
| ### Fixed | ||
|
|
||
| - Docs site auto-deploys again after bot-cut releases by correctly detecting tag-push context in `docs.yml`. (#953) | ||
| - Docs site actually auto-deploys after bot-cut releases now: triggers on tag push instead of via `workflow_call` (the branch added in #953 was unreachable from the bot's release event). (#981) |
There was a problem hiding this comment.
This #981 changelog line reads as if the fix was to trigger docs deploy on tag push "instead of" workflow_call, but the underlying change (as described in PR #981) is that docs.yml is still called as a reusable workflow and now correctly detects the caller's tag-push context (github.event_name == 'push' + ref_type == 'tag'). Consider rephrasing to avoid implying workflow_call was removed or replaced.
| - Docs site actually auto-deploys after bot-cut releases now: triggers on tag push instead of via `workflow_call` (the branch added in #953 was unreachable from the bot's release event). (#981) | |
| - Docs site actually auto-deploys after bot-cut releases now: `docs.yml` correctly detects the caller's tag-push context via `workflow_call` (the branch added in #953 was unreachable from the bot's release event). (#981) |
|
Audit fixup pushed (
Could not locate a "marketplace authoring" PR post-v0.9.4 — only 5 PRs landed since the tag: #985, #984, #981, #980, #926. Likely a recall slip with #974 SKILL_BUNDLE / Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com |
danielmeppiel
force-pushed
the
chore/release-0.10.0
branch
2 times, most recently
from
6ebda95 to
e628cbc
Compare
|
Updated for the post-cut merges (force-pushed
Final v0.10.0 = 7 PRs: #926, #790, #722, #980, #981, #985, #984, #989. Diff is now just CHANGELOG + pyproject -- branch is clean on top of main. Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
danielmeppiel
force-pushed
the
chore/release-0.10.0
branch
from
e628cbc to
f548886
Compare
TL;DR
Cuts v0.10.0. Five PRs ship since v0.9.4: one user-facing docs add, one CI fix that finally lands the post-release docs deploy, and three maintainer-tooling pieces (
pr-description-skillevals + mermaid hardening + Windows CI hotfix). Milestone0.9.5was renamed to0.10.0and the 40 open items moved to a fresh0.10.1bucket.Changes
pyproject.toml:0.9.4->0.10.0CHANGELOG.md:[Unreleased]promoted to[0.10.0] - 2026-04-27. Each entry is one line answering "so what" for users:#980README conversion block fornpx skills addtraffic#981docs auto-deploy on tag push (the real fix;#953had landed an unreachableworkflow_callbranch)#985evals suite forpr-description-skill(genesis-driven; deterministic, no API key)#984mermaid hardening (diagram-type-by-intent + GH-renderer gotchas)#979Windows CI hotfix (UTF-8 fixture read)Audit notes
PRs merged since v0.9.4: #985, #984, #981, #980, #979. PR #982 (multi-app shared/apm.md) is intentionally excluded -- still OPEN, blocked on upstream
microsoft/apm-actionbundles-file:input.The previous
[Unreleased]line crediting#953for the docs-deploy fix was incorrect (that was the v0.9.4 attempt that leftworkflow_callunreachable). Re-attributed to#981and the 0.9.4 entry left as-is.Milestones
0.9.5->0.10.0(was the next-up bucket).0.10.1.0.10.0->0.10.1. Closed items (3, including feat: experimental support for Microsoft 365 Copilot Cowork custom skills #913 cowork) stay in0.10.0.How to ship
Merge -> tag
v0.10.0push triggersbuild-release.yml-> bot cuts release ->docs.yml(now correctly tag-triggered per #981) deploys docs.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com