t.behrendt/k_deploy_workflows
1
0
Fork 0
Code Issues 1 Pull Requests Actions Activity

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

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-26 15:00:51 +02:00
Conversation 1 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2026-06-20 17:13:47 +02:00
Collaborator
Copy Link
Copy Source

This PR contains the following updates:

Package Type Update Change
https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action patch 0.1.35 → 0.1.39

Release Notes

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

v0.1.39

Compare Source

v0.1.38

Compare Source

v0.1.37

Compare Source

v0.1.36

Compare Source

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [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.35` → `0.1.39` | --- ### 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.39`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.38...0.1.39) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.38...0.1.39) ### [`v0.1.38`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.37...0.1.38) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.37...0.1.38) ### [`v0.1.37`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.36...0.1.37) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.36...0.1.37) ### [`v0.1.36`](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.35...0.1.36) [Compare Source](https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment/compare/0.1.35...0.1.36) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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 [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My4yMzMuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYWN0aW9uIiwiYXV0b21lcmdlIiwiZGVwcyJdfQ==-->
renovate-bot changed title from chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.36 to chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.39 2026-06-21 17:05:42 +02:00
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from ce3fd9780c to 2c56a518eb 2026-06-21 17:05:42 +02:00 Compare
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from 2c56a518eb to d6ef7a7d05 2026-06-23 06:04:17 +02:00 Compare
renovate-bot added 1 commit 2026-06-25 06:04:46 +02:00
chore(deps): update https://gitea.t000-n.de/t.behrendt/conventional-semantic-git-tag-increment action to v0.1.39 787ff8fa95
renovate-bot force-pushed renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x from d6ef7a7d05 to 787ff8fa95 2026-06-25 06:04:46 +02:00 Compare
t.behrendt approved these changes 2026-06-26 15:00:49 +02:00
t.behrendt merged commit 9613169e92 into main 2026-06-26 15:00:51 +02:00
t.behrendt deleted branch renovate/https-gitea.t000-n.de-t.behrendt-conventional-semantic-git-tag-increment-0.x 2026-06-26 15:00:51 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
Clear labels
action
automerge
deps
docker
go
k8s
npm
security
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/k_deploy_workflows#62
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?