v1.2.2

README.md

@@ -174,7 +174,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:
 
 ```Dockerfile
-RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.2.1/dumb-init_1.2.1_amd64.deb
+RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.2.2/dumb-init_1.2.2_amd64.deb
 RUN dpkg -i dumb-init_*.deb
 ```
 
@@ -185,7 +185,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:
 
 ```Dockerfile
-RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.1/dumb-init_1.2.1_amd64
+RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.2/dumb-init_1.2.2_amd64
 RUN chmod +x /usr/local/bin/dumb-init
 ```
 

VERSION

@@ -1 +1 @@
-1.2.1
+1.2.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, 0x32, 0x2e, 0x31, 0x0a
+  0x31, 0x2e, 0x32, 0x2e, 0x32, 0x0a
 };
 unsigned int VERSION_len = 6;

debian/changelog

@@ -1,3 +1,14 @@
+dumb-init (1.2.2) unstable; urgency=medium
+
+  * Fix a race condition which can cause the child to receive SIGHUP and
+    SIGCONT very shortly after start (#174).
+
+    In general this was very rare, but some environments (especially some
+    container and virtualization environments) appear to encounter it at a
+    much higher rate, possibly due to scheduler quirks.
+
+ -- Chris Kuehl <[email protected]>  Wed, 01 Aug 2018 16:36:22 -0700
+
 dumb-init (1.2.1) unstable; urgency=medium
 
   * Fix verbose debug logging for ignored signals.