t.behrendt/actions
1
0
Fork 0
Code Issues 2 Pull Requests 3 Actions Activity

chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.23 #13

Merged
t.behrendt merged 1 commits from renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x into main 2026-02-03 16:15:43 +01:00
Conversation 1 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2026-02-02 18:00:34 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change Pending
https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action patch 0.1.22 → 0.1.23 0.1.25 (+1)

Release Notes

t.behrendt/conventional-semantic-git-tag-increment (https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment)

v0.1.23

Compare Source

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment) | action | patch | `0.1.22` → `0.1.23` | `0.1.25` (+1) | --- ### Release Notes <details> <summary>t.behrendt/conventional-semantic-git-tag-increment (https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment)</summary> ### [`v0.1.23`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.22...0.1.23) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.22...0.1.23) </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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0Mi45Mi40IiwidXBkYXRlZEluVmVyIjoiNDIuOTIuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYWN0aW9uIiwiZGVwcyJdfQ==-->
renovate-bot added 1 commit 2026-02-02 18:00:34 +01:00
chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.23
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
7e835b88ab
t.behrendt approved these changes 2026-02-03 16:15:40 +01:00
t.behrendt merged commit 72551407e7 into main 2026-02-03 16:15:43 +01:00
t.behrendt deleted branch renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x 2026-02-03 16:15:43 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/actions#13
Delete Branch "renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?