File tree Expand file tree Collapse file tree 1 file changed +6
-8
lines changed
docs/contributing/dependencies Expand file tree Collapse file tree 1 file changed +6
-8
lines changed Original file line number Diff line number Diff line change @@ -281,15 +281,13 @@ A typical dependency workflow involves the following steps:
2812813 . Review the release notes of each dependency, for each released version between the current and
282282 the proposed upgrade. Identify if there are any deprecations or breaking changes affecting our
283283 code.
284- 1 . For ** breaking changes** , either resolve them yourself, or for major changes, coordinate with
285- the other teams.
286- 2 . For ** deprecations** , create high priority Jira tickets on the affected teams' backlogs with a
287- due date at least one sprint before the next scheduled major release of the dependency.
284+ - For ** breaking changes** , either resolve them yourself, or for major changes, coordinate with
285+ the other teams.
286+ - For ** deprecations** , create high priority Jira tickets on the affected teams' backlogs with a
287+ due date at least one sprint before the next scheduled major release of the dependency.
2882884 . Verify CI status.
289-
290- - This may also include re-running any failed workflows due to insufficient permissions when
291- Renovate created the pull request.
292-
289+ - This may also include re-running any failed workflows due to insufficient permissions when
290+ Renovate created the pull request.
2932915 . If test coverage is lacking, check out locally and manually confirm a few key areas.
2942926 . Review the proposed code changes and approve the PR.
2952937 . Update the ticket to include testing notes for QA.
You can’t perform that action at this time.
0 commit comments