build(deps): bump io.github.miniplaceholders:miniplaceholders-api from 2.2.3 to 3.1.0

[dependabot]

Bumps io.github.miniplaceholders:miniplaceholders-api from 2.2.3 to 3.1.0.

Release notes

Sourced from io.github.miniplaceholders:miniplaceholders-api's releases.

3.1.0 (10/10/2025)

Features

• feat: Sponge commands implementation
• feat: Implement parserel subcommand
• feat: Add --null argument to parse node
• misc: Added bstats metrics

Fixes

• fix: Fixed multiple loading expansions
• fix: Added nullability checks to RelationalAudience
• fix: Fixed command formatting

API Additions

• feat: Added LoadRequirement#requiredClass and LoadRequirement#anyOf
• docs: Replaced some uses of JetBrains annotations with jspecify
• feat: Allow the use of injected constructors when creating an ExpansionProvider

3.0.1

What's Changed

• chore(deps): update actions/setup-java action to v5 by @​renovate[bot] in MiniPlaceholders/MiniPlaceholders#278
• Fixed Fabric initialization
• Updated minimun Sponge-API usage

Full Changelog: MiniPlaceholders/MiniPlaceholders@3.0.0...3.0.1

Placeholders Refactor and Expansion Providers!

Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.

Expansion Provider

As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.

Rewritted API Usage

From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the MiniMessage#deserialize method so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.

[!IMPORTANT]
Due to these changes, most projects created for MiniPlaceholders v2 are incompatible with MiniPlaceholders v3. Please be patient while your favorite projects are updated to the new version.

At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...

[!NOTE]
These new expansions, as mentioned above, are no longer installed as separate plugins/mods. Now, you simply need to place them inside the MiniPlaceholders folder in the expansions folder.

... (truncated)

Changelog

Sourced from io.github.miniplaceholders:miniplaceholders-api's changelog.

3.1.0 (10/10/2025)

Features

• feat: Sponge commands implementation
• feat: Implement parserel subcommand
• feat: Add --null argument to parse node
• misc: Added bstats metrics

Fixes

• fix: Fixed multiple loading expansions
• fix: Added nullability checks to RelationalAudience
• fix: Fixed command formatting

API Additions

• feat: Added LoadRequirement#requiredClass and LoadRequirement#anyOf
• docs: Replaced some uses of JetBrains annotations with jspecify
• feat: Allow the use of injected constructors when creating an ExpansionProvider

Commits

• 6a084a6 release: Version 3.1.0
• d02ac7a [ci skip] Created CHANGELOG.md
• 9bcefee Merge pull request #305 from MiniPlaceholders/renovate/fabric.loader
• 47dd5a9 Merge pull request #302 from MiniPlaceholders/renovate/runtask
• 36dbeed fix(deps): update dependency net.fabricmc:fabric-loader to v0.17.3
• e19527a fix(deps): update runtask to v3.0.1
• f648dd8 misc: Added bstats metrics
• 079b88d docs: Use the NullMarked annotation throughout the module instead of in each ...
• 0f48a4b docs: Replaced some uses of JetBrains annotations with jspecify
• 2608e81 fix: Enable expansion providers after the server initializes.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[rexlManu]

Superseded by 83ad9a5, which updates MiniPlaceholders to 3.2.0 and adjusts the integration for the 3.x API.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.