nim-wiki/Creating-a-release.md at 3d847d40b73f867c81423b0ad5f767dcade14a59

ensure travis and appveyor is green (Usually the case these days) for the release branch 0-19, 0-20, etc
Update the version
- In system.nim
Tag the release, e.g. git tag -am "Version 0.15.0" v0.15.0
Push the tag: git push origin [tagname]
Nightlies now build the binaries for us: https://github.com/nim-lang/nightlies/releases
Ensure nightly builds exist
Recompile koch!
Generate the full docs; koch doc0 (not koch doc)
Merge 0-19 branch into master
Update csources via koch pushcsources

Website

Upload the produced .zips. For example: scp nim-0.18.0.tar.xz username@servername:/var/www/nim-lang.org/download/nim-0.18.0.tar.xz (change the version obviously)

Create a new blog post in _drafts titled: version-<ver>-released.md where <ver> is the version without any dots, e.g. 0180 for 0.18.0.
When ready to release:
- move the blog post into _posts, making sure to append the current date to its filename: 2017-09-31-title.md.
- modify config.yml's version key to the new version
- git commit
  - TIP: Here is a real-life example of a commit that signifies a release: 6f95916dee. The draft blog post was created in earlier commits, but hopefully it's pretty easy to figure out how it was made.
  - TIP2: You can see what a draft post looks like by running jekyll serve --drafts inside the website's jekyll directory.
- git push live master (the live remote is a strict secret)

export NIM_VER=<current_ver> (for example export NIM_VER=0.19.0).
Upload documentation to /var/www/nim-lang.org/$NIM_VER
Change docs symlink
- cd /var/www/nim-lang.org/
- ln -sfn $NIM_VER docs (change the version here)
- Verify this worked using ls -la | grep "docs"

Choosenim currently only supports gz so you will need to create a .tar.gz out of the .tar.xz:

Update the stable channel:

Update /var/www/nim-lang.org/channels using your favourite editor
- vim /var/www/nim-lang.org/channels/stable