Skip to content

Conversation

elastic-vault-github-plugin-prod[bot]
Copy link
Contributor

Updates references to the new release 9.0.5.

Merge after the release 9.0.4.

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot added Team:Automation Label for the Observability productivity team release labels Jul 13, 2025
@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot requested a review from a team as a code owner July 13, 2025 12:02
@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot requested review from kaanyalti and pkoutsovasilis and removed request for a team July 13, 2025 12:02
pierrehilbert
pierrehilbert previously approved these changes Jul 13, 2025
@pkoutsovasilis pkoutsovasilis requested a review from a team as a code owner July 14, 2025 08:34
# Conflicts:
#	.buildkite/bk.integration.pipeline.yml
@mergify
Copy link
Contributor

mergify bot commented Jul 15, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-version-next-9.0.5 upstream/update-version-next-9.0.5
git merge upstream/9.0
git push upstream update-version-next-9.0.5

@pkoutsovasilis
Copy link
Contributor

I had a sync with @v1v , and we both agree that this manual process of adding of env vars / pinning elastic agent version should not become permanent. I started working on this PR that will automate this process but more importantly the produced PRs by it will reflect correct file-ownership in the PR reviewers. That said, my proposal is just for this time, since these releases are almost upon us, we go with the manual approach; @pierrehilbert @ebeahan you follow what you did before, you wait only for an approval from elastic-agent-control-plane team (eng-prod team is not actually required to review this) and then when the CI is green you merge. Any objections anybody? 🙂

@mergify
Copy link
Contributor

mergify bot commented Jul 20, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-version-next-9.0.5 upstream/update-version-next-9.0.5
git merge upstream/9.0
git push upstream update-version-next-9.0.5

# Conflicts:
#	.buildkite/bk.integration.pipeline.yml
@elastic-sonarqube
Copy link

@elasticmachine
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @elasticmachine

@pierrehilbert pierrehilbert merged commit acfc876 into 9.0 Jul 23, 2025
19 checks passed
@pierrehilbert pierrehilbert deleted the update-version-next-9.0.5 branch July 23, 2025 13:02
@pkoutsovasilis
Copy link
Contributor

Draft PR that removes agent version pinning to be merged as soon as CI is green #9106 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release skip-changelog Team:Automation Label for the Observability productivity team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants