How to build and ship a release
These are the instructions for producing a release.
CircleCI will do most of the work for you. You will need to edit the draft release notes.
Please change the version number as appropriate. Substitute (for example)
3.20.0any place you see
VERSIONin this doc.
git checkout master
go mod tidy
git add -A
git commit -m "Update generated files for VERSION"
This will update the following generated files:
git tag -a v3.20.0
git push origin --tags
CircleCI Release Screenshot
The draft release notes are created for you. In this step you'll edit them.
The CircleCI build uses GoReleaser which produces the GitHub Release with Release Notes derived from the commit history between now and the last tag. These notes are just a draft and needs considerable editing. You can also find a copy of the release notes in the CircleCI
releasejob Artifacts. These release notes will be used in multiple places (release notes, email announcements, etc.)
Release notes style guide:
- Entries in the bullet list should be phrased in the positive: "Feature FOO now does BAR". This is often the opposite of the related issue, which was probably phrased, "Feature FOO is broken because of BAR".
- Every item should include the ID of the issue related to the change. If there was no issue, create one and close it.
- Sort the list most important/exciting changes earlier in the list.
- Items related to a specific provider should begin with the all-caps name of the provider, such as "ROUTE53: Added support for sandwiches (#100)"
Deprecation warningssection should just copy from
README.md. If you change one, change it in the README too (you can make that change in this PR).
This release includes many new providers (FILL IN), dozens
of bug fixes, and FILL IN.
### Breaking changes:
* FILL IN
### Major features:
* FILL IN
### Provider-specific changes:
* FILL IN
### Other changes and improvements:
* FILL IN
### Deprecation warnings:
Email the release notes to the mailing list: (note the format of the Subject line and that the first line of the email is the URL of the release)
ANNOUNCEMENT: dnscontrol v$VERSION has been released! https://github.com/StackExchange/dnscontrol/releases/tag/v$VERSION
Mention the fact that you did this release in your weekly accomplishments.
If you are at Stack Overflow:
- Add the release to your weekly snippets
- Run this build:
dnscontrol_embed - Promote most recent artifact into ExternalDNS repo
If you bump the major version, you need to change all the source files. The last time this was done (v2 -> v3) these two commands were used. They're included her for reference.
CircleCI is configured to run an integration test for any provider listed in the "provider" list. However the test is skipped if the
*_DOMAINvariable is not set. For example, the GCLOUD provider integration test is only run if
- Q: Where is the list of providers to run integration tests on?
- A: In
.circleci/config.ymllook for the "provider" list:
- Q: Where are non-secret environment variables stored?
- A: In
- 2.Add the name of the provider (ALL CAPS) to the "provider" list.
- 3.Any non-secret env variables needed? Add them to the "environment" section.
Overview: You will fork the repo and add any secrets to your fork. For security reasons you won't have access to the secrets from the main repository.
- 1.Fork StackExchange/dnscontrol in GitHub.If you already have a fork, be sure to use the "sync fork" button on the main page to sync with master.
- 3.Set up a CircleCI projectOn the projects page, find "dnscontrol". Click "Set Up Project". Use the "Fastest" method (use the existing
.circleci/config.ymlfile).If you get the error message below, go to the "Organization Settings" (left nav). Then "Security" (left nav) and set "Allow Uncertified Orbs" under "Orb Security Settings" to "Yes".
- 4.Add the secret env variables:Go to Project Settings (for this project), and "Environment Variables".
- Add env variable
provider_DOMAINwhere "provider" is the all caps name of the provider. For example add
BIND_DOMAINwith the value "example.com"
- 5.Start a buildFrom the pipelines page, you can trigger a build by setting the branch to "master" then click "trigger".Merges to "master" result in the software being built. Merges to any other branch causes integration tests to run.Verify that your tests are working properly by making a branch. You'll see on the
Run integration tests for _____ providerstep the results of the test.Some notes:
- Tests that are skipped take about 3 seconds to complete. In other words, if you look at a list of tests, you can tell which ones were skipped by looking at the completion time.
- Free accounts don't have access to
2xlargeinstanace. You'll either need to upgrade your CircleCI account or change
.circleci/config.ymlin your fork. Please be careful to not include that file when you send a PR. See #1935 (Anyone have tips on how to make that easier?)
Rebuilding flatter requires go1.17.1 and the gopherjs compiler.
Build the software:
export GOPHERJS_GOROOT="$(go1.17.1 env GOROOT)"
List out-of-date modules and update any that seem worth updating:
go install github.com/psampaz/[email protected]
go list -mod=mod -u -m -json all | go-mod-outdated -update -direct
# If any are out of date, update via:
go get module/path
# Once the updates are complete, tidy up:
go mod tidy