chore(deps): update coredns to 1.14.6 - #271
Merged
Merged
Conversation
Signed-off-by: Teko012 <112829523+Teko012@users.noreply.github.com>
hagaibarel
approved these changes
Jul 29, 2026
Contributor
Author
|
@hagaibarel Thanks for the quick approval! Looks like the pipeline is green. Should we merge? :) |
Collaborator
Merged, thanks for the PR! |
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why is this pull request needed and what does it do?
Updates the CoreDNS application to the latest release,
1.14.6(previously1.13.1).This bumps the chart
appVersionfrom1.13.1to1.14.6and, since this is a major application update, bumps the chartversionfrom1.46.2to1.47.0(minor) per the versioning guidelines. Theartifacthub.io/changeschangelog annotation has been updated to cover the change in this release.Which issues (if any) are related?
None.
Checklist:
Changes are automatically published when merged to
main. They are not published on branches.Note on DCO
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.