Skip to content

docs: finalize CHANGELOG.md for v2.0.0 release #645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alfredo1996 merged 1 commit into from
May 2, 2026
Merged

docs: finalize CHANGELOG.md for v2.0.0 release #645

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ All notable changes to NeoBoard are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

## [Unreleased] — v1.0.0 Community Launch
## [2.0.0] — 2026-05-02

### Added

Expand All @@ -21,12 +21,18 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
- Husky pre-commit hook with lint-staged (ESLint + Prettier)
- jsdom component tests enabled in app/ package
- Demo seed dashboards (Transform Playground)
- Database selector for per-widget database/schema override (#633)
- Per-card write toggle with server-side `can_write` enforcement (#633)
- Circle packing and choropleth chart gallery demo pages (#630)
- NeoDash migration tool: settings mapping and conversion notes (#626)
- Widget editor sub-component unit tests (#628)

### Changed

- License: Elastic License 2.0 with AI training restriction
- Widget editor: eliminated bidirectional state sync (Zustand store as single source of truth)
- Extracted pure business logic from components into testable lib/ files
- Widget editor decomposed into focused sub-components (#627)

### Fixed

Expand All @@ -36,6 +42,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
- Editor cache lookup for parameterized widgets (partial key match)
- Null/undefined values matching numeric zero in transform filters
- Query editor test teardown leak (dangling timers)
- Build: resolve pg/tls client bundle error breaking E2E tests (#629)
- Pre-existing type errors on release/2.0 branch (#632)

@coderabbitai coderabbitai Bot May 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify the fix wording on Line 46.
In a ### Fixed section, this line reads like a status note rather than a resolved change.

Proposed wording tweak 
-- Pre-existing type errors on release/2.0 branch (`#632`)
+- Resolved pre-existing type errors on release/2.0 branch (`#632`)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- Pre-existing type errors on release/2.0 branch (#632)
- Resolved pre-existing type errors on release/2.0 branch (`#632`)
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 46, The changelog entry under the "### Fixed" section
currently reads like a status note ("Pre-existing type errors on release/2.0
branch (`#632`)"); update that line to explicitly state the resolution, e.g.
change it to a past-tense fix description such as "Resolved pre-existing type
errors on release/2.0 branch (`#632`)", so it clearly reads as an item in the
Fixed list rather than a status note.


### Security

Expand Down Expand Up @@ -128,3 +136,5 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
- User management with admin/creator roles
- AES-256-GCM credential encryption
- Multi-tenant architecture with tenant_id isolation

[2.0.0]: https://github.com/alfredo1996/neoboard/releases/tag/v2.0.0
Comment on lines +139 to +140

@coderabbitai coderabbitai Bot May 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use a comparison URL for [2.0.0] on Line 140.
The current link targets the release tag page, not a version comparison. Keep a Changelog-style links should point to compare ranges.

Proposed link fix 
-[2.0.0]: https://github.com/alfredo1996/neoboard/releases/tag/v2.0.0
+[2.0.0]: https://github.com/alfredo1996/neoboard/compare/v0.9.1...v2.0.0
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[2.0.0]: https://github.com/alfredo1996/neoboard/releases/tag/v2.0.0
[2.0.0]: https://github.com/alfredo1996/neoboard/compare/v0.9.1...v2.0.0
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 139 - 140, Update the link target for the markdown
reference "[2.0.0]" in CHANGELOG.md so it points to the GitHub comparison URL
for the range that ends at the v2.0.0 tag (i.e., use a
/compare/<previous-tag>...v2.0.0 style URL) instead of the current release tag
page; locate the "[2.0.0]" reference and replace its href with the proper
compare-range URL that spans from the prior version tag to v2.0.0.