- Documentation improvements:
- Added documentation for Semaphore's configuration environment variables and how to configure Semaphore's GitHub App integration.
- Added a Redoc subsite for the API documentation.
- Summaries will now be interpreted using the first provided body paragraph unless defined in the summary property in the post metadata
- Broadcast messages can now have a "category," which you can set in the YAML front-matter.
The default behavior is
category: maintenance
, which matches the idiomatic use of broadcasts up to this point. However, you can also setcategory: info
to publish informational messages, like general announcements. The category is present in the JSON data model for broadcasts published from the API. Note that "category" is an enumeration: onlyinfo
ormaintenance
are allowed values. - Semaphore is now cross-published to the GitHub Container Registry,
ghcr.io/lsst-sqre/semaphore
. - Semaphore now runs on Python 3.10.
This release prevents the /v1/broadcasts
endpoint from showing disabled messages.
This is the initial working version of Semaphore, featuring the ability to source broadcast messages from GitHub, and get updates for those messages through GitHub webhooks.