Auto-updater does not find new releases from the same day.
See original GitHub issueDescribe the bug The auto-updater does not find new releases if they are released in the same day as the most recent release.
To Reproduce
- Create a new release draft.
- Publish the release.
- Repeat steps 1 and 2 in the same day.
- Attempt to have auto-update work.
Expected behavior
If the latest.yml
in /<repo>/releases/latest
has a different version than the current, it should be considered the latest.
Screenshots N/A
Additional context
This seems to stem from the fact that in semantic versioning, v1.2.3-456
, the 456
would be considered a pre-release. It might be best to identify a way to utilize package.json
and npm version
to use proper semantic versioning for releases to avoid this problem.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Autoupdate downloads new update, but does not successfully ...
You can see my releases from yesterday on github, I got that part working. However, my ultimate goal is to get auto update...
Read more >electron updater notify for new release but do not update or ...
electron updater 4.2.0 package do not download new release but can detect it. This is a private repository on github.
Read more >AutoUpdater Utility - Check Point Support Center
AutoUpdater is a Check Point process responsible for automatic updates. The latest updates are installed automatically on all relevant Check ...
Read more >Auto Updater - About the Documentation - Proofpoint
Auto Updater checks which version is currently installed on the endpoint and ... This way, you do not need to install new versions...
Read more >Release history for Microsoft AutoUpdate (MAU)
Therefore, you might receive a notification to update Microsoft AutoUpdate even if you're not running Office for Mac. To view release notes, see...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Then you will got: 22.1.31 -> 22.131 22.2.1 -> 22.21 Second is newest version but according to semver is oldest because 21 < 131.
Using day of year should solve it. I’ll try to make the appropriate changes ASAP (if the fuckingRussians don’t launch missiles into my city)
Now app version just reading from root
package.json
. You can implement your own versioning logic in getVersion() See change note: https://github.com/cawa-93/vite-electron-builder/discussions/870