update-github-actions-version
Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.
What this skill does
# Update GitHub Actions Version Update action versions in GitHub Actions workflow files, focusing on major version changes only. ## Important Principles: Explanation of GitHub Actions Version Tagging System - Using a major version number (e.g., `v4`) automatically fetches the latest minor and patch versions. - For example, `actions/checkout@v4` will automatically get versions like `v4.2.2`, `v4.3.0`. - **Do not** update from `v4` to a specific version like `v4.2.2` — this is unnecessary. - **Only update when the major version changes** (e.g., from `v5` to `v6`). > **Note:** Skip `fatjyc/[email protected]` updates as the new version is broken. ## Steps ### 0. Find Workflow Files Look for files in `.github/workflows/` recursively. Note that composite actions may be used — read both the composite action and the calling workflow simultaneously. ### 1. Check Current Versions Analyze the action versions used in the workflow files. ### 2. Query Latest Versions Query each action's latest version: ``` https://github.com/{owner}/{repo}/releases/latest ``` ### 3. Identify Actions Needing Updates Only update actions where the major version has changed: - ✅ Update: `docker/build-push-action@v5` → `@v6` - ❌ Skip: `actions/checkout@v4` → `@v4.2.2` > **Note:** Skip `fatjyc/[email protected]` updates as the new version is broken and v6.0 is fine. ### 4. Obtain Changelogs For actions requiring updates, retrieve changelogs to understand breaking changes. ### 5. Update Files Update version numbers and make adjustments for any breaking changes. ### 6. Commit Changes Git add and commit your changes with a clear message indicating the updates made. ## Example Illustration ### ✅ Correct Update ```yaml # From uses: docker/build-push-action@v5 # Update to uses: docker/build-push-action@v6 ``` ### ❌ Incorrect Update (Unnecessary) ```yaml # From uses: actions/checkout@v4 # Incorrectly updated to uses: actions/checkout@v4 .2 .2 ``` ### ✅ Correct Practice (Keep Unchanged) ```yaml # Keep unchanged uses :actions / checkout @ v 4 GitHub will automatically use the latest v 4.x.x release ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.