Viewing latest docs.
Switch version: v3

Changelog

A history of changes to Petal Pro

4.5.2 - 2026-11-16

4.5.2 needs 4.5.1 underneath. On 4.5.0 or older, take 4.5.1 first, see the upgrade guide.

Security

  • Browser password sign-in is limited. The sign-in form had no limit at all, so only the speed of the password check slowed a script working through passwords. An account now gets ten tries per ten minutes, counted before the password is checked, and a correct password counted on the account starts the count again. An email with no account is counted the same way, so a refusal doesn’t show whether the account exists. A refused attempt goes back to the sign-in page with “Too many attempts. Please try again later.” This has been the case since 4.0.0. See the upgrade guide.
    • A count on an account could be turned against its owner, because anyone who knows an email could keep the count full. So a browser that has signed in to an account is counted on its own first, through a new cookie, _petal_pro_web_sign_in_device (encrypted, HttpOnly, one year). A stranger who uses up an account’s count can then only block browsers that have never signed in to it. The cookie grants nothing else and stops counting when the account’s password changes. A sign-in from a trusted browser leaves the account’s count as it is, so other browsers stay refused until the window ends. List it in your cookie policy. A password reset also starts the account’s count again. See Trusted Browsers.
    • With CLIENT_IP_HEADER or TRUSTED_PROXY_HOPS set, one address also gets 100 failed tries per ten minutes across all accounts. Without either there is no limit per address, because every visitor would share it, and the app logs one warning when it sees proxy headers with neither set.
    • Upgrade: take lib/petal_pro_web/controllers/user_session_controller.ex and lib/petal_pro_web/live/auth/user_reset_password_live.ex. Each runs without the other. The reset only starts the API count again with the new API session_controller.ex below. A test suite that posts more than ten wrong passwords for one account inside ten minutes now sees the refusal.
  • Limits that protect an account are counted on the account, not on the text typed. The pin, API sign-in and password reset limits were keyed on the email as text. Postgres treats some spellings as the same email that String.downcase/1 leaves different. Each such spelling found the same account and got a fresh count, so on common database setups the 4.5.1 pin limit could be multiplied. Every account limit is now keyed on the user id found by the same lookup the sign-in uses. The password reset limit was keyed on the raw text, so capitals alone got round it. See Rate Limiting.
    • Upgrade: take lib/petal_pro_web/live/auth/passwordless_auth_live.ex, lib/petal_pro_api/controllers/session_controller.ex and lib/petal_pro_web/live/auth/user_forgot_password_live.ex. Each works on its own. If you keep your own copy of one, key its limit on user.id after looking the user up, not on the email. Step 3 of the upgrade guide shows the change for each.
  • An admin with a pending second factor could impersonate a user. Signing in puts the user in the session before the two-factor step, and POST /auth/impersonate only checked for an admin. Impersonating and switching back gave a full admin session without the code ever being asked for, so an admin’s password alone was enough. The controller now sends a pending sign-in to finish first. Impersonation is on by default.
    • Upgrade: take lib/petal_pro_web/controllers/user_impersonation_controller.ex. If you have routes of your own behind :require_admin_user without :authenticated, add :authenticated to them: they have the same hole.
  • Confirmation emails can’t be resent without limit. The resend form and POST /api/send-instructions had no limit, so anyone could send confirmation emails to an unconfirmed account’s address over and over. Both now share three per ten minutes for an account. The API answers a refusal with a 429.
    • Upgrade: take lib/petal_pro_web/live/auth/user_confirmation_instructions_live.ex and lib/petal_pro_api/controllers/registration_controller.ex.

Changed

  • Per-address limits count an IPv6 client by its /64. One subscriber usually holds a whole /64, so counting each address gave them a fresh budget on every request. Clients that arrive as IPv4-mapped or NAT64 addresses are counted as the IPv4 address they carry. ClientIp.get/2 is unchanged, so last_signed_in_ip and the audit log still record the full address. Take lib/petal_pro_web/client_ip.ex.
  • The passkey sign-in limit only applies when the client address is configured. Behind a proxy with neither setting made it was one count for the whole app, which a single caller could hold shut for everyone. A passkey can’t be guessed, so nothing is lost. Take lib/petal_pro_web/controllers/user_passkey_controller.ex, and test/petal_pro_web/controllers/user_passkey_controller_test.exs with it: the 4.5.1 “eleventh attempt” test fails against the new controller.
  • A malformed sign-in form post is an ordinary failure. A body with no email or password, or with a list where text should be, used to be a 500.

4.5.1 - 2026-11-14

Security

  • A passwordless sign-in pin could be guessed without limit. Asking for a pin was limited to three per ten minutes, but “Resend” was not: it issued a new pin with a fresh set of attempts every time it was called, so a script could alternate three guesses and a resend indefinitely. The same email in different capitals also got a limit each. Resend now goes through the same limit as the first request, and the limit is per account whatever the capitals. Guesses sent in parallel could also all pass the attempts check before any of them was counted; each guess now takes its attempt in one database statement before the pin is compared. With the fix an account gets nine guesses per ten-minute window on each machine, and up to twice that for a caller who straddles the end of a window. This has been the case since passwordless sign-in shipped. 4.5.2 closes a way round that limit: on some databases the same account could be reached under another spelling of its email, each with a count of its own, and on 4.5.2 the count is kept on the account. See the upgrade guide.
    • Upgrade: take lib/petal_pro/accounts/user_pin.ex and lib/petal_pro_web/live/auth/passwordless_auth_live.ex together. UserPin.check_pin/3 replaces validate_pin/3 followed by failed_attempt/1. Both old functions still work and are deprecated: validate_pin/3 now counts the attempt itself and failed_attempt/1 does nothing, so a LiveView you customised keeps its three guesses per pin and gets two deprecation warnings until you switch, which fail mix compile --warnings-as-errors. That is a stopgap, not the fix: the unlimited resend is in the LiveView. If you keep your own, make the six changes in step 3 of the upgrade guide: the main ones route its resend handler through send_pin/2, so a resend meets the same limit as the first request, and lower-case the email in the limit key. Until then “Resend” still issues pins without limit in your app. Take test/petal_pro/user_pin_test.exs with the new user_pin.ex too, because the 4.5.0 copy has a test that fails against it.
  • Two-factor codes are limited to five tries per five minutes. The TOTP step had no limit, so someone who already had a user’s password could work through six-digit codes until one matched. The limit is per user, counts every submit and needs no configuration. A correct code starts the count again, and a user who mistypes five times in a row waits out the window. Backup codes go through the same form and the same limit.
  • API sign-in is limited per account as well as per address. Ten tries per ten minutes for one email, whatever addresses they come from. A sign-in that works starts the count again, so a client that signs in often is not refused for its own successes. The per-address limit alone does nothing against a caller with many addresses (an IPv6 range, a botnet), who meets a fresh budget each time. 4.5.2 closes a way round this limit: on some databases the same account could be reached under another spelling of its email, each with a count of its own, and on 4.5.2 the count is kept on the account.

Fixed

  • The API and passkey rate limits count the client, not the proxy. The API sign-in (5 a minute), API registration (3 an hour) and passkey sign-in (10 a minute) limits were keyed on conn.remote_ip. Behind Fly, Render, nginx or any other proxy that is the proxy’s address, so every visitor shared one budget: three API registrations an hour for the whole app, and one caller could use any of the three up for everyone. They now use the address PetalProWeb.ClientIp resolves, the one last_signed_in_ip has recorded since 4.5.0, through the new PetalProWeb.ClientIp.rate_limit_key/2. This has been the case since the limits were added (4.0.0 for the API, 4.1.0 for passkeys). See the upgrade guide.
    • Upgrade: this only takes effect once the app knows which address is the client’s. If you have not set CLIENT_IP_HEADER or TRUSTED_PROXY_HOPS, nothing changes and visitors behind your proxy still share a budget. On Fly, add CLIENT_IP_HEADER = "fly-client-ip" to the [env] block of fly.toml (the same step as in the 4.5.0 notes). Behind Cloudflare use cf-connecting-ip; behind one nginx or Caddy use TRUSTED_PROXY_HOPS=1. See “Client IP Behind a Proxy” in DEPLOYMENT.md.
    • Upgrade: if you copied one of these rate_limit plugs, swap its conn.remote_ip line for PetalProWeb.ClientIp.rate_limit_key(conn, "<prefix>").
  • The passkey rate limit no longer counts page views, and it answers when it refuses. The sign-in page asks for a passkey challenge every time it loads, and each one counted against the same ten a minute as real sign-in attempts, so ordinary traffic could use the budget up. Past the limit the request was stopped without a response, which is a 500. Only sign-in attempts count now, and a refused one goes back to the sign-in page with “Too many attempts”.

4.5.0 - 2026-11-11

Security

  • UserAuth.get_ip/1 no longer trusts the client-written x-forwarded-for. It used to take the first x-forwarded-for entry, which the client controls. The new PetalProWeb.ClientIp returns the connection peer unless config names a trusted proxy. The chosen value is parsed strictly, and anything malformed falls back to the peer. last_signed_in_ip and impersonation audit entries now record a real address, and an x-forwarded-for entry over 255 characters, or one that isn’t valid UTF-8, can no longer 500 a sign-in after the session token was minted. See the upgrade guide.
    • Upgrade: on Fly, add CLIENT_IP_HEADER = "fly-client-ip" to the [env] block in fly.toml, or sign-ins will record Fly’s proxy address.
    • Upgrade: elsewhere, set CLIENT_IP_HEADER to your proxy’s header (e.g. cf-connecting-ip) or set TRUSTED_PROXY_HOPS (how many trailing x-forwarded-for entries your proxies append, default 0). TRUSTED_PROXY_HOPS=2 also works on Fly, and 1 works behind a single nginx. It must be a whole number, or the release fails to boot.
    • Behaviour change: for a peer that isn’t an IP, get_ip/1 now returns nil where it used to raise.
  • Production forces HTTPS. The new PetalProWeb.ForceSSLPlug wraps Plug.SSL with runtime config from config/runtime.exs (validated once at boot from PetalPro.Application). In prod it trusts x-forwarded-proto and fly-forwarded-proto (rewrite_on), redirects plain http (301 for GET and HEAD, 307 for other methods) and sends a one-year HSTS header on https responses. Because a proxied https request now counts as https, Plug marks the cookies it writes, including the session and remember-me cookies, Secure. HSTS itself sets no cookie flags. The session cookie options also set same_site: "Lax" and http_only: true outright. Behind Fly, Render, Railway and similar hosts, cookies no longer go out without Secure, and Firefox and Safari now treat the session cookie as Lax instead of sending it on every cross-site request. See the HTTPS section in DEPLOYMENT.md.
    • Upgrade: the new FORCE_SSL env var is on by default in prod (on when unset, true or 1, off for any other value). Behind a proxy that sends no forwarded-proto header, every request redirects to itself unless you set FORCE_SSL=false. Keep it on if you terminate TLS in the app.
    • Upgrade: an HTTP health check (for example one in fly.toml) needs an X-Forwarded-Proto: https header or a path exclusion in config :petal_pro, :force_ssl of the form exclude: [hosts: ["localhost", "127.0.0.1"], paths: ["/healthz"]] (keep the hosts entry, since any exclude replaces Plug.SSL’s default), or it gets a 301. Default TCP checks are unaffected.
  • Sentry request context. The new PetalProWeb.SentryContextPlug adds request context to Sentry events, using the same client IP as PetalProWeb.ClientIp. It masks sign-in secrets: the TOTP code, PIN, sign_in_token, passkey assertions, OAuth code and state, and confirm and reset tokens. It does nothing until SENTRY_DSN is set. If you care about what you send to Sentry, note that events now include request context, including the client IP.

Changed

  • Settings screens move to a two-pane layout. At lg and up the settings nav sits in its own pane, with a pill and primary-coloured text and icon on the active item, aria-current on the active link and a real nav landmark. The content card has new chrome. Below lg the nav becomes a horizontal scroll strip with edge fades, and the new ScrollStripHook keeps the active item centred. This covers every user, org and billing settings screen, and none of them need code changes on your side. page_header/1 and box/1 are unchanged. See the upgrade guide.
    • Upgrade: if you customised sidebar_tabs_container/1 or sidebar_menu_item/1 in page_components.ex, merge those by hand.
    • New pieces: assets/js/hooks/scroll-strip-hook.js (registered as ScrollStripHook in hooks/index.js), and scrollbar-none and scroll-strip-fade @utility blocks in app.css.
  • Every settings screen gets a header and its own page title. Each screen now opens with the new settings_header/1, which has a one-line description, and sets its own page_title, so browser tabs read “Email - Petal” or “Password - Petal” where stock used to show a literal “Settings” (profile, Your Data) or just the app name. Nav labels are now nouns: “Edit profile” becomes “Profile”, “Change email” becomes “Email”, “Edit password” becomes “Password”, “Edit notifications” becomes “Notifications” and the org “Edit” becomes “General”. This only changes copy, but tests that assert the old labels or headings need updating. Every string goes through gettext, so translations need the new msgids.
  • Settings forms share one layout. Single text, email and password fields are capped at max-w-md, so the profile, email, password and org forms no longer stretch inputs to about 900px. Every editable form ends in a border-t action bar with the primary button on the right. The password form keeps “Forgot your password?” on the left. Only classes and markup changed. Handlers, params and validations are untouched.
  • The billing screen is rebuilt around a plan card. The card shows the product, a Trial badge, the price, and a dl with the last invoice, the upcoming invoice and the next charge. Cancelling now goes through a destructive alert_dialog (“Keep my subscription” / “Cancel anyway”) that shows plan, price and next charge before you confirm. It replaces the dropdown and the browser data-confirm. With no subscription you get an <.empty> state with a single View plans button, and a provider failure shows a danger <.alert>. Event names, routes and params are unchanged, and cancel_subscription still drives the cancel. Tests that relied on data-confirm or the old spinner markup need updating.
  • Account deletion on Your Data becomes a danger-zone panel. The panel has a danger hairline, a warning icon chip and a list of consequences. The inline two-stage confirm is replaced by a destructive alert_dialog (“Delete my account” / “Keep my account”), and status notices are now <.alert>s. The GDPR flow and confirm_delete are unchanged. The show_delete_confirm and cancel_delete events that drove the old inline confirm are removed, so any code or tests that send them will break. Org deletion still has no UI, by design.
  • Notification preferences are switches. Each preference renders as <.field type="switch"> in place of a checkbox, and still sends the same toggle_preference event and payload. Channels locked by allow_disable_in_app / allow_disable_email show as disabled, always-on switches. Tests that select checkbox inputs may need updating.
  • TOTP setup is clearer. Setup is two numbered step cards (a framed QR code or a select-all mono secret), and the code field is now petal_components’ input_otp (6 segments, autocomplete="one-time-code"), so SMS and password-manager autofill work. It still posts user_totp[code]. Once 2FA is on, the screen shows a success-* status row, and backup codes are select-all mono chips. Disabling 2FA and regenerating backup codes move from data-confirm to destructive alert_dialogs. Form params are unchanged. Tests that assert “2FA Enabled” (now “2FA enabled”) or data-confirm selectors need updating. The input_otp wrapper takes the id, and the real input is id <> "-input" (totp-code-input in stock Pro).
  • The passkeys screen matches the rest of settings. Its six inner panels move to the gray-400 alpha ladder and --pc-radius. This also fixes two dark-mode contrast problems: the gray-800 key-icon circle and the gray-800/50 info wash. Only classes changed.
  • The last three hand-rolled modals now use <.modal> from petal_components. The onboarding LiveView and both email-link unsubscribe pages now render petal_components’ <.modal hide_header> in place of their own hand-rolled modal markup, and pick up the library’s dark mode and focus handling. If you customised the onboarding or unsubscribe templates, re-port them onto <.modal hide_header>.
  • Flash messages are toasts. PetalProWeb.Flash.flash_group/1 renders petal_components’ <.toast_group> with its put_flash bridge, so every put_flash(:info | :success | :warning | :error) shows as a stacked, swipe-to-dismiss toast with a progress bar. Call sites don’t change. The 10 second timer stays, and a new position attr sets where toasts appear. LiveViews can call PetalComponents.Toast.send_toast/3 for richer toasts. Only those four flash kinds reach the toast, so app-private flash keys stay out. The disconnected banner is unchanged. It can overlap a toast bottom-right, so use position="bottom-left" if that bothers you.
  • Empty states use <.empty>. Every hand-rolled empty state now has a title, a one-sentence description and a single CTA where a create action exists. Covered: the DataTable fallback on all admin indexes (with “Clear filters” when filtered), the notifications page and bell, admin chat history, admin user and org show memberships, the orgs list, org team invitations, passkeys, org invitations, the blog index, the admin dashboard chart panels, and the admin file picker, which had no empty state before. DataTable keeps empty_icon / empty_title / empty_description. The titles keep their wording, so tests that match the copy still pass. Tests that select the old empty-state markup (a bare <p>, a dashed box, an icon circle) need updating to the .pc-empty structure.
  • Status pills use <.status_badge> and roles use <.role_badge>. <.status_badge status={@status}> is a <.badge dot> rendered through the new PetalProWeb.StatusBadge (imported by use PetalProComponents). One status-to-colour map now covers subscriptions, the billing card, changelog draft/published/archived, user state, dashboard recently-joined and invitation state. Admin user show gains a Status row, the org team table gains a Status column, and every row in Admin > Users carries a role chip.
    • Removed helpers: ChangelogHelpers.status_badge_class/1 is gone, so call <.status_badge> in its place. The private role_label / role_badge_color helpers in OrgsLive and AdminOrgLive.Show are gone too.
    • Colour changes: trialing on the admin subscriptions table and the admin role both go from warning to info. On the dashboard, unconfirmed becomes a warning chip and not-onboarded a gray chip (both were a red X). To restore the old colours, edit status_color/1 or role_color/1 in PetalProWeb.StatusBadge.
  • petal_components 4.6.0 to 4.18.0. The minimum is now ~> 4.18, and phoenix 1.8.16, phoenix_html 4.4.0 and phoenix_pubsub 2.4.1 come along. The update also moves Pro’s production web server, bandit 1.12 to 1.14 and thousand_island 1.5 to 1.6, plus smaller bumps to lazy_html, plug_crypto, elixir_make and fine. See the upgrade guide.
    • Upgrade: run mix deps.update petal_components after taking this release.
    • Upgrade: Layouts.empty/1 is renamed to Layouts.blank/1, because the library now ships <.empty>, so calls to Layouts.empty break.
    • Upgrade: the library now exports names Pro used to define (combo_box from 4.12, data_table from 4.13, plus the four components under Removed). PetalProComponents imports the free modules, drops the Pro copies it deletes, and keeps Pro’s own data_table with import PetalComponents.DataTable, except: [data_table: 1]. If you edited that file, match the 4.5.0 import list in the upgrade guide or the build fails with “call is ambiguous”.
    • What you pick up along the way:
      • 4.6.1/4.6.2: dark and ghost surfaces follow the remapped gray, so sign-in inputs and dropdown triggers match Pro’s slate panels.
      • 4.11: hide_header on <.modal>.
      • 4.12: free combo_box.
      • 4.13: free data_table.
      • 4.15: <.empty>, a :footer slot on modal, and dropdown auto-flip (a dropdown panel opens upward when there’s no room below).
      • 4.16: Typeset font tokens (--pc-font-heading, --pc-font-body, --pc-font-mono), so one @theme block can retype the whole UI, plus lining numerals on counters, a single error ring on input_group, and a slide_over that falls back instead of crashing on an unknown origin.
      • 4.16.1: shrink-0 on the colour-scheme switch and icon triggers.
      • 4.17.1: multi-select combo_box posts values in pick order.
      • 4.18.0: the toast hook no longer logs a console error on controller-rendered pages, and <.alert> gains dismiss_label.
      • New components such as empty, slider, filters, kbd and qr_code are available.
  • Flop 0.26.3 to 0.27.0. This supports the new DataTable FlopBridge (below). Pro’s two settings modules were updated for it.
    • Upgrade: mix.exs still allows ~> 0.20, so the bump comes from mix.lock. Flop 0.27.0 requires :ecto_type on every join field and custom field, so your own Flop.Schema derivations with join_fields or custom_fields fail until they’re annotated.
    • Behaviour change: 0.27 caps filters per request at 20 by default (max_filters).

Removed

  • Four Pro components retire in favour of their petal_components versions. color_scheme_switch, language_select, local_time and social_button are now provided by the free library, so the Pro copies are deleted. PetalProComponents imports the free modules, so use PetalProComponents still provides every name. The ColorSchemeHook and LocalTimeHook JS hooks are deleted. See the upgrade guide.
    • Upgrade: delete the four old files in lib/petal_pro_web/components/pro_components/ (color_scheme_switch.ex, language_select.ex, local_time.ex, social_button.ex), and assets/js/hooks/color-scheme-hook.js and local-time-hook.js along with their index.js entries. Fully qualified calls such as PetalProWeb.ColorSchemeSwitch.color_scheme_switch break, so use the plain tags.
    • color_scheme_switch: now requires an id. <PetalProWeb.ColorSchemeSwitch.color_scheme_switch_js /> in the head becomes <.color_scheme_script />. It uses the same localStorage.scheme key, so saved preferences survive, and it adds live system-preference tracking and cross-tab sync.
    • local_time: now requires an id. for= becomes at=. luxon preset= names and format= token strings are replaced by format="datetime" (the default, roughly the old DATETIME_MED), "date", "time", "relative" or a map of Intl.DateTimeFormat options. locale now defaults to the browser’s own, where it used to default to "en". luxon is now orphaned in package.json and can be dropped.
    • social_button: logo= becomes provider= and link_type="a" to= becomes href= (navigate= and patch= cover the live link types). The twitter bird is now x. variant now defaults to "outline", where it used to default to "solid".
    • language_select: a straight swap.
    • If you have a customised fork of the old Pro copies, keep it and skip this part.
  • Tom Select. PetalProWeb.ComboBox, the ComboBoxHook, assets/css/combo-box.css (about 12 KB) and the tom-select npm package are deleted. The two admin membership pickers and the petal.gen.live / petal.gen.html generators now render <.field type="combobox"> from petal_components, which carries its value in a hidden native select. Selections now survive a LiveSocket reconnect through LiveView’s own form recovery (customer issue #306). A new tom_select_retired_test.exs fails if any remnant is left. See the upgrade guide.
    • Upgrade: <.combo_box label= help_text= /> becomes <.field type="combobox" label= help_text= />. tom_select_plugins (its remove_button plugin) becomes clearable, which is off by default where the old remove button was on, and remove_button_title becomes remove_label. multiple, create, max_items, placeholder, disabled, required, remote_options_event_name and remote_options_target keep their names. tom_select_options and tom_select_options_global_variable have no equivalent.
    • Behaviour change: a disabled single-select combobox posts nothing for its field, because there is no longer a hidden "" input.
    • Cleanup: delete assets/js/hooks/combo-box-hook.js and its ComboBoxHook line in hooks/index.js, assets/css/combo-box.css and its @import in app.css, and lib/petal_pro_web/components/pro_components/combo_box.ex with its import PetalProWeb.ComboBox in PetalProComponents (replaced by import PetalComponents.ComboBox). Then run npm uninstall tom-select --prefix assets.
    • If you have a forked wrapper, keep it and skip this part.

Added

  • Layout shell options. sidebar_layout gains a mobile_top_right slot. Menu items take related_pages, matched by one shared function, PetalProWeb.SidebarMenu.menu_item_active?/2, and the active link carries aria-current. In stock config :subscribe relates :subscribed and :billing, so Subscribe stays highlighted on billing pages. sidebar_user_profile gains a top_nav variant and an id attr, so the user menu can live in a top bar.
    • Upgrade: matching is explicit (no prefix match), so add related_pages for any nested page that should light up an item.
    • Upgrade: the colour-scheme switches now have fixed ids (in 4.4.0 each render got a random UUID): sidebar-user-profile-color-scheme in the sidebar user dropdown (prefixed by the new id attr, default sidebar-user-profile), navbar-color-scheme / navbar-color-scheme-mobile in the stacked layout and public-navbar-color-scheme on public pages.
  • DataTable FlopBridge. PetalPro.DataTable.FlopBridge connects Flop queries to petal_components’ free data_table, and a differential test gate checks 986 cases against the library’s in-memory engine. No admin screen uses it yet, so nothing visible changes. It lays the groundwork for moving admin screens to the free data_table later.
  • A third collision-guard test. It compiles the real use PetalProWeb, :html import scope to catch name clashes between Pro and petal_components.
  • Generator CI job. Every petal.gen.* generator runs on every push and its output has to compile, so generator drift shows up in CI.

Fixed

  • The billing screen no longer crashes at a month boundary. The meter summary guards compared DateTime structs with >, which compares them structurally, so a valid Aug 31 to Sep 1 window failed with FunctionClauseError. That hit metered subscriptions in the first days of any month whose billing period started the month before. The check now uses DateTime.compare/2 (or an integer compare for Unix timestamps). An inverted range now raises a clear ArgumentError.
  • The failed billing state no longer shows “No active subscriptions” under the error. A provider failure now renders only the danger <.alert>.
  • Semantic colour utilities always render their real colour. The semantic aliases in colors.css (danger, success and the rest) used @theme inline. Tailwind v4 tree-shakes each stop separately, so a semantic stop went unresolved unless the matching literal palette stop happened to be used somewhere, and utilities like text-danger-400 silently fell back to inherited gray. The alias block now uses plain @theme. If you edited assets/css/colors.css, make the same one-line change on your alias block.
  • The unsubscribe pages are clickable again. Under Tailwind v4 the gray overlay on both email-link unsubscribe pages painted over the confirmation panel and blocked clicks. The move to <.modal> (above) replaces that hand-rolled markup.
  • Sidebar menu items with the same label no longer produce duplicate HTML ids. Ids now derive from :name, falling back to a slug of the label. This applies to menu_item_<name>_anchor and dropdown_<name> / dropdown_<name>_button. It fixes invalid markup and broken id-based test selectors when menus reuse a label, such as “Settings” in both the org and user groups (customer issue #298). Stock ids change wherever a name differs from its label: menu_item_organizations_anchor is now menu_item_orgs_anchor, and in the admin sidebar menu_item_users_anchor is now menu_item_admin_users_anchor and menu_item_live_dashboard_anchor is now menu_item_server_anchor. Custom JS, CSS or tests that target the old label-derived ids need updating.
  • Combo box selections survive a LiveSocket reconnect (customer issue #306). See the Tom Select removal above.
  • Mobile layouts clear the iOS browser bar. sidebar_layout and stacked_layout use h-dvh in place of h-screen, so the sidebar’s profile row and the last line of a page no longer sit under the browser bar. <.layout type="stacked"> also renders the caller’s top_right / top_right_mobile slots, which it used to drop.
  • mix quality passes end to end on a fresh clone again. A too-deep function in the passkey settings LiveView is flattened for credo --strict. The S3 module now signs download and delete requests with the full SigV4 config, which clears 11 dialyzer warnings with no new ignore entries.
  • Flash messages on controller-rendered pages no longer log a console error. A flash on a page rendered by a controller, not a LiveView, used to log “unable to push hook event. LiveView not connected” in the browser console, because the toast hook tried to talk to a LiveView that wasn’t there. Fixed upstream in petal_components 4.18.0, which this release requires.
  • The Stripe logo on the landing page draws in full. A doubled minus sign in its SVG path data stopped the browser parsing partway through, so the “p” lost its counter, the “e” never drew and every visit logged an SVG path error in the console.

4.4.0 - 2026-07-17

Changed

  • Adopted petal_components v4.6. aurora and border_beam used to be Petal Pro components. They are now part of the free petal_components library, rebuilt with glow, multiple beams, and spring easing, so Pro deletes its own copies and consumes the free ones like every other component. The dependency minimum is now ~> 4.6. Take Pro 4.4.0 before you run mix deps.update petal_components: bump petal_components first on an older Pro and the build fails with function border_beam/1 imported from both PetalProWeb.BorderBeam and PetalComponents.BorderBeam, call is ambiguous, because both libraries now export it. aurora is the same problem but quieter, since Pro never calls it itself. If you customised either component a handful of attributes were renamed. See the upgrade guide for the rename tables and, if your membership has lapsed, a complete manual fix that needs no repo access.
  • Ported the sign-in card to the free border_beam. auth_layout now uses the free component (gradient_color_start becomes color_from, gradient_color_end becomes color_to, animation_duration becomes duration). The free beam styles its own panel, so the card’s background, border and radius classes came out, and the corner radius now follows your --pc-radius theme token. Dark mode picks up the library’s material in place of the old translucent blur.

Removed

  • floating_div and its @floating-ui/dom npm dependency. It had no call sites left in Pro. Reach for the free popover in top-layer mode (<.popover top_layer>) instead, which covers the same case of a panel escaping a clipped container. A <.floating_div> in your own code raises a compile error on upgrade; the upgrade guide has the swap.

Added

  • Reserved-namespace guard test. test/petal_pro_web/components/petal_components_collision_test.exs walks both libraries at runtime and fails if any Pro component defines a name that use PetalComponents also exports. This is what stops the ambiguous-import bug from ever coming back, and it drops straight into your own test suite.
  • Excluded the petal_components showcase from the Tailwind scan. assets/css/app.css gains a @source not line for the dependency’s showcase example modules, so their markup stops pulling extra classes into your CSS build.

4.3.0 - 2026-06-24

Added

  • Private S3 buckets. Set private: true in your :s3 config and uploads stay out of public view. consume_uploaded_entries/2 stores just the object key, and PetalPro.FileUploads.download_url/1 returns a short-lived presigned GET URL when you display the file. It is a no-op for public buckets and other providers, so you can call it unconditionally in your templates.
  • Cloudflare R2 and Fly Tigris support. Point the new endpoint config at R2, Tigris, or any S3-compatible service and uploads, downloads, and deletes all run through the same presigned path. Both ride on the existing S3 provider.
  • File deletion across providers. Every upload provider now implements delete_file/1, and a user’s old avatar is removed from storage automatically when they replace or clear it.
  • SAML SSO recipe. A new /recipes:add-saml-sso walkthrough for wiring up enterprise identity providers (Okta, Microsoft Entra, Google Workspace), with the security prerequisites spelled out.

4.2.0 - 2026-06-08

Changed

  • Upgraded to Petal Components v4. Petal Components dropped Alpine.js (every component is now Phoenix.LiveView.JS only) and ships its own JS. assets/js/app.js now imports the petal_components bundle and merges its hooks into the LiveSocket - these power the password / copyable / clearable inputs, the accordion, and the Chat components. Alpine.js stays for Petal Pro’s own components (sidebar persistence etc.), so nothing else changes for you. The js_lib attribute was removed from <.dropdown>, <.accordion>, and the menu components and now raises if passed - if you’ve customised a call site that passes js_lib, drop it. See the Petal Components v4 upgrade guide.

4.1.0 - 2026-05-21

Added

  • WebAuthn passkey authentication - register up to 5 passkeys (Face ID, Touch ID, hardware keys) from your security settings. Two modes: primary auth (passwordless sign-in) and second factor (2FA on top of password). Includes cloned authenticator detection via sign count validation and a guard against passkey 2FA bypass in require_authenticated_user/2
  • Persistent admin chat history - AI admin chat conversations are now stored in the DB. They survive reloads and restarts, and the sidebar lists recent conversations so you can pick up where you left off
  • mix quality now runs credo --strict and dialyzer - fresh clones pass both out of the box. Existing projects will need to clean up any strict credo violations and get dialyzer running

Fixed

  • Passkey sign-in session establishment before redirect
  • Cloned authenticator detection via sign count validation
  • Passkey 2FA bypass guard in require_authenticated_user/2

4.0.0 - 2026-05-04

Added

  • GDPR compliance — “Your Data” settings page (/app/users/your-data) lets users download all personal data as JSON and submit account deletion requests with soft-delete, anonymization cascade, and Oban background processing
  • Per-type notification preferences — users can toggle in-app and email channels independently per notification type; security-critical notifications (e.g. password changes) are forced-on and cannot be disabled
  • Notifications.notify/3 entry point — single dispatch function that checks per-user, per-type preferences before sending in-app or email notifications
  • Welcome notification on registration and password change alert on password update
  • Admin MCP server — exposes admin tools to external AI clients (Claude Code, Claude Desktop) via JSON-RPC 2.0 at POST /api/mcp with bearer token auth; set MCP_ADMIN_TOKEN env var
  • AI cost tracking — Req plugin that automatically logs every AI API call with token counts, costs, and timing to the ai_call_logs table
  • Admin chat tools — ManageUser (suspend/unsuspend/delete/restore/promote), ListOrgs, ManageOrg (rename/delete/members), and GetAiCallStats
  • Changelog MCP tools — list_changelog_updates, manage_changelog, and create_changelog_update for AI admin chat and external MCP clients
  • In-app feedback system — users can submit feedback from any page; admin dashboard for reviewing and managing submissions
  • Sentry error monitoring — auto-activates when SENTRY_DSN env var is set; no code changes required
  • Hammer-based rate limiting — applied to auth endpoints via plugs
  • Resend email adapter — set RESEND_API_KEY to use Resend for transactional email via Swoosh
  • Production Dockerfile — ready-to-use containerized deployment
  • Generic JS hooks collection — infinite scroll, scroll to bottom, scroll to hash, select all, share
  • Email component enhancements — configurable gap, gray button variant, and callout boxes
  • Dev scripts — server.sh, reset_db.sh, kill_db.sh for common development tasks
  • Lightweight page view analytics — bot filtering and daily aggregation
  • Daily Slack digest worker — activity summaries via Oban cron
  • Slow query telemetry logging — configurable threshold for dev environment
  • Interactive DB schema visualizer — dev page with Mermaid ER diagrams (pan/zoom), domain-grouped tables, column details with PK/FK indicators
  • Hierarchical route tree — collapsible tree view mirroring URL path structure with verb badges and click-to-copy helpers
  • 22 AI-powered recipe commands (.claude/commands/recipes/) — Claude Code slash commands for common customizations: auth, billing, feature removal, integrations, structural changes
  • Claude Code sub-agents — schema-architect, test-runner, elixir-reviewer, heex-reviewer, ui-ux-reviewer
  • Claude Code skills and commands — CI, commit, review, changelog, scaffolding workflows
  • COMPONENTS.md — reference document cataloging all available components and JS hooks
  • CLAUDE.md project instructions — scoped per directory for in-repo AI context

Updated

  • Jido AI for admin chat — replaced LangChain with native Jido.Action modules under PetalPro.AI.AdminChat.Actions.*, registered in ActionRegistry and shared by both the chat LiveView and the MCP server
  • Req for all HTTP calls — replaced HTTPoison and Tesla throughout
  • Sidebar-only layout — converted to sidebar-only; no desktop header; integrated user profile and notification badge
  • Styler upgraded from 0.11 to 1.11 — run mix format after upgrading
  • Changelog context — restructured ChangelogUpdates → Changelog with proper schema naming (Update, Like, Read), Flop DataTable with pagination/sorting/filtering on admin index, shared ChangelogHelpers module, comprehensive test coverage, and SEO meta descriptions on public pages
  • Modularized seed system — split into production and development modules
  • Fly.io deploy — now triggers on push to main
  • NPM packages updated — including ESbuild, with updated esbuild.js
  • Sidebar collapse button — redesigned as flush edge tab with directional chevrons; deferred transitions prevent flash on load
  • Updated deps — phoenix_live_view 1.1.27, petal_components 3.0.2, jido 2.1, sentry 12.0.3, swoosh 1.23.1

Fixed

  • Wallaby test race condition in signup flow

3.0.0 - 2025-07-22

  • Upgrades Petal Pro to Tailwind 4!
  • New Pro components - Aurora and BorderBeam
  • Adds support for Stripe metered usage
  • Replaces Admin Jobs with Oban Web
  • Adds TailwindFormatter
  • Port is configurable for the test environment
  • Updated: Adds mix assets.build
  • Updated: Combobox will warn if :tom_select_options_global_variable includes load handler and :remote_options_event_name is set
  • Fixed: SubscribeController redirects and shows Stripe error
  • Fixed: Authenticated views no longer auto-subscribe to user notifications
  • Fixed: Adds missed exception for blog route
  • Fixed: Seeder clears posts/files properly
  • Fixed: Post/File is based on PetalPro.Schema
  • Fixed: Combobox does not disappear when navigating to another page

Upgrade Notes

Petal Pro has been upgraded to Tailwind 4. Some utilities have been removed or renamed. See the Tailwind upgrade guide for more information.

To upgrade to Tailwind 4 in your project, make sure you update mix.exs:

- {:tailwind, "~> 0.2", runtime: Mix.env() == :dev}
+ {:tailwind, "~> 0.3", runtime: Mix.env() == :dev}

And config.exs (note that the paths have changed and that you need 4.0.9 or above):

config :tailwind,
- version: "3.3.3",
+ version: "4.1.11",
default: [
args: ~w(
- --config=tailwind.config.js
- --input=css/app.css
- --output=../priv/static/assets/app.css
+ --input=assets/css/app.css
+ --output=priv/static/assets/app.css
),
- cd: Path.expand("../assets", __DIR__)
+ cd: Path.expand("..", __DIR__)
]

Don’t forget to run:

mix tailwind.install

Updated app.css

app.css has been updated to support CSS first configuration:

app.css
@import "tailwindcss";
@source "../../deps/petal_components/**/*.*ex";
@import "../../deps/petal_components/assets/default.css";
@import "./colors.css";
@import "./combo-box.css";
@import "./editorjs.css";
@import "./animations.css";
@import "../node_modules/tippy.js/dist/tippy.css" layer(components);
@plugin "@tailwindcss/typography";
@plugin "@tailwindcss/forms";
@plugin "@tailwindcss/aspect-ratio";
@plugin "./tailwind_heroicons.js";
...

To see the latest changes for 3.0.0, go to:

https://github.com/petalframework/petal_pro/tree/v3.0.0/assets/cssgithub.com

The following files have changed:

  • app.css
  • combo-box.css
  • editorjs.css

The following files have been added:

  • colors.css
  • animations.css
  • tailwind_heroicons.js

Finally, tailwind.config.js has been removed.

Now you should be able to follow the Tailwind upgrade guide to update the rest of your project. Running mix format should automatically arrange tailwind classes in your project.

2.2.0 - 2024-12-19

  • Upgrades Petal Pro to LiveView 1.0.1!
  • Admin/User AI chat - use LangChain to interrogate Petal Pro
  • Content Editor component - based on Editor.js
  • Blog/Content Management System - leveraging Content Editor
  • Updated: Using latest Heroicons from Petal Components 2.0.6
  • Updated: address gettext deprecation issue
  • Updated: petal.gen.live uses Table instead of Data Table (and is based on streams). Use the --data-table option to generate templates using a Data Table
  • Updated: Compatability increased for code generated by phx.gen.live and phx.gen.html
  • Fixed: sticky class for stacked layout
  • Fixed: Sub-menu will display for Stacked Layout in mobile mode
  • Fixed: User notifications marked as read based on socket url (previously only worked with conn request path)
  • Fixed: Combobox has rounded corners after selection

Upgrade Notes

In Petal Components, the heroicons dependency has been replaced with an alternate CSS-based approach. This is based on what has been implemented in the Phoenix repo - the reasoning is explained in this issue. To upgrade an existing Petal Pro project, add the dependency in mix.exs:

mix.exs
def deps do
[
+ {:heroicons,
+ github: "tailwindlabs/heroicons",
+ tag: "v2.1.5",
+ app: false,
+ compile: false,
+ sparse: "optimized"},
]
end

This will download a copy of the source SVG files directly from GitHub (into deps/heroicons/optimized). Then the following code will process these files to create custom CSS classes:

assets/tailwind.config.js
const colors = require("tailwindcss/colors");
const plugin = require("tailwindcss/plugin");
+ const fs = require("fs");
+ const path = require("path");
module.exports = {
plugins: [
+ // Embeds Heroicons (https://heroicons.com) into your app.css bundle
+ // See your `CoreComponents.icon/1` for more information.
+ //
+ plugin(function({matchComponents, theme}) {
+ let iconsDir = path.join(__dirname, "../deps/heroicons/optimized")
+ let values = {}
+ let icons = [
+ ["", "/24/outline"],
+ ["-solid", "/24/solid"],
+ ["-mini", "/20/solid"],
+ ["-micro", "/16/solid"]
+ ]
+ icons.forEach(([suffix, dir]) => {
+ fs.readdirSync(path.join(iconsDir, dir)).forEach(file => {
+ let name = path.basename(file, ".svg") + suffix
+ values[name] = {name, fullPath: path.join(iconsDir, dir, file)}
+ })
+ })
+ matchComponents({
+ "hero": ({name, fullPath}) => {
+ let content = fs.readFileSync(fullPath).toString().replace(/\r?\n|\r/g, "")
+ let size = theme("spacing.6")
+ if (name.endsWith("-mini")) {
+ size = theme("spacing.5")
+ } else if (name.endsWith("-micro")) {
+ size = theme("spacing.4")
+ }
+ return {
+ [`--hero-${name}`]: `url('data:image/svg+xml;utf8,${content}')`,
+ "-webkit-mask": `var(--hero-${name})`,
+ "mask": `var(--hero-${name})`,
+ "mask-repeat": "no-repeat",
+ "background-color": "currentColor",
+ "vertical-align": "middle",
+ "display": "inline-block",
+ "width": size,
+ "height": size
+ }
+ }
+ }, {values})
+ })
],
};

2.0.0 - 2024-08-15

  • Petal Framework is merged into Petal Pro
  • Npm packages recipe is merged in as default
  • Persistent user notifications
  • Graphs/stats dashboard in the Admin console
  • See who’s currently active (via Presence) in the Admin console
  • If user belongs to only one org, current org is automatically set
  • User.is_admin is replaced with User.role. User role is an enum
  • Integrate :typed_ecto_schema with Ecto.Schema fallback for users who have not installed it.
  • Orgs are added to log view
  • Ecto insights tab is enabled in LiveDashboard
  • Fixed: Edge case for Combo Box - Tom Select is re-generated when there is a change in option count
  • Fixed: App does not crash when impersonating a user and the session has expired
  • Fixed: Subscription logs weren’t working!
  • Fixed: Race condition with subscription create/update when responding to Stripe web hooks
  • Fixed: In docker compose, postgres container will not auto-restart if stopped

Upgrade Notes

Starting with this release, the Petal Framework is no longer referenced as an external package, and the private Petal hex repo it came from has since been shut down. If your Dockerfile has a RUN --mount=type=secret,id=PETAL_LICENSE_KEY step that adds that repo, delete the whole step and drop the PETAL_LICENSE_KEY build secret with it. Nothing replaces it, because nothing is fetched from petal.build at build time any more:

  • Petal Pro itself is a zip you download from petal.build/users/downloads after purchase. The code lives in your own repo.
  • The components come from public Hex. Add {:petal_components, "~> 4.17"} to your deps in mix.exs, run mix deps.get, and put use PetalComponents in your web module.

You may need to add nodejs and npm:

Dockerfile
# install build dependencies
+ RUN apt-get update -y && apt-get install -y build-essential git nodejs npm \
+ && apt-get clean && rm -f /var/lib/apt/lists/*_*

In the past mix assets.setup would install Tailwind CSS and esbuild. Tailwind is now installed with mix setup, esbuild is installed via npm with mix assets.deploy. You’ll need to remove:

Finally, lib/petal_pro_web/petal_framework_translations.ex is no longer required. Components like the DataTable can use Gettext directly.

1.8.0 - 2024-04-04

  • JSON API: You can use the Petal Pro API for user management (register, sign in and update). It comes with OpenAPI support out of the box. Includes Swagger UI
  • Update: Can sync all Stripe subscriptions including cancelled ones
  • Added expanded user and org admin pages
  • Fixed: PetalProWeb.Controllers.UserAuth.disconnect_user_liveviews doesn’t disconnect the user’s live views #216
  • Fixed: Passwordless sign in issue from latest Phoenix Live View fixed #222
  • Update: Sidebar layout now collapsible

1.7.0 - 2024-11-01

  • Stripe integration - can buy subscriptions and manage them - support for both individuals and orgs
  • Use styler for code formatting
  • Updated landing page components to a more modern look

Upgrade Notes

Starting in this release, we now use Styler to format our codebase. This means there will be a large amount of changes. To minimise merge or rebase conflicts when upgrading, we recommend you swap out Recode with Styler first:

Then, replace the content of .credo.exs with the one in this repo.

Finally, run the formatter for Styler to take care of things:

Another change we recommend you make before upgrading, especially if you’ve made changes to your landing page, is to rename PetalProWeb.Components.LandingPage to PetalProWeb.LandingPageComponents, make sure you also rename the file from landing_page.ex to landing_page_components.ex.

Given the amount of changes in this release, we recommend you backup your branch, then use merge instead of rebase to bring your branch up to date.

1.6.2 - 2023-11-03

  • Fix bug where users registering via passwordless / 3rd parties would not get invites to orgs

1.6.1 - 2023-9-28

  • Important passwordless security fix - anyone using passwordless should update
  • Update deps

1.6.0 - 2023-7-05

New

  • <.image_upload> component for uploading single images like avatars. Used in user settings
  • Local, Cloudinary and S3 support for <.image_upload>
  • User impersonation - admins can login as any user without knowing their password - available via the Admin console (under the User menu).

Updated

  • All forms now use the new FormField structure
  • <.public_layout> has been moved into public.html.heex (it’s likely you’ll want to modify this to your brand and hence a component doesn’t make sense)

Fixed

  • Reset password page now accessible when logged in (previously would redirect)

Removed

  • Page builder (it was getting too complex to manage - let us know if you used this a lot and we’ll consider bringing it back)

1.5.2 - 2023-4-20

New

  • Uses the petal_framework private package (deletes all the _petal_framework folders). This will allow for an easier upgrade process in the future, especially for components like the data table.
  • Data Table supports base_url_params. Keep custom query params when changing sort order.
  • Data Table is now self contained in the live view - code isn’t scattered across the model and context.
  • Added mix recode for code linting and refactoring
  • Use <.flash_group> to show flash messages (Petal Framework 0.3.0)

Changes

  • Enabled Wallaby tests by default (mix test)
  • Updated Tailwind to 3.3
  • Updated Erlang to 25.3
  • Added rename_project lib to replace custom mix task

Breaking

Fixed

  • Data table going blank when changing page size
  • Navigation problems for the Data Table when setting the default_limit via a schema file
  • Fix Finch issue with email sending

1.5.1 - 2023-3-10

New

  • Develop Petal Pro in GitHub CodeSpaces!
  • Data Table column - can now filter by a select list
  • Data Table column - can now filter by a float

Changed

  • topbar.js version updated to 2.0
  • mix setup no longer fetches tailwind/esbuild if they already exist
  • Upgrade Petal Components to 1.0
  • Data Table is now a function component

Fixed

  • Github auth working again

1.5.0 - 2023-2-10

Changed

Fixes

1.4.1 - 2022-11-15 16:30:00

Added

  • Add Petal Enhance (recipes)

Fixes

  • Fix admin users modal. Clicking off the modal now works
  • Change avatar_url to text in DB for long URLs
  • Whitelist Google profile picture images in CSP
  • Fix Mailbluster unsubscribe route + documentation

1.4.0 - 2022-10-12 23:44:20

Added

  • Updated to LiveView 0.18 + Petal Components 0.18
  • All components updated with declarative assigns (attr / slot)
  • Data table component
  • Local time component
  • Sobelow for security checking
  • Coveralls for code test coverage
  • test.yml Github action for code quality
  • Easily modifiable content security policy to help prevent XSS
  • Added a docker-compose.yaml that adds Postgres so you don’t need to install it

Changed

  • Router significantly more streamlined
  • Some routes have been moved into their own files: AdminRoutes, AuthRoutes, DevRoutes, MailblusterRoutes
  • Users are forced to be confirmed to access /app routes (easily configurable)
  • Use Ecto enums for org roles

Fixes

  • Fix reset password failing when signed in
  • Clean up dashboard_live.ex - some old code unused was left in there
  • Improved SEO meta tags in _head.html.eex
  • Show a warning in the logs when no title/meta_desciprion is set on a public page
  • Added open-graph.png (to be replaced by dev)
  • Fix require_confirmed_user plug
  • Fix landing page GSAP not working

1.3.0 - 2022-06-17 02:43:55

Added

  • Two-factor authentication using time-based one time passwords (paired with something like Google Authenticator)

Changed

  • Decoupled DashboardLive from Orgs so you can get started quicker if you don’t want orgs
  • Can pass a custom header class to the public layout
  • Sidebar and stacked layouts now support grouped menu items (see dev_layout_component.ex for an example)
  • Update Tailwind to 3.1
  • Split CSS into different files thanks to Tailwind 3.1

Fixed

  • Onboarding now remembers user_return_to
  • Fixed nav dropdown bug after modal toggle
  • Fixed gettext in live views

1.2.0 - 2022-05-31 07:34:11

Added

  • Login with Google & Github - easy to add more auth providers
  • Passwordless auth - register/sign in via a code sent to your email
  • Orgs - create an org, invite & manage members, and more
  • User lifecycle actions - run code after actions like register, sign_in, sign_out, password_reset, etc
  • New generator: mix petal.gen.html (same args as phx.gen.html)
  • New component: <.markdown content=””> & <.pretty_markdown content=””> (uses Tailwind Typography plugin)
  • Added License and Privacy pages (with some content from a template to get you started)
  • New layout: <.layout type=”public”>, for public marketing related pages like landing, about us, privacy, etc
  • Hooks can now be run in dead views if compatible (see color-scheme-hook.js as an example)

Changed

  • Simpler config access (PetalPro.config(:app_name) instead of Application.get_env(:petal_pro, :app_name))
  • Refactor <.layout> to take less props
  • Refactor dark/light mode system. Much simpler now and no longer needs cookies
  • Put Petal Pro Components in their own folder for easier future upgrades (can duplicate if you want to modify them)
  • Sidebar and stacked layout have a new slot for the top right corner (if you want to add something like a notifications bell)

Fixed

  • Log metadata wasn’t being cast
  • More user actions are logged
  • Fixed petal.live generator tests
  • Added tests for user settings live views

1.1.1 - 2022-03-12 20:45:36

  • Bump Oban version to stop random error showing
  • Bump Petal Components
  • Use new <.table> component in petal.gen.live generator & logs
  • Dark mode persists on all pages with cookies
  • Fix logo showing twice in emails
  • Improved the Fly.io deploy flow
  • Fix admin user search
  • Remove guide (this is now online)

1.1.0 - 2022-02-28 00:08:52

  • Added generator mix petal.gen.live
  • Add gettext throughout public facing templates
  • Improved dev_guide
  • Add Oban
  • Easy Fly.io deployment