feat: Announce OIDC email change and announce new scraper capabilities (#7963)

frontend/app/components/Domain/Announcement/Announcements/2026-07-27_1_oidc-email-verification.vue

@@ -0,0 +1,64 @@
+<template>
+  <div>
+    <p>
+      If your server signs users in with an external identity provider (OIDC), Mealie now requires that
+      provider to confirm the user's email address before allowing the login.
+    </p>
+    <p>
+      This prevents an unverified, self-asserted email address from being used to match (and sign in) to
+      an existing Mealie account.
+    </p>
+    <div v-if="user?.admin">
+      <hr class="mt-2 mb-4">
+      <p>
+        As an admin, be aware that this is a <strong>breaking change</strong> for identity providers that do
+        not emit the <code>email_verified</code> claim. Those logins now fail, and
+        <code>[OIDC] email_verified claim is missing or false</code> is written to the server logs.
+      </p>
+      <div class="mb-2">
+        You have two options:
+        <ul class="ml-6">
+          <li>Configure your identity provider to include the <code>email_verified</code> claim (recommended)</li>
+          <li>Set <code>OIDC_REQUIRES_EMAIL_VERIFICATION=false</code> to restore the previous behavior</li>
+        </ul>
+      </div>
+      <p>
+        Most providers (Authentik, Authelia, Keycloak, Google, Entra ID, ...) send this claim already and are
+        unaffected. See the OIDC docs for details:
+        <br>
+        <v-btn
+          class="mt-2"
+          color="primary"
+          href="https://docs.mealie.io/documentation/getting-started/authentication/oidc-v2/#email-verification"
+          target="_blank"
+        >
+          OpenID Connect (OIDC)
+        </v-btn>
+      </p>
+    </div>
+    <div v-else>
+      <p>
+        If you can no longer sign in with your external account, contact your server admin. They may need to
+        update the server's OIDC configuration.
+      </p>
+    </div>
+  </div>
+</template>
+
+<script setup lang="ts">
+import type { AnnouncementMeta } from "~/composables/use-announcements";
+
+const { user } = useMealieAuth();
+</script>
+
+<script lang="ts">
+export const meta: AnnouncementMeta = {
+  title: "OIDC logins now require a verified email",
+};
+</script>
+
+<style scoped lang="css">
+p {
+  padding-bottom: 8px;
+}
+</style>

frontend/app/components/Domain/Announcement/Announcements/2026-07-27_2_scraper-proxy-flaresolverr.vue

@@ -0,0 +1,71 @@
+<template>
+  <div>
+    <p>
+      Importing recipes from a URL is now more reliable. Mealie does a better job of looking like a real
+      browser, rotates between several browser signatures, and retries more intelligently when a site
+      pushes back. This works out of the box, with no configuration.
+    </p>
+    <p>
+      Some sites sit behind bot protection (such as Cloudflare) that blocks requests made by a server, no
+      matter how they're made. For those, Mealie can now optionally fall back to two extra layers.
+    </p>
+    <div class="mb-2">
+      <ul class="ml-6">
+        <li>
+          <strong>Proxy support</strong>, which routes recipe and image requests through a proxy. This
+          helps with sites that block your server's IP address.
+        </li>
+        <li>
+          <strong>FlareSolverr support</strong>, which hands the page to a real headless browser as a last
+          resort. This helps with challenges that Mealie can't get past on its own.
+        </li>
+      </ul>
+    </div>
+    <div v-if="user?.admin">
+      <hr class="mt-2 mb-4">
+      <p>
+        Both are optional and off by default, so nothing changes unless you configure them. Mealie
+        escalates only as far as it needs to for each import: a direct fetch first, then the proxy (if
+        set), then FlareSolverr (if set, and only when the page is still blocked).
+      </p>
+      <p>
+        Both are enabled with environment variables. Mealie does not ship or manage either one. You supply
+        the proxy, and host FlareSolverr yourself (it runs nicely as a sidecar container). See the
+        configuration docs for the settings, setup details, and an example compose file:
+        <br>
+        <v-btn
+          class="mt-2"
+          color="primary"
+          href="https://docs.mealie.io/documentation/getting-started/installation/backend-config/#recipe-scraper"
+          target="_blank"
+        >
+          Backend Configuration
+        </v-btn>
+      </p>
+    </div>
+    <div v-else>
+      <p>
+        If a recipe URL still refuses to import, let your server admin know. They can enable these extra
+        options on the server.
+      </p>
+    </div>
+  </div>
+</template>
+
+<script setup lang="ts">
+import type { AnnouncementMeta } from "~/composables/use-announcements";
+
+const { user } = useMealieAuth();
+</script>
+
+<script lang="ts">
+export const meta: AnnouncementMeta = {
+  title: "Better recipe imports, with proxy and FlareSolverr support",
+};
+</script>
+
+<style scoped lang="css">
+p {
+  padding-bottom: 8px;
+}
+</style>