Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Update dependency net.kyori:adventure-text-serializer-legacy to v4.9.3 #43

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 31, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
net.kyori:adventure-text-serializer-legacy 4.8.1 -> 4.9.3 age adoption passing confidence

Release Notes

KyoriPowered/adventure

v4.9.3

🌏 Adventure 4.9.3

This is a small backport of some further issues discovered in the development process of 4.10.0

Fixes 🐛

v4.9.2

🌏 Adventure 4.9.2

This is a small backport of some issues discovered in the development process of 4.10.0

Fixes 🐛

v4.9.1

🌏 Adventure 4.9.1
Fixes 🐛

v4.9.0

🌏 Adventure 4.9.0

Adventure 4.9.0 is a feature release of Adventure, providing new API, some nice performance improvements for the GSON serializer, and a few bug fixes.

Additions ✨
Fixes 🐛
Dependency updates
  • Bump examination from 1.1.0 to 1.3.0
  • Bump JetBrains annotations to 22.0.0
  • serializer-configurate3: Bump Configurate dependency to 3.7.2
  • serializer-configurate4: Bump Configurate dependency to 4.1.1

Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@dkim19375 dkim19375 merged commit f4d4818 into master Oct 31, 2021
@dkim19375 dkim19375 deleted the renovate/net.kyori-adventure-text-serializer-legacy-4.x branch October 31, 2021 13:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants