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 to v23.0.8 #513

Merged
merged 1 commit into from
May 15, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 23.0.5 -> 23.0.8 age adoption passing confidence

Release Notes

semantic-release/semantic-release (semantic-release)

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 added the type:dependencies 🔧 Update one or more dependencies label Apr 7, 2024
@renovate renovate bot enabled auto-merge (squash) April 7, 2024 15:53
Copy link

codecov bot commented Apr 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 31.61%. Comparing base (5937788) to head (986d200).
Report is 3 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #513      +/-   ##
==========================================
+ Coverage   31.34%   31.61%   +0.26%     
==========================================
  Files          58       58              
  Lines        3155     3122      -33     
==========================================
- Hits          989      987       -2     
+ Misses       2166     2135      -31     
Flag Coverage Δ
shulker-addon-matchmaking 21.90% <ø> (+0.38%) ⬆️
shulker-crds 92.30% <ø> (ø)
shulker-kube-utils 11.25% <ø> (-0.44%) ⬇️
shulker-operator 59.45% <ø> (+0.96%) ⬆️
shulker-utils 88.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 12 files with indirect coverage changes

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from a32b8cd to 618d2bc Compare April 17, 2024 18:21
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23.0.6 chore(deps): update dependency semantic-release to v23.0.7 Apr 17, 2024
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 618d2bc to 6bae103 Compare April 23, 2024 21:58
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23.0.7 chore(deps): update dependency semantic-release to v23.0.8 Apr 23, 2024
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 3cb3252 to df22c12 Compare May 15, 2024 12:38
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from df22c12 to 986d200 Compare May 15, 2024 12:41
@renovate renovate bot merged commit e4ff1be into main May 15, 2024
14 of 15 checks passed
@renovate renovate bot deleted the renovate/semantic-release-monorepo branch May 15, 2024 12:54
Copy link

🎉 This issue has been resolved in version 0.9.0 🎉

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
type:dependencies 🔧 Update one or more dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants