t.behrendt/sec-actions
0
0
Fork 0
Code Issues 2 Pull Requests Actions Activity

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

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-06-13 12:52:04 +02:00
Conversation 1 Commits 1 Files Changed 2
+2 -2
renovate-bot commented 2026-03-25 12:13:25 +01:00
Collaborator
Copy Link
Copy Source

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.29 → 0.1.35 0.1.36

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

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

v0.1.35

Compare Source

v0.1.34

Compare Source

v0.1.33

Compare Source

v0.1.32

Compare Source

v0.1.31

Compare Source

v0.1.30

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.29` → `0.1.35` | `0.1.36` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### 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.35`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.34...0.1.35) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.34...0.1.35) ### [`v0.1.34`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.33...0.1.34) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.33...0.1.34) ### [`v0.1.33`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.32...0.1.33) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.32...0.1.33) ### [`v0.1.32`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.31...0.1.32) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.31...0.1.32) ### [`v0.1.31`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.30...0.1.31) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.30...0.1.31) ### [`v0.1.30`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.29...0.1.30) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.29...0.1.30) </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:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My41LjQiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImFjdGlvbiIsImRlcHMiXX0=-->
renovate-bot requested review from t.behrendt 2026-03-25 12:13:26 +01:00
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.30 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.31 2026-04-19 11:11:41 +02:00
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.31 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.32 2026-04-28 12:15:24 +02:00
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from 1c04723b78 to 4f53d3171c 2026-04-28 12:15:25 +02:00 Compare
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.32 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.33 2026-06-04 12:20:39 +02:00
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from 4f53d3171c to 9557f3c0a6 2026-06-04 12:20:39 +02:00 Compare
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.33 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.34 2026-06-07 12:17:38 +02:00
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from 9557f3c0a6 to 7e544eadbb 2026-06-07 12:17:38 +02:00 Compare
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.34 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.35 2026-06-07 13:51:36 +02:00
renovate-bot added 1 commit 2026-06-07 13:51:37 +02:00
chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.35
renovate/stability-days Updates have met minimum release age requirement
Details
CI / Test Setup Trivy amd64 (pull_request) Successful in 10s
Details
CI / Test Get Images From Files (pull_request) Successful in 5s
Details
CI / Test Setup Trivy arm64 (pull_request) Successful in 29s
Details
CI / Test Merge SARIF Files (pull_request) Successful in 5s
Details
CI / Test Setup DB (pull_request) Successful in 2m37s
Details
9cc3b7a779
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from 7e544eadbb to 9cc3b7a779 2026-06-07 13:51:37 +02:00 Compare
t.behrendt approved these changes 2026-06-13 12:51:25 +02:00
t.behrendt merged commit ef285207f1 into main 2026-06-13 12:52:04 +02:00
t.behrendt deleted branch renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x 2026-06-13 12:52:04 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
Clear labels
action
automerge
bug
Something is not working
 deps
docker
duplicate
This issue or pull request already exists
 enhancement
New feature
 go
help wanted
Need some help
 invalid
Something is wrong
 k8s
npm
question
More information is needed
 security
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/sec-actions#53
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?