メニュー
This skill should be used when the user asks about "upgrade temporal", "temporal version upgrade", "migrate temporal", "update temporal server", "upgrade cluster", "schema migration", "SDK compatibility", or needs help planning safe Temporal upgrades.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks about deploying Hugo to AWS S3, S3 static site hosting, Hugo with CloudFront, the hugo deploy command, configuring Hugo's deployment section, GitHub Actions with AWS OIDC for Hugo, S3 bucket static website configuration, CloudFront cache invalidation after Hugo deploy, or choosing between GitHub Pages and S3 for Hugo hosting. Also applies when GitHub Pages limitations (auth, custom headers, size) require an alternative deployment target.
This skill should be used when the user asks about deploying Hugo to GitHub Pages, setting up a GitHub Actions workflow for Hugo, Hugo CI/CD pipeline, content-aware path filtering for Hugo builds, caching Hugo modules in CI, Hugo PR preview deployments, Hugo build workflow, or configuring GitHub Pages deployment for a Hugo site. Also applies when troubleshooting GitHub Actions workflow failures related to Hugo builds.
This skill should be used when the user asks about Hugo's data directory, loading YAML or JSON or TOML data files in Hugo templates, using .Site.Data to access structured data, data-driven navigation or menus, rendering datasets or bibliographies or registries from data files, generating content from data, using range to iterate over data collections, Hugo resources.GetRemote for external data, or organizing data files for large projects. Also applies when the user wants to drive site content or navigation from structured data rather than hardcoding it in templates.
This skill should be used when the user asks about Hugo shortcodes, creating custom shortcodes, Hugo render hooks, custom rendering for links or images or headings or code blocks, Hugo taxonomies (tags, categories, custom), page bundles and page resources, content formatting beyond basic markdown, creating callout boxes or tabs or admonitions in Hugo, or customizing how Hugo processes markdown elements. Also applies when the user wants to add reusable content components to their Hugo site.
This skill should be used when the user asks about Hugo themes, installing a theme, customizing a theme, overriding theme layouts or partials, Hugo template lookup order, creating a Hugo theme from scratch, Hugo asset pipeline (SCSS, PostCSS), Hugo baseof.html, or theme configuration parameters. Also applies when evaluating which theme to use, switching themes, or troubleshooting theme-related rendering issues.
This skill should be used when the user asks about Hugo module mounts, mounting multiple directories into Hugo's content tree, aggregating docs from scattered directories, using hugo mod init, configuring module.mounts in hugo.toml, building a unified documentation site from a monorepo, mapping subdirectory docs/ folders into a single Hugo site, or understanding Hugo's union file system. Also applies when the user has a repository with multiple docs/ directories that need to be presented as a single site. This is the core skill for multi-directory content aggregation.
| name | upgrade-guide |
| description | This skill should be used when the user asks about "upgrade temporal", "temporal version upgrade", "migrate temporal", "update temporal server", "upgrade cluster", "schema migration", "SDK compatibility", or needs help planning safe Temporal upgrades. |
| version | 1.1.0 |
Safe procedures for upgrading Temporal server, SDKs, and schema versions.
Follow sequential upgrade paths for major versions. Do not skip major versions:
1.21.x -> 1.22.x -> 1.23.x -> 1.24.x
Check SDK compatibility before upgrading:
Always backup both the main and visibility databases before upgrading:
pg_dump -h <host> -U temporal temporal > temporal_backup_$(date +%Y%m%d).sql
pg_dump -h <host> -U temporal temporal_visibility > temporal_visibility_backup_$(date +%Y%m%d).sql
kubectl scale deployment <worker-deployment> --replicas=0 -n <app-namespace>
Wait for workers to drain active tasks before proceeding.
helm repo update
helm upgrade temporal temporal/temporal \
--namespace temporal \
-f values.yaml \
--version <target_version>
Check release notes for migration requirements. Use the temporal-sql-tool from the admintools pod to apply versioned schema changes.
temporal operator cluster health
temporal operator cluster describe
kubectl get pods -n temporal
Update your application's SDK dependency to a compatible version, then deploy:
kubectl apply -f worker-deployment.yaml
kubectl rollout status deployment/<worker-deployment> -n <app-namespace>
If issues occur after upgrading:
helm rollback temporal <previous-revision> -n temporalkubectl rollout undo deployment/<worker> -n <app-namespace>/tl-upgrade command for interactive upgrade planningtemporal-ops agent for operational guidance during upgradesversioning-guide skill for workflow versioning during SDK updates