0.1.14
All checks were successful
CD / Release (push) Successful in 14s
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.9.1` -> `24.10.0`](https://renovatebot.com/diffs/npm/@types%2fnode/24.9.1/24.10.0) | | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.25.11` -> `0.25.12`](https://renovatebot.com/diffs/npm/esbuild/0.25.11/0.25.12) | `0.27.0` (+1) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.25.12`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#02512) [Compare Source](https://github.com/evanw/esbuild/compare/v0.25.11...v0.25.12) - Fix a minification regression with CSS media queries ([#​4315](https://github.com/evanw/esbuild/issues/4315)) The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for `@media <media-type> and <media-condition-without-or> { ... }` was missing an equality check for the `<media-condition-without-or>` part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression. - Update the list of known JavaScript globals ([#​4310](https://github.com/evanw/esbuild/issues/4310)) This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global `Array` property is considered to be side-effect free but accessing the global `scrollY` property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties: From [ES2017](https://tc39.es/ecma262/2017/): - `Atomics` - `SharedArrayBuffer` From [ES2020](https://tc39.es/ecma262/2020/): - `BigInt64Array` - `BigUint64Array` From [ES2021](https://tc39.es/ecma262/2021/): - `FinalizationRegistry` - `WeakRef` From [ES2025](https://tc39.es/ecma262/2025/): - `Float16Array` - `Iterator` Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from `Iterator`: ```js // This can now be tree-shaken by esbuild: class ExampleIterator extends Iterator {} ``` - Add support for the new `@view-transition` CSS rule ([#​4313](https://github.com/evanw/esbuild/pull/4313)) With this release, esbuild now has improved support for pretty-printing and minifying the new `@view-transition` rule (which esbuild was previously unaware of): ```css /* Original code */ @​view-transition { navigation: auto; types: check; } /* Old output */ @​view-transition { navigation: auto; types: check; } /* New output */ @​view-transition { navigation: auto; types: check; } ``` The new view transition feature provides a mechanism for creating animated transitions between documents in a multi-page app. You can read more about view transition rules [here](https://developer.mozilla.org/en-US/docs/Web/CSS/@​view-transition). This change was contributed by [@​yisibl](https://github.com/yisibl). - Trim CSS rules that will never match The CSS minifier will now remove rules whose selectors contain `:is()` and `:where()` as those selectors will never match. These selectors can currently be automatically generated by esbuild when you give esbuild nonsensical input such as the following: ```css /* Original code */ div:before { color: green; &.foo { color: red; } } /* Old output (with --supported:nesting=false --minify) */ div:before{color:green}:is().foo{color:red} /* New output (with --supported:nesting=false --minify) */ div:before{color:green} ``` This input is nonsensical because CSS nesting is (unfortunately) not supported inside of pseudo-elements such as `:before`. Currently esbuild generates a rule containing `:is()` in this case when you tell esbuild to transform nested CSS into non-nested CSS. I think it's reasonable to do that as it sort of helps explain what's going on (or at least indicates that something is wrong in the output). It shouldn't be present in minified code, however, so this release now strips it out. </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:eyJjcmVhdGVkSW5WZXIiOiI0Mi4xLjMiLCJ1cGRhdGVkSW5WZXIiOiI0Mi4xLjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=--> Reviewed-on: https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/pulls/31 Reviewed-by: t.behrendt <t.behrendt@noreply.localhost> 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 }}
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 tofalse.max-tags(optional): Maximum number of tags to fetch when looking for the latest non-pre-release tag. Defaults to50.
Outputs
new-tag: The incremented semantic version tag (e.g.,1.2.3or1.2.3-rc-abc123for prerelease)
Languages
TypeScript
99.1%
JavaScript
0.9%