From 443d3418785f89efb07aca05cedd21831002f1fe Mon Sep 17 00:00:00 2001
From: ephys <zoe@ephys.dev>
Date: Mon, 24 Jan 2022 19:47:34 +0100
Subject: [PATCH] docs: document breaking change from #13951

---
 docs/manual/other-topics/upgrade-to-v7.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/docs/manual/other-topics/upgrade-to-v7.md b/docs/manual/other-topics/upgrade-to-v7.md
index 07646f672738..91243ebdf047 100644
--- a/docs/manual/other-topics/upgrade-to-v7.md
+++ b/docs/manual/other-topics/upgrade-to-v7.md
@@ -36,3 +36,23 @@ sequelize.connectionManager.getConnection({ type: 'read' });
 Sequelize v7 fully supports MS SQL Server 2017 (version 14) onwards, up from 2012 (version 13) in
 Sequelize v6, as this matches Microsoft's own [mainstream support](
 https://docs.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-life-overview?view=sql-server-ver15#lifecycle-dates).
+
+### Overridden Model methods won't be called internally
+
+`Model.findOne` and `Model.findAll` are used respectively by `Model.findByPk` and `Model.findOne`.
+This is considered an implementation detail and as such, starting with Sequelize v7,
+overrides of either of these methods will not be called internally by `Model.findByPk` or `Model.findOne`.
+
+In other words, doing this won't break:
+
+```typescript
+class User extends Model {
+  static findOne() {
+    throw new Error('Do not call findOne');
+  }
+}
+
+// this would have thrown "Do not call findOne" in v6
+// but it works in v7
+User.findByPk(1);
+```