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

[ci] Run the App update helper regression suite in CI

Open Beginner friendly
  • Is something wrong?
#184 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python
Domain
ci-cd

Research direction

Start in .github/workflows/ci.yml and pick the job that runs on every push and pull request, such as the L0-L2 static, unit, contract job, checking that its runner has Python 3. Add one step that runs python3 -I -B scripts/docker/app-update-helper.test.py. Run that command locally first to confirm it passes; done means a deliberately broken assertion fails the CI job on a pull request while the unmodified suite passes.

Written by the indexing model from the issue text.

Description

enhancement

Problem

CI never runs the App update helper's own regression suite, scripts/docker/app-update-helper.test.py. No workflow job, package script or repository gate invokes it; the only Python in .github/workflows/ci.yml is a host snapshot step. The helper stops, renames, restores and starts the running App during a supported update, so a regression in it can leave a user's App stopped, and today only a manual run would catch it.

This gap let a release-blocking defect reach staging during the v0.1.0-rc.1 cycle: an exact-commit update to the commit already running stopped the App, then refused Web publication, then failed automatic restoration because no candidate container existed. The fix added three regressions to this file. They pass when run directly (python3 -I -B scripts/docker/app-update-helper.test.py), but nothing enforces them.

Suggested fix

Add one step that runs python3 -I -B scripts/docker/app-update-helper.test.py to a CI job that runs on every push and pull request, for example the "L0-L2 static, unit, contract" job if its test image has Python 3, or otherwise a runner-level job that uses the runner's system Python. The suite uses only the standard library and in-process fakes, needs no Docker and finishes in about 25 seconds. No new runner, wrapper or dependency is needed. Note that scripts/validate-test-governance.mjs recognizes only JavaScript and TypeScript test files, so no existing gate reports this gap; running the file directly also fails the step if the file is renamed or removed.

Acceptance

A deliberately broken helper assertion fails the CI job on a pull request, and the unmodified suite passes there.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
12h 53m
Merged PRs (30d)
13

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 lingkaix/openkit

All issues in lingkaix/openkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.