docs(blog): add v3.3.0 release blog post

[gauthier-th]

Description

Add the v3.3.0 and v3.2.0 release blog post.

How Has This Been Tested?

cd gen-docs
pnpm start

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Documentation
  • Added release notes for Seerr v3.2.0 and v3.3.0 outlining “What’s New,” blocklist upgrades, expanded language support, notifications & webhooks improvements, additional quality-of-life enhancements, and a “New Contributors” section.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new release notes blog post was added for Seerr versions 3.2.0 and 3.3.0, documenting feature highlights including blocklist upgrades, expanded language support, notification enhancements, and recognizing first-time contributors with GitHub links.

Changes

Seerr v3.2.0 and v3.3.0 Release Notes

Layer / File(s)	Summary
Release notes document with metadata and highlights gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md	YAML front-matter with title, description, slug, and authors; feature highlights spanning blocklist improvements, i18n expansions, and notification/webhook enhancements; new contributors list with GitHub links; and a closing "What's Next" section header.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• fallenbagel
• 0xSysR3ll

Poem

🐰 Two releases stitched in a markdown song,
Notes and contributors gathered along,
Blocklists trimmed and languages grown,
Webhooks humming in a brighter tone,
A rabbit cheers — the changelog's strong!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title references v3.3.0 release blog post, but the changeset includes both v3.2.0 and v3.3.0 release notes, making it partially incomplete.
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.
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.}

---

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

🧹 Nitpick comments (1)

gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md (1)

61-98: ⚡ Quick win

Add a closing “What’s Next” section for release-note continuity.

This post currently ends after the contributors list. Adding a short “What’s Next” section (with a link to the next/related release note) keeps consistency with your release-note flow and improves navigation.

✏️ Proposed addition

+## What's Next
+
+Continue with the next release notes here: [Seerr v3.1.0: Critical Security Release](/blog/seerr-3-1-0-security-release).

🤖 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 `@gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md` around lines
61 - 98, Add a closing "What's Next" section immediately after the contributors
list: create a short heading "What's Next" and one sentence linking to the next
or related release note (e.g., "Read the v3.4.0 release notes" or similar) with
a relative URL, and optionally include a one-line pointer to the project roadmap
or contribution guide; place this new section at the end of
gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md so the post
flows consistently from contributors -> What's Next.

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

Inline comments:
In `@gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md`:
- Line 47: The image alt text is wrong: update the markdown image tag that
currently reads ![Webhook Custom Headers](./discord-multiple-ids.png) so the alt
text describes the actual file (e.g., "Discord multiple IDs" or "Discord -
multiple IDs") instead of "Webhook Custom Headers"; locate the occurrence by
searching for the filename discord-multiple-ids.png and replace the alt string
while leaving the image path intact to improve accuracy and accessibility.

---

Nitpick comments:
In `@gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md`:
- Around line 61-98: Add a closing "What's Next" section immediately after the
contributors list: create a short heading "What's Next" and one sentence linking
to the next or related release note (e.g., "Read the v3.4.0 release notes" or
similar) with a relative URL, and optionally include a one-line pointer to the
project roadmap or contribution guide; place this new section at the end of
gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md so the post
flows consistently from contributors -> What's Next.

🪄 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: c3a4e8ab-ddbd-4f45-a4bf-c14e2413b35e

📥 Commits

Reviewing files that changed from the base of the PR and between 63175f5 and bb43b22.

⛔ Files ignored due to path filters (4)

• gen-docs/blog/2026-06-01/blocklist-region-language.png is excluded by !**/*.png
• gen-docs/blog/2026-06-01/discord-multiple-ids.png is excluded by !**/*.png
• gen-docs/blog/2026-06-01/server-side-i18n.png is excluded by !**/*.png
• gen-docs/blog/2026-06-01/webhook-custom-headers.png is excluded by !**/*.png

📒 Files selected for processing (1)

• gen-docs/blog/2026-06-01/seerr-3-2-0-and-3-3-0-release-notes.md