question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Auto updater wants to update to a pre-release version

See original GitHub issue

Describe the bug The auto updater of the gha runner want to upgrade to a prerelease

To Reproduce

  1. Start the runner on version 2.263.0
  2. 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:closed
  • Created 3 years ago
  • Reactions:7
  • Comments:20 (5 by maintainers)

github_iconTop GitHub Comments

6reactions
arash-bizcovercommented, Aug 24, 2020

Since Microsoft purchased Github …

4reactions
hrosscommented, Aug 25, 2020

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):

  1. Runner updates are made to this repo and committed to master
  2. Changes are tested internally at GitHub
  3. Changes are rolled into a release as a prerelease
  4. The prerelease runner is slowly rolled to different rings of customers via autoupdate, starting with internal customers and moving to larger and larger rings of customers
  5. When the changes have rolled to every customer on the service and our telemetry indicates there are no issues, we mark the runner as “released”

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).

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found