diff --git a/CHANGES.md b/CHANGES.md
index bd41b057..816c4792 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -2,6 +2,14 @@
 
 ## Latest
 
+## v0.4.2 (2016-12-7)
+
+#### Improvements
+
+* Add RPM packages to Copr
+* Fix packaged `contrib/systemd` units
+* Update Go version to 1.7.4
+
 #### Examples
 
 * Upgrade Kubernetes v1.4.6 (static manifest) example clusters
diff --git a/Documentation/deployment.md b/Documentation/deployment.md
index 12bab708..94203712 100644
--- a/Documentation/deployment.md
+++ b/Documentation/deployment.md
@@ -21,23 +21,23 @@ Choose one of the supported installation options:
 Download the latest coreos-baremetal [release](https://github.com/coreos/coreos-baremetal/releases) to the provisioner host.
 
 ```sh
-$ wget https://github.com/coreos/coreos-baremetal/releases/download/v0.4.1/coreos-baremetal-v0.4.1-linux-amd64.tar.gz
-$ wget https://github.com/coreos/coreos-baremetal/releases/download/v0.4.1/coreos-baremetal-v0.4.1-linux-amd64.tar.gz.asc
+$ wget https://github.com/coreos/coreos-baremetal/releases/download/v0.4.2/coreos-baremetal-v0.4.2-linux-amd64.tar.gz
+$ wget https://github.com/coreos/coreos-baremetal/releases/download/v0.4.2/coreos-baremetal-v0.4.2-linux-amd64.tar.gz.asc
 ```
 
 Verify the release has been signed by the [CoreOS App Signing Key](https://coreos.com/security/app-signing-key/).
 
 ```
 $ gpg --keyserver pgp.mit.edu --recv-key 18AD5014C99EF7E3BA5F6CE950BDD3E0FC8A365E
-$ gpg --verify coreos-baremetal-v0.4.1-linux-amd64.tar.gz.asc coreos-baremetal-v0.4.1-linux-amd64.tar.gz
+$ gpg --verify coreos-baremetal-v0.4.2-linux-amd64.tar.gz.asc coreos-baremetal-v0.4.2-linux-amd64.tar.gz
 # gpg: Good signature from "CoreOS Application Signing Key <security@coreos.com>"
 ```
 
 Untar the release.
 
 ```sh
-$ tar xzvf coreos-baremetal-v0.4.1-linux-amd64.tar.gz
-$ cd coreos-baremetal-v0.4.1-linux-amd64
+$ tar xzvf coreos-baremetal-v0.4.2-linux-amd64.tar.gz
+$ cd coreos-baremetal-v0.4.2-linux-amd64
 ```
 
 ## Install
@@ -256,7 +256,7 @@ Run the most recent tagged and signed `bootcfg` [release](https://github.com/cor
 ```sh
 $ sudo rkt trust --prefix coreos.com/bootcfg
 # gpg key fingerprint is: 18AD 5014 C99E F7E3 BA5F  6CE9 50BD D3E0 FC8A 365E
-$ sudo rkt run --net=host --mount volume=data,target=/var/lib/bootcfg --volume data,kind=host,source=/var/lib/bootcfg quay.io/coreos/bootcfg:v0.4.1 --mount volume=config,target=/etc/bootcfg --volume config,kind=host,source=/etc/bootcfg,readOnly=true -- -address=0.0.0.0:8080 -rpc-address=0.0.0.0:8081 -log-level=debug
+$ sudo rkt run --net=host --mount volume=data,target=/var/lib/bootcfg --volume data,kind=host,source=/var/lib/bootcfg quay.io/coreos/bootcfg:v0.4.2 --mount volume=config,target=/etc/bootcfg --volume config,kind=host,source=/etc/bootcfg,readOnly=true -- -address=0.0.0.0:8080 -rpc-address=0.0.0.0:8081 -log-level=debug
 ```
 
 Create machine profiles, groups, or Ignition configs at runtime with `bootcmd` or by using your own `/var/lib/bootcfg` volume mounts.
@@ -266,7 +266,7 @@ Create machine profiles, groups, or Ignition configs at runtime with `bootcmd` o
 Run the latest or the most recently tagged `bootcfg` [release](https://github.com/coreos/coreos-baremetal/releases) Docker image.
 
 ```sh
-sudo docker run --net=host --rm -v /var/lib/bootcfg:/var/lib/bootcfg:Z -v /etc/bootcfg:/etc/bootcfg:Z,ro quay.io/coreos/bootcfg:v0.4.1 -address=0.0.0.0:8080 -rpc-address=0.0.0.0:8081 -log-level=debug
+sudo docker run --net=host --rm -v /var/lib/bootcfg:/var/lib/bootcfg:Z -v /etc/bootcfg:/etc/bootcfg:Z,ro quay.io/coreos/bootcfg:v0.4.2 -address=0.0.0.0:8080 -rpc-address=0.0.0.0:8081 -log-level=debug
 ```
 
 Create machine profiles, groups, or Ignition configs at runtime with `bootcmd` or by using your own `/var/lib/bootcfg` volume mounts.
diff --git a/Documentation/dev/release.md b/Documentation/dev/release.md
index ab3d5d88..629de635 100644
--- a/Documentation/dev/release.md
+++ b/Documentation/dev/release.md
@@ -3,6 +3,12 @@
 
 This guide covers releasing new versions of coreos-baremetal.
 
+## Version
+
+Create a release commit which updates old version references.
+
+    export VERSION=v0.4.2
+
 ## Tag
 
 Tag, sign the release version, and push it to Github.
@@ -20,7 +26,6 @@ Publish the release on Github with release notes.
 
 Build the release tarballs.
 
-    export VERSION=v0.4.1
     make release
 
 ## ACI
diff --git a/Documentation/getting-started-docker.md b/Documentation/getting-started-docker.md
index 120da1a4..fc18c40e 100644
--- a/Documentation/getting-started-docker.md
+++ b/Documentation/getting-started-docker.md
@@ -43,7 +43,7 @@ Run the latest `bootcfg` Docker image from `quay.io/coreos/bootcfg` with the `et
 
 or run the latest tagged release.
 
-    sudo docker run -p 8080:8080 --rm -v $PWD/examples:/var/lib/bootcfg:Z -v $PWD/examples/groups/etcd:/var/lib/bootcfg/groups:Z quay.io/coreos/bootcfg:v0.4.1 -address=0.0.0.0:8080 -log-level=debug
+    sudo docker run -p 8080:8080 --rm -v $PWD/examples:/var/lib/bootcfg:Z -v $PWD/examples/groups/etcd:/var/lib/bootcfg/groups:Z quay.io/coreos/bootcfg:v0.4.2 -address=0.0.0.0:8080 -log-level=debug
 
 Take a look at the [etcd groups](../examples/groups/etcd) to get an idea of how machines are mapped to Profiles. Explore some endpoints exposed by the service, say for QEMU/KVM node1.
 
diff --git a/Documentation/getting-started-rkt.md b/Documentation/getting-started-rkt.md
index 32f8d354..2662898c 100644
--- a/Documentation/getting-started-rkt.md
+++ b/Documentation/getting-started-rkt.md
@@ -70,7 +70,7 @@ Run the latest `bootcfg` ACI with rkt and the `etcd` example.
 
 or run the latest tagged release signed by the [CoreOS App Signing Key](https://coreos.com/security/app-signing-key/).
 
-    sudo rkt run --net=metal0:IP=172.18.0.2 --mount volume=data,target=/var/lib/bootcfg --volume data,kind=host,source=$PWD/examples --mount volume=groups,target=/var/lib/bootcfg/groups --volume groups,kind=host,source=$PWD/examples/groups/etcd coreos.com/bootcfg:v0.4.1 -- -address=0.0.0.0:8080 -log-level=debug
+    sudo rkt run --net=metal0:IP=172.18.0.2 --mount volume=data,target=/var/lib/bootcfg --volume data,kind=host,source=$PWD/examples --mount volume=groups,target=/var/lib/bootcfg/groups --volume groups,kind=host,source=$PWD/examples/groups/etcd coreos.com/bootcfg:v0.4.2 -- -address=0.0.0.0:8080 -log-level=debug
 
 If you get an error about the IP assignment, stop old pods and run garbage collection.
 
diff --git a/contrib/k8s/bootcfg-deployment.yaml b/contrib/k8s/bootcfg-deployment.yaml
index 06b5da14..4b650248 100644
--- a/contrib/k8s/bootcfg-deployment.yaml
+++ b/contrib/k8s/bootcfg-deployment.yaml
@@ -16,7 +16,7 @@ spec:
     spec:
       containers:
         - name: bootcfg
-          image: quay.io/coreos/bootcfg:v0.4.1
+          image: quay.io/coreos/bootcfg:v0.4.2
           env:
             - {name: BOOTCFG_ADDRESS, value: "0.0.0.0:8080"}
             - {name: BOOTCFG_LOG_LEVEL, value: "debug"}
diff --git a/contrib/systemd/bootcfg-for-tectonic.service b/contrib/systemd/bootcfg-for-tectonic.service
index e06fca26..b7f987ce 100644
--- a/contrib/systemd/bootcfg-for-tectonic.service
+++ b/contrib/systemd/bootcfg-for-tectonic.service
@@ -4,7 +4,7 @@ Documentation=https://github.com/coreos/coreos-baremetal
 
 [Service]
 Environment="IMAGE=quay.io/coreos/bootcfg"
-Environment="VERSION=v0.4.1"
+Environment="VERSION=v0.4.2"
 Environment="BOOTCFG_ADDRESS=0.0.0.0:8080"
 Environment="BOOTCFG_RPC_ADDRESS=0.0.0.0:8081"
 Environment="BOOTCFG_LOG_LEVEL=debug"
diff --git a/contrib/systemd/bootcfg-on-coreos.service b/contrib/systemd/bootcfg-on-coreos.service
index debae20d..dee7713c 100644
--- a/contrib/systemd/bootcfg-on-coreos.service
+++ b/contrib/systemd/bootcfg-on-coreos.service
@@ -4,7 +4,7 @@ Documentation=https://github.com/coreos/coreos-baremetal
 
 [Service]
 Environment="IMAGE=quay.io/coreos/bootcfg"
-Environment="VERSION=v0.4.1"
+Environment="VERSION=v0.4.2"
 Environment="BOOTCFG_ADDRESS=0.0.0.0:8080"
 ExecStartPre=/usr/bin/mkdir -p /etc/bootcfg
 ExecStartPre=/usr/bin/mkdir -p /var/lib/bootcfg/assets