Repository navigation
chore: update CI actions, fix lint warnings, harden debugpy tests - #4
Merged
Merged
Conversation
cmaranes
force-pushed
the
chore/ci-and-lint-cleanup
branch
2 times, most recently
from
October 22, 2026 13:52
c117cac to
c100b7c
Compare
cmaranes
changed the title
checkout v7, setup-node v7, setup-python v7, cache v6, upload-artifact v7, download-artifact v8 (fails on digest mismatch). Removes the Node 20 action-runtime deprecation warnings; Node 20 itself is end-of-life. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JBDmV8VxTwVxxpuC8NMG8y
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JBDmV8VxTwVxxpuC8NMG8y
- The fixture stops via breakpoint() instead of an editor breakpoint, which raced with debugpy startup on slow runners. - On CI the debugger still occasionally (~1 in 25 jobs) never reports the stop. The suite now retries the debugger start once, and a failure includes the Debug Adapter Protocol traffic and the activeStackItem state so the cause can be diagnosed if it recurs. - Clear the preview folder first: a manual F5 session that never terminated left a .ply that the file-count assertions counted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JBDmV8VxTwVxxpuC8NMG8y
cmaranes
force-pushed
the
chore/ci-and-lint-cleanup
branch
from
October 22, 2026 14:32
c2735bd to
3823afa
Compare
cmaranes
changed the title
3 tasks done
3 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #3, based on the warnings in the v0.1.0 release run.
checkout@v7,setup-node@v7,setup-python@v7,cache@v6,upload-artifact@v7anddownload-artifact@v8. The build moves from Node 20 (EOL) to Node 22. I checked the release notes for each major: the breaking changes only affect self-hosted runners or downloads by artifact ID. download-artifact v8 now fails on a hash mismatch, which is what we want for a release.if. No behavior change.breakpoint()instead of relying on an editor breakpoint. That removed one race, but the flake still happened about 1 in 25 jobs afterwards.activeStackItemstate. A consistent failure still fails, and if the flake recurs we'll have the evidence to find its root cause..vscode/ply_previewin the fixture workspace first. A manual F5 session that never terminated had left a.plybehind, and the file-count assertions counted it.Not solved
The root cause of the rare missed stop is unknown. 15 instrumented CI jobs in a row passed, so no failure log was captured.
Test plan
npm run lint: 0 problemsnpm testlocally: 6/6, including with the first debugger start forced to failbreakpoint()change, 1 failure in about 25 CI jobs; 15 consecutive instrumented jobs passed🤖 Generated with Claude Code
https://claude.ai/code/session_01JBDmV8VxTwVxxpuC8NMG8y