Skillshare Release

Prepare or review a skillshare release. An optional version argument is an explicit requested version, not permission to commit, merge, tag, push, or publish.

Before acting, run python3 scripts/ai-context.py release testing. These topics are the source of truth for authorization, version policy, automation and verification.

Workflow

1. Identify the release

Inspect Git status, the latest published release and the open Release PR. Preserve unrelated work. The manifest at .github/release-please-manifest.json is the release version source; the development CLI still defaults to dev.

Pushes to main create or update a Release PR. If one is missing, report the workflow state and required repository permissions. Dispatch the Release Please workflow only when the user authorizes that external action.

For 0.x, fix and perf increment patch; feat and breaking changes increment minor. A breaking change needs migration notes. Moving to 1.0.0 requires an explicit version decision. For an override, use a Release-As: X.Y.Z commit footer or a reviewed release-as configuration value; remove a configuration override after it has been consumed. Do not edit the tracking manifest by itself to request a release.

Explicit version requests

When the user requests a version such as 0.23.3, prepare a Release-As: 0.23.3 footer on a normal development commit that will reach main before the Release PR is merged. For a batch with multiple commits, adding it once to the final commit is sufficient; the override chooses the version for the entire pending release, including the earlier changes. Intermediate versions do not need to be published.

fix: correct sync behavior

Release-As: 0.23.3

With merge or rebase-merge, preserve the footer in the development commit. With squash-merge, copy it into the final squash commit message on GitHub; do not assume the individual commit messages will be preserved. Keep the Conventional Commit subject and a blank line before the footer. If multiple pending commits request different versions, the newest override wins; inspect the pending range for conflicting requests before proceeding.

After the commit reaches main, verify that Release Please creates or updates the Release PR to the requested version. Review its manifest and synchronized metadata before merging. Adding a footer alone does not create the release tag or publish anything. Follow the existing authorization boundary when committing, pushing or merging.

2. Sync documentation first

Before touching the Release PR, run /skillshare-update-docs over the pending range <latest published tag>..origin/main. Check every user-visible feat, fix and breaking change against the command pages, guides, troubleshooting, built-in skill and README, in English and every translated locale, and note the commits that need no documentation change. Then build the whole website inside the devcontainer the way the Website Pages workflow does:

cd website && npm run build

For a minor or major release (any feat or breaking change in the range), also update the README:

• Rewrite the Latest callout near the top of README.md for the new version, and the same callout in every translated README (README-de.md, README-es.md, README-fr.md, README-ja.md, README-ko.md, README-pt-BR.md, README-zh-CN.md, README-zh-TW.md), each in its own language.
• Add the release's contributors to the Contributors section of README.md (the translations link to it). A contributor is the author of an issue or PR the range references, or a commit author or Co-authored-by in the range, other than the maintainer. Skip anyone already listed, and verify each account exists before adding its avatar link: