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 @txo/semantic-release to v2 #694

Merged
merged 4 commits into from
May 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@txo/semantic-release ^1.0.8 -> ^2.0.8 age adoption passing confidence

Release Notes

technology-studio/semantic-release (@​txo/semantic-release)

v2.0.8

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.8 (2fba136)

v2.0.7

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.7 (01815cf)

v2.0.6

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.6 (9889008)

v2.0.5

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.5 (9d73c3f)

v2.0.4

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.4 (1e88a35)

v2.0.3

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.3 (80408ca)

v2.0.2

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.2 (d97388f)

v2.0.1

Compare Source

Bug fixes
  • deps: update dependency semantic-release to ^23.0.1 (e0207b8)

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • deps: move the release config to .config folder to fix the breaking change

  • fix(deps): update dependency semantic-release to v23

  • chore: move release config to .config folder to fix breaking change

Bug fixes

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 Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch 2 times, most recently from a51c014 to 356e623 Compare February 7, 2024 19:49
@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch from 356e623 to 2ae2b18 Compare March 4, 2024 12:29
@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch 3 times, most recently from 761cdb0 to 4134983 Compare March 18, 2024 19:16
@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch from 4134983 to 27c991a Compare March 24, 2024 20:16
@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch from 27c991a to cad4afa Compare April 4, 2024 02:14
@renovate renovate bot force-pushed the renovate/txo-semantic-release-2.x branch from cad4afa to 9c54328 Compare April 10, 2024 04:40
Copy link
Contributor Author

renovate bot commented Apr 16, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@erik-slovak erik-slovak merged commit 3849191 into main May 3, 2024
3 checks passed
@erik-slovak erik-slovak deleted the renovate/txo-semantic-release-2.x branch May 3, 2024 14:20
@txo-github-bot
Copy link

🎉 This PR is included in version 4.0.33 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant