-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker image rocketchat/rocket.chat:6.2.6 contains Rocket.Chat 6.2.5 #29555
Comments
Same for the tar version. Looks like the version number was not bumped up. |
Yes I can confirm this, too on a manual installation. |
Same problem here... |
thx everyone for letting us know.. we're using a new automation script to publish the release, but looks like the version bump on some key files is missing.. but I can guarantee it has the fix from the change log.. I'll be working on improving the automation to fix this asap |
Same problem... |
Description:
When firing up the Docker image
rocketchat/rocket.chat:6.2.6
from Docker Hub, it will identify itself as Rocket.Chat 6.2.5.Steps to reproduce:
docker run --name mongo_test mongo:6.0.6 mongod --oplogSize 128 --replSet rs0 --storageEngine=wiredTiger
docker exec -it mongo_test mongosh localhost/rocketchat --eval "rs.initiate({ _id: 'rs0', members: [ { _id: 0, host: 'localhost:27017' } ]})"
docker run --name rocketchat_test -e MONGO_OPLOG_URL=mongodb://mongo:27017/local?directConnection=true -e MONGO_URL=mongodb://mongo:27017/rocketchat?directConnection=true --link mongo_test:mongo -p 127.0.0.1:3000:3000 rocketchat/rocket.chat:6.2.6
Expected behavior:
Rocket.Chat 6.2.6 will start. There will be no banner about a newer version being available. rocket.cat will not send me a message that nudges me to update to the most recent version.
Actual behavior:
Rocket.Chat 6.2.5 will start. It shows a banner about a Rocket.Chat 6.2.6 being available. I receive a message from rocket.cat telling me to update to 6.2.6.
Server Setup Information:
Client Setup Information
Issue is client-agnostic.
Relevant logs:
The text was updated successfully, but these errors were encountered: