Update release notes for 1.7.5

[sejas]

Proposed Changes

• Update release notes to capture changes shipped in 1.7.5

Testing Instructions

• Review RELEASE-NOTES.txt for accuracy and tone consistency with previous releases

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors? (Tests pass, no errors)

[sejas]

@claude review this PR

[claude]

Claude finished @sejas's task in 1m 38s —— View job

---

PR Review: Update release notes for 1.7.5

• Gather context
• Read changed files
• Review release notes content
• Post final review

---

Overview

This PR replaces auto-generated release notes (raw commit titles) with curated, user-friendly entries for 1.7.5. The curation approach — removing internal tooling changes, dependency bumps, and test fixes — is consistent with how prior releases like 1.7.4 were written. Overall the content reads well.

Issues Found

Style inconsistency — trailing period (line 19)

One bullet ends with a period while all others do not:

* Improved compatibility with Studio sites with legacy mu-plugin in the filesystem. #2655

All other entries in 1.7.5 (and throughout the entire file) omit trailing punctuation. The period should be removed.

Fix this →

---

Potentially Missing User-Facing Items

A few commits that landed in the release branch appear user-facing but are not in the notes. These may have been intentionally omitted — worth a quick check:

Commit	Feature	Rationale for inclusion
#2527	Add support for Blueprints login	Landed in this branch (0619a2b) and enables a new auth flow for Blueprint users
#2571	Add Blueprint details step to blueprint selection flow	User-visible Blueprint UI step
#2602	Add default Blueprint description from steps	User-visible Blueprint UX improvement
#2657	Make site create CLI command interactive	CLI UX improvement for users who script site creation
#2666	Improve welcome screen shown in offline mode	User-visible UI improvement

These are low-severity observations — if they were intentionally scoped out (e.g., shipped as internal improvements, or deferred), the current notes are fine.

---

What's Working Well

• The curation is clean and appropriately removes ~40 dependency bumps, test fixes, and internal tooling PRs
• Verb tense and phrasing ("Added", "Fixed", "Improved", "Disabled") is consistent throughout and matches prior releases
• Multiple related PRs are correctly grouped (e.g., #2649, #2656 for the debug log buttons; #2618, #2654 for accessibility)
• The dependency update line correctly calls out the key packages (Electron, WordPress Playground, PHP-WASM, Sentry)

Summary

One minor fix needed: remove the trailing period on line 19. A second pass on whether the Blueprint login (#2527) and CLI interactive create (#2657) warrant a mention is also recommended, as both are directly user-facing changes.

[Copilot]

Pull request overview

Updates the project’s release notes to reflect the shipped changes in version 1.7.5, keeping end-user documentation current alongside the codebase.

Changes:

• Replaced the verbose 1.7.5 changelog list with a concise, user-focused summary of key features, fixes, and improvements.
• Consolidated dependency update items into a single high-level entry.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[katinthehatsite]

This is a pretty big change - perhaps it could be moved up in this list. Although, for users, it is not as that impactful

[wojtekn]

Do we need this entry at all? I would skip entries that are about changing the repo structure, build systems, etc.

[sejas]

Removed! 49d56fb

Thank you both!

[katinthehatsite]

The changes look good to me, I left some minor comments mostly related to grammar