v0.7.1
What's new
⚠️ Breaking Changes
This release of orchestrion
is a major re-design: in order to improve the coverage achievable with Orchestrion, it moved from being a coding-time tool (where check-in instrumented code) to a build-time tool, moving the instrumentation code completely out of the way.
Migration from versions up to 0.6.0
:
- in order to avoid doubly-instrumented code, we strongly advise users of Orchestrion until version
0.6.0
to runorchestrion -rm .
to remove any existing orchestrion-inserted code from their codebase before upgrading to Orchestrion0.7.0
and greater. - once done, follow the installation instructions in the README file.
Highlights
Orchestrion now runs as a Go toolchain -toolexec
tool, allowing it to instrument all Go code included in the final binary, including any and all transitive dependencies as well as the standard library; while only changing a single build command. This allows maximization of the profiling and application security coverage, without requiring any significant developer effort.
The instrumentation code remains out of the way so that developers can focus on building their product without having to worry about – or be distracted by – verbose instrumentation code.
Bug fixes
- Dot-imports result in instrumentation failure (#50)
- Cannot decorate multiple packages with the same apparent package name (#56)
Full Changelog: v0.6.0...v0.7.1