0.0.3
All checks were successful
CD / Release (push) Successful in 42s
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `.gitea/workflows/cd.yaml` (github-actions) * `.gitea/workflows/ci.yaml` (github-actions) * `package.json` (npm) * `.nvmrc` (nvm) ### What to Expect With your current configuration, Renovate will create 3 Pull Requests: <details> <summary>chore(deps): update actions/checkout action to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-5.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v5` </details> <details> <summary>chore(deps): update dependency conventional-commits-parser to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/conventional-commits-parser-6.x` - Merge into: `main` - Upgrade [conventional-commits-parser](https://github.com/conventional-changelog/conventional-changelog) to `^6.0.0` </details> <details> <summary>chore(deps): update dependency node to v22</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-22.x` - Merge into: `main` - Upgrade [node](https://github.com/nodejs/node) to `22` </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:94693a990c975907e7f13da3309b9d56ba02b3983519b41786edf5cf031e457c--> Reviewed-on: #3 Co-authored-by: Renovate Bot <renovate@t00n.de> Co-committed-by: Renovate Bot <renovate@t00n.de>
Conventional Semantic Git Tag Increment
A GitHub Action that automatically increments semantic version tags based on conventional commit messages.
Doesn't assume that you are using any special packaging software, etc. It just relies on Git having tags and commit messages.
Usage
Basic workflow
name: Auto-tag
on:
push:
branches: [main]
jobs:
tag:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: tbehrendt/conventional-semantic-git-tag-increment@v1
id: tag
with:
token: ${{ secrets.GITHUB_TOKEN }}
- name: Create and push tag
run: |
git tag ${{ steps.tag.outputs.new-tag }}
git push origin ${{ steps.tag.outputs.new-tag }}
With custom last tag
- uses: tbehrendt/conventional-semantic-git-tag-increment@v1
with:
last-tag: "v2.1.0"
token: ${{ secrets.GITHUB_TOKEN }}
Examples
| Commit Message | Current Tag | New Tag | Reason |
|---|---|---|---|
feat: add user authentication |
v1.0.0 |
v1.1.0 |
New feature |
fix: resolve login bug |
v1.1.0 |
v1.1.1 |
Bug fix |
feat!: change API response format |
v1.1.1 |
v2.0.0 |
Breaking change |
docs: update README |
v2.0.0 |
v2.0.1 |
Documentation update |
Inputs
last-tag(optional): Starting tag to increment from. If not provided, uses the latest tag in the repository.token(required): GitHub token for repository access. Use${{ github.token }}for public repos or a PAT for private repos.
Outputs
new-tag: The incremented semantic version tag (e.g.,1.2.3)
Languages
TypeScript
99.1%
JavaScript
0.9%