Skip to content

Releases

v2.6.1

Choose a tag to compare

@michelecanini michelecanini released this 12 Nov 11:14

🔎 Two fixes for how search engines and share previews read your pages. Every page told search engines it had an Italian version, translated or not, and the share image of a blog post sat behind a redirect. A PATCH: git pull, npm install. Nothing to migrate and nothing to configure.

Fixed

  • Pages declare only the languages they really have. The language library added a header to every response pointing at the /it/ version of the page, even where no translation exists, and there that address showed the English text marked as Italian. The header is off: each page declares its languages in its metadata, as the translated docs already did, and the sitemap lists them
  • Blog share images answer without a redirect. The image of each post was declared at an address with an internal /en/ prefix, which redirected to the real one. It now has its own route, /og/blog/<slug>, declared in the post's metadata; the picture is the same

v2.6.0

Choose a tag to compare

@michelecanini michelecanini released this 11 Nov 10:20

🧩 A cookie consent banner you can switch on, and a GitLab mirror of the kit. The banner ships off, because the kit sets no cookies that need consent; turn it on the day you add analytics with cookies or an ad pixel, and those scripts wait for a yes. The repository is now also on GitLab, for anyone who does not use GitHub or cannot reach it. A MINOR: git pull, npm install. Nothing to migrate, and both new variables are optional: leave them unset and nothing changes.

Added

  • Cookie consent, off by default, behind NEXT_PUBLIC_COOKIE_CONSENT="true": a banner with Accept and Reject that look the same, where closing counts as a rejection and the choice holds for six months; Cookie settings in the footer opens it again. Load scripts that set cookies through <ConsentScript> instead of next/script and they run only after Accept; with the variable off it is plain next/script. The sample /cookies page follows the switch. Configuration has the details and a screenshot
  • A GitLab mirror at gitlab.com/openstarterkit/nextjs-saas-starter-kit, with the same commits and tags. Getting started and the README give its clone command
  • NEXT_PUBLIC_GITLAB_URL: a second button, Get it on GitLab, next to the GitHub one on the pricing page, both now with their logos. Unset, the button does not show

Changed

  • A live demo on another domain opens in a new tab, from the hero, the navbar, the footer and the mobile menu, so the visitor keeps your page. The local sign-in a clone falls back to stays in the same tab
  • Getting started explains the install scripts npm skips. Recent npm versions list the ones from Prisma and unrs-resolver at the end of npm install: the kit does not need them, and there is nothing to approve
  • Dependencies: minimatch 11.0.1 or later through an override, for a moderate advisory under typescript-eslint that only runs while linting; npm audit is clean, development tools included. Minor updates to lucide-react, resend, tailwindcss, vitest, Playwright, @shikijs/rehype and @types/node

v2.5.3

Choose a tag to compare

@michelecanini michelecanini released this 06 Nov 11:33

🔒 A security update: Better Auth 1.7.18, Next.js 16.4.5, and five fixes in how the kit enforces its own rules. Several rules lived only in the server actions behind the kit's forms, so a request sent to the auth API directly did not meet them; they are now enforced where every request goes through. If you run the kit with email configured and two-factor authentication, with a public demo, or with one-time payments, update. A PATCH: git pull, npm install. Nothing to migrate. If you enable a delayed payment method in Stripe (SEPA, ACH, Bacs and the like), add the two events listed under Billing to your webhook endpoint.

Security

  • Better Auth 1.7.18, with the fixes the project published on November 3 (see its security advisories). Among them, for features the kit uses: an OAuth email the provider did not verify, email change links, and revoked sessions with the cookie cache
  • Next.js 16.4.5, with the fixes published on November 3 (see its security advisories)
  • Two-factor accounts can no longer sign in with a magic link or with the automatic sign-in after verifying an email, whichever way the request arrives. The magic link endpoint also keeps the per-address limit when it is called directly
  • On a public demo (DEMO_MODE), what the demo's actions refuse is refused over the auth API too: listing or ending sessions, two-factor setup, deleting the account, changing its email or password, signing up and resetting a password. The Active sessions card is unchanged
  • Names are escaped in every email (welcome, subscription, purchase, cancellation), as the contact and invitation emails already were. A display name is capped at 100 characters wherever it is set, and may not contain a web address, which mail clients would turn into a link: the forms say so, and a name sent to the auth API directly is replaced
  • A one-time purchase is granted once it is paid. With a delayed payment method the checkout completes before the money arrives; the purchase now waits for checkout.session.async_payment_succeeded, and checkout.session.async_payment_failed grants nothing. Card payments behave as before
  • The newsletter export writes cells that start with =, +, - or @ as text, and the signup's source keeps only the labels the kit's forms send; anything else falls back to the default and the address is still recorded

v2.5.2

Choose a tag to compare

@michelecanini michelecanini released this 30 Oct 10:35

🔒 A public demo no longer shows its visitors each other's IP address. Everyone in a demo signs in to the same shared accounts, so Active sessions listed every visitor's session with its full address, and anyone could end the others' sessions. With DEMO_MODE on, your own session keeps its full address, the others show only the first half, and ending sessions is off. If you run a public demo of your product, update. A PATCH: git pull, npm install. Nothing to migrate and nothing to configure; outside the demo nothing changes.

Fixed

  • Active sessions on the demo: other visitors' addresses are cut to their first half on the server (203.0.•••.•••, the first two groups of an IPv6), so the full address never reaches the page; how long ago replaces the minute; a line on top says how many people are in the demo right now; End session and End all other sessions are off, and the two actions refuse on the server too
  • Two-factor confirmation on the demo answers like the other three 2FA actions. Setup never starts there, so nothing could be confirmed; now the action says so itself

Added

  • A line on the demo's sign-in page: the accounts are shared and reset every night, other visitors see only part of your IP address, with a link to the privacy policy

v2.5.1

Choose a tag to compare

@michelecanini michelecanini released this 28 Oct 16:39

🌱 npm run db:seed and npm run db:seed:demo work again. Since 2.3.3 both stopped with a usage message instead of seeding: two packages each installed a command called dotenv, and the one that answered did not know the option the scripts used. A PATCH: git pull, npm install. Nothing to migrate and nothing to configure. npx prisma db seed, the command of the first steps, was never affected.

Fixed

  • The two seed scripts load .env and .env.local through Node, as npm run check:deploy already does, instead of a dotenv command. A variable already set in the shell still wins over the files, so DATABASE_URL=... npm run db:seed:demo seeds the database you name
  • dotenv-cli is gone from the dependencies: nothing uses it any more, and it is what made the dotenv command ambiguous

v2.5.0

Choose a tag to compare

@michelecanini michelecanini released this 28 Oct 15:15

🛠️ An admin panel that keeps up as users grow, and a way to upgrade for whoever is on the free tier. Users and the waitlist get pages of their own, paginated, and a search of the users now goes past its first page. The account menu moves to the foot of the sidebar, with your plan and Upgrade plan. A MINOR: git pull, npm install. Nothing to migrate and nothing to configure.

Added

  • The users of the admin panel have a page of their own, /admin/users, with an entry in the sidebar, ten to a page and the page buttons centred as on the blog. Past seven pages the middle ones fold into dots, on the blog too: 1 … 4 5 6 … 50. On the overview they sat under the metrics and the chart, and every page of results took you back to the top of the overview. The overview keeps the numbers, the revenue and the waitlist, with a link to the users; an old /admin?page= or ?search= link lands on the same results
  • The waitlist has a page of its own too, /admin/waitlist, with every signup ten to a page and the export. The overview showed the latest eight and nothing past them; it keeps the confirmed count, as a fourth card next to the users, the subscriptions and the MRR
  • Upgrade plan in the account menu, for whoever is on the free tier, leading to the plans on the Billing page; it goes once they pay. Above it, your email and the plan you are on
  • Active sessions show the first five, this device and the four newest, with a button for the rest: an account signed in on many devices no longer makes Settings a long scroll
  • A thin bar at the top while a page loads, on the public pages and for a link that leaves for another site in the same tab, like a live demo. It shows after 120 ms, so a fast page opens without it, and goes when the next page arrives. The dashboard and the admin keep the dimmed overlay
  • The theme in the account menu: light, dark or system, next to the switch in the header, which stays. The two read the same choice
  • GEMINI.md, one line that imports AGENTS.md, so Gemini CLI reads the same rules as Claude Code, Cursor, GitHub Copilot and Codex
  • Your own code can be plain JavaScript, in Getting started: pages and components as .js or .jsx files next to the kit's TypeScript work as they are, because tsconfig.json has allowJs

Changed

  • The account menu at the foot of the sidebar, in the dashboard and the admin: your avatar and name, and a menu that opens upwards with your email and your plan, Settings, Billing, the theme and Log out, which was Sign out. On a phone, with no sidebar, the avatar stays top right. On the public pages a signed-in visitor gets the Dashboard button and the account menu top right
  • Settings, opened as a modal, keeps its title and the close button in a bar fixed at the top, and the rest scrolls under it
  • The admin is marked by its breadcrumbs: Admin in red, in place of the badge next to the logo, which a wide logo or a long product name pushed out of the sidebar
  • The icon in front of the breadcrumbs follows the section, the same one the sidebar highlights: the folder on Projects, the card on Billing, the gear on Settings; in the admin the shield on the overview, which the sidebar now shows too, and the person on Users. It was always the grid of the dashboard home
  • The changelog page is as wide as the docs, with the versions on the right: one entry per release, the version number alone, highlighted as you read; each release has its own anchor, like /changelog#v2-4-0. The latest release has a green dot
  • Dependencies: postcss-selector-parser 7.1.6 or later through an override, for a moderate advisory under @tailwindcss/typography that only runs at build time. The generated CSS is identical. The full audit, development included, is at zero

Fixed

  • A search in the admin users had a single page, however many people matched: the number of pages came from the rows on screen, not from the matches. They are counted now
  • Two buttons said something other than what they show to screen readers and voice control (WCAG 2.5.3): the avatar-only account button, now Open account menu after the initial, and the docs language switch, now English (Change language)
  • The grey text of the danger zones, in Settings and on a project, was below the 4.5:1 contrast on their red tint. It is darker there now
  • Previous and Next of a pagination, on the first and last page, are announced as unavailable instead of being hidden from screen readers. They look the same
  • Dev Login shows a spinner while it signs you in, like the other sign-in buttons
  • Someone removed from the Resend audience by hand can sign up to the newsletter again. Their address stayed confirmed in the database, so a new signup sent nothing. Now it sends a new confirmation, as for someone who unsubscribed from a Broadcast

v2.4.0

Choose a tag to compare

@michelecanini michelecanini released this 24 Oct 14:11

🧭 Breadcrumbs in the dashboard header, and your account behind the avatar, top right. The sidebar keeps only navigation; where you are and who you are move up into the header, where most apps keep them. This is a MINOR: git pull, npm install. Nothing to migrate, and the one new environment variable is optional.

Added

  • Breadcrumbs in the header of the dashboard and the admin, next to the button that folds the sidebar: Dashboard › Projects › Website, with the area's icon in front. They are built from the address, so a new page gets its crumb from a label in labels in its layout (src/app/(dashboard)/layout.tsx, src/app/(admin)/layout.tsx), without being listed anywhere else. A page with a name of its own, like a project, gives it with <BreadcrumbName name={...} />; until it does, the crumb is left out rather than shown as an id. The trail at the top of the project page moved up into the header
  • The account menu, top right, behind the avatar, on every screen size: Settings, Billing and Sign out, with your name and email at the top of it. They leave the top of the sidebar
  • Your product's name under the footer of the public pages, if you want it: large and faint, its lower edge cut by the page, your siteConfig.name. Off by default, so nothing changes until you set NEXT_PUBLIC_SHOW_FOOTER_WORDMARK="true", see Configuration. Decoration only, hidden from screen readers

Changed

  • The Admin Panel sits at the bottom of the sidebar, under a rule, apart from the entries you use every day, with Developer docs under it: the kit's manual on openstarterkit.dev, in a new tab, in the phone menu too. Only while developing and in a demo (DEMO_MODE), never in your production app, whose users would find setup instructions instead of help
  • "Demo" instead of "Sign in" when the link goes to the demo. With NEXT_PUBLIC_DEMO_URL set, the navbar link points at your demo, where no visitor has an account of their own, so it now says so. Without it nothing changes
  • "Pricing" in the footer opens /pricing, not the pricing section of the home page. The top menu still scrolls to the section. A link from every page is what tells search engines the pricing page matters, and a link to a section only counts for the home
  • No rule above the "Built with" badge at the bottom of the dashboard, so removing the badge no longer leaves an empty strip with a line over it
  • Dependencies: next and eslint-config-next 16.4.3, lucide-react 1.61, react-hook-form 7.91, dotenv 18.0.9, and fast-uri 3.1.9 under @hookform/resolvers, for four moderate advisories on URI parsing. Production dependencies audit at zero

Fixed

  • The Google and GitHub buttons show only when their keys are set. On a fresh clone they were always there, and a click ended on Better Auth's CLIENT_ID_AND_SECRET_REQUIRED: the error overlay in development, an error page in production. Now the login page and Settings show a provider only with both its keys, and src/auth.ts registers only those, the same way the magic link already hides without email. A provider you already connected stays in Settings, to be disconnected. One key set without the other still stops the boot, as before
  • Deleting the account of the last administrator no longer cancels their subscription first. The refusal came after the cancel at Stripe, so the account stayed and its subscription was gone. The last-admin check now runs before Stripe is touched

v2.3.7

Choose a tag to compare

@michelecanini michelecanini released this 20 Oct 14:36

🔐 Next.js 16.4.2, for the security advisories of October 14. One of them lets crafted requests tie up the CPU of any App Router app with a Server Action, and the kit has several: update now. The other two, remote code execution through use cache functions and through SVG image optimization, do not reach the kit as it ships (it has no use cache, and sharp was already at the fixed 0.35.5), but they reach an app that adds either. This is a PATCH: git pull, npm install. Nothing to migrate and nothing to configure.

Security

Changed

  • better-auth and @better-auth/prisma-adapter 1.7.12: cookie attributes aligned with RFC 6265bis, cookies cleared once a session expires, and OAuth callbacks through the OAuth proxy checked like the direct ones
  • Dependencies: react and react-dom 19.3.1, prisma, @prisma/client and @prisma/adapter-pg 7.10.1, react-hook-form 7.90, zod 4.6.7, lucide-react 1.60, @hookform/resolvers 5.9.2, vitest and @vitest/coverage-v8 5.0.5, @axe-core/playwright 4.14. The minimum versions in package.json move up with them, so a fresh install gets the fixed releases. Production dependencies audit at zero

Fixed

  • No band around the page loader in dark mode. On a large screen the strip behind the spinning logo came out a shade off the rest of the dimmed page; the loader now has a layer of its own

v2.3.6

Choose a tag to compare

@michelecanini michelecanini released this 17 Oct 09:59

⚡ The proxy stops reading the session on every request. It did so on public pages, link prefetches and crawler visits too, where nothing uses it, and on Vercel that was most of a small site's function time. Now it reads it only on sign-in, the dashboard, the admin and the billing routes. This is a PATCH: git pull, npm install. Nothing to migrate and nothing to configure.

Added

  • Images and videos in the docs. A Markdown image pointing into public/media/ shows on GitHub and on the site alike, with the Markdown title as its caption; an .mp4 gets player controls, and a file.dark.webp next to an image is used in dark mode. The rule is in AGENTS.md
  • The Quick start as a short looping clip, in the README and in Getting started: clone, install and the first page of the app, recorded on a fresh clone
  • Running the kit on any Node.js host, in Deployment: build and start as the Next.js self-hosting guide describes, and the one thing that does not come along off Vercel, the cron that resets a public demo

Changed

  • src/proxy.ts reads the session only on the routes in AUTH_ROUTES, ADMIN_ROUTES and PROTECTED_ROUTES. The redirects are the same, and a new test fails if a public page reads it again. If you added a private area outside /dashboard, it still belongs in PROTECTED_ROUTES, as the comment in the file says
  • The menu button takes over below 1280 px, so a tablet in landscape gets the menu instead of a row of links that ran into the edges. The menu stops at the bottom of the screen and scrolls, so a phone on its side reaches every item
  • The docs say what Vercel's free plan is for: the Hobby plan is for non-commercial projects, so an app that takes payments needs Vercel Pro or another host. In the README and in Deployment
  • Dependencies: next and eslint-config-next 16.4.0, the Radix packages to their current releases, lucide-react 1.59, resend 6.34.1, @playwright/test 1.64.1, dotenv 18.0.8, @types/node 26.6.5. Production dependencies audit at zero

Fixed

  • Someone who unsubscribed through a Broadcast can sign up again. The unsubscribe link in a Broadcast is Resend's: it marked the contact unsubscribed on Resend and left the database saying confirmed, so a new signup got nothing at all. The endpoint now asks Resend about an address it already has as confirmed, and sends a new confirmation when Resend has it unsubscribed; confirming brings the contact back on both sides. See Newsletter & waitlist
  • Opening a guide from the docs index no longer shrinks the page. From 1536 px up the public pages are 12% larger, and the guides were the only ones left out
  • Videos in public/ load. The proxy took /file.mp4 and /file.webm for pages and answered 404

Documentation

  • The API version of the Stripe webhook endpoint: the endpoint has its own, chosen when you create it, and the events follow that one, not the version in src/lib/stripe.ts. Pick the same one, and update the endpoint whenever the kit changes apiVersion. In Deployment and Billing

If you customised the proxy, the navbar or the newsletter

Expect conflicts in src/proxy.ts, src/components/landing/navbar.tsx, nav-links.tsx, mobile-menu.tsx, src/lib/email.ts and src/app/api/newsletter/route.ts: see Upgrading.

v2.3.5

Choose a tag to compare

@michelecanini michelecanini released this 10 Oct 14:03

📨 Bring your own email provider. Every email the kit sends now goes through one function, so moving from Resend to SMTP, Postmark or any other service means rewriting one file, and a new guide walks through two examples. Asked for in #48. This is a PATCH: git pull, npm install. Nothing to migrate and nothing to configure: Resend stays the default and works as before.

Added

  • sendEmail() and emailEnabled() in src/lib/email-transport.ts. Every email goes through the first, and every "is email set up?" asks the second instead of reading RESEND_API_KEY in nine places. Email shows Nodemailer over SMTP and Postmark, the three behaviours to keep when you swap, and a note on text messages
  • A one-line signup in the footer of every public page, feeding the same double opt-in list as the pricing waitlist, with footer as its source in the admin export. It stays off until you set WAITLIST_ENABLED="true", once your real privacy policy is live (the one that ships is a placeholder), and needs an email provider; WAITLIST_ENABLED, until now meaningful only on the kit's own site, is the gate for every form that collects addresses on its own. Disabled in demo mode. The line above the field is in footer.signup; to drop the form, delete its line in footer.tsx. See Newsletter & waitlist
  • Every code block in the docs and the blog has a header: the file name when the fence gives one, otherwise the language (Terminal, TypeScript, .env...), and the Copy button on the right

Changed

  • One loading state for every page change in the dashboard and the admin: the page dims as behind a dialog, with the logo turning in the middle, after 120 ms. Pages without a loading.tsx of their own no longer sit still while the next one loads, back and forward included
  • The account menu sits at the top of the sidebar, under the logo, in the dashboard and the admin, and opens downwards. Its items are unchanged
  • The landing hero: the headline is two lines of the same size, a little bolder than medium, the subtitle runs wider, and from 1280 px up the dashboard preview scales to the full content width. The preview follows the real sidebar, with the account menu under the logo, and its theme switch turns only the preview light or dark: a .light class now scopes the light theme inside a dark page, as .dark already did the other way round. A clone without a hero.$product.trust line shows nothing under the buttons
  • The top menu is as wide as the footer's content, and from 1536 px up the public pages grow by 12% as a whole, so on a wide monitor the content no longer fills barely half the screen. The dashboard and the admin are not affected
  • Dependencies: react-hook-form 7.89, vitest and @vitest/coverage-v8 5.0.3, @shikijs/rehype 4.5, @types/node 26.6, dotenv 18.0.5, lucide-react 1.50, pg 8.23.1

Fixed

  • Buttons and other clickable controls show the pointer cursor again. Tailwind 4 dropped the rule that gave it to them, so most of the app showed the arrow. One rule in globals.css puts it back for buttons, selects, checkboxes, radios, file inputs, summary and labels, never on a disabled control, and a cursor-* class still wins over it. The items of a Select use it too, like the dropdown menu's
  • A page change starts at the top again. From a scrolled page, the logo or a menu link could land halfway down the next one, often on a section: the smooth scrolling in globals.css animated the jump, and since Next.js 16 the router turns it off during navigation only when <html> carries data-scroll-behavior="smooth", which the root layout now sets. The section links keep scrolling smoothly

Security

  • sharp and source-map-js move to their fixed versions (two high advisories). sprintf-js has no fixed version: it reaches the kit only through argparse 1, which js-yaml 3 under gray-matter uses for its own command line and never while reading the docs. An override scoped to that chain moves it to argparse 2. Production dependencies audit at zero

If you customised the layouts, the landing, the loading pages or the emails

Expect conflicts in src/app/(dashboard)/layout.tsx, src/app/(admin)/layout.tsx, the loading.tsx files, src/lib/email.ts, src/components/blog/code-block.tsx, src/components/landing/hero.tsx, src/components/landing/footer.tsx and src/app/globals.css: see Upgrading.