nextcloud / nextcloud/updater

Different version offered by update server via Server (via updatenotification app) versus in Updater (both web and command line modes)

Open
#122 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: check for update
Dominant language
PHP
Stars
51
Forks
40
Avg merge
2d 19h
Merged PRs (30d)
3

Description

Today I wanted to upgrade our nextcloud version. First upgrading from 11.0.2 to 11.0.3 which was promoted in the updater settings dialouge. The channel was at default set to stable.

After running the updater, which I'm pretty sure also showed 11.0.3, I clicked 'take me to the main page and do web update' which confusingly showed a front page in maintenance mode. After pressing f5 once it then showed an upgrade to 12.0 message which was even more confusing.

The update then ran more or less fine and now I'm expectantly on NC 12.

What is the expected behaviour? Was the displayed target version wrong and I correctly got v12.0 or should I indeed have gotten v11.0.3?

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

Compare the version offered by the server through the updatenotification app with the version shown by the Updater in web and command-line modes. Start by reproducing the upgrade flow described in the issue; done means the displayed target version is consistent across those paths or the expected difference is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
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.