Skip to content

release: @stackwright/cli@0.8.6 — back-merge & js-yaml override fixes#435

Merged
perasperaactual merged 8 commits into
mainfrom
dev
May 17, 2026
Merged

release: @stackwright/cli@0.8.6 — back-merge & js-yaml override fixes#435
perasperaactual merged 8 commits into
mainfrom
dev

Conversation

@perasperaactual
Copy link
Copy Markdown
Contributor

Release: @stackwright/cli@0.8.6

What's in this release

Three patch fixes to the CLI's release and back-merge pipeline:

  • fix-back-merge-loop: Upgrade the back-merge rebase conflict handler from a one-shot block to a loop. dev can accumulate multiple alpha-bump commits that all modified .changeset/pre.json — the previous one-shot ||{ } only resolved the first conflict.
  • fix-back-merge-pre-json-conflict: Fix back-merge into dev failing with a modify/delete conflict on .changeset/pre.json during rebase. The release workflow deletes this file via changeset pre exit, but dev's alpha-bump commits still reference it.
  • fix-js-yaml-override-conflict: Fix js-yaml version override conflict in pnpm overrides that caused yaml.safeLoad is removed errors when running changeset pre exit in CI.

Packages published

Package From To
@stackwright/cli 0.8.5 0.8.6

All other packages unchanged.

Checklist

  • 733 unit tests passing
  • pnpm format clean
  • pnpm lint clean (no errors)
  • pnpm-lock.yaml in sync
  • All 3 changesets scoped and reviewed

Stackwright Bot and others added 8 commits May 16, 2026 14:10
…rebase (#426)

Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
…evel (#430)

Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
…de + button contrast (#431)

Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
…ive guards (#432)

* docs(a11y): document intentional Chromium-only CI scope for accessibility tests

* fix(a11y): migrate FAQ to Radix Accordion, video accessible name, fix trap/carousel test guards

* chore: update lockfile for @radix-ui/react-accordion in @stackwright/core

* test(core): update FAQ test for Radix Accordion refactor

The FAQ component was refactored to use Radix UI Accordion in this PR.
Update the stale test to click the trigger before asserting answer
visibility, and rename it to accurately reflect the new DOM structure.

---------

Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
@github-actions
Copy link
Copy Markdown
Contributor

🧪 Coverage Report\n\n### Overall Coverage\n\n| Metric | Coverage |\n|--------|----------|\n| Lines | ⚠️ 74.79% |\n| Statements | ⚠️ 73.74% |\n| Functions | ⚠️ 74.74% |\n| Branches | ⚠️ 64.79% |\n\n### Coverage by Package\n\n| Package | Lines | Statements | Functions | Branches |\n|---------|-------|-----------|-----------|----------|\n| @stackwright/build-scripts | 82.83% | 81.53% | 83.75% | 74.93% |\n| @stackwright/cli | 56.35% | 56.03% | 53.14% | 55.01% |\n| @stackwright/collections | 100.00% | 92.85% | 100.00% | 85.71% |\n| @stackwright/core | 79.58% | 78.34% | 76.97% | 62.51% |\n| @stackwright/icons | 100.00% | 100.00% | 100.00% | 100.00% |\n| @stackwright/mcp | 86.89% | 84.71% | 78.43% | 66.07% |\n| @stackwright/nextjs | 84.52% | 83.52% | 77.27% | 83.16% |\n| @stackwright/themes | 98.85% | 93.68% | 96.15% | 82.35% |\n| @stackwright/types | 82.63% | 81.99% | 84.21% | 64.45% |\n\n---\n📊 Full HTML report available in workflow artifacts\n

@github-actions
Copy link
Copy Markdown
Contributor

✅ Visual Regression Test Results

Status: ✅ All visual tests passed!

All screenshots match the baseline. No visual regressions detected! 🎉

@github-actions
Copy link
Copy Markdown
Contributor

⚡ Performance Benchmark Results

✅ Build Time Benchmarks: PASSED

✅ Bundle Size Benchmarks: PASSED

❌ Runtime Vitals Benchmarks: FAILED

📝 Note: Detailed results are available in the job logs.

🎯 Performance Budgets:

  • Build time: <70s total
  • First-load JS: <100KB gzipped
  • FCP: <1.5s, LCP: <2.5s, TTI: <3s

Updated: 2026-05-17T18:53:18.256Z

@github-actions
Copy link
Copy Markdown
Contributor

♿ Accessibility Test Results

Overall Status: ✅ 0/0 tests passed

🦮 WCAG 2.1 AA Compliance

No WCAG test results available

⌨️ Keyboard Navigation

No keyboard navigation test results available


⚠️ No accessibility tests were executed. Check the workflow logs for setup issues.

📊 Detailed Report

Download the full HTML accessibility report from the workflow artifacts for:

  • Detailed WCAG violation descriptions
  • Specific element selectors and fixes
  • Color contrast issues
  • Keyboard navigation flow analysis

🔍 Testing Checklist

Our accessibility tests verify:

  • ✅ WCAG 2.1 Level AA compliance
  • ✅ Color contrast in light and dark modes
  • ✅ Tab key navigation through all interactive elements
  • ✅ Focus indicators are visible
  • ✅ No keyboard traps
  • ✅ Skip links and ARIA landmarks
  • ✅ Screen reader compatibility

Powered by @axe-core/playwright and Playwright

@perasperaactual perasperaactual merged commit 58bb2b3 into main May 17, 2026
24 of 26 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