Open ben851 opened 6 months ago
As a developer of notify I want to be reasonably sure that dependency updates to notification-utils will not break the system.
We need to be able to update our dependencies on a regular basis without creating system outages.
Investigate improvements to the notification-utils PR CI to catch these types of dependency failures in the future.
Close to the business, what's the value?
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
Description
As a developer of notify I want to be reasonably sure that dependency updates to notification-utils will not break the system.
WHY are we building?
We need to be able to update our dependencies on a regular basis without creating system outages.
WHAT are we building?
Investigate improvements to the notification-utils PR CI to catch these types of dependency failures in the future.
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps