← All releases
Sixteen work items, 15 changes, and two database migrations, which add empty columns and rewrite nothing. A small release: leaders can move a scout's in-progress merit badge to a newer edition, swimming classification dates show on member pages, the newsletter archive opens to more members, and Activity Credit leaves the menus where picking it made invisible events. Email delivery tracking is built but stays off until the email service is set up for it.
What's new on the site
Advancement
- A leader can move an in-progress merit badge to a newer edition. When BSA publishes a new version of a badge, scouts already working on it stayed on the old one; ranks could switch, badges could not. A blue card now shows Change Version when a newer edition exists. The confirmation shows which signed requirements carry over and which are new. One known gap: the old card can still appear in badge lists after the switch. That fix comes in a later release.
Scouts and families
- Swimming classification date shows on a scout's page, next to the classification, and can be edited there. The date was stored but appeared nowhere.
Email and messages
- The newsletter archive is open to more members. Reading past issues needed the Communications level that is used to write them (level 4). Anyone with Communications level 1 or above can now read the archive.
- Email delivery tracking is built, and it stays off for now. Once switched on, a broadcast's recipient list will show Delivered, Bounced, Delayed or Marked as spam for each person, and a member whose address hard-bounces will get a flag on their profile. Today "Delivered" only means the message was handed to the email service. It needs the email service set up first, so nothing changes on the site in this release.
Events
- Activity Credit is gone from three menus. The repeating-event rule form, the calendar-feed form and the planning-item form offered "Activity Credit" as an event type. Picking it made a series of events that never appear on the calendar and cannot be deleted. The repeating-events import now refuses it too. Activity Credit events still come only from the activity-credit import.
The phone app
- A refused offline change is reported once. When the page and the phone's background sync both sent the same queued batch, the server saw it twice and the status bar showed the refusal twice. The batch is now sent once.
Behind the scenes
Nothing here changes what you see on the site.
- Feed-imported events record when they were published. Events from an outside calendar feed were saved as Published with no publish time. A planned Unarchive button would have brought an archived feed event back as a Draft, and it would stop counting for advancement credit. New feed events are stamped, and a command stamps the existing ones.
- Parent access rules were consolidated. Nothing changes on the site.
- The attendance page reads hiking and service tags from data it already loaded, instead of asking the database again per event.
- Developer tooling: the dev-troop teardown command refuses to touch a real troop, and a check stops new code from starting a badge without its requirement rows.