RocketChat / RocketChat/Rocket.Chat

"Update your Rocket.ChatNew version available (%s)" - not possible to update with snap install

Open
#30,845 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

In last two weeks I saw the message Update your Rocket.ChatNew version available (%s) for many times.

But why? I use Rocket.Chat server installed from snap package 6.x/stable. It's not possible to update Rocket.Chat from my current version 6.4.4 to the latest version 6.4.5.

Is there any solution? I'm using snap channel 6.x/stable. In 6.x/edge there is the latest version 6.4.5. Should I switch snap channel from stable to switch? Is it a good idea?

According to official Snapcraft documentation I think the edge channel is not a good idea:

edge: for users wanting to closely track development.

Edge releases often include a moving stream of changes without QA or review promises and are typically built automatically by a CI process from an arbitrary source code snapshot. Often the CI will only publish after some sort of automatic QA passed, and code reviews remain a good practice, but these are project specific. Assume edge releases may break often.

In Rocket.Chat documentation is stable channel: --channel=4.x/stable.

image

  • Version of Rocket.Chat Server: 6.4.4
  • Operating System: Debian 12
  • Deployment Method: snap
  • Number of Running Instances: 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the documented stable channel with the reported 6.x/stable and 6.x/edge channels, using the Snapcraft channel guidance linked in the issue. Done means the supported upgrade path for the 6.4.4-to-6.4.5 case is established and the update notice or deployment documentation is corrected as needed.

Written by the indexing model from the issue text.

Assessment

Domain
devops, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.