satisfactorymodding / satisfactorymodding/SatisfactoryModManager
Automatic updater detects tags with no matching release, softlocking app until published
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 500
- Forks
- 94
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 2
Description
Creating releases involves creating a tag, then manually editing a draft release and manually hitting publish. We noticed with 3.0.4 (which had a longer changelog to edit) that when people opened the mod manager in the mean time, the update was still presented even though the release was not published yet.
The issue resolved itself once the release was published.
Ideally the update system could be improved to not detect these "incomplete updates".
Reports of this on the discord:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the automatic updater's release and tag check, using the reported unpublished-release scenario as the reproduction case. The work is done when a tag with an unpublished draft release is no longer presented as an available update, while published releases continue to be detected.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100