4.0.1 release

[JeroenDeDauw]

Depends on

• Fix page dedup cache preventing retry after failed API calls #94

Summary by CodeRabbit

• Bug Fixes

  • Fixed redirect and type errors
  • Fixed redirect title resolution
  • Fixed title icon redirects
  • Fixed page deduplication cache persistence
  • Updated translations

• Chores

  • Bumped version to 4.0.1

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request bumps the extension version to 4.0.1 and adds corresponding release notes documentation. The changes consist of a version string update in extension.json and a new release notes section in README.md listing five bug fixes, with no modifications to functional code.

Changes

Cohort / File(s)	Summary
Version 4.0.1 Release extension.json, README.md	Version number incremented from 4.0.0 to 4.0.1; new release notes section added to README documenting five fixes including redirect/type errors, redirect title resolution, title icon redirects, page deduplication cache persistence, and translation updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Version 4.0.1 release' clearly and directly summarizes the main change: bumping the extension version from 4.0.0 to 4.0.1 and adding corresponding release notes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rel401

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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 `@README.md`:
- Line 370: Confirm and correct the release date string "Released on March 2nd,
2026." in the README: either update it to the actual release date (e.g., March
1, 2026) or replace it with a non-specific placeholder like "Release date: TBD"
before merging; ensure the final commit restores the accurate date once release
timing is confirmed.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 434e7db and 0e0704d.

📒 Files selected for processing (2)

• README.md
• extension.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Please confirm the release date before merge.

Released on March 2nd, 2026 is future-dated relative to this PR creation date (March 1, 2026). If the release timing shifts, this line will become inaccurate.

🤖 Prompt for AI Agents

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

In `@README.md` at line 370, Confirm and correct the release date string "Released
on March 2nd, 2026." in the README: either update it to the actual release date
(e.g., March 1, 2026) or replace it with a non-specific placeholder like
"Release date: TBD" before merging; ensure the final commit restores the
accurate date once release timing is confirmed.