Release v1.1.2

README.md

@@ -158,7 +158,7 @@ If you don't have an internal apt server, you can use `dpkg -i` to install the
 One possibility is with the following commands in your Dockerfile:
 
 ```bash
-RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.1.1/dumb-init_1.1.1_amd64.deb
+RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.1.2/dumb-init_1.1.2_amd64.deb
 RUN dpkg -i dumb-init_*.deb
 ```
 
@@ -169,7 +169,7 @@ Since dumb-init is released as a statically-linked binary, you can usually just
 plop it into your images. Here's an example of doing that in a Dockerfile:
 
 ```bash
-RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.1.1/dumb-init_1.1.1_amd64
+RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.1.2/dumb-init_1.1.2_amd64
 RUN chmod +x /usr/local/bin/dumb-init
 ```
 

VERSION

@@ -1 +1 @@
-1.1.1
+1.1.2

VERSION.h

@@ -1,6 +1,6 @@
 // THIS FILE IS AUTOMATICALLY GENERATED
 // Run `make VERSION.h` to update it after modifying VERSION.
 unsigned char VERSION[] = {
-  0x31, 0x2e, 0x31, 0x2e, 0x31, 0x0a
+  0x31, 0x2e, 0x31, 0x2e, 0x32, 0x0a
 };
 unsigned int VERSION_len = 6;

debian/changelog

@@ -1,3 +1,12 @@
+dumb-init (1.1.2) unstable; urgency=low
+
+  * Fix race when the child exits very quickly that leads to dumb-init not
+    reaping the child. This should be pretty rare and most likely to happen
+    when dumb-init's child fails to exec (such as when you try to run a file
+    that doesn't exist).
+
+ -- Chris Kuehl <[email protected]>  Mon, 25 Jul 2016 22:46:40 -0700
+
 dumb-init (1.1.1) unstable; urgency=medium
 
   * Fix segfault when passing unknown arguments (thanks @asottile for