v0.8.0

[danyi1212]

What's Changed

Features

• Reverted OpenTelemetry integration by @danyi1212 in Reverted OpenTelemetry integration #766

Bug fixes and minor improvements

• Added hierarchical lock for applying data updates by @danyi1212 in Added hierarchical lock for applying data updates #745
• Added additional test for hierarchical lock by @danyi1212 in Added additional test for hierarchical lock #768
• cedar-agent-test-arm-build by @EliMoshkovich in cedar-agent-test-arm-build #753
• delete one build and change back to ubuntu-latest by @EliMoshkovich in delete one build and change back to ubuntu-latest #755

Full Changelog: 0.7.16...0.8.0

---

This discussion was created from the release v0.8.0.

[danyi1212]

Why this revert?

Since introducing OpenTelemetry support in v0.7.16, we’ve encountered multiple issues that have impacted both OPAL and its users. These include:

• Bugs in trace collection, leading to incomplete or missing telemetry data.
• Integration difficulties, especially in Alpine Linux environments.
• Documentation gaps, making it harder for users to correctly configure and use OpenTelemetry with OPAL.
• Unexpected stability issues, affecting both open-source users and Permit’s production environment.

These issues have significantly slowed down development and introduced challenges that we weren’t able to fully anticipate before merging the feature.

What’s Next?

• OpenTelemetry will remain available in OPAL v0.7.x, where we’ll continue to apply patches and fixes.
• Starting from OPAL v0.8.x, OpenTelemetry will be removed while we work on refining the implementation.
• Once we’ve improved stability, documentation, and integration, we plan to reintroduce OpenTelemetry in a future release.

We appreciate everyone’s patience as we work through this, and we’re committed to bringing OpenTelemetry back in a way that’s more reliable and user-friendly. If you have feedback or suggestions, we’d love to hear from you!