chore(main): release 0.4.1

[c-thiel]

🤖 I have created a release beep boop

0.4.1 (2026-03-24)

Bug Fixes

• always show snackbar on 403 errors (#113) (47e6994)
• claude.md (fda8b0a)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Walkthrough

Bumps package version from 0.4.0 → 0.4.1: updates package.json and release-please/.release-please-manifest.json, and adds a new 0.4.1 changelog entry (2026-03-24) with a Bug Fixes item referencing claude.md (commit fda8b0a).

Changes

Cohort / File(s)	Summary
Release metadata & changelog CHANGELOG.md, package.json, release-please/.release-please-manifest.json	Version bumped from 0.4.0 → 0.4.1; added 0.4.1 changelog section dated 2026-03-24 with one bug-fix entry referencing claude.md (commit fda8b0a).

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly Related PRs

• lakekeeper/console-components#90: Another automated release bump touching CHANGELOG.md, package.json, and release-please manifest.
• lakekeeper/console-components#84: Release bump that updates the same set of release metadata files.
• lakekeeper/console-components#105: Automated release commit modifying changelog, package.json version, and release-please manifest.

Suggested Labels

autorelease: tagged

Poem

🐰 A tiny hop, a version nudge,
From 0.4.0 to 0.4.1 I judge,
Changelog penned, the manifest aligned,
A carrot cheer for fixes signed! 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(main): release 0.4.1' directly and accurately summarizes the main change: a version bump and release of version 0.4.1, which matches the changeset that updates version numbers in three files and adds a changelog entry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--components--console-components

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 3-9: Update the CHANGELOG.md entry for version 0.4.1: replace the
vague "claude.md" line under "Bug Fixes" with a clear, one-line description of
the actual change (e.g., the bug fixed in the claude integration or the
documentation update), and if it was only a documentation change move the entry
from "Bug Fixes" into a "Documentation" or "Chores" section; edit the line
containing "* claude.md
([fda8b0a](https://github.com/lakekeeper/console-components/commit/fda8b0a79651ee8d29d1cd7aac6df7856f51b2dc))"
to the specific text referencing the function/feature affected (for example the
claude integration handler or README update) so users can understand what was
fixed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 62537b75-e632-477c-b16e-aa3ccf40baa8

📥 Commits

Reviewing files that changed from the base of the PR and between 5db2c14 and 72a4603.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• CHANGELOG.md
• package.json
• release-please/.release-please-manifest.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Clarify the bug fix description.

The changelog entry references "claude.md" as a bug fix, which is unusual. Typically, bug fixes describe functional changes rather than referencing markdown files. Could you clarify:

1. What functionality was fixed?
2. Is this a documentation update that should be categorized differently (e.g., "Documentation" or "Chore" rather than "Bug Fixes")?

A clearer description would help users understand what was actually fixed in this patch release.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 3 - 9, Update the CHANGELOG.md entry for version
0.4.1: replace the vague "claude.md" line under "Bug Fixes" with a clear,
one-line description of the actual change (e.g., the bug fixed in the claude
integration or the documentation update), and if it was only a documentation
change move the entry from "Bug Fixes" into a "Documentation" or "Chores"
section; edit the line containing "* claude.md
([fda8b0a](https://github.com/lakekeeper/console-components/commit/fda8b0a79651ee8d29d1cd7aac6df7856f51b2dc))"
to the specific text referencing the function/feature affected (for example the
claude integration handler or README update) so users can understand what was
fixed.

[c-thiel]

🤖 Created releases:

• v0.4.1

🌻