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

Update dependency eu.cloudnetservice.cloudnet:bridge to v4.0.0-RC11.1 #8

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eu.cloudnetservice.cloudnet:bridge (source) 4.0.0-RC10 -> 4.0.0-RC11.1 age adoption passing confidence

Release Notes

CloudNetService/CloudNet-v3 (eu.cloudnetservice.cloudnet:bridge)

v4.0.0-RC11.1: - Blizzard

Compare Source

Update 4.0.0-RC11.1 - Blizzard

We are pleased to announce the release candidate 11.1 for CloudNet 4.0. This release contains some hotfixes for problems that arised with the release of RC11. We urge all users to install the update, as we will no longer provide support for RC11. Users who want to switch from 3.4.X to 4.0 can find instructions in the release information for RC1.

Please also see the changelog for RC6, this contains the detailed information about the switch to Dependency Injection in the API.

Cheers!
(Please remember, CloudNet is provided as-is - we are not responsible for data loss or corruption. You are encouraged to back up your files before any updates!)

Important notice

  • Make sure to update ProtocolLib to the latest 5.3.0-RELEASE
  • Everybody who disabled Spark can re-enable Spark now safely
  • Ensure that CloudPerms is removed from all your templates

Changelog

Fixes

  • Spark async-profiler is disabled on non arm systems as it causes server crashes (#​1533)
  • Recent versions of Spigot/Paper no longer crash with a java.lang.VerifyError: Bad return type error (#​1535)
  • The default task setup is back when executing the CloudNet setup for the first time (#​1534)
Dependencies
artifact id usage
driver When developing plugins or modules, available on all platforms.
node When developing a module which needs more specific access to node functions than the driver can offer.
wrapper-jvm When developing plugins which need some more specific access to the service api than the driver can offer.
bridge When trying to catch player events and/or interacting with players regardless where they are on the network.
bom When you want to import all dependencies with the same version based on the imported bill of materials.

To add the CloudNet dependency using gradle:

repositories {
  // ensure maven central is added
  mavenCentral()
}

dependencies {
  // optional - you can also specify versions directly
  implementation platform('eu.cloudnetservice.cloudnet:bom:4.0.0-RC11.1')
  compileOnly 'eu.cloudnetservice.cloudnet:driver'

  // without bom
  compileOnly 'eu.cloudnetservice.cloudnet:driver:4.0.0-RC11.1'
}

To add the CloudNet dependency using maven:

<!-- optional - you can also specify versions directly -->
<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>eu.cloudnetservice.cloudnet</groupId>
      <artifactId>bom</artifactId>
      <version>4.0.0-RC11</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

<dependencies>
  <dependency>
    <groupId>eu.cloudnetservice.cloudnet</groupId>
    <artifactId>driver</artifactId>
    <version>4.0.0-RC11</version> <!-- only needed when bom is not used -->
    <scope>provided</scope>
  </dependency>
</dependencies>

🔗 Links

v4.0.0-RC11: - Blizzard

Compare Source

Update 4.0.0-RC11 - Blizzard

We are pleased to announce the eleventh release candidate for CloudNet 4.0. This release includes fixes for reported issues and some improvements. We urge all users to install the update, as we will no longer provide support for RC10. Users who want to switch from 3.4.X to 4.0 can find instructions in the release information for RC1.

Please also see the changelog for RC6, this contains the detailed information about the switch to Dependency Injection in the API.

Cheers!
(Please remember, CloudNet is provided as-is - we are not responsible for data loss or corruption. You are encouraged to back up your files before any updates!)

Upgrading

Due to some changes the upgrading step is a bit more complicated this time.

  • CloudNet requires JDK 23 everywhere now.
  • Velocity 3.3.0-SNAPSHOT is required now.

After installing JDK 23 download the CloudNet.zip and replace your launcher.jar with the one from the archive.

As announced the CloudPerms module and thus the SimpleNameTags and Chat plugins are not available anymore. Please delete the CloudPerms module before starting.

Changelog

Breaking API

  • The Task class was replaced with the CompletableFutures from the standard library. Some helper methods can be found in the TaskUtil class.

Improvements

  • Minecraft 1.21.1 is now fully supported (#​1477)
  • Limbo Minecraft servers are now supported (#​1412)
  • ServiceRemoteInclusions have a new cache strategy option to determine how to cache them (#​1413)
  • NPCs can now be rotated using the new rotate command (#​1497)
  • The networking was fully rewritten to the new JDK 22 classfile api (#​1433)
  • The terminal is now using a new implementation (#​1441)
  • WorldEdit and FAWE can now be used in older Minecraft Versions together with JDK 22 (#​1429)
  • New cloudnet luckperms plugin to bring tasks and groups into luckperms (#​1258)

Fixes

  • The npc command sets the showfullservices option now correctly.
  • Fabric fake players are not detected as real players anymore.
  • Skipping the proxy fallback question is now working again.
Dependencies
artifact id usage
driver When developing plugins or modules, available on all platforms.
node When developing a module which needs more specific access to node functions than the driver can offer.
wrapper-jvm When developing plugins which need some more specific access to the service api than the driver can offer.
bridge When trying to catch player events and/or interacting with players regardless where they are on the network.
bom When you want to import all dependencies with the same version based on the imported bill of materials.

To add the CloudNet dependency using gradle:

repositories {
  // ensure maven central is added
  mavenCentral()
}

dependencies {
  // optional - you can also specify versions directly
  implementation platform('eu.cloudnetservice.cloudnet:bom:4.0.0-RC11')
  compileOnly 'eu.cloudnetservice.cloudnet:driver'

  // without bom
  compileOnly 'eu.cloudnetservice.cloudnet:driver:4.0.0-RC11'
}

To add the CloudNet dependency using maven:

<!-- optional - you can also specify versions directly -->
<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>eu.cloudnetservice.cloudnet</groupId>
      <artifactId>bom</artifactId>
      <version>4.0.0-RC11</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

<dependencies>
  <dependency>
    <groupId>eu.cloudnetservice.cloudnet</groupId>
    <artifactId>driver</artifactId>
    <version>4.0.0-RC11</version> <!-- only needed when bom is not used -->
    <scope>provided</scope>
  </dependency>
</dependencies>

🔗 Links


Configuration

📅 Schedule: Branch creation - "on the first day of the month" (UTC), 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.

@renovate renovate bot added the Renovate label Nov 1, 2024
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.

0 participants