t.behrendt/conventional-semantic-git-tag-increment

Go to file

CD / Release (push) Successful in 12s

Details

chore(deps): update dependencies (non-major) (#16 )

This PR contains the following updates:

| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | minor | [`24.3.1` -> `24.5.2`](https://renovatebot.com/diffs/npm/@types%2fnode/24.3.1/24.5.2) | `24.6.2` (+2) |
| [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.25.9` -> `0.25.10`](https://renovatebot.com/diffs/npm/esbuild/0.25.9/0.25.10) |  |
| [ts-jest](https://kulshekhar.github.io/ts-jest) ([source](https://github.com/kulshekhar/ts-jest)) | devDependencies | patch | [`29.4.1` -> `29.4.2`](https://renovatebot.com/diffs/npm/ts-jest/29.4.1/29.4.2) | `29.4.4` (+1) |

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

### [`v0.25.10`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#02510)

[Compare Source](https://github.com/evanw/esbuild/compare/v0.25.9...v0.25.10)

- Fix a panic in a minification edge case ([#&#8203;4287](https://github.com/evanw/esbuild/issues/4287))

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value `undefined` in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  ```js
  function identity(x) { return x }
  identity({ y: identity(123) })
  ```

- Fix `@supports` nested inside pseudo-element ([#&#8203;4265](https://github.com/evanw/esbuild/issues/4265))

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as `::placeholder` for correctness. The [CSS nesting specification](https://www.w3.org/TR/css-nesting-1/) says the following:

  > The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as `@supports`, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  ```css
  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @&#8203;supports (color: blue) { color: blue }
  }

  /* Old output (with --supported:nesting=false) */
  ::placeholder {
    color: red;
  }
  body :is() {
    color: green;
  }
  @&#8203;supports (color: blue) {
     {
      color: blue;
    }
  }

  /* New output (with --supported:nesting=false) */
  ::placeholder {
    color: red;
  }
  body :is() {
    color: green;
  }
  @&#8203;supports (color: blue) {
    ::placeholder {
      color: blue;
    }
  }
  ```

</details>

<details>
<summary>kulshekhar/ts-jest (ts-jest)</summary>

### [`v29.4.2`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2942-2025-09-15)

[Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.1...v29.4.2)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjQxLjEyNC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Reviewed-on: https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/pulls/16
Reviewed-by: t.behrendt <t.behrendt@noreply.localhost>
Co-authored-by: Renovate Bot <renovate@t00n.de>
Co-committed-by: Renovate Bot <renovate@t00n.de>

2025-10-02 08:02:24 +02:00

.gitea/workflows

feat: add ability to create pre-release tags (#17 )

2025-09-30 17:29:47 +02:00

dist

feat: add ability to create pre-release tags (#17 )

2025-09-30 17:29:47 +02:00

src

feat: add ability to create pre-release tags (#17 )

2025-09-30 17:29:47 +02:00

.gitignore

chore: initial-commit (#1 )

2025-08-17 22:52:19 +02:00

.nvmrc

chore: bump nodejs to 24 (#15 )

2025-09-05 18:44:13 +02:00

.prettierrc

chore: initial-commit (#1 )

2025-08-17 22:52:19 +02:00

action.yml

feat: add ability to create pre-release tags (#17 )

2025-09-30 17:29:47 +02:00

jest.config.js

chore: initial-commit (#1 )

2025-08-17 22:52:19 +02:00

LICENSE

Initial commit

2025-08-17 20:20:08 +02:00

package-lock.json

chore(deps): update dependencies (non-major) (#16 )

2025-10-02 08:02:24 +02:00

package.json

chore: bump nodejs to 24 (#15 )

2025-09-05 18:44:13 +02:00

README.md

feat: add ability to create pre-release tags (#17 )

2025-09-30 17:29:47 +02:00

renovate.json

ci: adjust renovate to group non-majors (#12 )

2025-09-04 15:21:50 +02:00

tsconfig.json

chore: initial-commit (#1 )

2025-08-17 22:52:19 +02:00

README.md

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 }}

With prerelease tags

- uses: tbehrendt/conventional-semantic-git-tag-increment@v1
  with:
    prerelease: "true"
    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

Prerelease Examples

Commit Message	Current Tag	New Tag (prerelease)	Reason
`feat: add user authentication`	`v1.0.0`	`1.1.0-rc-abc123`	New feature
`fix: resolve login bug`	`v1.1.0`	`1.1.1-rc-def456`	Bug fix

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.
prerelease (optional): Whether to create a prerelease tag with -rc-<github.sha> suffix. Defaults to false.
max-tags (optional): Maximum number of tags to fetch when looking for the latest non-pre-release tag. Defaults to 50.

Outputs

new-tag: The incremented semantic version tag (e.g., 1.2.3 or 1.2.3-rc-abc123 for prerelease)