All new code requires tests to ensure against regressions.
However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.
[X] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
This PR adds the ability for the backend to send out webhooks whenever a new package, or package version is published.
This Webhooks, as discussed on Discord, will then be sent to the Pulsar Discord Server to allow not only admins, but users to gain better insight into what's being published in real time, and lets community members show off their packages easier, or let others find new working packages easier.
Webhooks will be sent after the return is given to the user so they don't have to wait on this process.
To configure webhooks, the backend will need a username for them when sending, and will need URLs for both the package and version publishing (Although these can be the same)
Requirements
Filling out the template is required.
All new code requires tests to ensure against regressions.
[X] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
This PR adds the ability for the backend to send out webhooks whenever a new package, or package version is published.
This Webhooks, as discussed on Discord, will then be sent to the Pulsar Discord Server to allow not only admins, but users to gain better insight into what's being published in real time, and lets community members show off their packages easier, or let others find new working packages easier.
Webhooks will be sent after the return is given to the user so they don't have to wait on this process.
To configure webhooks, the backend will need a username for them when sending, and will need URLs for both the package and version publishing (Although these can be the same)