xinyouhe/cms-SiteForge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

upgrade: adopt V8.21.3 (V8.13→8.21.3: P5 SFTP/S3, P6 multilingual, editor overhaul, enterprise hardening)

Browse Source 
Overlay ~150 upstream items onto our V8.12 base, preserving trade-pro
theme, registry tests, and design docs. Re-applied our patch set
(discovery/env_for/blocks.css/type-mapping/theme_color/frontend entries,
test_theme_pro_v3 mods) — all anchors survived upstream evolution.

New platform enhancement (fixes upgrade-introduced regression):
multilingual.site_locale now honors settings_json.locale, plus
PUT /api/i18n/sites/{id}/locale — standalone English sites get
<html lang='en'> under the V8.15 locale-rewrite pipeline.

compose: adopt V8.21.3 (image 8.21.3-dev.1, /api/ready probes, MySQL/S3
env) with project name pinned to siteforge-v8-10 (data volumes).

Tests: 356 passed / 11 failed — all 11 confirmed pre-existing in
pristine V8.21.3 on this host (10 upstream Windows env + our build test
now green after locale fix). Patch registry updated in plan doc.

Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
浅念
2026-10-23 12:31:03 +08:00
parent 257c89e159
commit 601451f22b
218 changed files with 10441 additions and 628 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.env.example
+7 -3
View File
@@ -13,9 +13,9 @@ SITEFORGE_PG_PASSWORD=GENERATE_STRONG_URL_SAFE_PASSWORD
SITEFORGE_PG_DB=siteforge
# Must be HTTPS and trusted deployment endpoint; never set to an arbitrary user URL
SITEFORGE_DEPLOY_STAGING_URL=
SITEFORGE_DEPLOY_STAGING_SECRET=
SITEFORGE_DEPLOY_STAGING_SECRET_REF=
SITEFORGE_DEPLOY_PRODUCTION_URL=
SITEFORGE_DEPLOY_PRODUCTION_SECRET=
SITEFORGE_DEPLOY_PRODUCTION_SECRET_REF=
# Release agent is deployed as an isolated service on the receiving host
SITEFORGE_DEPLOY_SECRET=
@@ -34,5 +34,9 @@ SITEFORGE_MYSQL_CA_FILE=
# SITEFORGE_MYSQL_READ_USER=<use Docker secret instead>
# SITEFORGE_MYSQL_READ_PASSWORD=<use Docker secret instead>
# Preferred remote signing secret reference (instead of plaintext _SECRET)
# SITEFORGE_DEPLOY_STAGING_SECRET_REF=env:SITEFORGE_DEPLOY_STAGING_SECRET
# SITEFORGE_DEPLOY_STAGING_SECRET_REF=env:SITEFORGE_STAGING_TOKEN
# SITEFORGE_STAGING_TOKEN=<independent random 32+ char token, delivered only to Worker>
# SITEFORGE_DEPLOY_PRODUCTION_SECRET_REF=file:siteforge_deploy_production
# Mount /run/secrets/siteforge_deploy_production in Worker using a private Compose override.
# Set SITEFORGE_DEPLOY_SECRET_REF=file:siteforge_deploy_production in the remote Agent.
# Never reuse the same token between staging and production.