Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release signing page references wrong file as signature

Open
  • Is something wrong?
#839 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Open the release signing page and compare its archive-signature description with lib/upgrade/upgrade_supported.go at the linked upstream line. Update the documentation so the referenced signature filename matches the implementation for all operating systems, then verify the page renders correctly.

Written by the indexing model from the issue text.

Description

Release signing page says:

In a genuine release archive you expect to find the syncthing binary (syncthing.exe on Windows) and an accompanying signature syncthing.sig (syncthing.exe.sig on Windows)

But lib/upgrade from syncthing/syncthing actually uses release.sig for every OS:

https://github.com/syncthing/syncthing/blob/2ae15aa4546b8cf76cd6077303aa6b97e2e043ee/lib/upgrade/upgrade_supported.go#L362

Dominant language
Python
Stars
328
Forks
653
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from syncthing/docs

All issues in syncthing/docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.