SNYK: Upgrade com.azure:azure-storage-blob from 12.30.0 to 12.32.0

[kissalk]

Snyk has created this PR to upgrade com.azure:azure-storage-blob from 12.30.0 to 12.32.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 8 versions ahead of your current version.

• The recommended version was released 2 months ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by CodeRabbit

• Chores
  • Updated Azure Storage Blob library dependency to the latest version.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The pom.xml file was updated to upgrade the Azure Storage Blob dependency version from 12.30.0 to 12.32.0 in the dependencyManagement section.

Changes

Cohort / File(s)	Summary
Dependency Version Updates pom.xml	Updated com.azure:azure-storage-blob version in dependencyManagement from 12.30.0 to 12.32.0

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A blob of storage, fresh and new,
Version bumped from thirty, two!
From point-oh to two-point-two it goes,
Dependencies dance as the version grows. 🚀

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is provided but does not follow the repository's required template structure with sections like 'Description of Changes', 'Testing Performed', 'Unit Testing', and 'Documentation Updated'.	Update the description to follow the repository template with explicit sections for Description of Changes, Testing Performed, Unit Testing checklist, and Documentation Updated.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly and specifically identifies the main change: upgrading the Azure Storage Blob dependency from version 12.30.0 to 12.32.0, which matches the file-level changes in pom.xml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira 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 4cdb159 and e4d1e23.

📒 Files selected for processing (1)

• Java/pom.xml

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

**: Pull requests that have "TECH_DEBT" in the title should only contain changes related to typos, unused code, linter/IDE suggestions, swagger specification updates,
and logging improvements. These TECH_DEBT PRs must not affect core functionality. All PRs that are not considered technical debt must include information on what
testing was performed in the description of the PR. If it does not, ask the author to provide details on what testing was performed.
When reviewing code, suggest unit tests using XUnit in the following scenarios:

• If/Else or Switch/Case blocks are introduced or modified — ensure each branch has a corresponding unit test.
• Logic that depends on service or interface configuration — suggest tests to validate different implementations are correctly resolved.
• No network activity (HTTP calls, sockets, etc.) should appear in unit tests. Recommend using mocks (via Moq) for any external communication.
  Large unit tests should be avoided; keeping unit tests small and focused on targeted business logic (i.e. string sanitization)

**: Pull requests that have DOCS in the title should only contain changes related to documentation within the /docs folder or in .md files through-out the code-base. The description
of the PR should specify what documentation was updated. Documentation updates should use EventCatalog.dev structure, where service-specific functionality should be described
in the service's index.mdx (i.e. /services/XXX/index.mdx or /domains/XXX/services/YYY/index.mdx). Configurations that are shared by multiple services should be
reflected in the /docs/docs/config files.

Files:

• Java/pom.xml

🧠 Learnings (1)

📓 Common learnings

Learnt from: seanmcilvenna
Repo: lantanagroup/link-cloud PR: 1241
File: Azure_Pipelines/azure-pipelines.db-schema-creation.yaml:251-270
Timestamp: 2025-11-06T19:08:10.347Z
Learning: In the lantanagroup/link-cloud repository, CI/CD pipeline changes (such as modifications to Azure Pipelines YAML files) are not considered functional features to the application and can be included in TECH_DEBT pull requests.

⏰ 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). (7)

• GitHub Check: Integration Tests
• GitHub Check: Unit Tests for DotNet
• GitHub Check: Smoke Test with Docker Compose
• GitHub Check: Unit Tests for Java
• GitHub Check: Build Documentation
• GitHub Check: Analyze (java-kotlin)
• GitHub Check: Analyze (csharp)

🔇 Additional comments (2)

Java/pom.xml (2)

151-151: Provide testing information in the PR description.

Per the coding guidelines, all PRs that are not considered technical debt must include information on what testing was performed in the description. Even though this is an automated Snyk PR for a dependency upgrade, please add details about what testing was performed to validate this upgrade (e.g., regression tests, integration tests, deployment to a test environment).

As per coding guidelines, PRs without "TECH_DEBT" in the title require testing details.

---

151-151: Upgrade to azure-storage-blob 12.32.0 is safe — no breaking changes or security advisories found.

Release notes show only additive changes: new service version support (2025-11-05), additional copy-error fields for copy-related APIs, and improved error messages. No code modifications required.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}