Skip to content

release dev#310

Closed
perasperaactual wants to merge 16 commits into
mainfrom
dev
Closed

release dev#310
perasperaactual wants to merge 16 commits into
mainfrom
dev

Conversation

@perasperaactual
Copy link
Copy Markdown
Contributor

No description provided.

perasperaactual and others added 16 commits April 4, 2026 02:47
- Add provenance: true to setup-node in prerelease and release workflows
- Replace pnpm publish -r with npm publish --provenance loop
- npm publish supports native OIDC authentication
- Update CLAUDE.md and CONTRIBUTING.md to emphasize dev branch targeting

Aligns with pro repo publishing strategy.
YAML doesn't allow duplicate keys at the same level.
Remove 27 stale changeset files that have already been applied
and update stackwright-docs package.json if needed
Regenerate lockfile to fix frozen-lockfile CI failure.
The package.json was missing react-dom as an explicit dependency,
causing frozen-lockfile CI failures. Add it and regenerate lockfile.
The ui-shadcn package has no test files (it's a thin adapter over Radix UI
+ Tailwind CSS). Excluding it from test commands prevents vitest from failing
with 'No test files found' error.
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
stackwright-docs Error Error Apr 7, 2026 4:47pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026

🧪 Coverage Report\n\n### Overall Coverage\n\n| Metric | Coverage |\n|--------|----------|\n| Lines | ⚠️ 74.30% |\n| Statements | ⚠️ 73.19% |\n| Functions | ⚠️ 74.25% |\n| Branches | ⚠️ 64.15% |\n\n### Coverage by Package\n\n| Package | Lines | Statements | Functions | Branches |\n|---------|-------|-----------|-----------|----------|\n| @stackwright/build-scripts | 83.98% | 82.73% | 84.61% | 75.00% |\n| @stackwright/cli | 55.24% | 54.97% | 52.11% | 55.47% |\n| @stackwright/collections | 100.00% | 92.85% | 100.00% | 85.71% |\n| @stackwright/core | 79.95% | 78.57% | 77.77% | 62.02% |\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 | 87.23% | 87.23% | 84.61% | 79.71% |\n| @stackwright/themes | 98.85% | 93.68% | 96.15% | 82.35% |\n| @stackwright/types | 97.40% | 97.43% | 75.00% | 100.00% |\n\n---\n📊 Full HTML report available in workflow artifacts\n

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026

⚡ Performance Benchmark Results

✅ Build Time Benchmarks: PASSED

❌ Bundle Size Benchmarks: FAILED

❌ 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-04-07T16:49:06.838Z

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026

✅ Visual Regression Test Results

Status: ✅ All visual tests passed!

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

perasperaactual added a commit that referenced this pull request Apr 7, 2026
Examples use 'next lint' instead of ESLint directly, causing CI to fail with:
  Invalid project directory: examples/stackwright-docs/lint

The lint task in CI was including all workspace packages (including examples)
via pnpm turbo:lint. Excluding examples from the lint task fixes this.

Closes #310
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026

♿ 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 added a commit that referenced this pull request Apr 7, 2026
* refactor(otters): relocate to packages/otters/src/ for proper monorepo structure (#299)

* chore: bump prerelease versions [skip ci]

* chore: refresh prerelease mode after v0.7.0 release [skip ci]

* fix(ci): add push trigger to release workflow for main branch

* feat: add Turborepo for incremental builds and intelligent caching (#304)

* docs: add architecture principles and CI philosophy (#301)

* feat: add Turborepo for incremental builds and intelligent caching (#305)

* fix: enable npm OIDC provenance and update branching docs

- Add provenance: true to setup-node in prerelease and release workflows
- Replace pnpm publish -r with npm publish --provenance loop
- npm publish supports native OIDC authentication
- Update CLAUDE.md and CONTRIBUTING.md to emphasize dev branch targeting

Aligns with pro repo publishing strategy.

* fix: merge duplicate env blocks in ci.yml

YAML doesn't allow duplicate keys at the same level.

* chore: clean up consumed changesets

Remove 27 stale changeset files that have already been applied
and update stackwright-docs package.json if needed

* chore: sync pnpm-lock.yaml with package.json

Regenerate lockfile to fix frozen-lockfile CI failure.

* fix: add missing react-dom dependency to stackwright-docs

The package.json was missing react-dom as an explicit dependency,
causing frozen-lockfile CI failures. Add it and regenerate lockfile.

* docs: update CLAUDE.md and CONTRIBUTING.md, add .turbo/ to gitignore (#307)

* fix: exclude @stackwright/ui-shadcn from test commands (#309)

The ui-shadcn package has no test files (it's a thin adapter over Radix UI
+ Tailwind CSS). Excluding it from test commands prevents vitest from failing
with 'No test files found' error.

* fix: exclude examples from turbo lint in CI (#311)

Examples use 'next lint' instead of ESLint directly, causing CI to fail with:
  Invalid project directory: examples/stackwright-docs/lint

The lint task in CI was including all workspace packages (including examples)
via pnpm turbo:lint. Excluding examples from the lint task fixes this.

Closes #310

---------

Co-authored-by: github-actions <github-actions@github.com>
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