Announcements
Announcements are official posts from admins or publishers that carry elevated visibility — pinned at the top of their section, highlighted with a distinct badge, and delivered as notifications to subscribers. They are the primary channel for communicating updates, breaking changes, and important news.
Who Can Post Announcements
| Announcement Type | Who Can Post | Where It Appears |
|---|---|---|
| Platform announcement | Admin team only | Pinned at top of the Announcements section; banner visible on marketplace homepage |
| Package announcement | Package publisher (in their own package's forum) | Pinned in the package's forum section; appears in Announcements section with package tag |
| Security advisory | Admin team or package publisher | Same as platform or package announcement; additionally triggers a priority notification to all tenants who have the affected package installed |
Posting a Package Announcement
Publishers use announcements for their packages to communicate major releases, deprecations, and known issues. To post a package announcement:
Announcement Behavior
Always Pinned
Announcement threads are permanently pinned at the top of their section. They cannot be unpinned by the publisher after posting — only admins can unpin announcements.
Replies Enabled
Users can reply to announcement threads. The announcement post itself is read-only (cannot be edited by non-admin non-publisher users), but the reply thread below it is open.
Distinct Visual Style
Announcement threads have a highlighted background and a megaphone icon in listings, distinguishing them from standard discussion and Q&A threads.
Notification on Publish
Users who subscribed to the package or forum receive an in-platform notification and email when a new announcement is published. The notification includes the announcement title and the first 200 characters of the body.
Best Practices for Package Announcements
- Post a new thread per major release — Don't edit old announcements to add new version information. Each release deserves its own thread so users can find historical announcements cleanly.
- Use "Security Advisory" type for vulnerability disclosures — This triggers priority notifications to installed-package tenants, ensuring broad reach for urgent updates.
- Include migration steps for breaking changes — If a new version introduces breaking changes, include the full migration guide in the announcement body. Users should not have to navigate externally to understand what changed.
- Acknowledge the deprecation timeline clearly — When deprecating a package or a major version, state the exact date the old version will stop receiving patches.
Once posted, announcement threads are permanent. They can be edited for corrections (edit history is tracked), but they cannot be deleted by the publisher — only admins can remove announcement threads. This ensures that historical communications remain accessible to users who relied on them.