GH-533 Update all dependencies (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
actions/checkout	action	major	v3.6.0 -> v4.1.1
actions/setup-java	action	major	v3.13.0 -> v4.0.0
actions/upload-artifact	action	major	v3.1.3 -> v4.0.0
com.google.guava:guava	dependencies	major	32.1.3-jre -> 33.0.0-jre
net.kyori:blossom (source)	dependencies	major	1.3.1 -> 2.1.0

---

Release Notes

actions/checkout (actions/checkout)

v4.1.1

Compare Source

What's Changed

• Update CODEOWNERS to Launch team by @​joshmgross in https://github.com/actions/checkout/pull/1510
• Correct link to GitHub Docs by @​peterbe in https://github.com/actions/checkout/pull/1511
• Link to release page from what's new section by @​cory-miller in https://github.com/actions/checkout/pull/1514

New Contributors

• @​joshmgross made their first contribution in https://github.com/actions/checkout/pull/1510
• @​peterbe made their first contribution in https://github.com/actions/checkout/pull/1511

Full Changelog: actions/checkout@v4.1.0...v4.1.1

v4.1.0

Compare Source

• Add support for partial checkout filters

v4.0.0

Compare Source

• Support fetching without the --progress option
• Update to node20

actions/setup-java (actions/setup-java)

v4.0.0

Compare Source

What's Changed

In the scope of this release, the version of the Node.js runtime was updated to 20. The majority of dependencies were updated to the latest versions. From now on, the code for the setup-java will run on Node.js 20 instead of Node.js 16.

Breaking changes

• Update Node.js runtime to version 20 by @​aparnajyothi-y in https://github.com/actions/setup-java/pull/558

Non-breaking changes

• Adding support for microsoft openjdk 21.0.0 by @​ralfstuckert in https://github.com/actions/setup-java/pull/546
• Update @​actions/cache dependency and documentation by @​IvanZosimov in https://github.com/actions/setup-java/pull/549
• Implementation of the cache-dependency-path option to control caching dependency by @​itchyny in https://github.com/actions/setup-java/pull/499

New Contributors

• @​ralfstuckert made their first contribution in https://github.com/actions/setup-java/pull/546
• @​itchyny made their first contribution in https://github.com/actions/setup-java/pull/499

Full Changelog: actions/setup-java@v3...v4.0.0

actions/upload-artifact (actions/upload-artifact)

v4.0.0

Compare Source

What's Changed

The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.

For more information, see the @​actions/artifact documentation.

New Contributors

• @​vmjoseph made their first contribution in https://github.com/actions/upload-artifact/pull/464

Full Changelog: actions/upload-artifact@v3...v4.0.0

KyoriPowered/blossom (net.kyori:blossom)

v2.1.0: 🌼 blossom 2.1.0

blossom 2.1.0 is a feature release introducing some minor QOL features, and fixing handling of included files. It should be a straightforward upgrade for existing users of Blossom 2.0.1.

✨ Features

• Add default variant template property when using variants by @​jpenilla in https://github.com/KyoriPowered/blossom/pull/37
• feat: Add helper API to make it easier to register custom sets by @​zml2008 in https://github.com/KyoriPowered/blossom/pull/38

🐛 Fixes

• Fix included files by @​jpenilla in https://github.com/KyoriPowered/blossom/pull/36

Full Changelog: KyoriPowered/blossom@v2.0.1...v2.1.0

v2.0.1: 🌼 blossom 2.0.1

A hotfix release for blossom 2.0.0. See its release notes for information about the major changes in that release.

🐛 Fixes

• fix: Correct inverted header newline condition by @​zml2008 in https://github.com/KyoriPowered/blossom/pull/27

Full Changelog: KyoriPowered/blossom@v2.0.0...v2.0.1

v2.0.0: 🌼 blossom 2.0.0

NOTE 2.0.1 has been released as a hotfix to this version, resolving an issue with applying headers. See its release notes for details about those changes. We recommend using 2.0.1 instead, but the following release notes still provide helpful migration advice.

Blossom 2.0.0 is a complete redesign of the Blossom plugin to provide a fully featured solution for source and resource templating. It is based on the template engine used to build Sponge's math library. See the README for an introduction to Blossom v2's features.

Migrating from Blossom v1

The key difference in functionality with v2 is that only source files within the specific templates root will be processed as templates -- all other source files will have no other change.

This allows more efficient execution since templates only need to be regenerated when there are actual changes, and means that any compile errors in non-templated files will be linked correctly in IDE logs. Template output will also be exposed correctly to any IDE run configurations, since templates are processed at project import time.

The quickest migration from v1 starts with a buildscript like:

sourceSets {
  main {
    blossom {
      javaSources {
        // template values here
        property("token", value)
      }
    }
  }
}

Then place files that should be processed as templates in src/main/java-templates. These are Pebble templates, so the variable syntax is {{ token }}. See their documentation for more of the language's features.

Substitute java with groovy, kotlin, or scala as desired.

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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]

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.