177f0be21c
# History ## 0.25.5 Install/update via the bootstrap script: ```shell wget https://raw.githubusercontent.com/dokku/dokku/v0.25.5/bootstrap.sh sudo DOKKU_TAG=v0.25.5 bash bootstrap.sh ``` ### Bug Fixes - #4787: @josegonzalez Do not require double quotes when issuing dokku run commands - #4816: @josegonzalez Set the DOKKU_HOST_ROOT on docker container start - #4810: @josegonzalez Handle udp ports when fetching network config - #4812: @josegonzalez Silence stderr when fetching a command from the Procfile - #4800: @josegonzalez Add help2man os package for copyfiles make target to devcontainer - #4796: @josegonzalez Remove the --restart flag from pre-deploy chown containers ### New Features - #4809: @josegonzalez Implement storage:ensure-directory command - #4801: @josegonzalez Expose git-from-archive and git-from-image plugin triggers - #4785: @josegonzalez Add support for VSCode Dev Containers ### Documentation - #4819: @stephenheron Fixed typo in tar documentation - #4824: @dy3l Fix GitLab case - #4822: @josegonzalez Add a note about using the registry:login command for private image deployments - #4808: @francipvb Added a comment about Dockerfile deployment - #4807: @FinnWoelm Docs: Fix instructions for enabling Docker Buildkit - #4786: @josegonzalez Add missing argument from trigger documentation - #4780: @adam12 Update source for `dokku-update` ### Tests - #4828: @josegonzalez Update golang in test apps to latest version - #4815: @josegonzalez tests: use python3 shebang for shellcheck-to-junit script - #4814: @josegonzalez Add wget to devcontainer to fix shfmt installation - #4791: @josegonzalez Fix test running in devcontainer ### Other - #4813: @dependabot[bot] chore(deps-dev): bump heroku/heroku-buildpack-php from 197 to 198 in /tests/apps/php - #4802: @dependabot[bot] chore(deps): bump django from 3.1.12 to 3.1.13 in /tests/apps/dockerfile-release - #4784: @josegonzalez Upgrade vector image to 0.16.x
65 lines
3.7 KiB
Markdown
65 lines
3.7 KiB
Markdown
# Release Process
|
|
|
|
Dokku is released in intervals *at most* three weeks apart, though may be released much quicker.
|
|
|
|
To propose a release, the following tasks need to be performed:
|
|
|
|
```shell
|
|
export PACKAGECLOUD_TOKEN=SOME_TOKEN
|
|
# supports major/minor/patch/betafish
|
|
contrib/release-dokku
|
|
```
|
|
|
|
> If you are a maintainer and need the PACKAGECLOUD_TOKEN in order to make a release, please contact @josegonzalez to get this information.
|
|
|
|
As well, the Arch Linux package description *must* be updated via `vagrant up build-arch` (needs to be done after the tag is pushed to GitHub, because it is based on that)
|
|
|
|
## Versioning
|
|
|
|
Dokku follows semver standards. As we are not yet at a stable release, breaking changes will require *only* a minor release, while all other changes only require a patch release. Once we hit stable, breaking changes will require a major release.
|
|
|
|
At the moment, tags need not be signed, though that may change in the future.
|
|
|
|
## Arch Linux Packages
|
|
|
|
Arch Linux packages are not really build, because all that is needed for an Arch User Repo (AUR) package is the description of how to build the package. To make this process as easy as possible there is a vagrant box called `build-arch` that updates the version of this build description (a file called `PKGBUILD`), then runs some helper scripts to fill all additional information and does test if the package could be build. Then only those changes need to be pushed to the AUR repo and an updated version of the package is ready for usage for our Arch Linux users. For detailed information see the section below.
|
|
|
|
The workflow looks like this:
|
|
|
|
```shell
|
|
# having dokku-arch in ../dokku-arch
|
|
vagrant up build-arch
|
|
# wait for "==> build-arch: ==> Finished making: dokku 0.25.5-2 (Mon Feb 22 23:20:37 CET 2016)"
|
|
cd ../dokku-arch
|
|
git add PKGBUILD .SRCINFO
|
|
git commit -m 'Update to dokku 0.9.9'
|
|
git push aur master
|
|
```
|
|
|
|
> If you are a maintainer and need access to the AUR repositories in order to make a release, please contact @morrisjobke or @josegonzalez to get this co-maintainership.
|
|
|
|
### Detailed information for Arch Linux packages
|
|
|
|
All of the information to build the Arch Linux package is in the AUR git repository (see [dokku AUR page](https://aur.archlinux.org/packages/dokku/)). The release of a AUR package only consists of pushing the package information into the AUR git repo. Then users could use that information to build the package on their machines.
|
|
|
|
To update the package clone the repository and adjust the files in the repository. Then a helper script - `updpkgsums` - to update the SHA sum could be called (check against the original SHA sum). Another helper script - `mksrcinfo` - needs to be called to update the meta information of the package in a file called `.SRCINFO`. The next step builds the package locally for verification - `makepkg`. As last step commit your changes and push the commit.
|
|
|
|
* dependencies are defined in the `depends` attribute in `PKGBUILD`
|
|
* build steps during package build time are defined in the `package()` method in `PKGBUILD`
|
|
* steps that should be executed during install/update/remove time are defined in the file `dokku.install`
|
|
* detailed information about all attributes in `PKGBUILD` could be found in the [Arch Linux wiki](https://wiki.archlinux.org/index.php/PKGBUILD)
|
|
* detailed information about the AUR workflow could be found in the [AUR article](https://wiki.archlinux.org/index.php/Arch_User_Repository) in the Arch Linux wiki
|
|
|
|
That is the usual workflow:
|
|
|
|
```shell
|
|
updpkgsums # update sha sums - compare them with the original ones
|
|
mksrcinfo # update package metadata for AUR
|
|
makepkg # test package builds
|
|
git add PKGBUILD .SRCINFO
|
|
git commit -m 'Update to dokku 0.9.9'
|
|
git push
|
|
```
|
|
|
|
> If there is something unclear simply ask @morrisjobke for help.
|