Version 0.63.0
New features
Verify GitLab webhooks with a signing token
GitLab webhooks can now use a signing token. Generate one in GitLab, paste it into the Webhook card on your GitLab integration, and every push GitLab sends is checked for authenticity before it updates your catalog. You can keep your existing secret token while you switch over, so no pushes are missed.
Improvements
Improved security around integration settings
We tightened how integration secrets are handled, so they stay private to the connections that use them.
Webhook URL and secret in one place
A Git integration's page now has one Webhook card with the endpoint URL, a copy button, and the button to rotate the webhook secret. Everything you need to connect your Git provider's webhook is in one spot.
Bug fixes
Refresh syncs your descriptor, and failed syncs explain themselves
Select Refresh on an entity's Repository tab and its componecat.yaml is read again along with the repository details, so an edit shows up right away. When a descriptor can't be applied to the entity it describes, that entity now tells you why, instead of suggesting you turn ingestion on. You can also name a descriptor's owner by the team's ID as well as by its name.