Bump io.opentelemetry.contrib:opentelemetry-cloudfoundry-resources from 1.59.0-alpha to 1.60.0-alpha

[dependabot]

Bumps io.opentelemetry.contrib:opentelemetry-cloudfoundry-resources from 1.59.0-alpha to 1.60.0-alpha.

Release notes

Sourced from io.opentelemetry.contrib:opentelemetry-cloudfoundry-resources's releases.

Version 1.59.0

This release targets the OpenTelemetry Java Instrumentation 2.30.0.

⚠️ Breaking changes

• Declarative config YAML now only accepts integer millisecond values for duration properties. Users should no longer specify ms as a suffix in duration literals (eg. 100ms should be given as just 100). (#2988)

Disk buffering

• Replace the read-after-write delay with atomic rename: the writer now appends to <timestamp>.tmp and atomically renames to its final numeric name on close, so finalized files become visible to the reader immediately. Orphan *.tmp files left behind by an unclean shutdown are recovered on the next storage open. The minFileAgeForReadMillis default changes from 33s to 0 and is no longer required to be greater than maxFileAgeForWriteMillis. (#2897)

Dynamic control

• Align to name and ID in spec for policies (#2926)
• Add identity to existing policy classes (#2942)
• Add deleted policy (#2943)
• Apply deleted policy to telemetry policy deletion flow (#2944)
• Make TelemetryPolicy an interface (#2948)
• Refactor sourceKey to policyId to align to spec (#2949)
• Add initializing from declarative config. (#2967)
• Align aggregation to spec (#2960)
• Add priority ordering to sources (#2970)
• Add SourceKind to TelemetryPolicy (#2972)
• Sampling rate is only changed if it has changed value (#2957)
• SourceKind is now propagated across validation and policy creation (#2973)
• Drop comparable policies according to priority for an update (#2974)
• Add change checking for file & http sources (#2975)
• Refactor OpampPolicyProvider for other PolicyProviders (#2987)

GCP resources

• Add a limit on the metadata server response body size read into memory at once by the resource detector (#2883)

IBM MQ metrics

• Queue manager uptime is now reported (#2835)
• Update metric unit from 'microseconds' to 'us' (#2887)
• Remove the in development notice of the IBM MQ metrics component and move it to beta (#2982)

OpAMP client

• Add the ability to receive custom messages (#2990)

🙇 Thank you

This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:

@​atoulme

... (truncated)

Changelog

Sourced from io.opentelemetry.contrib:opentelemetry-cloudfoundry-resources's changelog.

Changelog

Unreleased

Version 1.60.0 (2026-08-28)

⚠️ Breaking changes

• Remove the deprecated EventToSpanEventBridge log processor and its declarative configuration entry. (#3029)

Dynamic control

• Fix policy parsing for JSON and line-based configurations so valid policies are accepted consistently. (#3010)

GCP authentication extension

• Add support for ID token authentication for GCP exports. (#2999)

Version 1.59.0 (2026-07-24)

⚠️ Breaking changes

• Declarative config YAML now only accepts integer millisecond values for duration properties. Users should no longer specify ms as a suffix in duration literals (eg. 100ms should be given as just 100). (#2988)

Disk buffering

• Replace the read-after-write delay with atomic rename: the writer now appends to <timestamp>.tmp and atomically renames to its final numeric name on close, so finalized files become visible to the reader immediately. Orphan *.tmp files left behind by an unclean shutdown are recovered on the next storage open. The minFileAgeForReadMillis default changes from 33s to 0 and is no longer required to be greater than maxFileAgeForWriteMillis. (#2897)

Dynamic control

• Align to name and ID in spec for policies (#2926)
• Add identity to existing policy classes (#2942)
• Add deleted policy (#2943)
• Apply deleted policy to telemetry policy deletion flow

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)