docs: Add compatibility considerations to issue and change templates

endojs · Jan 22, 2024 · 643f0e3 · 643f0e3
1 parent a22c936
commit 643f0e3
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/.github/ISSUE_TEMPLATE/work_item.md b/.github/ISSUE_TEMPLATE/work_item.md
@@ -13,6 +13,8 @@ assignees: ''
 
 ## Security Considerations
 
+## Compatibility Considerations
+
 ## Scaling Considerations
 
 ## Test Plan

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -15,6 +15,10 @@ refs: #XXXX
 
 <!-- Does this change introduce new assumptions or dependencies that, if violated, could introduce security vulnerabilities? How does this PR change the boundaries between mutually-suspicious components? What new authorities are introduced by this change, perhaps by new API calls?  -->
 
+### Compatibility Considerations
+
+<!-- Does this change break any prior usage patterns? Does this change allow usage patterns to evolve? -->
+
 ### Scaling Considerations
 
 <!-- Does this change require or encourage significant increase in consumption of CPU cycles, RAM, on-chain storage, message exchanges, or other scarce resources? If so, can that be prevented or mitigated? -->