Update dependency orhun/git-cliff to v2.13.1 #6
No reviewers
Labels
No labels
bug
chore
dependency
duplicate
enhancement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
shared/oci!6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/orhungit-cliff"
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?
This PR contains the following updates:
2.11.0→2.13.1Release Notes
orhun/git-cliff (orhun/git-cliff)
v2.13.1Compare Source
2.13.1 - 2026-04-26
🐛 Bug Fixes
v2.13.0Compare Source
2.13.0 - 2026-04-26
⛰️ Features
🐛 Bug Fixes
--with-commitdoes not change version (#1484) - (3d6a7cb)doc_auto_cfgand fix internal link (#1373) - (0a0a795)require.resolveto resolve binary path (#1392) - (39cd76e)🚜 Refactor
📚 Documentation
⚡ Performance
🧪 Testing
⚙️ Miscellaneous Tasks
◀️ Revert
reqwest::Response::error_for_status(#1374) - (2037127)Build
New Contributors ❤️
v2.12.0Compare Source
2.12.0 - 2026-01-20
⛰️ Features
--skip-tagscli argument (#1334) - (32cf8c5)🐛 Bug Fixes
📚 Documentation
⚙️ Miscellaneous Tasks
New Contributors ❤️
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.
This PR has been generated by Renovate Bot.
93d6e84847tod45ee87912Update dependency orhun/git-cliff to v2.12.0to Update dependency orhun/git-cliff to v2.13.1View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.