Auto updater wants to update to a pre-release version
See original GitHub issueDescribe the bug The auto updater of the gha runner want to upgrade to a prerelease
To Reproduce
- Start the runner on version
2.263.0
- It will show the following message in the output:
Runner update in progress, do not shutdown runner.
Downloading 2.267.1 runner
Expected behavior I don’t want auto update at all, but being auto updated to a pre-release version is far from acceptable. At least I only want to be updated to a stable version.
Runner Version and Platform
2.263.0
OS of the machine running the runner? OSX/Windows/Linux/… Linux
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:20 (5 by maintainers)
Top Results From Across the Web
Autoupdate to pre-release versions - Node Operators
It started rolling out to nodes that got 1.67.1 first. Once all nodes are updated, the latest version will update as well. These...
Read more >GitHub Integration - Auto-Updater
So the Updater checks the GitHub Releases API for versions that are higher than the currently installed version (based on GitHub Release tags, ......
Read more >Auto Update
Simplified auto-update is supported on Windows if you use the default NSIS target, but is not supported for Squirrel.Windows. You can easily migrate...
Read more >Enabling Pre-Release Updates - Online Documentation Portal
Turn off automatic updates. When the developers advise you that a fix has been released you will want to enable automatic updates again....
Read more >None of my sites start after upgrading to 2.3.2 from 2.3.x Pre ...
I was excited to install 2.3.2 over the pre-release of 2.3.1 but sadly, none of my sites work now. I get: This site...
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 FreeTop 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
Top GitHub Comments
Since Microsoft purchased Github …
Apologies for any confusion caused by our runner release process and how it may impact rollout. For transparency’s sake, here is the current process that has been followed since actions GA (as far as I’m aware):
Prerelease versions of the runner are considered stable, working and are rolled out to customers (obviously bugs can happen and we might have to roll back a runner version, which is why we would consider it prerelease until it has made it to all of our customers).
We could change the runner version to a “release” after it makes it through our internal customers and testing. That might help with the confusion on the terminology, although it would not change our testing process (just marking it earlier as released).