feat(apm): activate apm-sync on the .github consumer#195
Merged
Conversation
Wire this repo into the central apm-sync reusable (v1.8.0). On a weekly schedule or manual dispatch it runs `apm update` against apm.yml's DevSecNinja/ai-toolkit dependency and opens a PR when upstream primitives changed — activating the apm-sync flow on its first real consumer. Uses the App identity (RELEASE_PLEASE_APP_ID / _PRIVATE_KEY) so required CI fires on the sync PR, matching the release-please caller pattern.
The apm-sync reusable installs the CLI from the official aka.ms installer (microsoft/apm GitHub release), so the Renovate datasource for apm-version should be github-releases on microsoft/apm, not pypi.
This was referenced Jun 21, 2026
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 free
to 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.
What
Activates the apm-sync flow by wiring this repo (the first real APM consumer) into the central
apm-syncreusable shipped in v1.8.0 (#194/#188)..githubalreadyapm installedDevSecNinja/ai-toolkit(pinned#v0.1.1inapm.yml), but ai-toolkit has since shippedv0.2.0+ (skill, MCP servers, agent). This caller runsapm updateweekly (or on dispatch) and opens achore: sync APM primitivesPR when upstream changed.Details
v1.8.0tag SHA, with# v1.8.0comment + re-pin note — matching therelease-please-caller.ymlconvention in this repo.RELEASE_PLEASE_APP_ID/RELEASE_PLEASE_APP_PRIVATE_KEY) so the sync PR triggers required CI — same secrets as release-please.apm-versionpinned + Renovate-tracked viamicrosoft/apmGitHub releases (the reusable installs the CLI from the officialaka.msinstaller).workflow_dispatchfor on-demand runs.How to verify
After merge, trigger Actions → APM Sync → Run workflow. Expected: it installs
apm, runsapm update, and (because the pinned#v0.1.1is behindv0.2.0) opens a PR bumpingapm.yml/apm.lock.yamland redeploying the refreshed primitives into.github/.Follow-up
Other consumer repos can adopt the same caller via
docs/apm-sync-onboarding.md(they'd use the external pinned form rather than this self-reference).