Foundry PF2e Rapid 7.10.x Update Reflects Paizo Spring Errata, Fixes Automations
The volunteer-maintained pf2e system for Foundry VTT pushed rapid 7.10.x releases (7.10.0 `43663b6`, 7.10.1 `4326af8`) that, per a project summary, update data to reflect Paizo’s Spring 2026 errata and fix bugs.

The volunteer-maintained Pathfinder Second Edition (pf2e) system for Foundry Virtual Tabletop issued rapid maintenance in the 7.10.x series that, according to an accompanying summary, "explicitly updates data to reflect Paizo’s Spring 2026 errata" and addresses a wide range of bugs. The supplied release fragments include tags for 7.10.0 with commit `43663b6` and 7.10.1 with commit `4326af8`, and mark the activity as recent around the event date of February 27, 2026.
Repository fragments also show a follow-up tag 7.11.0 tied to commit `ba88e6f` and a prior tag 7.9.1 at `74af732`, each listed next to the actor label @github-actions. The supplied capture includes a separate tag 0.0.1 for sf2e with commit `6e5481a` and the literal line "First beta release of Starfinder Second Edition," documenting that the repository records both pf2e and an sf2e beta tag in its releases history.
The partial changelog headings visible in the capture include "System Improvements", "Bugfixes", and "Data Updates", and the literal token `flags.system` appears among the fragments. The original summary of the update is truncated in the supplied material, ending with the fragment "The release notes show an empha", indicating the release notes in this capture were not preserved in full even where headings are present.

The GitHub release page capture provided to this report repeatedly failed to render full entries, displaying exact error strings such as "There was an error while loading. Please reload this page.", "Uh oh!", "Sorry, something went wrong.", and "No results found" multiple times. Those repeated UI errors in the supplied fragments obscure the detailed changelog lines that would enumerate which automations or specific rules were changed to align with Paizo’s Spring 2026 errata.
Taken together, the explicit artifacts in the supplied material show active maintenance and tagged releases at 7.10.0 (`43663b6`), 7.10.1 (`4326af8`), and 7.11.0 (`ba88e6f`) with automated release commits by @github-actions, plus changelog headings for data and bug fixes. The project summary's claim that the 7.10.x updates "explicitly update data to reflect Paizo’s Spring 2026 errata" is present in the supplied summary text, but the captured GitHub fragments do not contain the full release notes that would confirm which data files or automations were modified. The repository tags and commit hashes in the capture demonstrate rapid activity; however, the repeated loading errors prevent a complete, line-by-line accounting of the bugfixes and automation repairs from the supplied material.
Know something we missed? Have a correction or additional information?
Submit a Tip

