Pelilauta

Changelog

CHANGELOG.md carries Pelilauta releases from 21.0.0-rc.2 onward.

21.1.4

  • fix(session): Session state starts unverified on each page load. Member controls, reaction reads, library queries, and read-state subscriptions wait for server agreement. Account replacement clears stale profile presentation and rejects obsolete read results. (#182, #215)
  • fix(threads): Public thread HTML no longer carries requester-specific Bluesky permissions. Sharing controls use the verified browser identity. (#212)
  • docs: Specifications define public-page progressive enhancement, onboarding hints, and outage behavior. ADR 0005 uses the existing session endpoint without an additional UID cookie.

21.1.3

  • fix(session): Forced sign-out after an API authentication failure clears the session cookie and local user data before signing out of Firebase. Failed logout keeps the reader on the current page with the incomplete-logout notice. (#207)

  • fix(session): Logout waits for a session cookie request already sent before deleting the cookie, and a late sign-in or session restore cannot restore local user data after logout. Sign-in and session restore for the same account send one session request.

  • fix(session): The browser confirms a signed-in session only when the server verifies a session cookie for the same account, and recreates a missing or mismatched cookie. A temporary verification or network failure leaves the reader signed in to Firebase for a later check, and the service worker neither caches session status nor replays a session request. (#178)

  • fix(session): Logout deletes the session cookie first, clears local user data second, and signs out of Firebase last. A failed step stops the logout, keeps the Firebase session, and tells the reader to try again. Logout also clears the persisted subscriber data. (#180)

  • test(session): Sign-in redirects only after the server creates the session cookie. (#179)

  • fix(threads): A thread created as non-public is stored as non-public. A thread created without the flag stays public. (#167)

  • fix(threads): A thread, reply or edit sent while the page restores the signed-in session waits for the session and is saved. (#198)

21.1.2

  • fix(markdown): The server bundles the HTML sanitizer so Markdown pages render on the Netlify runtime.

21.1.1

  • fix(design-system): Marked URL links truncate with an ellipsis inside authored content, and reply bubbles fit narrow columns. (#199)

  • fix(markdown): Thread bodies, replies, previews, snippets, RSS items, handouts and wiki pages render Markdown through one renderer, and its output and stored HTML pass one sanitization policy before reaching the page. Single newlines break lines everywhere, footnote links stay within the body that contains them, and a bare URL carries class="url". (#200)

  • fix(inbox): Following a notification marks it read. Failed acknowledgment leaves it unread and allows navigation. (#189)

  • fix(inbox): Notifications clear when the signed-in reader changes, and delayed updates from the previous reader cannot restore them.

  • fix(threads): A live reply that shifts the discussion no longer shows a reply under another author's name, profile link, avatar or date. (#175)

  • fix(threads): A thread opened before the subscription has loaded is marked read once it arrives, instead of staying unread. (#176)

  • fix(inbox): A reply notification links to the reply, at /threads/<thread>#<reply>; one stored with the thread key alone links to the discussion. Each reply creates its own notification. (#172)

21.1.0

  • The contract records that version 21 serves pelilauta.social, and that Firestore, Storage and Auth carry production data.
  • fix(i18n): A post whose author profile does not resolve displays the anonymous label instead of the key app:meta.anonymous.
  • fix(threads): A thread page opens a live reply subscription only for an active signed-in session, releases it on sign-out, account change and page departure, and says when live updates fail. (#165)
  • fix(threads): The server reads a discussion's replies in creation order, and a malformed reply is skipped without discarding the rest. (#165)
  • fix(threads): A thread page carries its replies, with bodies and attachments, in the initial document, so an anonymous reader reads them without JavaScript. (#165)
  • fix(threads): An anonymous or unresolved session reads no reaction documents for a thread's replies. (#165)
  • fix(threads): A thread page names each reply's author in the initial document, resolved on the server, so a reader without JavaScript sees who wrote each reply and the replies trigger no browser profile read. (#165)
  • fix(threads): A thread page names the opening post's author in the initial document, resolved on the server through a shared server-side fetch helper, so the opening post triggers no browser profile read. (#165)
  • fix(threads): A thread page exposes #discussion, gives each reply a permalink and the discussion an end-of-discussion link, both working without JavaScript, and a malformed live reply no longer discards the other changes in its snapshot. (#165)
  • feat(threads): A signed-in reader's ?jumpTo=<timestamp> link lands at the last reply created at or before the timestamp, resolved from the URL alone; ?jumpTo=unread no longer targets unread replies.
  • fix(threads): A live reply snapshot keeps Firestore's creation order, so a reply inserted between two others appears between them. (#165)
  • fix(threads): The opening post's reaction document is read only for a signed-in session that Firebase has confirmed. (#165)
  • fix(threads): The live reply subscription and reaction reads wait for Firebase to confirm the persisted session, and a failure notice clears when the session ends. (#165)
  • fix(profiles): The profile route answers with the avatar of a profile stored with the legacy photoURL field. (#165)
  • test(threads): The anonymous reaction-read test names a data-fetching boundary and checks the opening post's reaction and attributed content; a new test covers a persisted session Firebase has not confirmed. (#165)
  • chore(threads): The thread page files conform to the lint rules.
  • fix(seo): A page's canonical URL is its path alone, so a thread link carrying ?jumpTo= resolves to one canonical conversation. (#165)
  • fix(threads): A thread is marked read once Firebase confirms the signed-in account, so a stale persisted session writes nothing. (#165)

21.0.0

Pelilauta v21 leaves beta and replaces v18.

21.0.0-rc.4

  • feat(site-import): An imported page keeps the dates its source file carries, so the site index orders imported pages by authoring date. An import stamps a file that carries no dates.
  • fix(site-import): An import writes the site page index once for the whole batch instead of once per page.
  • fix(front-page): Returning to the front page through a view transition keeps the welcome section hidden from a signed-in member.

21.0.0-rc.3

  • fix(threads): A signed-in member sees the chat bar on a thread page without an invitation to join the discussion. (#149, #151)
  • fix(i18n): The magic-link verification prompt, the missing-profile panel in Settings, the empty handout list, and the site import flow read text from the locale files. (#154)
  • fix(onboarding): Entering a nickname another member holds displays the taken-nickname notice and disables registration. (#156)
  • fix(reactions): The reaction button fetches the current reaction state from Firestore on mount. (#157)

21.0.0-rc.2

  • feat: Pelilauta publishes the changelog at /changelog.html, and the footer version links to it. (#145)
  • feat(forms): A fieldset displays as a borderless group with even spacing between its fields, and its legend takes the heading style of the surrounding section.
  • fix(settings): A member toggles the color theme from the Actions section of Settings and from the header switch.
  • fix(front-page): The stream cards float over the poster.
  • fix(site): Deleting a site reports success and returns to the library.
  • fix(site): The theming settings show the background poster behind the site card and the forms.