Description
Hi folks, especially @diego.sampaio:
It seems as though the content of the release bundle has changed without having a new release.
I downloaded the 2.1.0 release on Sep 30. And I downloaded it again today, Oct 4th. See the difference:
thomas@td-work:~/Downloads$ sha256sum rocket.chat-2.1.0.tar "rocket.chat-2.1.0 (1).tar"
96255ebf6178e202ec6b5456ec44a7d8155b9d1629657cf29f19ca2736d040f1 rocket.chat-2.1.0.tar
869a95b23a23993b00755fdb063dd569aa3a165b2bdaf292cb9b8dc916afbbaf rocket.chat-2.1.0 (1).tar
thomas@td-work:~/Downloads$ ls -latr | grep rocket
-rw-rw-r-- 1 thomas thomas 141444105 Sep 30 08:54 rocket.chat-2.1.0.tar
-rw-rw-r-- 1 thomas thomas 141532115 Oct 4 11:10 rocket.chat-2.1.0 (1).tar
Is there a background to that? Otherwise I would have to assume some malicious activity.
Cheers
Thomas
1 Like
hi @TwizzyDizzy
yes, I have re-triggered the release build on Sep 30th - as you can see here https://circleci.com/gh/RocketChat/Rocket.Chat/46512
the first one was ran on the release date, Sep 27th - https://circleci.com/gh/RocketChat/Rocket.Chat/46496
the reason behind this was to use an updated Docker base image (https://github.com/RocketChat/Docker.Base.Image) with updated NodeJS version (8.15.1 instead of 8.11.4) , which is the officially supported version by the Meteor version we’re using now, and includes some important security fixes.
I was not sure how to communicate this, but I thought important doing the update.
1 Like
Ha! I see. Thanks for getting back! 
Cheers
Thomas
Is that what caused the UID to change? I had to change all of my permissions when I upgraded to 2.1.
actually, yes. the new base image has a different UID and GID https://github.com/RocketChat/Docker.Base.Image/pull/7/
O.o. Seemed far fetched for me, should have shut up and just said nothing! Sorry!
Cheers
Thomas