Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Hosted deployment: remove the legacy runner loop and legacy claim payload

Open
  • Is something wrong?
#336 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
api

Research direction

Start by confirming that #335 has landed and that one release of notice has passed, since the issue is blocked until then. The work is removing the legacy combined runner loop, its claim and complete path, and the legacy claim response that carries job input and secrets, while keeping the runner API at version 1. Done means the image smoke test (T01) finds no legacy loop, an old claim without the feature returns a documented error (T02), the split flow is unchanged (T03), and the release notes state the removal and required App version (T04).

Written by the indexing model from the issue text.

Description

area: runner post-mvp type: chore

Part of ##316. Later.

Problem

Once the split is the default and has been stable, the legacy combined loop and the legacy claim payload (job input and secrets in the claim response) are dead weight and a larger attack surface.

Design

Remove the legacy loop's claim and complete path and the legacy claim response after one release of notice. The runner API stays version 1; an old claim without the feature gets a documented error. All supported Apps must already have the new API.

Scope

Deletion, a documented error, docs, release notes.

Depends on

##335 and one release of notice.

Test cases

ID kind level case expected
T01 regression image smoke the image contains no legacy loop
T02 error integration an old claim without the feature a documented error
T03 regression integration split flow unchanged
T04 docs review release notes state the removal and the required App version
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
1h 18m
Merged PRs (30d)
186

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExpidetGames/code-reviewer

All issues in ExpidetGames/code-reviewer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.