A Temporal plugin release spans several skill and plugin repositories. This repo is the CI that coordinates that work. Dispatch Plugin Release here to ship new content across:
Skills:
skill-temporal-cloud-setupskill-temporal-developerskill-temporal-opsskill-temporal-serverless
Plugins:
claude-temporal-plugincodex-temporal-plugincursor-temporal-plugin
| Strategy | Skills | Plugins | Effect |
|---|---|---|---|
patch / minor / major |
yes | yes | 1. Bump version 2. Open a release PR and auto merge it 3. Create a GitHub Release 4. Use this new release |
latest |
yes | yes | Use the latest release instead of releasing a new version |
rollback |
yes | no | Use v{rollback_version} instead of releasing a new version |
When syncing content between the skills and the plugins the following nodes are checked out:
SKILL.mdreferencesscriptsassets
The content is then placed in the following locations:
- Cursor and Claude:
skills/{name} - Codex:
plugins/temporal/skills/{name}
| Secret | Description |
|---|---|
APP_CLIENT_ID |
GitHub App client ID |
APP_PRIVATE_KEY |
GitHub App private key (PEM) |
The app needs Contents (write) and Pull Requests (write) permissions.
- Install the GitHub App on the new skill repo with Contents (write) and Pull Requests (write).
- In
.github/workflows/plugin-release.ymladd the new inputs, then append the repo to all skill matrices. - In
.github/workflows/bump-plugin.ymladd a nameddownload-artifactstep into that skill's dest folder.
skill-temporal-example_package_strategy: *skill_package_strategy
skill-temporal-example_rollback_version: *rollback_version
...
skill_repo: [..., skill-temporal-example]