From 4044573ae776c7fbcb5f8fe7e1acd56312741dd8 Mon Sep 17 00:00:00 2001 From: Steve Boyd Date: Tue, 8 Feb 2022 17:44:09 +1300 Subject: [PATCH] DOC Clarify which branch to target for third-party dependency changes (#10216) --- docs/en/05_Contributing/01_Code.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/en/05_Contributing/01_Code.md b/docs/en/05_Contributing/01_Code.md index 8aeae5aff..5a10a469c 100644 --- a/docs/en/05_Contributing/01_Code.md +++ b/docs/en/05_Contributing/01_Code.md @@ -111,6 +111,7 @@ Silverstripe CMS public APIs explicitly exclude: Other entities might be considered to be included or excluded from the public APIs on case-by-case basis. +Any updates to third party dependencies in composer.json should aim to target the default branch for a minor release if possible. Targeting a patch release branch is acceptable if updating dependencies is required to fix a bug. ### The Pull Request Process