mit einem Klick
release-workflows
// Use when changing GitHub workflows, Lerna versioning, package publish, or post-merge docs hooks (revalidate + SDK indexer).
// Use when changing GitHub workflows, Lerna versioning, package publish, or post-merge docs hooks (revalidate + SDK indexer).
| name | release-workflows |
| description | Use when changing GitHub workflows, Lerna versioning, package publish, or post-merge docs hooks (revalidate + SDK indexer). |
| last_verified | "2026-05-21T00:00:00.000Z" |
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.
| 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. |
publish-package.yml is dispatched manually with a publish boolean. It
runs pnpm lerna publish --conventional-commits --no-private --yes --no-verify-access and pushes the version commit + tags back to main.revalidate-sdk-content.yml posts changed docs/pages/**/*.md and
docs/pages/**/*.mdx paths to the docs site revalidation API on main.trigger-sdk-indexer.yml dispatches index-sdk-references to
alchemyplatform/docs when docs/docs.yml changes on main.lerna.json sets distTag: latest and does not pin allowBranch, so Lerna
publishes from main (and master) by default. The v4.x.x branch sets
allowBranch: "v4.x.x" locally so legacy backports can publish.Use when writing or modifying Vitest tests, `.vitest` setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior.
Use when changing package management, workspace config, build scripts, generated outputs, Turborepo/Lerna config, or local validation in aa-sdk.
Use when editing `docs/**/*.mdx`, generated reference docs, TypeDoc comments, `typedoc.json`, `docs/docs.yml`, or documentation review instructions.
Use when throwing, catching, wrapping, documenting, or testing runtime errors in aa-sdk packages.
Use when changing package entry points, `exports` maps, public API barrels, import paths, or subpath exports in aa-sdk packages.
Use when changing `packages/smart-accounts`, account implementations, modules, permissions, nonces, deferred actions, or account address helpers.