Skip to content

Commit

Permalink
Fix PLONE_BACKEND_PATCH_VERSION
Browse files Browse the repository at this point in the history
Add latest versions to In-place migrations
  • Loading branch information
stevepiercy committed Dec 20, 2024
1 parent 4f06837 commit b9056cf
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/backend/upgrading/intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,8 +118,8 @@ If you are at Plone 2.5 and want to upgrade to the latest Plone 6, you should ap

- First upgrade from Plone 2.5 to the latest Plone 3 version (3.3.6).
- Then upgrade from Plone 3 to the latest Plone 4 version (4.3.20).
- Then upgrade from Plone 4 to the latest Plone 5 version.
- Then upgrade from Plone 5 to the latest Plone 6 version.
- Then upgrade from Plone 4 to the latest Plone 5 version (5.2.15).
- Then upgrade from Plone 5 to the latest Plone 6 version ({PLONE_BACKEND_PATCH_VERSION}).


(introduction-upgrade-strategies-export-import-migrations-label)=
Expand Down
2 changes: 1 addition & 1 deletion docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -441,7 +441,7 @@ def source_replace(app, docname, source):
# Dict of replacements.
source_replacements = {
"{PLONE_BACKEND_MINOR_VERSION}": "6.0",
"{PLONE_BACKEND_PATCH_VERSION}": "4",
"{PLONE_BACKEND_PATCH_VERSION}": "6.0.14",
}

# Finally, configure app attributes.
Expand Down

0 comments on commit b9056cf

Please sign in to comment.