Self-hosted runner errors about lock_to_account_id now point to --lock-to-account and say the value must be an organization member
found in this entry's text, named in this entry
First cited
1
The earliest release whose published evidence quoted SELF_HOSTED_RUNNER_LOCK_TO_ACCOUNT was v2.1.296, 9 Oct 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
ReleaseDateThe span that was quoted
v2.1.2969 Oct 2026SELF_HOSTED_RUNNER_LOCK_TO_ACCOUNT
Presence across releases
1
BuildsHow manyDatesReading
v2.1.224 – v2.1.30974 builds7 Aug 2026 → 22 Oct 2026 ◆in the build
Build by build
74
One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.
