Skip to content

Bump to v0.43.0-beta.1#3161

Merged
wwwillchen merged 1 commit intodyad-sh:mainfrom
wwwillchen-bot:bump-to-v0-43-0-beta-1
Apr 7, 2026
Merged

Bump to v0.43.0-beta.1#3161
wwwillchen merged 1 commit intodyad-sh:mainfrom
wwwillchen-bot:bump-to-v0-43-0-beta-1

Conversation

@wwwillchen
Copy link
Copy Markdown
Collaborator

@wwwillchen wwwillchen commented Apr 7, 2026

#skip-bb


Open with Devin

@wwwillchen wwwillchen requested review from a team and Copilot April 7, 2026 20:50
@wwwillchen wwwillchen merged commit fa39a9a into dyad-sh:main Apr 7, 2026
9 of 10 checks passed
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

βœ… Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@dyad-assistant
Copy link
Copy Markdown
Contributor

dyad-assistant bot commented Apr 7, 2026

πŸ” Dyadbot Code Review Summary

Verdict: βœ… YES - Ready to merge

βœ… No issues found. PR is a trivial version bump (0.42.0 β†’ 0.43.0-beta.1) in package.json; multi-agent review skipped as unnecessary.


Generated by Dyadbot multi-agent code review

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps the app/package version to the next prerelease (0.43.0-beta.1) for the dyad npm package.

Changes:

  • Update package.json version from 0.42.0 to 0.43.0-beta.1

πŸ’‘ Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

{
"name": "dyad",
"version": "0.42.0",
"version": "0.43.0-beta.1",
Copy link

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package.json version was bumped, but package-lock.json still reports version 0.42.0 (both top-level and packages[""] entries). Please regenerate/update the lockfile (or otherwise keep it in sync) so npm ci/install doesn't leave the repo in a dirty state or produce confusing package metadata.

Suggested change
"version": "0.43.0-beta.1",
"version": "0.42.0",

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the version in package.json to 0.43.0-beta.1. A review comment correctly identifies that the package-lock.json file is now out of sync with this change and recommends updating it to maintain dependency consistency.

{
"name": "dyad",
"version": "0.42.0",
"version": "0.43.0-beta.1",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The package-lock.json file is out of sync with this version change. It still shows version 0.42.0 while this change updates package.json to 0.43.0-beta.1. This can lead to inconsistent dependency installations.

Please run npm install to update the lock file and commit the changes.

To prevent this in the future, consider updating the scripts/bump-version.mjs script to automate this step.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

🎭 Playwright Test Results

❌ Some tests failed

OS Passed Failed Flaky Skipped
🍎 macOS 409 3 7 131
πŸͺŸ Windows 406 9 4 131

Summary: 815 passed, 12 failed, 11 flaky, 262 skipped

Failed Tests

🍎 macOS

  • queued_message.spec.ts > editing queued message restores attachments and selected components
    • Error: expect(locator).toBeVisible() failed
  • queued_message.spec.ts > canceling queued message edit clears restored components
    • Error: expect(locator).toBeVisible() failed
  • socket_firewall.spec.ts > build mode - blocked unsafe npm package shows the real socket verdict and preserves app files
    • Error: expect(locator).toBeVisible() failed

πŸͺŸ Windows

  • context_manage.spec.ts > manage context - default
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed
  • context_manage.spec.ts > manage context - smart context
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed
  • context_manage.spec.ts > manage context - exclude paths
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed
  • context_manage.spec.ts > manage context - exclude paths with smart context
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed
  • github.spec.ts > should connect to GitHub using device flow
    • Error: expect(locator).toBeVisible() failed
  • github.spec.ts > create and sync to new repo
    • TimeoutError: page.waitForSelector: Timeout 5000ms exceeded.
  • github.spec.ts > create and sync to new repo - custom branch
    • TimeoutError: locator.click: Timeout 30000ms exceeded.
  • github.spec.ts > create and sync to existing repo
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed
  • github.spec.ts > create and sync to existing repo - custom branch
    • Error: expect(locator).toMatchAriaSnapshot(expected) failed

πŸ“‹ Re-run Failing Tests (macOS)

Copy and paste to re-run all failing spec files locally:

npm run e2e \
  e2e-tests/queued_message.spec.ts \
  e2e-tests/socket_firewall.spec.ts

⚠️ Flaky Tests

🍎 macOS

  • approve.spec.ts > write to index, approve, check preview (passed after 1 retry)
  • chat_image_generation.spec.ts > generate image from chat - full flow (passed after 1 retry)
  • context_limit_banner.spec.ts > context limit banner shows 'running out' when near context limit (passed after 2 retries)
  • debugging_logs.spec.ts > clear filters button works (passed after 1 retry)
  • setup_flow.spec.ts > Setup Flow > setup banner shows correct state when node.js is installed (passed after 1 retry)
  • setup_flow.spec.ts > Setup Flow > node.js install flow (passed after 2 retries)
  • visual_editing.spec.ts > swap image via URL (passed after 1 retry)

πŸͺŸ Windows

  • github.spec.ts > github clear integration settings (passed after 1 retry)
  • setup_flow.spec.ts > Setup Flow > setup banner shows correct state when node.js is installed (passed after 1 retry)
  • setup_flow.spec.ts > Setup Flow > node.js install flow (passed after 2 retries)
  • telemetry.spec.ts > telemetry - reject (passed after 1 retry)

πŸ“Š View full report

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.

3 participants