martin
3. Juli 2026 um 06:43
4
Das Überspringen zu „Permanent“ passiert normalerweise nicht, wodurch in diesem Fall ein Fehler mit dem Benachrichtigungslink aufgedeckt wurde, der hier behoben wurde:
main ← issue/perm-uc-notif-redirect
merged 05:28AM - 03 Jul 26 UTC
When an upcoming change was automatically enabled, the notification
linked admi… ns to the upcoming changes config page. But once a change
reaches permanent status it no longer appears there (that page only
lists experimental through stable) and instead surfaces on the What's
New page. So if the notification was left unread until the change became
permanent, clicking it dropped the admin on an empty filtered list.
This resolves the change's status at click time rather than baking it
into the notification. The permanent change names are now exposed to
staff via the site serializer, and the notification's link checks them:
if every referenced change is now permanent, it sends the admin to
What's New scrolled to that change's card; otherwise it keeps the
existing upcoming changes page where the still non-permanent changes
remain actionable.
To support the scroll, every What's New item now has a stable id anchor,
and the page accepts a scrollTo query param that scrolls to and briefly
highlights the matching card once the feed loads.
<img width="1106" height="423" alt="image" src="https://github.com/user-attachments/assets/353304b3-1590-407a-b3f2-7d0a0c1d0a38" />
<img width="1163" height="782" alt="image" src="https://github.com/user-attachments/assets/26e2d8d2-173f-455b-83a8-a0f3fc907243" />
Außerdem werden Änderungen bei „Permanent“ auf der Seite /admin/whats-new angezeigt, die ich bereits in Introducing Upcoming Changes, a system to manage new features and changes to existing functionality in your community - #41 by martin erwähnt habe, und ich habe diese Information nun zum Eröffnungspost dieses Themas hinzugefügt.
4 „Gefällt mir“