Release tag v2.4.1 doesn't match the plugin's version 2.4.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Inspect the release packaging workflow and the plugin.json and package.json version fields mentioned in the report. Start by checking how the release tag and ZIP version are set during a build. Done when a release artifact reports the same version as its tag, so plugin managers do not offer the same update repeatedly.
Written by the indexing model from the issue text.
Description
Hi! Thanks for the plugin.
The latest release is tagged v2.4.1, but the plugin inside its ZIP reports version 2.4.0 (the version in its plugin.json / package.json).
Plugin managers that compare the installed version with the latest release tag (like DeckyHub) read 2.4.0 → v2.4.1 as an upgrade. Installing it puts the same 2.4.0 back, so users are offered the same update over and over.
Could the next release use matching versions? Either set version to the tag's number before building the ZIP, or tag the release with the version the plugin reports.
Found by DeckyHub's registry check; the original report is mazillka/deckyhub-plugin#243.
- Dominant language
- Go
- Stars
- 225
- Forks
- 9
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 72
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from Liquid-co/OpenSave
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in Liquid-co/OpenSave
Similar issues
-
[Bug] Custom tool truncation leaves unused stream copies openPossibly taken @OUAO-FRANK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[v3] KeyBindingManager calls (Add/Remove) are not converted into a case-insensitive accelerator.KeyOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
crmne/hyprmoncfg#114 · 1 comment ·
Maintainers usually reply within 1 day
-
runtime: usleep sleeps nanoseconds instead of microseconds on linux/mips and linux/mips64Possibly taken @BRobertson7 claimed this today. Opencompiler/runtime
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100