feat: packet-events 2.9.1

[felipepasc]

…adata

Summary by CodeRabbit

• Chores

  • Updated several dependency versions for improved stability and compatibility.

• Refactor

  • Enhanced type safety and nullability in entity metadata handling, resulting in stronger guarantees and clearer method signatures. No changes to user-facing behavior.

[coderabbitai]

Walkthrough

The changes introduce enhanced type safety and nullability annotations for entity metadata handling in the codebase. Method signatures and field types are updated to use parameterized generics and explicit nullability, while several dependency versions are updated in the build configuration. No control flow or logic is altered.

Changes

File(s)	Change Summary
api/.../meta/EntityMeta.java	Updated method signatures to use @NotNull and generic EntityData<?> return types.
api/.../meta/Metadata.java	Changed field and variable types from raw EntityData to EntityData<?> for type safety.
libs.versions.toml	Bumped versions for adventure, jetbrains-annotations, gson, and packetevents.

Poem

In fields of code where entities dwell,
Type safety blooms, and warnings quell.
With generics strong and nulls declared,
Our metadata’s well-prepared!
Dependencies rise, the versions sing—
A safer hop for everything.
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[felipepasc]

@Tofaa2

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

api/src/main/java/me/tofaa/entitylib/meta/EntityMeta.java (1)

274-282: Parameter clientVersion remains unused – consider pruning or wiring it in.

The method now advertises non-nullability and generic safety (👍), but it still ignores the supplied ClientVersion, returning the same list for every call. Either document the intentional no-op or route the version through to Metadata so callers get version-specific data in the future.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 49943c9 and a4ce058.

📒 Files selected for processing (3)

• api/src/main/java/me/tofaa/entitylib/meta/EntityMeta.java (1 hunks)
• api/src/main/java/me/tofaa/entitylib/meta/Metadata.java (5 hunks)
• libs.versions.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (3)

libs.versions.toml (1)

2-5: Double-check downstream compatibility for the four bumped libraries.

All four updates are minor/patch releases, but they still carry API surface changes (e.g., Adventure 4.22 adds new ComponentLike helpers, PacketEvents ≥ 2.9 bumps some enum names). Please re-run the full integration test suite on the lowest and highest Minecraft server versions you support to ensure no runtime regressions slip in.

api/src/main/java/me/tofaa/entitylib/meta/EntityMeta.java (1)

279-282: Generic wildcard migration looks good.
The override now matches the updated Metadata#getEntries() signature and keeps the list immutable, eliminating raw-type warnings.

api/src/main/java/me/tofaa/entitylib/meta/Metadata.java (1)

108-110: Return type now fully parameterised – nice cleanup.
The unchecked warning suppression is still required for getIndex, but the public API is now type-safe.

[Tofaa2]

lgtm!