[x] Add the CAKE_GITHUB_USERNAME and CAKE_GITHUB_PASSWORD environment variables into your system. These should be of a user who has access to the Cake GitHub Repository.
[x] Make sure develop branch of cake-build/cake is up to date git fetch then git rebase origin/develop.
[x] Make sure main branch of cake-build/cake is up to date git fetch then git rebase origin/main.
[x] Make sure develop branch of cake-build/website is up to date git fetch then git rebase origin/develop.
[x] Make sure master branch of cake-build/website is up to date git fetch then git rebase origin/master.
[x] Make sure master branch of cake-build/example is up to date git fetch then git rebase origin/master.
[x] Make sure develop branch of cake-build/resources is up to date git fetch then git rebase origin/develop.
[x] Make sure master branch of cake-build/resources is up to date git fetch then git rebase origin/master.
[x] Make sure that all issues associated with pull requests getting released in this milestone are associated with the milestone, or that the pull request is associated with the milestone, if no issue was created.
[x] Make sure you have a fork of Homebrew/homebrew-core
[x] Make sure upstream points at Homebrew/homebrew-core
[x] Make sure master branch of Homebrew/homebrew-core is up to date; git fetch then git rebase upstream/master.
Automated Approach
[x] Make sure you have a fork of Homebrew/homebrew-core.
[x] Run the Prereqs.ps1 file, using the following as an example .\Prereqs.ps1 -GithubUsername gep13 (use your own username). This will clone a new version of all required repositories.
Let people know that things are happening...
[x] Go to the Gitter room for Cake and inform people that a release is away to happen. Use a message similar to the following @/all We will soon start preparing for the [0.27.1 release](https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.
[x] Go to the Gitter room for Cake-Contrib and inform people that a release is away to happen. Use a message similar to the following @/all We will soon start preparing for the [0.27.1 release](https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.
[x] Go to the General Channel in the Slack Team for Cake-Contrib and inform peoploe that a release is away to happen. Use a message similar to the following @channel We will soon start preparing for the 0.27.1 release (https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.
[x] Using the Cake Twitter account, tweet to let people know that the release is away to happen. Use something like the following We are starting to prepare our next release, 0.27.1 (https://github.com/cake-build/cake/milestone/50). This is your friendly reminder that if you haven't pinned to a specific version of Cake, you should do it now :-) https://cakebuild.net/docs/tutorials/pinning-cake-version
[x] Retweet the above from the cake-contrib twitter account
GitHub Issues Pre-requisites
[x] Make sure all issues within the milestone are tagged with either Bug, Feature, Improvement, Documentation, Breaking change, or Build
[x] Make sure all issues associated with the milestone are closed
[x] Make sure that all issues only have 1 label associated with them
When doing a release
[x] Create branch locally to match the name of the release, for example git checkout -b release/0.7.0 develop
[x] Update releasenotes.md to include next version number as a placeholder and save the file
[x] Create release notes on GitHub using the ReleaseNotes task (.\build.ps1 -Target ReleaseNotes)
[x] Update releasenotes.md with generated content (making sure to keep the formatting the same)
[x] Build everything (./build.ps1) to make sure it works.
[x] Commit the changes to releasenotes.md and solutioninfo.cs. Use comment like (build) Updated version and release notes.
[x] At this point, if you want to share the work to date, and validate something, push the local release branch to GitHub
[x] Assuming everything is ok, switch to main branch (git checkout main)
[x] Merge release branch to the maingit merge --no-ff release/0.7.0
[x] Build everything (./build.ps1) to make sure it works (we can never be too sure).
[x] Assuming that everything went ok, go to the draft release in GitHub and click Edit
[x] Click the Publish Release button
[x] This will trigger another build in AppVeyor, but this time with a tag.
[x] From the AppVeyor Log, take a note of the generated Hash from the Publish-HomeBrew task
[x] Switch to develop branch git checkout develop
[x] Merge release branch into develop git merge --no-ff release/0.7.0
[x] Resolve any merge conflicts
[x] Bump the Cake Tool Version number in build.ps1 and build.sh to the latest released version, i.e. the version you just released
[x] Build everything (./build.ps1) to make sure it works.
[x] Commit the changes to build.ps1 and build.shNOTE: There will be other changes to the *.json files as well, commit everything. Use commit message like (build) Updated Cake tool to version 0.13.0
[x] Push develop branch.
[x] Delete the local release branch that was created git branch -d release/0.7.0 (and the remote one, if pushed to GitHub git push origin --delete release/0.7.0)
When doing a hotfix
[ ] Create branch locally to match the name of the hotfix, for example git checkout -b hotfix/0.27.1 main
[ ] If there is an open Pull Request, which is targetting the wrong base branch, do the following (where 2133 is the number of PR on GitHub)
[ ] git fetch origin pull/2133/head:pr2133
[ ] git checkout pr2133
[ ] git rebase --onto hotfix/0.27.1 develop
[ ] git checkout hotfix/0.27.1
[ ] git merge --no-ff pr2133
[ ] Update releasenotes.md to include next version number as a placeholder and save the file
[ ] Create release notes on GitHub using the ReleaseNotes task (.\build.ps1 -Target ReleaseNotes or ./build.sh --target releasenotes
[ ] Update releasenotes.md with generated content (making sure to keep the formatting the same)
[ ] Build everything (./build.ps1 or ./build.sh) to make sure it works.
[ ] Commit the changes to releasenotes.md and solutioninfo.cs Use comment like (build) Updated version and release notes.
[ ] At this point, if you want to share the work to date, and validate something, push the local hotfix branch to GitHub
[ ] Assuming everything is ok, switch to main branch (git checkout main)
[ ] Merge hotfix branch into maingit merge --no-ff hotfix/0.6.4
[ ] Build everything (./build.ps1 or ./build.sh) to make sure it works (we can never be too sure).
[ ] Bump the Cake Tool Version number in build.ps1 and build.sh to the latest released version, i.e. the version you just released
[ ] Commit the changes to build.ps1 and build.sh. Use commit message like (build) Updated Cake tool to version 0.13.0
[ ] Build everything (./build.ps1 or ./build.sh) to make sure it works.
[ ] Push develop branch.
[ ] Delete the local hotfix branch that was created git branch -d hotfix/0.6.4 (and the remote one, if pushed to GitHub git push origin --delete hotfix/0.6.4)
After a release/hotfix
[x] Make sure that everything has pushed correctly to nuget
[x] Make sure that everything has pushed correctly to chocolatey
cake.portableNOTE: This package might be subject to moderation, and might not appear immediately
[x] Move to homebrew repository
[x] Create a new branch for current release git checkout -b cake-0.7.0
[x] Open the Formula/cake.rb
[x] Update the url (line 4) to be the new download location
[x] Update the sha256 (line 5) to be the value that was generated earlier by the Publish-HomeBrew task
[x] Commit the changes to cake.rbNOTE: Commit message should use the following format cake 0.12.0NOTE: Make sure to use a lower case C as that is the preferred formatting in the Homebrew repo
[x] Push the new branch to your fork
[x] Open a PR against the master branch of Homebrew/homebrew-core
[x] Move to example repository
[x] Open the tools/packages.config file
[x] Update the Cake version number to be the same as the version that you have just released
[x] Build everything (./build.ps1 or ./build.sh) to make sure it works.
[x] Commit changes. Use message similar to (build) Updated Cake tool to version 0.13.0
[x] Push branch
[x] Move to resources repository
[x] Switch to the develop branch git checkout develop
[x] Open the packages.config file
[x] Update the Cake version number to be the same as the version that you have just released
[x] Commit changes. Use message similar to (build) Updated Cake tool to version 0.13.0
[x] Push branch git push
[x] Switch to the master branch git checkout master
[x] Merge changes from develop branch git merge --no-ff develop
[x] Push branch git push
[x] Move to website repository
[x] Create a branch for a new blog post git checkout -b 0.7.0-Blog-Post develop
[x] Create Blog Post i.e. .\input\blog\2017-03-07-cake-v0.18.0-released.md
[x] You can get contibutors using the console secrets\Processes\FetchContributors
dotnet restore
dotnet run "cake-build" "cake" "v0.17.0" "v0.18.0" "authors.text"
[x] Bump the Cake Tool Version number in tools\package.config to the latest released version, i.e. the version you just released
[x] Commit changes to tools\package.config file using message similar to (build) Updated Cake tool to version 0.14.0
[x] Commit blog post using message similar to v0.14.0 Blog Post
[x] Push branch and submit pull request
[x] Make sure that the AppVeyor build succeeds successfully
[x] Have someone else verify the contents
[x] Merge the Pull Request
[x] Go to develop.cakebuild.net once you receive the Azure notification in Slack to say that the development site is deployed. Make sure that it works as expected.
[x] Switch to develop branch git checkout develop
[x] Update local develop branch git fetch then git rebase origin/develop
[x] Delete local branch that was created git branch -d 0.7.0-Blog-Post
[x] Switch to master branch git checkout master
[x] Merge develop to mastergit merge --no-ff developNOTE: This will also update the documentation for the various Addins/Tools on the site, so if any new aliases have been added, these will be included in the build.
[x] Push master branch git push
[x] Go to cakebuild.net once you receive the Azure notification in Slack to say that the development site is deployed. Make sure that it works as expected.
[x] Go to the Cake-Contrib Gitter Room and let people know that it was released. Use something like @/all Version 0.27.1 of the Cake has just been released, https://www.nuget.org/packages/Cake.
[x] Go to the Cake-Contrib Slack Team and in the General Room let people know that it was released. Use something like @channel Version 0.27.1 of the Cake has just been released, https://www.nuget.org/packages/Cake.
Useful information
Repository Pre-requisites
Manual Approach
developbranch ofcake-build/cakeis up to dategit fetchthengit rebase origin/develop.mainbranch ofcake-build/cakeis up to dategit fetchthengit rebase origin/main.developbranch ofcake-build/websiteis up to dategit fetchthengit rebase origin/develop.masterbranch ofcake-build/websiteis up to dategit fetchthengit rebase origin/master.masterbranch ofcake-build/exampleis up to dategit fetchthengit rebase origin/master.developbranch ofcake-build/resourcesis up to dategit fetchthengit rebase origin/develop.masterbranch ofcake-build/resourcesis up to dategit fetchthengit rebase origin/master.Homebrew/homebrew-coreHomebrew/homebrew-coremasterbranch ofHomebrew/homebrew-coreis up to date;git fetchthengit rebase upstream/master.Automated Approach
Homebrew/homebrew-core.Prereqs.ps1file, using the following as an example.\Prereqs.ps1 -GithubUsername gep13(use your own username). This will clone a new version of all required repositories.Let people know that things are happening...
@/all We will soon start preparing for the [0.27.1 release](https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.@/all We will soon start preparing for the [0.27.1 release](https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.@channel We will soon start preparing for the 0.27.1 release (https://github.com/cake-build/cake/milestone/50) of Cake. So this is a friendly reminder to pin your Cake version.We are starting to prepare our next release, 0.27.1 (https://github.com/cake-build/cake/milestone/50). This is your friendly reminder that if you haven't pinned to a specific version of Cake, you should do it now :-) https://cakebuild.net/docs/tutorials/pinning-cake-versionGitHub Issues Pre-requisites
When doing a release
git checkout -b release/0.7.0 developreleasenotes.mdto include next version number as a placeholder and save the fileReleaseNotestask (.\build.ps1 -Target ReleaseNotes)releasenotes.mdwith generated content (making sure to keep the formatting the same)./build.ps1) to make sure it works.releasenotes.mdandsolutioninfo.cs. Use comment like(build) Updated version and release notes.mainbranch (git checkout main)maingit merge --no-ff release/0.7.0./build.ps1) to make sure it works (we can never be too sure).mainbranch.Publish-HomeBrewtaskdevelopbranchgit checkout developgit merge --no-ff release/0.7.0build.ps1andbuild.shto the latest released version, i.e. the version you just released./build.ps1) to make sure it works.build.ps1andbuild.shNOTE: There will be other changes to the *.json files as well, commit everything. Use commit message like(build) Updated Cake tool to version 0.13.0developbranch.git branch -d release/0.7.0(and the remote one, if pushed to GitHubgit push origin --delete release/0.7.0)When doing a hotfix
git checkout -b hotfix/0.27.1 maingit fetch origin pull/2133/head:pr2133git checkout pr2133git rebase --onto hotfix/0.27.1 developgit checkout hotfix/0.27.1git merge --no-ff pr2133releasenotes.mdto include next version number as a placeholder and save the fileReleaseNotestask (.\build.ps1 -Target ReleaseNotesor./build.sh --target releasenotesreleasenotes.mdwith generated content (making sure to keep the formatting the same)./build.ps1or./build.sh) to make sure it works.releasenotes.mdandsolutioninfo.csUse comment like(build) Updated version and release notes.mainbranch (git checkout main)maingit merge --no-ff hotfix/0.6.4./build.ps1or./build.sh) to make sure it works (we can never be too sure).mainbranch.Publish-HomeBrewtaskdevelopbranchgit checkout developgit merge --no-ff hotfix/0.6.4build.ps1andbuild.shto the latest released version, i.e. the version you just releasedbuild.ps1andbuild.sh. Use commit message like(build) Updated Cake tool to version 0.13.0./build.ps1or./build.sh) to make sure it works.developbranch.git branch -d hotfix/0.6.4(and the remote one, if pushed to GitHubgit push origin --delete hotfix/0.6.4)After a release/hotfix
git checkout -b cake-0.7.0Formula/cake.rbPublish-HomeBrewtaskcake.rbNOTE: Commit message should use the following formatcake 0.12.0NOTE: Make sure to use a lower caseCas that is the preferred formatting in the Homebrew repomasterbranch ofHomebrew/homebrew-coretools/packages.configfile./build.ps1or./build.sh) to make sure it works.(build) Updated Cake tool to version 0.13.0git checkout developpackages.configfile(build) Updated Cake tool to version 0.13.0git pushgit checkout mastergit merge --no-ff developgit pushgit checkout -b 0.7.0-Blog-Post develop.\input\blog\2017-03-07-cake-v0.18.0-released.mdsecrets\Processes\FetchContributorstools\package.configto the latest released version, i.e. the version you just releasedtools\package.configfile using message similar to(build) Updated Cake tool to version 0.14.0v0.14.0 Blog Postdevelopbranchgit checkout developgit fetchthengit rebase origin/developgit branch -d 0.7.0-Blog-Postmasterbranchgit checkout masterdeveloptomastergit merge --no-ff developNOTE: This will also update the documentation for the various Addins/Tools on the site, so if any new aliases have been added, these will be included in the build.masterbranchgit push@/all Version 0.27.1 of the Cake has just been released, https://www.nuget.org/packages/Cake.@channel Version 0.27.1 of the Cake has just been released, https://www.nuget.org/packages/Cake.DevOpsCsharpRelease NotesDotnetContinuous Integration