Changelog
Version 1 · Create the canonical changelog for delivered QWebHub v1.2.0 through v1.2.2 changes.
QWebHub Changelog
v1.2.2 — 2026-08-20
Changed
- Replaced the overly brown light theme with a soft neutral-grey palette.
- Kept the main background visibly darker than white while using lighter cards and inputs for clear separation.
- Retained the stronger light-theme text and label weights introduced in v1.2.1.
- Updated the shared theme asset version so browsers load the corrected palette.
- Added shared non-secret FTP host and username defaults to the all-project Odin deployment launcher.
- Updated shared-static configuration and harness documentation to use the
optimized
Global Assests/Iconsset instead of source artwork.
Scope
-
Changes are confined to the QWebHub repository. The shared middleware applies the selected theme across mounted modules, while the deployment and static configuration updates support all integrated projects.
-
GitHub delivery: PR #3, merge commit
0509d03.
v1.2.1 — 2026-08-19
Added
- Added a QWebHub light/dark selector using the existing
qdb-themepreference. - Added a QWebHub-owned theme bootstrap to every integrated HTML module response.
Changed
- The selected theme now follows users between QWebHub and all mounted modules.
- Replaced the stark light background with a deeper warm cream
#ebe3d8. - Increased light-theme text weight and contrast for users with reduced vision.
- Updated cards, inputs, borders, hover states, and title bands to warmer cream tones.
Scope
-
Only the QWebHub repository was changed; module repositories were not modified.
-
GitHub delivery: PR #2, merge commit
df928f9.
v1.2.0 — 2026-08-18
Added
- Added a versioned remote SHA-256 deployment manifest per remote project root.
- Added bounded parallel FTP uploads with 1-8 workers and one connection per worker.
- Added one bounded retry for transient connection failures.
- Added read-only
--verify-remoteintegrity checks. - Added accurate connected
--dry-runand explicit--offline-dry-runmodes.
Changed
- Deployment skip decisions now require SHA-256 manifest matches rather than FTP size or time matches.
- QWebHub is now the source of truth used by all supported module launchers.
- Deploy-all remains project-sequential and stops immediately when a project fails.
- The manifest is published only after every planned upload succeeds.
Fixed
- Fixed false
SKIPresults when changed local and remote files have equal byte sizes. - Fixed deployment batches continuing into later projects after an FTP failure.
Verified
- Unit and fake-FTP integration tests cover manifests, same-size changes, bounded concurrency, independent worker connections, retry, failed-manifest suppression, password precedence, dry-run safety, and remote drift detection.