Skip to content

Bump to v1.5.0#3709

Merged
wwwillchen merged 1 commit into
dyad-sh:mainfrom
wwwillchen:bump-to-v1-5-0
Jun 29, 2026
Merged

Bump to v1.5.0#3709
wwwillchen merged 1 commit into
dyad-sh:mainfrom
wwwillchen:bump-to-v1-5-0

Conversation

@wwwillchen

@wwwillchen wwwillchen commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

#skip-bb


Note

Low Risk
Version metadata only; no application, dependency, or runtime code changes.

Overview
Promotes the dyad package from 1.5.0-beta.1 to stable 1.5.0.

Updates the root version field in package.json and the matching root package entry in package-lock.json so npm metadata reflects the release.

Reviewed by Cursor Bugbot for commit d8e4862. Bugbot is set up for automated code reviews on this repo. Configure here.

Review in cubic

@cursor

cursor Bot commented Jun 29, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_eb16bdb4-f090-4c8e-af60-628969028d84)

@wwwillchen wwwillchen merged commit 268a083 into dyad-sh:main Jun 29, 2026
10 of 12 checks passed

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

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.

Code Review

This pull request updates the project version from 1.5.0-beta.1 to 1.5.0 in package.json and package-lock.json. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Copilot AI left a comment

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.

Pull request overview

Promotes the root dyad package from prerelease 1.5.0-beta.1 to the stable 1.5.0 by updating npm version metadata in the root manifest and lockfile.

Changes:

  • Update root package.json "version" to 1.5.0.
  • Update package-lock.json top-level "version" and root package entry (packages[""]) to 1.5.0.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Bumps root package version to 1.5.0.
package-lock.json Keeps lockfile version metadata in sync with the root package version (1.5.0).

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

@dyad-assistant

Copy link
Copy Markdown
Contributor

πŸ” Dyadbot Code Review Summary

Verdict: βœ… YES - Ready to merge
Recommendation: ready

Minimal version bump from 1.5.0-beta.1 to 1.5.0 across package.json and package-lock.json (3 lines changed). All three version locations are consistent. No code, dependency, or runtime changes.

  • forge.config.ts reads version from package.json dynamically at build time, so no additional file edits are needed.
  • The isPrereleaseVersion() utility in the release scripts checks for a - in the version string; "1.5.0" will correctly be treated as a stable release.
  • The backup manager's upgrade detection (semver comparison) will correctly recognize the promotion from 1.5.0-beta.1 to 1.5.0.

βœ… No issues found by persona-based review.


Generated by Dyadbot persona-based code review

@github-actions

Copy link
Copy Markdown
Contributor

🎭 Playwright Test Results

❌ Some tests failed

OS Passed Failed Flaky Skipped
🍎 macOS 526 6 3 169
πŸͺŸ Windows 527 1 4 169

Summary: 1053 passed, 7 failed, 7 flaky, 338 skipped

Failed Tests

🍎 macOS

  • local_agent_code_search.spec.ts > local-agent - code search
    • Error: expect(received).toBe(expected) // Object.is equality
  • package_manager.spec.ts > build mode - safe npm package installs through the real socket firewall path
    • Error: Command failed: npx --prefer-offline --yes sfw@2.0.4 --help
  • package_manager.spec.ts > build mode - blocked unsafe npm package shows the real socket verdict and preserves app files
    • Error: Command failed: npx --prefer-offline --yes sfw@2.0.4 --help
  • setup_flow.spec.ts > Setup Flow > node.js install flow
    • TimeoutError: locator.click: Timeout 30000ms exceeded.
  • supabase_migrations.spec.ts > supabase migrations
    • Error: expect(locator).toBeEnabled() failed
  • supabase_migrations.spec.ts > supabase migrations with native git
    • Error: expect(locator).toBeEnabled() failed

πŸͺŸ Windows

  • setup_flow.spec.ts > Setup Flow > node.js install flow
    • TimeoutError: locator.dispatchEvent: Timeout 30000ms exceeded.

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

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

npm run e2e \
  e2e-tests/local_agent_code_search.spec.ts \
  e2e-tests/package_manager.spec.ts \
  e2e-tests/setup_flow.spec.ts \
  e2e-tests/supabase_migrations.spec.ts

⚠️ Flaky Tests

🍎 macOS

  • chat_input.spec.ts > send button disabled during pending proposal (passed after 1 retry)
  • context_limit_banner.spec.ts > context limit banner shows 'costs extra' for long context (passed after 1 retry)
  • visual_editing.spec.ts > swap image via URL (passed after 1 retry)

πŸͺŸ Windows

  • app_screenshot.spec.ts > captures an app screenshot after the first generated commit (passed after 1 retry)
  • chat_input.spec.ts > send button disabled during pending proposal (passed after 1 retry)
  • mention_files.spec.ts > mention file (passed after 1 retry)
  • queued_message.spec.ts > queued messages > can be reordered, deleted, and edited (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.

2 participants