chore: bump ai-toolkit APM pin to v0.3.0 - #201
Merged
Merged
Conversation
Manual pin bump (mirrors what the new Renovate apm.yml manager will do) to exercise the apm-materialize workflow end-to-end and pull in ai-toolkit's v0.2.0 primitives (instruction, skill, agent, MCP servers). The materialize workflow should append the refreshed apm.lock.yaml and deployed files.
Retarget v0.3.0 (just released) instead of v0.2.0 so the materialize workflow deploys the full primitive set — the commit-and-release skill, the Dutch agent, and the GitHub + MS Learn MCP servers — not only the instruction that shipped in v0.2.0.
The end-to-end materialize test deployed the Dutch agent primitive to .github/agents/dutch-real-estate-agent.agent.md (the APM Copilot target for agents), which dprint tried to reformat — the same generated-content issue already handled for .github/prompts and .github/instructions. Add .github/agents/** to the dprint excludes; it was missed in the original exclusion set because no consumer had deployed an agent yet.
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Result: the full producer→consumer loop works ✅
End-to-end test of the Renovate-style pin bump +
apm-materialize.yml(#199), now updating.githubto ai-toolkit v0.3.0.I bumped only the
apm.ymlpin (v0.1.1 → v0.3.0). The materialize workflow fired automatically and committed back the lockfile + every deployed primitive — proving all five APM primitive types flow through:.github/prompts/.github/instructions/devsecninja-conventions.instructions.md.github/agents/dutch-real-estate-agent.agent.md.agents/skills/commit-and-release/SKILL.md.vscode/mcp.json(GitHub + MS Learn)The materialize commit re-triggered CI and passed (App-token push-back confirmed working).
A real gap this test caught
dprint initially failed on the deployed agent —
.github/agents/**wasn't in the dprint excludes (it was missed in #194's exclusion set because no consumer had deployed an agent yet). Fixed in this PR by adding.github/agents/**; since it's the centralconfig-syncsource, the fix propagates to every repo. All 17 checks now green.Note
Earlier I mistakenly thought the skill/agent/MCP failed to deploy at v0.2.0 due to target detection — actually they simply weren't in v0.2.0 (they shipped in v0.3.0, which I cut as part of this). Target auto-detection (
copilot) worked correctly all along.