Update Armeria version to 1.33.2

[armerian]

Summary by CodeRabbit

• Chores
  • Upgraded Armeria dependency from 1.33.1 to 1.33.2 to incorporate the latest upstream fixes and improvements.
  • Patch update enhances stability, performance, and compatibility with no expected behavior changes.
  • Backward-compatible; no user action required.
  • Improves overall reliability and reduces potential edge-case issues observed in prior patch versions.

[coderabbitai]

Walkthrough

A single dependency update: the Armeria version in the versions block of dependencies.toml was bumped from 1.33.1 to 1.33.2. No other files or public APIs were changed.

Changes

Cohort / File(s)	Summary
Dependency version bump dependencies.toml	Updated Armeria version from 1.33.1 to 1.33.2 in [versions].

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled through the vines of deps today,
A tiny hop from .1 to .2—hurray!
Armeria hums, the cables stay tight,
Burrow’s secure for another night.
With whisker-twitch pride, I stamp and thump—
“Patch-level joy!”—a celebratory jump. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-armeria-version

---

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.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit 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:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

dependencies.toml (1)

96-99: Optional: Update Armeria Javadoc URL to match the BOM version.

The Javadoc URL is still pinned to 1.27.0 while 1.33.2 docs are available; consider aligning for consistency.

 [libraries.armeria]
 module = "com.linecorp.armeria:armeria"
- javadocs = "https://www.javadoc.io/doc/com.linecorp.armeria/armeria-javadoc/1.27.0/"
+ javadocs = "https://www.javadoc.io/doc/com.linecorp.armeria/armeria-javadoc/1.33.2/"

Armeria Javadoc 1.33.2 exists on Maven Central. (repo.maven.apache.org)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f4344ab and 8c86cbe.

📒 Files selected for processing (1)

• dependencies.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). (16)

• GitHub Check: build-windows-latest-jdk-21
• GitHub Check: build-ubuntu-latest-jdk-21-snapshot
• GitHub Check: build-ubuntu-latest-jdk-17-coverage
• GitHub Check: build-ubuntu-latest-jdk-17-min-java-11
• GitHub Check: build-macos-latest-jdk-21
• GitHub Check: build-ubuntu-latest-jdk-11
• GitHub Check: lint
• GitHub Check: flaky-tests
• GitHub Check: build-ubuntu-latest-jdk-17-min-java-11
• GitHub Check: build-ubuntu-latest-jdk-11
• GitHub Check: build-macos-latest-jdk-21
• GitHub Check: build-windows-latest-jdk-21
• GitHub Check: build-ubuntu-latest-jdk-21-snapshot
• GitHub Check: build-ubuntu-latest-jdk-17-coverage
• GitHub Check: flaky-tests
• GitHub Check: lint

🔇 Additional comments (1)

dependencies.toml (1)

6-6: Armeria 1.33.2 bump looks good (artifact is published).

Confirmed armeria-bom 1.33.2 is available on Maven Central as of August 28, 2025, so this version ref is valid. (repo.maven.apache.org)