Bump github.com/elastic/elastic-agent-autodiscover from 0.6.3 to 0.6.4 #3588
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/elastic/elastic-agent-autodiscover](https://github.com/elastic/elastic-agent-autodiscover) from 0.6.3 to 0.6.4. - [Release notes](https://github.com/elastic/elastic-agent-autodiscover/releases) - [Changelog](https://github.com/elastic/elastic-agent-autodiscover/blob/main/CHANGELOG.md) - [Commits](elastic/elastic-agent-autodiscover@v0.6.3...v0.6.4) --- updated-dependencies: - dependency-name: github.com/elastic/elastic-agent-autodiscover dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
automation
skip-changelog
Team:Elastic-Agent
|
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
|
This pull request does not have a backport label. Could you fix it @dependabot[bot]? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
|
SonarQube Quality Gate
|
🌐 Coverage report
|
pierrehilbert
deleted the
dependabot/go_modules/github.com/elastic/elastic-agent-autodiscover-0.6.4
branch
|
@pierrehilbert this contains a breaking change to autodiscover, it needs the changelog fragment from #3591 (review). Possibly just forward porting that PR to main once it merges will do it. |
|
Correct me if I'm wrong here but because we will have the changelog in 8.10.X and main is for 8.12, we won't need to have the fragment on main "even if it would have been cleaner" as this will be removed and we will get it in the 8.10.X consolidated changelog |
|
👍 yes you are correct, I am used to seeing the changes go to main first but this is fine as is. |
Bumps github.com/elastic/elastic-agent-autodiscover from 0.6.3 to 0.6.4.
Commits
285f0bbDisable Deployment and Replicaset enrichment by default (#62)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)