tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

DOC Clarify which branch to target for third-party dependency changes (#10216)

Browse Source
This commit is contained in:
Steve Boyd 2022-02-08 17:44:09 +13:00 committed by GitHub
parent 756e67d746
commit 4044573ae7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/en/05_Contributing/01_Code.md
View File

@ -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. 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 ### The Pull Request Process