Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Registration closing times and tier availability
Repositories: Partners dashboard, Partners API, and Rego site. Status: FIFM closing-time correction published; hosted Rego badge verified after release.
What’s Changed
Registration and tier closing times in the EMS editor now use the event’s time zone when displayed and saved. The FIFM Sponsor tier’s intended 24 September, 11:59 pm Philippine closing time is corrected in the live registration data. Rego now shows a red Closed badge and blocks selection when a tier or event has closed or filled. Gift tiers and add-ons also respect their availability windows, and the API checks add-on windows during purchase.
Impact
Attendees can identify unavailable tiers immediately. Event operators can set registration times without a silent time-zone shift.
Validation
The FIFM public API confirms the corrected Sponsor and event closing instants. Local type checks, time-zone and availability checks, and desktop/mobile badge fixtures passed. The hosted FIFM Sponsor card shows a red Closed badge; authenticated EMS editing and purchase submission were not exercised live.
Clearer random-draw changes between Rego tiers
Repository: Rego site. Status: Validated locally; hosted display remains to verify after release.
What’s Changed
When adjacent tiers offer the same random-draw designs, those designs stay in the regular inclusion list. A change in the number of designs drawn appears as a short grouped inclusion card with an outlined up or down icon, the previous count, and the new count. Replacement notes have their own outlined icon. Newly offered designs still appear as additions.
Impact
Attendees can see the actual difference between tiers without the same design being presented as new again.
Validation
Rego typecheck, build, and desktop/mobile tier browser fixtures passed locally, including increased and decreased draw counts and an expanded bundle. Hosted display remains to verify.
Variants-only switch for Rego inclusions
Repositories: Partners dashboard, Partners API, and Rego site. Status: Database migration published; application changes validated locally and hosted behavior unverified.
What’s Changed
The inclusion item-type dropdown now describes the item itself. A separate Variants only switch in the same card removes the base item and requires fixed or random variant selections in each tier. Variants inherit the inclusion’s selected item type. Active controls for inclusions and their variants now use switches.
Impact
Operators can choose a meaningful item type, such as Print, while offering only its designs. Existing Set records are converted to General item with Variants only enabled, retaining their tier selections. Attendees continue to see grouped variant entries without a duplicate base item.
Validation
Dashboard, API, and Rego typechecks and browser fixtures passed locally. The migration was applied, and a read-only database query confirmed the legacy Set type is absent and variants inherit their parent type. Hosted registration and fulfilment remain to verify.
Grouped random draws in Rego tiers
Repository: Rego site. Status: Validated locally; hosted display remains to verify after release.
What’s Changed
Random draws now appear under one inclusion heading in rego tiers, including draws configured as alternatives. The number of included designs and repeat rule appear once above the nested design names. Set and bundle draws use the same grouped presentation.
Impact
Attendees can see which designs belong to the same draw without reading the draw rule beside every design. The tier still shows each configured design by its title.
Validation
Rego typecheck and desktop/mobile browser fixtures passed, including a nine-design random draw.
Variant-only inclusion Sets
Repositories: Partners dashboard, Partners API, and Rego site. Status: Database migration published; application changes validated locally and hosted behavior unverified.
What’s Changed
Organisers can mark an inclusion as a Set when its name groups designs rather than describing a separate item. Each selected tier must configure its Set variations. Fixed groups include the chosen designs; random groups draw from their candidates. The Set itself is not added as a base item, sold separately, or counted in fulfilment. The public tier list groups the designs under the Set name and aligns Set and bundle headings with standalone inclusions.
Impact
Attendees see the actual included or drawn designs without a misleading replacement claim or duplicate parent item. Operators should configure variation groups for every tier that includes a Set before saving the catalog.
Validation
Dashboard, API, and Rego source checks and desktop/mobile catalog fixtures passed locally. The database migration was published, and a read-only query confirmed that the Set type is accepted. Hosted registration and fulfilment remain to verify.
Rego variant details show only their own information
Repository: Rego site. Status: Validated locally; hosted display remains to verify after release.
What’s Changed
Inclusion variation detail popups show the title, description, and image configured for that specific variation. Parent inclusion delivery, size, availability, and other details stay with the parent item. Variations without their own details have no Details control.
Impact
Attendees see accurate details for each design when comparing registration tiers and browsing all inclusions. Organisers should add a description or image to a variation if they want it to have a detail popup.
Validation
Rego typecheck, source build, and desktop/mobile tier comparison fixtures passed. Hosted display remains to verify.
Rego tiers follow price order and clearer comparisons
Repositories: Partners dashboard, Partners API, and Rego site. Status: Validated locally; hosted display remains to verify after release.
What’s Changed
Registration tiers appear from lowest to highest price in the EMS catalog and public Rego page. A tier describes an inclusion as replacing another only when a cheaper tier actually offered that base inclusion.
Impact
Event operators can review tier pricing in a consistent order. Attendees can compare upgrades without seeing a replacement claim for an item absent from the cheaper tier.
Validation
Dashboard, API, and Rego checks plus desktop/mobile tier comparison fixtures passed. Hosted display remains to verify.
Rego shows variation designs individually
Repositories: Rego site and Partners API. Status: Validated locally; hosted display remains to verify after release.
What’s Changed
Tier cards and the all-inclusions showcase now list each configured variation under its own title and details. Random groups also state how many designs are assigned and whether designs may repeat.
Impact
Attendees can explore each configured design while seeing how many random designs their tier includes. The actual assignment remains unknown until the tier’s configured reveal point.
Validation
Rego and API typechecks, direct React Router build, API Worker dry run, public projection fixture, and desktop/mobile tier and registration-summary browser fixtures passed. The full Rego metadata build needs the local API on port 8787, which was unavailable during validation.
Assigned requirement responders can upload evidence
Repositories: Partners dashboard and Partners API. Status: Validated locally; hosted behavior remains to verify after release.
What’s Changed
The My Work requirement modal now has a visible file drop area alongside its file picker. Responsible and Accountable responders can upload evidence for their assigned requirements without a separate file-management permission. A pending safety scan no longer stops the response from being submitted; the evidence remains unavailable for download or acceptance until its scan passes.
Impact
Assigned responders can attach one file to a requirement response by choosing it or dragging it into the modal. If submission needs a retry, the already uploaded file is reused. Reviewers must wait for a clean scan before accepting evidence.
Validation
Dashboard and API typechecks, Worker dry run, requirement role policy checks, and a browser fixture covering file drag and drop, upload, failed submission, and retry passed.
My Work opens planning details in a modal
Repository: Partners dashboard. Status: Validated locally; hosted behavior remains to verify after release.
What’s Changed
Calendar and Gantt links now open My Work details in a modal instead of adding a separate card above the workspace. Requirement details include the description, instructions, acceptance criteria, response type, evidence upload, and confirmation before submission. The “Do this next” card now has a View details button.
Impact
Staff can read the full requirement and respond from the same modal. Other planning entries show their assignment and available actions in a modal, keeping My Work’s page layout intact.
Validation
Partners typecheck and production build passed. Browser fixtures covered calendar and Gantt links, requirement details and submission, next-action details, Board and List views, and mobile layout.