[dependabot]

Bumps com.ibm.cos:ibm-cos-java-sdk from 2.15.1 to 2.15.2.

Release notes

Sourced from com.ibm.cos:ibm-cos-java-sdk's releases.

Release 2.15.2

Content

Defect Fixes

• Deprecation notice for IBM COS SDK Java V1

Changelog

Sourced from com.ibm.cos:ibm-cos-java-sdk's changelog.

2.15.2

Content

Defect Fixes

• Deprecation notice for IBM COS SDK Java V1

Commits

• c359c67 Release 2.15.2
• See full diff in compare view

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• parent

✅ POM dependency changes: targeted tests included

Changed properties: ibm-cos-sdk-version

Modules affected by dependency changes (1)

• :camel-ibm-cos

---

🔬 Scalpel shadow comparison — Scalpel: 10 of 723 tested, 3 compile-only — current: 0 all tested

Maveniverse Scalpel detected 10 affected modules (current approach: 0).

Changed properties: ibm-cos-sdk-version

Skip-tests mode would test 10 modules (2 direct + 0 downstream), skip tests for 3 (generated code, meta-modules)

⚠️ Modules only in Scalpel (10)

• camel-ibm-cos
• camel-jbang-mcp
• camel-jbang-plugin-mcp
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-jbang-run
• camel-jpa
• camel-launcher-container
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin

Modules Scalpel would test (10)

• camel-ibm-cos ← effective dep com.ibm.cos:ibm-cos-java-sdk
• camel-jbang-mcp ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator
• camel-jbang-plugin-mcp ← depends on affected reactor module org.apache.camel:camel-jbang-core
• camel-jbang-plugin-tui ← depends on affected reactor module org.apache.camel:camel-jbang-core
• camel-jbang-plugin-validate ← depends on affected reactor module org.apache.camel:camel-jbang-core
• camel-jbang-run ← depends on affected reactor module org.apache.camel:camel-catalog
• camel-jpa ← effective property camel.surefire.fork.additional-vmargs
• camel-launcher-container ← depends on affected reactor module org.apache.camel:camel-launcher
• camel-yaml-dsl-validator ← depends on affected reactor module org.apache.camel:camel-catalog
• camel-yaml-dsl-validator-maven-plugin ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator

Modules with tests skipped (3)

• camel-itest
• camel-yaml-dsl
• camel-yaml-dsl-deserializers

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

All tested modules (38 modules, 6m 20s total)

Total reactor time: 6m 20s

Module	Duration	Status
Camel :: JPA	54.6s	SUCCESS
Camel :: YAML DSL :: Validator	30.9s	SUCCESS
Camel :: Component DSL	26.6s	SUCCESS
Camel :: Catalog :: Camel Catalog	26.2s	SUCCESS
Camel :: JBang :: Plugin :: Validate	25.7s	SUCCESS
Camel :: JBang :: Run	25.0s	SUCCESS
Camel :: IBM :: Cloud Object Storage	24.7s	SUCCESS
Camel :: YAML DSL	24.0s	SUCCESS
Camel :: JBang :: Plugin :: Kubernetes	23.2s	SUCCESS
Camel :: Kamelet Main	18.5s	SUCCESS
Camel :: Docs	16.5s	SUCCESS
Camel :: JBang :: Plugin :: Testing	13.3s	SUCCESS
Camel :: Assembly	9.5s	SUCCESS
Camel :: YAML DSL :: Deserializers	9.0s	SUCCESS
Camel :: Catalog :: Camel Route Parser	8.3s	SUCCESS
Camel :: Catalog :: Camel Report Maven Plugin	8.3s	SUCCESS
Camel :: All Components Sync point	5.9s	SUCCESS
Camel :: JBang :: Plugin :: Generate	5.6s	SUCCESS
Camel :: YAML DSL :: Validator Maven Plugin	4.8s	SUCCESS
Camel :: Catalog :: Maven	3.3s	SUCCESS
Camel :: YAML DSL :: Maven Plugins	3.3s	SUCCESS
Camel :: Catalog :: Suggest (deprecated)	2.1s	SUCCESS
Camel :: JBang :: Plugin :: MCP	1.9s	SUCCESS
Camel :: Coverage	1.4s	SUCCESS
Camel :: JBang :: Integration tests	1.2s	SUCCESS
Camel :: Parent	1.2s	SUCCESS
Camel :: Catalog :: Dummy Component	1.0s	SUCCESS
Camel :: Catalog :: Console	0.9s	SUCCESS
Camel :: JBang :: Plugin :: Edit	0.8s	SUCCESS
Camel :: Endpoint DSL :: Support	0.7s	SUCCESS
Camel :: JBang :: Main	0.7s	SUCCESS
Camel :: Launcher :: Container	0.5s	SUCCESS
Camel :: Endpoint DSL	n/a
Camel :: Integration Tests	n/a
Camel :: JBang :: Core	n/a
Camel :: JBang :: MCP	n/a
Camel :: JBang :: Plugin :: TUI	n/a
Camel :: Launcher	n/a

Top 20 slowest modules:

• Camel :: JPA (54.6s)
• Camel :: YAML DSL :: Validator (30.9s)
• Camel :: Component DSL (26.6s)
• Camel :: Catalog :: Camel Catalog (26.2s)
• Camel :: JBang :: Plugin :: Validate (25.7s)
• Camel :: JBang :: Run (25.0s)
• Camel :: IBM :: Cloud Object Storage (24.7s)
• Camel :: YAML DSL (24.0s)
• Camel :: JBang :: Plugin :: Kubernetes (23.2s)
• Camel :: Kamelet Main (18.5s)
• Camel :: Docs (16.5s)
• Camel :: JBang :: Plugin :: Testing (13.3s)
• Camel :: Assembly (9.5s)
• Camel :: YAML DSL :: Deserializers (9.0s)
• Camel :: Catalog :: Camel Route Parser (8.3s)
• Camel :: Catalog :: Camel Report Maven Plugin (8.3s)
• Camel :: All Components Sync point (5.9s)
• Camel :: JBang :: Plugin :: Generate (5.6s)
• Camel :: YAML DSL :: Validator Maven Plugin (4.8s)
• Camel :: Catalog :: Maven (3.3s)

---

⚙️ View full build and test results

[oscerd]

Patch bump (2.15.1 to 2.15.2), no API change expected, CI green with the ibm-cos dependents built against it. Clean.

Claude Code on behalf of oscerd

[davsclaus]

TL;DR

Approve: patch bump, CI green. Blockers: None. Other findings: 1 (informational)

The only change listed for 2.15.2 is a deprecation notice; the pom only moves transitive versions that Camel mostly manages in the parent anyway. Only parent/pom.xml changes.

[Informational] Upstream now announces "IBM COS SDK Java V1 End-of-Support on August 6, 2027" and recommends the V2 SDK. camel-ibm-cos is built on the V1 line, so a JIRA to plan the move would be worth it. Not related to this bump.

---

Claude Code on behalf of davsclaus. This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.

[davsclaus]

@dependabot rebase