docs: update v23.1.4 release notes intro

[thepastaclaw]

Update v23.1.4 release notes title and intro

Issue being fixed or feature implemented

The current v23.1.x release notes describe the v23.1.4 changelog, but the
top-level title still said v23.1.3. Review also noted that the intro should
say this release brings performance improvements and bug fixes, not GUI
improvements or the one-word bugfixes spelling.

What was done?

• Updated the doc/release-notes.md title from Dash Core version v23.1.3 to
  Dash Core version v23.1.4.
• Updated the intro text to say the release brings performance improvements and
  bug fixes.

How Has This Been Tested?

• Ran git diff --check.
• Verified the first line of doc/release-notes.md is now
  # Dash Core version v23.1.4.
• Verified the intro now says performance improvements and bug fixes.
• Ran pre-PR code review and got ship.

Breaking Changes

None.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone

[thepastaclaw]

@coderabbitai review

[github-actions]

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Walkthrough

The release notes document doc/release-notes.md has been updated to reflect the v23.1.4 patch. The title header changes from v23.1.3 to v23.1.4, and the accompanying description is updated from "bringing GUI improvements and bugfixes" to "bringing performance improvements and bug fixes."

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title 'docs: update v23.1.4 release notes intro' clearly and directly describes the main change—updating release notes documentation to reflect v23.1.4 with revised introductory text.
Description check	✅ Passed	The description provides clear context about the issue, the changes made, testing performed, and follows the project's checklist format, all directly related to the release notes updates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[UdjinM6]

consider fixing intro text too - "bringing GUI improvements and bugfixes" -> "bringing performance improvements and bugfixes"

[thepastaclaw]

Updated the intro wording to “performance improvements and bugfixes” in 0495b47. Thanks!

[thepastaclaw]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

🧹 Nitpick comments (1)

doc/release-notes.md (1)

3-3: 💤 Low value

Use standard spelling "bug fixes" instead of "bugfixes".

The term should be two words for consistency with standard English orthography and the document's own style (e.g., "Change log" on line 53 uses two words).

✏️ Proposed fix

-This is a new patch version release, bringing performance improvements and bugfixes.
+This is a new patch version release, bringing performance improvements and bug fixes.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@doc/release-notes.md` at line 3, In the release notes summary sentence,
change the spelling of "bugfixes" to "bug fixes" (two words) to align with
standard English orthography and maintain consistency with the document's
existing style conventions elsewhere in the file.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@doc/release-notes.md`:
- Line 3: In the release notes summary sentence, change the spelling of
"bugfixes" to "bug fixes" (two words) to align with standard English orthography
and maintain consistency with the document's existing style conventions
elsewhere in the file.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: f4e934c8-d8bd-448c-bdaa-51bf04dee562

📥 Commits

Reviewing files that changed from the base of the PR and between 3826688 and 0495b47.

📒 Files selected for processing (1)

• doc/release-notes.md

[thepastaclaw]

Applied CodeRabbit’s wording nit: “bug fixes” in 10b6309.

[thepastaclaw]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[UdjinM6]

might want to update pr title and description accordingly now

[UdjinM6]

utACK 10b6309

[thepastaclaw]

Updated the PR title and description to cover both the title and intro wording changes.

[thepastaclaw]

✅ Review complete (commit 10b6309)

[thepastaclaw]

Code Review

Trivial docs-only change to v23.1.4 release notes: corrects the title from v23.1.3 to v23.1.4 and rewords the intro to accurately describe the release contents. Targeting v23.1.x is appropriate for a real release notes update. No issues found.

Note: posted as a COMMENT review because GitHub does not allow approving my own PR.