chore: remove agent version pinning in the CI #9223
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.





What does this PR do?
This PR removes the pinned AGENT_VERSION, AGENT_PACKAGE_VERSION, and BEAT_VERSION values from the CI environment and updates the .package-version file to 9.1.1.
It also re-enables the upgrade_broken_package_test.go test that was previously skipped due to reliance on pinned versions, since that constraint is now resolved.
Also, I had to bump beats dependency to the commit of 9.1.1 DRA and this required some extra changes in TestGetOtelConfig unit-test
PS: as discussed #8978 (comment) a review from observablt-ci and observablt-ci-contractors is not required (cc @ebeahan @pierrehilbert )
Why is it important?
The version pinning was introduced as a temporary workaround to support the 9.1.0 release. Now that 9.1.1 DRA is released, we are reverting to an unpinned state.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None. This only impacts internal CI setup and test gating. End users are not affected.
How to test this PR locally
Open a draft PR 🙂
Related issues