How sedzisz/semantic-version-action works
This GitHub Action turns a configured change token into a semantic-version bump and writes version outputs for the calling workflow. Its main flow validates the mapping, dispatches one of three detection modes, maps the detected token to a bump, reads the latest Git tag, calculates the next version, and writes the result. The README also documents Docker-based use; source excerpts show the runtime logic but not the action or container wiring.
Main entry points: entrypoint.py Action Runtime
Components 9
Change Detection
- Action Runtime
entrypoint.py - Change Detection
entrypoint.py
Version Calculation
- Token Mapping
entrypoint.py - Version Calculation
entrypoint.py
Action Outputs
- Workflow Outputs
Other components
- Calling Workflow
- GitHub Event Context
- Git Repository
- Docker Runner
Connections 9
- Calling Workflow → Action Runtime: starts with inputs
- Action Runtime → Change Detection: dispatches detection
- GitHub Event Context → Change Detection: provides labels
- Git Repository → Change Detection: provides commit or branch
- Action Runtime → Token Mapping: maps detected token
- Action Runtime → Git Repository: reads version tags
- Action Runtime → Version Calculation: calculates bump
- Action Runtime → Workflow Outputs: writes outputs
- Docker Runner → Action Runtime: runs container