Skip to content

fix(ci): repair invalid workflow and stale lockfile - #17

Merged
muhammetsafak merged 1 commit into
mainfrom
fix/wave3-ci
Oct 24, 2026
Merged

muhammetsafak merged 1 commit into
mainfrom
fix/wave3-ci

Conversation

@muhammetsafak

Copy link
Copy Markdown
Member

Root causes of the red main CI (run 40116710349):

  1. runner.temp used in job-level env of the redis job: not an allowed context, so GitHub rejected the whole workflow ("workflow file issue"). The results path is now exported via GITHUB_ENV in a first step.
  2. package-lock.json pinned @babelqueue/core 1.10.0 while sqs/kafka/redis require ^1.13.0; npm ci fails on that mismatch. Lockfile refreshed (only that entry changes).

Verified locally: actionlint clean, npm ci, build, typecheck, lint, npm test. Live Redis job is verified by this PR's CI.

…ockfile to core 1.13.0

The runner context is not allowed in job-level env, which made ci.yml
invalid (the run failed with a workflow file issue). The lockfile also
still pinned @babelqueue/core 1.10.0 while sqs, kafka and redis require
^1.13.0, so npm ci would have failed.
@muhammetsafak
muhammetsafak merged commit e4fa2ac into main Oct 24, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant