action.version

@lssm-tech/action.version

Website: https://contractspec.io

GitHub Action for automated ContractSpec version management in CI.

What It Does

• Standalone action with no workspace dependencies
• Configured entirely via action.yml; no TypeScript source

Usage

name: ContractSpec Version Manager
on: pull_request
jobs:
  contractspec:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      packages: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v6
      - uses: lssm-tech/contractspec/packages/apps/action-version@main
        with:
          github-packages-token: ${{ secrets.CONTRACTSPEC_PACKAGES_TOKEN }}

For affected private GitHub Packages dependencies, github-packages-token must be a GitHub token that can read the ContractSpec packages granted to the consuming repository, bot, or GitHub App.

Inputs

• mode (default: analyze) — Action mode: analyze (check only) or bump (apply changes)
• auto-bump (default: false) — Whether to automatically applying bumps based on impact analysis
• commit-message (default: chore(release): bump spec versions [skip ci]) — Commit message for version bumps
• create-pr (default: false) — Create a Pull Request instead of pushing directly
• pr-title (default: chore(release): version packages) — Title for the Pull Request
• pr-branch (default: release/next-versions) — Branch name for the Pull Request
• github-token (default: ${{ github.token }}) — GitHub Token for creating PRs
• github-packages-token — Optional token used to configure private GitHub Packages auth before dependency installs

Outputs

• has-changes — Whether changes were detected/applied
• specs-bumped — Number of specs bumped

Key Files

• action.yml — GitHub Action definition (entry point)
• tests/action-version.test.ts — standalone host test (bun run test): runs the action.yml steps locally with recording bun/bunx/git/gh stubs; requires jq

Recent Updates

• Replace eslint+prettier by biomejs to optimize speed
• PublishConfig not supported by bun
• Move automation into actions

Notes

• Do not change action.yml inputs/outputs without updating downstream workflow consumers
• This is a standalone action — avoid adding workspace dependencies unless necessary