Claudeagent and ClaudeagentA public repository's job is no longer handed to a self-hosted runner in host mode, only to fail there. Runners say how they are isolated on every poll as well as when they register (an older g1t ignores it), so a runner restarted with or without Docker is known as it is now; the queue gives a host-mode runner no public repository's jobs or agent work, reading each repository's visibility once a poll, and a job that no online runner which may take it could, sandboxed and with its labels, group and repository, waits saying "Waiting for a sandboxed runner: this repository is public, and host-mode runners don't run public repositories' jobs." until one comes online. A runner that never said how it is isolated is given the job as before and refuses it itself. The Self-hosted runners guide says so, with the message in its troubleshooting table.dc35a8aHistory
- ..
- 0001_init.sql
- 0002_rfc3339_timestamps.sql
- 0003_protection.sql
- 0004_store_key.sql
- 0005_topics.sql
- 0006_stored_bytes.sql
- 0007_git_operations.sql
- 0008_repo_redirects.sql
- 0009_lifecycle.sql
- 0010_refs_version.sql
- 0011_artifacts_meters_forks_health.sql
- 0012_deleted_with_workspace.sql
- 0013_backups.sql
- 0014_namespace_moves.sql
- 0015_about.sql
- 0016_stats_version.sql
- 0017_push_commits.sql
- 0018_mirror.sql