Reference
Release notes#
Every package version, newest first. A version marked pre-release is a build we install into our own test orgs; it has not been promoted, and it is not the one an AppExchange listing would install.
Upgrading from a build older than 1.0.0-1
Versions built before September 2026 used a throwaway namespace and cannot be upgraded from. Uninstall that package first, then install the current version. See Installation.
1.0.0-5 — 5 September 2026 · pre-release#
- The staff consoles now check for a package licence seat. A user who holds the permission set but no seat sees a notice in place of the console; assign seats under Setup → Installed Packages → Manage Licenses. Donor and guest pages never check for a seat.
- Donor portal sign-in is now a two-step emailed code instead of an emailed link. The donor types their email, receives an eight-character code that is good for 15 minutes and works once, and types it on the next screen. Sessions end after a period of inactivity and after a fixed maximum, the donor can sign out, and staff can end one by setting the donor's Portal Access Token record to Revoked. Links sent before the upgrade stop working; donors simply request a code. The wording on both sign-in screens comes from your Donor Portal settings — review it after upgrading. See Donor portal and Publish the donor portal.
- The Fundraisers console is rebuilt as a tabbed workspace, and a new Donors console tab joins it in the app: find any donor, open them as a tab, send a portal code, print or email a receipt, refund a gift, or answer a request. See Donors console.
- Dialogs on record pages (refunds, campaign updates, documents, FAQs, custom questions, event tickets) use the platform's standard modal. Appearance only; nothing to configure.
- Security-review readiness: every open finding in the package's AppExchange readiness audit is closed, and the inventory is re-checked on every change. See Security & code quality.
1.0.0-4 — 2 September 2026 · pre-release#
- Stripe credential fields are now named for what they must hold: a restricted key. A Payment Account that points at an unrestricted secret key is rejected with a message that says what to change. Existing accounts keep working; re-open Payments in the Settings console to see the new names.
- The Settings console tells you which credential names are yours to choose and which are fixed by the platform.
- The Code Analyzer findings the package carries are published with a verdict on each one, under Security & code quality.
1.0.0-3 — 1 September 2026 · pre-release#
- Every scratch and test org is pinned to the US locale so currency behaviour is predictable. The product supports US and UK orgs only.
- A Goal Amount on an Ongoing fundraiser is rejected at save time instead of being ignored.
- Internal clean-up across most Apex and Lightning components after a full Code Analyzer pass. No behaviour change is expected; the suite runs at 95% coverage.
1.0.0-2 — 1 September 2026 · pre-release#
- First build with every pull request gated on Code Analyzer and on 90% Apex coverage.
- The Settings console's Site & Domain step no longer lists an Event Registration page that the package does not ship.
1.0.0-1 — 1 September 2026 · pre-release#
- First version under the
pledgivonamespace. Everything shipped in the earlier test builds is here: campaigns, one-off and recurring giving through Stripe, ticketed events, the donor portal, receipts, refunds, reconciliation jobs, the embeddable donate widget, and optional NPSP sync. - After installing, follow After you install. The package seeds what it is allowed to seed; the rest is a short checklist in the Get Started panel inside the app.