Feat/minimessage tags

[TheBjoRedCraft]

No description provided.

[Copilot]

Pull request overview

Adds new MiniMessage tags to the core Surf API MiniMessage holder to support additional themed formatting and a small-caps text transformation, plus bumps the project version.

Changes:

• Register a new <note> color tag backed by Colors.NOTE.
• Add a new <small> MiniMessage tag intended to render text in small caps via toSmallCaps().
• Bump version from 3.33.4 to 3.33.5.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
surf-api-core/surf-api-core/src/main/kotlin/dev/slne/surf/api/core/minimessage/SurfMiniMessageHolder.kt	Adds <note> color tag and a <small> modifying tag (small caps).
gradle.properties	Bumps project version to 3.33.5.

Comments suppressed due to low confidence (2)

surf-api-core/surf-api-core/src/main/kotlin/dev/slne/surf/api/core/minimessage/SurfMiniMessageHolder.kt:106

• SmallCapsTag.apply clears children for both TextComponent and non-TextComponent nodes. This will drop nested components produced by other tags (e.g., styles/gradients/hover/click content represented as children) and can change message structure unexpectedly. The modifier should generally preserve children and only adjust the current node’s text content when applicable.

            if (current is TextComponent) {
                return current.content(current.content().toSmallCaps())
                    .children(emptyList())
            }
            return current.children(emptyList())

surf-api-core/surf-api-core/src/main/kotlin/dev/slne/surf/api/core/minimessage/SurfMiniMessageHolder.kt:82

• A new <small> tag is registered, but it isn’t documented in the KDoc “Available Custom Tags” section. Please add it (and what it does) so consumers can discover it.

            tagBuilder.tag("small") { _, _ -> SmallCapsTag() }
        }

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[mergify]

queue

⚠️ Configuration not compatible with required_status_checks ruleset rule

Details

The ruleset rule parameter required_status_checks.strict_required_status_checks_policy is not compatible with draft PR checks. To keep this ruleset enabled, update your Mergify configuration to enable in-place checks: set merge_queue.max_parallel_checks: 1, set every queue rule batch_size: 1, and avoid two-step CI (make merge_conditions identical to queue_conditions). Otherwise, you can disable the Require branches to be up to date before merging option, or allow Mergify to bypass the ruleset or disable the entire ruleset.