GHAzDO: Add re-run behavior note to stale pipeline alert cleanup

laurajjiang · laurajjiang · commit a07baf6230ee · 2026-03-30T11:07:07.000-07:00
diff --git a/release-notes/2026/includes/ghazdo/sprint-271-update.md b/release-notes/2026/includes/ghazdo/sprint-271-update.md
@@ -47,4 +47,4 @@ These events provide visibility into when and by whom security features are conf
 
 Advanced Security now automatically hides alerts associated with pipeline configurations that have not been run in over 90 days. Alert fingerprints in Advanced Security are tied to specific pipeline configurations, so when a pipeline job or stage is changed, previously associated alerts can become orphaned if they were also resolved as part of the pipeline update.
 
-With this change, alerts linked to stale pipeline configurations are automatically hidden, reducing noise and ensuring that your alert results reflect your current CI/CD setup. You can also use the delete analysis API to manually hide alerts associated with specific pipeline configurations that are no longer in use.
+With this change, alerts linked to stale pipeline configurations are automatically hidden, reducing noise and ensuring that your alert results reflect your current CI/CD setup. If you re-run a previously stale pipeline configuration after its alerts have been hidden, any previously open alerts will return as active, open alerts. You can also use the delete analysis API to manually hide alerts associated with specific pipeline configurations that are no longer in use.

Original file line number	Diff line number	Diff line change
`@@ -47,4 +47,4 @@ These events provide visibility into when and by whom security features are conf`
`47`	`47`
`48`	`48`	`Advanced Security now automatically hides alerts associated with pipeline configurations that have not been run in over 90 days. Alert fingerprints in Advanced Security are tied to specific pipeline configurations, so when a pipeline job or stage is changed, previously associated alerts can become orphaned if they were also resolved as part of the pipeline update.`
`49`	`49`
`50`		`-With this change, alerts linked to stale pipeline configurations are automatically hidden, reducing noise and ensuring that your alert results reflect your current CI/CD setup. You can also use the delete analysis API to manually hide alerts associated with specific pipeline configurations that are no longer in use.`
	`50`	`+With this change, alerts linked to stale pipeline configurations are automatically hidden, reducing noise and ensuring that your alert results reflect your current CI/CD setup. If you re-run a previously stale pipeline configuration after its alerts have been hidden, any previously open alerts will return as active, open alerts. You can also use the delete analysis API to manually hide alerts associated with specific pipeline configurations that are no longer in use.`