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

fix(deps): update dependency space.arim.libertybans:bans-api to v1.1.0-snapshot #15

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
space.arim.libertybans:bans-api 1.1.0-M2 -> 1.1.0-SNAPSHOT age adoption passing confidence

Release Notes

A248/LibertyBans (space.arim.libertybans:bans-api)

v1.1.0-RC2: A Modest Leap Forward

Compare Source

This Leap Day release brings additional stabilization to the 1.1.0 series. Mostly, this consists of solving a few edge cases, making LibertyBans more correct, more accurate, and closer to perfection. We also have a few new features and improvements.

There are no breaking changes in this release compared to 1.1.0-RC1. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.

Bug-fixes:

  • Use serializable isolation to fully handle overlapping punishment commands (b10c847)
  • Smoothly transition the mute cache across usage of /libertybans restart (9cb950b)
  • Detecting the plugin messaging channel no longer emits false warnings (2985be9)

New features:

  • Fantastic Polish translation by @​szyha (#​242)
  • The exemption addon based on LuckPerms weights can now be configured to exempt targets with the same weight as the operator (#​249)

Improvements:

  • Resolve literal UUID arguments in more places (063de6c)
  • Include sub-commands like version, usage, and help in tab-completion (063de6c)

Other:

v1.1.0-RC1: Closer to 1.1.0: Are we there yet?

Compare Source

Having accomplished a slew of exciting new features, this release prepares the way for the impending LibertyBans 1.1.0. The progress made since 1.0.x, in the form of 1.1.0-M1, 1.1.0-M2, and 1.1.0-M3 now enters the release candidate phase.

I would like to thank everyone who tested the layouts feature while it was in development builds. I don't remember who everyone is, but please feel free to remind me if you don't see yourself inside /libertybans about.

There are no breaking changes in this release compared to 1.1.0-M3. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.

Bug-fixes:

  • UUID mismatch on Sponge when player info forwarding is configured (#​229))
  • The 'show-applicable-for-history' turned /warns into /history (fb14929)
  • Folia-specific deadlock on tab completion (#​224)

New features:

  • Punishment layouts, based on a tiered system of escalation. Also known variously as templates, stacked punishments, escalation tracks, etc. (#​180)
  • Kick player via plugin messaging (f7d228d and 235dace)
  • Scoped punishments applicable to a configured server or group of servers (#​146)

API improvements:

  • Add method to get back a builder from a draft punishment by @​MCMDEV and @​KoxSosen (#​211)
  • API for alt detection and management (fdf46d9)
  • Allow retrieving player name from PostPunishEvent and PostPardonEvent (#​76)
  • Complete API for server scopes (#​146)

Other:

  • Create a standalone implementation, currently intended for zxfq's web panel (ed6215b)
  • Faster unmute resolution when synchronizing across instances (19a6494)
  • Add warning to Sponge if newer listener registration API unavailable (19a6494)
  • Initialize the H2 driver if possible; improve driver initialization generally (fb14929)

In 1.1.0, all API additions since 1.0.x will become enshrined in our semantic versioning guarantee, a basic requirement for a stable API not provided by competing punishment plugins. This release candidate (RC) serves the purpose of easing the rollout of 1.1.0 in a gradual, stable fashion. Remember, our Versioning and Support Policy means that anyone, from individual servers to large networks running multiple instances, can enjoy the stability of a LibertyBans release and rest assured that they will receive critical bug-fixes.

v1.1.0-M3: A Release of Relief

Compare Source

With this release comes compatibility improvements and bug-fixes for the most recent Minecraft versions. LibertyBans is now guaranteed to work on 1.20 and 1.20.1 despite changes to server libraries and Paper APIs.

It is again possible to run LibertyBans on the older MariaDB versions 10.3, 10.4, and 10.5. Many users shared hosts' do not yet provide newer MariaDB versions. However, we nonetheless strongly encourage users to pressure hosts to update their database servers. Operating a more recent database will make your server run smoother and be more responsive to gameplay. It will also enable plugin developers to write code more effectively -- and better code means fewer bugs, sleeker design, and high-quality features.

There are no breaking changes in this release compared to 1.1.0-M2. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.

Bug-fixes:

  • Compatibility with Spigot/Paper 1.20's library changes (#​215)
  • Add Paper 1.20.1 support due to Folia API transplant (#​219)
  • Avoid printing warning message on newer Velocity versions due to added library (#​214)
  • Redeclare API methods to preserve binary compatibility (#​207)

New features:

  • Add shortcut-reasons addon (#​124)
  • Support MariaDB 10.3-10.5 by rewriting queries (4a5a095)
  • Ban Bedrock users even when Floodgate isn't installed, by overriding prefix detection (#​195)

API improvements:

  • Add DraftPunishment setter to PunishEvent. Enables modifying the reason and other details when a new punishment is created, as in the shortcut-reasons addon (#​212)

Other:

Attentive users will observe that I (A248) have returned from a personal hiatus due to travel purposes. However, I am very grateful to Simon, LibertyBans' co-maintainer, for providing hot-fixes and development builds when newer Spigot and Paper versions broke LibertyBans. Thanks to Simon, and also @​potatoru for contributing a PR, the bugs were quashed within a couple weeks, at least in development builds. All praise and well-being due to whichever deity you worship, we have now reached a stable release wherein the compatibility bugs are eradicated for good. Therefore I am happy, and relieved, to present this release to you.


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 was generated by Mend Renovate. View the repository job log.

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.

0 participants