Skip to content

Commit 06e4bd1

Browse files
committed
Added point about packages
1 parent 129d463 commit 06e4bd1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

16/umbraco-cms/fundamentals/setup/upgrading/downgrades-and-rerunning-migrations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: Discusses the possibility of downgrading to a previous version, alo
88

99
Downgrades are not a supported feature of the Umbraco product.
1010

11-
The reason for this is the Umbraco migration scheme only supports upward migrations.
11+
The primary reason for this is the Umbraco migration scheme only supports upward migrations.
1212

1313
When updating to a new version, often there are migrations to run that will make changes to Umbraco schema and data. This is done to bring the database to a state that will support the functionality of the version being upgraded to.
1414

@@ -18,6 +18,8 @@ Given that, it can't be guaranteed that a database from a later version will wor
1818

1919
If you wish to downgrade to an earlier version of Umbraco, it's best to also revert to a compatible database backup. You will need one from the version you are downgrading to.
2020

21+
Other factors that may preclude downgrading include packages you may be using. They may not be compatible with the lower version or support downgrades themselves.
22+
2123
## Particular downgrades are possible and safe
2224

2325
That said, between some versions, a downgrade may be possible and perfectly safe. There may be no migrations that run between them. Or, as is often the case, the migrations are backward compatible (for example adding a new, nullable field to a database table).

0 commit comments

Comments
 (0)