GitLab Major Security Update for CVE-2016-4340

Why is the latest official GitLab CE docker image 7 months old[1]? Is that no longer a recommended install method?<p>[1] <a href="https:&#x2F;&#x2F;hub.docker.com&#x2F;r&#x2F;gitlab&#x2F;gitlab-ce&#x2F;builds&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hub.docker.com&#x2F;r&#x2F;gitlab&#x2F;gitlab-ce&#x2F;builds&#x2F;</a><p>EDIT: Maybe I&#x27;m looking in the wrong place? The &quot;latest builds&quot; page shows activity from 7 months ago, but the &quot;tags&quot; page is showing &quot;latest&quot; updated 6 days ago. Does that just refer to the source repo tag, or a successful build that (for some reason) doesn&#x27;t show in the builds page?

It feels to me as if GitLab is pushing (major) security updates very often. Now there are two reasons I can think of this happening:<p>- They are very open about security vulnerabilities and fix them fast.<p>- There are some inherent defects in their software that cause these security vulnerabilities to come up so frequently.<p>I&#x27;d like to believe it&#x27;s the first.<p>EDIT: formatting.

No details, just like the posts about this yesterday. Obligatory &#x27;check our blog later for more.&#x27;

So just to clarify because its as clear as mud, 8.7 is still affected so we are waiting for an update ?

why do they release it at 5pm PDT? A lot of people are leaving work on the west coast. The rest of the country people are home eating dinner. EU is sleeping. Really stupid time.