release workflow updates#402
Merged
Merged
Conversation
Contributor
🧪 Coverage Report\n\n### Overall Coverage\n\n| Metric | Coverage |\n|--------|----------|\n| Lines |
|
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
Contributor
⚡ 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:
Updated: 2026-05-08T03:17:05.280Z |
Prevents phantom commits from accumulating in dev's ancestry. Previously, git merge main preserved all old dev commit SHAs as reachable ancestors of dev HEAD — causing dev→main PRs to show dozens of already-released commits. With git rebase origin/main -X ours: - dev's unique commits are replayed cleanly on top of main - No merge commit bloat - Future dev→main PRs only show genuinely new work - Force push to dev is safe here (CI-managed branch) Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
Contributor
♿ Accessibility Test ResultsOverall Status: ✅ 0/0 tests passed 🦮 WCAG 2.1 AA ComplianceNo WCAG test results available ⌨️ Keyboard NavigationNo keyboard navigation test results available 📊 Detailed ReportDownload the full HTML accessibility report from the workflow artifacts for:
🔍 Testing ChecklistOur accessibility tests verify:
Powered by @axe-core/playwright and Playwright |
…prepublishOnly guard
perasperaactual
had a problem deploying
to
development
GitHub Actions
Failure
Contributor
❌ Visual Regression Test ResultsStatus: ❌ Visual regression tests failed Visual differences were detected! Please review:
📸 Baseline screenshots are committed to the repo for reproducible testing. |
…403) * fix(core,types): remove zod internals from published .d.ts - Replace z.ZodTypeAny in ContentTypeEntry / registerContentType / getContentTypeSchema with a local ZodSchema structural interface - Fix siteDefaults.ts relative source import → import type from package, eliminating z.core.$strip cascade in bundled declarations - Add workspace sibling packages to tsup external array - Replace z.ZodSchema / z.ZodTypeAny[] in PrebuildPlugin with ZodLike Consumer projects can delete stackwright-core.d.ts stub overrides. * fix(cli): update stale scaffold template package versions VERSIONS constant in buildPackageJson() was 4+ releases behind: - @stackwright/core: ^0.7.0 → ^0.8.0 - @stackwright/nextjs: ^0.3.1 → ^0.5.0 - @stackwright/icons: ^0.3.0 → ^0.5.0 - @stackwright/build-scripts: ^0.4.0 → ^0.7.0 (critical — plugin API is 0.5.0+) - @stackwright/ui-shadcn: ^0.1.0 → ^0.1.0 (minor range correct) - @stackwright/otters: ^0.2.0-alpha.0 → ^0.2.0 Adds scripts/sync-versions.mjs — run before releases to keep VERSIONS in sync with workspace package.json files automatically. * chore: update pnpm lockfile after cli package.json changes * fix: resolve CI failures — ZodLike discriminated union, internal cast, basic-ftp CVE - ZodLike interface now uses a discriminated union so TypeScript correctly narrows result.error in prebuild.ts validateIntegrationConfig() - Cast extraContentSchemas to z.ZodTypeAny[] internally in prebuild.ts; ZodLike is the public API surface, real Zod schemas are safe to cast - Update basic-ftp pnpm override from >=5.3.0 to >=5.3.1 (GHSA-rpmf-866q-6p89) * fix: apply same discriminated-union fix to ZodSchema in core zod-compat.ts contentRenderer.tsx accesses validation.error.issues after an !validation.success guard — same narrowing issue as plugin.ts ZodLike. Apply the identical discriminated-union pattern so TS18048 is resolved. * fix: update stale scaffold test expectation for @stackwright/core version The template-processor.ts already uses '^0.8.0' for swCore but the test was asserting '^0.7.0' — stale snapshot. Bump to match reality. --------- Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
perasperaactual
had a problem deploying
to
development
GitHub Actions
Failure
Contributor
🧪 Coverage Report\n\n### Overall Coverage\n\n| Metric | Coverage |\n|--------|----------|\n| Lines |
|
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
…404) Co-authored-by: Stackwright Bot <bot@per-aspera.dev>
perasperaactual
had a problem deploying
to
development
GitHub Actions
Failure
Contributor
🧪 Coverage Report\n\n### Overall Coverage\n\n| Metric | Coverage |\n|--------|----------|\n| Lines |
|
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
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.
No description provided.