Hi @Marvin, while doing prefect upgrades how is the upgrades for notifications block handled ?

Here's the distilled information about how Prefect handles upgrades for notification blocks: 1. Migration Handling for Existing Blocks: - If you have existing blocks created before the upgrade, you can migrate them to the new version by adding the required missing values. - You can bypass validation for local Block classes while loading old versions and set new fields to appropriate values before overwriting the old block values. - For more details, you can check the registering and migrating blocks section here: Register and Migrate Blocks. 2. Database Migration Commands: - Upgrades and downgrades for Prefect might include database migrations. - Commands include

prefect server database upgrade -y

for upgrading and

prefect server database downgrade -y -r <revision>

for downgrading. - Detailed commands and further guidance can be found here: Database Migrations. 3. Notifications After Upgrades: - For Prefect Cloud, there are options for automation notifications with additional controls compared to self-hosted setups. - Notifications trigger alerts based on the state changes in your flow and task runs, enabling you to manage and respond to those changes efficiently. - Further documentation here: Notifications in Prefect. For specific implementation steps or troubleshooting tips, it might be useful to scour through related GitHub pull requests and issues, like this one where notifications docs links were updated: GitHub PR 11391. It's essential to keep an eye on Prefect-specific release notes and documentation for any subtle changes or additional commands introduced in new versions.