@
chore: back-merge main into dev (reconcile release version stamps) Absorbs main (previous release) into dev ahead of the next release. All conflicts were VERSION-stamp comments/tags in manifests, SECURITY.md and issue-branch.yml — kept dev's current line. No functional changes. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @
This commit is contained in:
+2
-5
@@ -1,6 +1,8 @@
|
||||
# Changelog
|
||||
## [Unreleased]
|
||||
|
||||
## [02.60.00] --- 2026-07-12
|
||||
|
||||
|
||||
## [02.59.00] --- 2026-07-12
|
||||
|
||||
@@ -62,8 +64,3 @@
|
||||
|
||||
### Fixed
|
||||
- Package `postflight` now removes the orphaned `com_component-mokosuitebackup` registration (stray extension record, admin menu items, schema rows, and `administrator/` folder) left behind by the old "Type - Name" component `<name>` — self-healing on update so affected sites reconcile to the real `com_mokosuitebackup`. (#213 follow-up)
|
||||
|
||||
## [02.56.08] --- 2026-07-05
|
||||
|
||||
### Fixed
|
||||
- Component manifest `<name>` reverted to the element-safe `MokoSuiteBackup`. The "Type - Name" convention derived element `com_component-mokosuitebackup`, registering a duplicate component and leaving the real `com_mokosuitebackup` orphaned on the old version. (#213)
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
/* 02.60.00 — no schema changes */
|
||||
Reference in New Issue
Block a user