Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github.com/coredns/coredns from 1.3.0 to 1.6.6 #246

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 28, 2023

Bumps github.com/coredns/coredns from 1.3.0 to 1.6.6.

Changelog

Sourced from github.com/coredns/coredns's changelog.

Makefile for releasing CoreDNS

The release is controlled from coremain/version.go. The version found there is

used to tag the git repo and to build the assets that are uploaded to GitHub.

The release should be accompanied by release notes in the notes/ subdirectory.

These are published on coredns.io. For example see: notes/coredns-1.5.1.md

Use make -f Makefile.release notes to create a skeleton notes document.

Be sure to prune the PR list a bit, not everything is worthy!

As seen in notes/coredns-1.5.1.md we want to style the notes in the following manner:

* important changes at the top

* people who committed/review code (the latter is harder to get)

* Slightly abbreviated list of pull requests merged for this release.

Steps to release, first:

1. Up the version in coremain/version.go

2. Do a make -f Makefile.doc # This has been automated in GitHub, so you can probably skip this step

3. go generate

4. Send PR to get this merged.

Then:

1. Open an issue for this release

2. In an issue give the command: /release master VERSION

Where VERSION is the version of the release - the release script double checks this with the

actual CoreDNS version in coremain/version.go

3. (to test as release /release -t master VERSION can be used.

See https://github.com/coredns/release for documentation README on what needs to be setup for this to be

automated (can still be done by hand if needed). Especially what environment variables need to be

set! This further depends on Caddy being setup and dreck running as a plugin in Caddy.

To release we run, these target from the this Makefile.release ordered like:

* make release

* make github-push

Testing this is hard-ish as you don't want to accidentally release a coredns. If not executing the github-push target

you should be fine.

Docker image creation and upload are now separate steps, because it often failed before. See the Makefile.docker for

details.

ifeq (, $(shell which curl)) $(error "No curl in $$PATH, please install") endif

NAME:=coredns

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 28, 2023
Bumps [github.com/coredns/coredns](https://github.com/coredns/coredns) from 1.3.0 to 1.6.6.
- [Release notes](https://github.com/coredns/coredns/releases)
- [Changelog](https://github.com/coredns/coredns/blob/master/Makefile.release)
- [Commits](coredns/coredns@v1.3.0...v1.6.6)

---
updated-dependencies:
- dependency-name: github.com/coredns/coredns
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/coredns/coredns-1.6.6 branch from 6a01b30 to 42177c7 Compare March 3, 2023 18:26
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Mar 3, 2023

Superseded by #260.

@dependabot dependabot bot closed this Mar 3, 2023
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/coredns/coredns-1.6.6 branch March 3, 2023 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants