Repository navigation
fix(vis): tear down run services and report preflight errors - #30
Conversation
Cleanup was installed after the runtime was built and the run:before hook ran, so a failure there, or a dry run, left services booted by this run running. Install cleanup as soon as services are wired and keep the rest inside the try/finally. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Remote provider and repo detection in the release-PR check and the push-rule check could reject, so the publish preflight threw instead of returning a result. Record those errors as a _preflight failure and stop. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
|
Thank you for following the naming conventions! 🙏 |
commit: |
Merging this PR will not alter performance
|
## @visulima/vis [6.1.3](https://github.com/visulima/vis/compare/@visulima/vis@6.1.2...@visulima/vis@6.1.3) (2026-10-17) ### Bug Fixes * **vis:** tear down run services and report preflight errors ([#30](#30)) ([80d5a91](80d5a91))
Summary
Two fixes from the review of the refactor, applied on top of current
main. The refactor itself is already inmainvia #25, so this PR does not touch the module split.run:beforehook run inside thetry/finally. Regression test:run-teardown-on-throw.test.ts, which fails on the previous handler._preflightfailure instead of rejectingpublishContext. Regression test:orchestrator-preflight-guard.test.ts, which fails on the previous preflight.Behaviour change: a dry run now also runs teardown, and a failed remote lookup returns a failure result instead of throwing.
Testing
lint:typesandcheck:schemas-driftpass.audit-offlinefails in the full run and passes alone. Therelease-plan-perftest that failed in the base run passes here.Needs manual check before merge
🤖 Generated with Claude Code