alchemyplatform Release Workflows
aa-sdk has a single manual package publish workflow on main and two
post-merge docs hooks that affect external systems. The legacy v5 beta and v5
docs sync workflows were retired when v5 graduated to main.
Rules
| Rule | When to read |
|---|---|
| Package publish | Before changing .github/workflows/publish-package.yml or Lerna config. |
| Main docs hooks | Before changing docs revalidation or SDK indexer workflows. |
Evidence
publish-package.ymlis dispatched manually with apublishboolean. It runspnpm lerna publish --conventional-commits --no-private --yes --no-verify-accessand pushes the version commit + tags back tomain.revalidate-sdk-content.ymlposts changeddocs/pages/**/*.mdanddocs/pages/**/*.mdxpaths to the docs site revalidation API onmain.trigger-sdk-indexer.ymldispatchesindex-sdk-referencestoalchemyplatform/docswhendocs/docs.ymlchanges onmain.lerna.jsonsetsdistTag: latestand does not pinallowBranch, so Lerna publishes frommain(andmaster) by default. Thev4.x.xbranch setsallowBranch: "v4.x.x"locally so legacy backports can publish.