Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @semantic-release/git to v10 - autoclosed #6

Closed
wants to merge 1 commit into from

Conversation

goraxe
Copy link
Owner

@goraxe goraxe commented Nov 29, 2023

This PR contains the following updates:

Package Type Update Change
@semantic-release/git devDependencies major ^9.0.0 -> ^10.0.0

Release Notes

semantic-release/git (@​semantic-release/git)

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (7ab65f8)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

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.

@goraxe goraxe force-pushed the renovate/semantic-release-git-10.x branch from 19b6194 to 44b1755 Compare December 13, 2023 11:48
@goraxe goraxe changed the title chore(deps): update dependency @semantic-release/git to v10 chore(deps): update dependency @semantic-release/git to v10 - autoclosed Dec 13, 2023
@goraxe goraxe closed this Dec 13, 2023
@goraxe goraxe deleted the renovate/semantic-release-git-10.x branch December 13, 2023 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants