Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Feature]: Define Desktop updater behavior across release channels

Ouverte
  • Quelque chose ne va pas ?
#3,481 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust, tauri
Domaine
desktop, release

Piste de recherche

Start by reading .github/workflows/nightly-artifacts.yml and tracing the Desktop updater configuration and version comparison it feeds. Evaluate the proposed channel policies and document the selected behavior, including visibility and channel switching rules. Done means builds do not offer another channel's release solely due to SemVer ordering, including the stated Nightly versus stable example.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Problem / opportunity
The Nightly desktop build is compiled as the nightly channel, but the current Nightly artifact workflow points its Tauri updater endpoints at the stable latest-v1.json feed because a Nightly updater feed is not published yet. As a result, a Nightly install can offer stable 1.0.6 as an update over 1.0.6-nightly.20261019, even though the Nightly build comes from a commit 128 commits ahead of v1.0.6. Comparing versions across channels makes the older stable code appear newer and can prompt an unintended cross-channel downgrade.

Proposed behavior
Please define the Desktop updater's release-channel policy and make feed selection and version comparison follow it. Possible designs to evaluate:

  • All-channel build: let users choose stable, beta, or nightly updates, with explicit channel-aware version ordering and clear behavior when switching channels.
  • Stable-only build: check only stable releases and never present beta or Nightly builds as updates.
  • Nightly-only build: check only the Nightly feed, so a stable release cannot be offered as an update to a newer Nightly build.

The chosen behavior should make the active channel visible and avoid treating a release from another channel as a newer update solely because of SemVer ordering.

Product surface
Cross-cutting

Details, examples, or constraints
For example, on 1.0.6-nightly.20261019, the updater should not offer stable 1.0.6 as a newer build when its source commit is older. If channel switching is supported, make the switch explicit and define whether moving between channels is an update, downgrade, or reinstall.

Langage dominant
Rust
Étoiles
2.3k
Forks
236
Merge moyen
7 h 39 min
PR mergées (30 j)
251

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de GCWing/OpenBitFun

Toutes les issues de GCWing/OpenBitFun

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.