Release

Tag and create a GitHub release, only after verifying CI passes

Tufin 758a4dc 927 B Updated

File contents

Release workflow

Before tagging and releasing, verify that CI has passed:

  1. Find the latest CI run for the current branch:
    gh run list --branch $(git branch --show-current) --limit 5
    
  2. Check that all required workflow runs have completed successfully (go, lint, govulncheck, etc.)
  3. If any run is still in progress, wait for it to complete before proceeding
  4. If any run has failed, stop and report the failure — do NOT tag or release

Only after all CI checks pass:

  1. Determine the version tag (from user input or by incrementing the latest tag)
  2. Tag the commit: git tag <version>
  3. Push the tag: git push origin <version>
  4. Create the GitHub release: gh release create <version> ...
    • Use --prerelease for beta/rc tags
    • Include a summary of changes since the previous release

Tufin/oasdiff/tree/main/.claude/skills/release commit 758a4dc584

Frequently asked questions

npx skillmds add tufin/release