toki/nexo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nexo/services/core/UPSTREAM.md
toki e82990ddff chore: upstream sync and roadmap updates 
- Update README with latest project status
- Archive upstream-runtime milestone and update roadmap
- Update Mattermost Android build configuration
- Sync upstream references for core and push-proxy services
2026-05-30 15:44:06 +09:00

2.1 KiB
Raw Blame History

Core Upstream

services/core/ is derived from the Mattermost server repository.

  • Source: https://github.com/mattermost/mattermost.git
  • Branch: master
  • Baseline tag: v11.4.2
  • Baseline commit: bcf511968217cd0f65cbead926e03260bfcd1011
  • Snapshot date: 2026-05-30
  • Snapshot source: /config/workspace/mattermost/mattermost/
  • Snapshot target: /config/workspace/nexo/services/core/

Component Baseline

Server and webapp are tracked from the same upstream repository baseline, but they should be reviewed as separate runtime surfaces when a snapshot is updated.

Component Workspace path Upstream path Baseline tag Baseline commit
Server services/core/server/ server/ v11.4.2 bcf511968217cd0f65cbead926e03260bfcd1011
Webapp services/core/webapp/ webapp/ v11.4.2 bcf511968217cd0f65cbead926e03260bfcd1011

Update Record

When the server or webapp baseline changes, update this file with:

  • upstream branch, tag, and commit SHA used for the snapshot
  • snapshot date, source clone path, and target workspace path
  • component scope: server, webapp, or both
  • patch inventory: upstream snapshot patches, nexo-local patches, and removed patches
  • validation summary or a link to the evidence document used before merge

Do not change the baseline tag or commit only because a staging clone was pulled. A new baseline is recorded after snapshot diff review and the relevant smoke checks pass.

Patch Boundary

Keep product-specific changes small and easy to compare against this baseline. Prefer compose files, workspace docs, helper wrappers, or narrowly documented compatibility patches over direct edits to upstream-owned server or webapp code.

Any nexo-local patch inside services/core/server/ or services/core/webapp/ must be listed in the update record with its path, reason, upstream rebase risk, and validation result. Existing patch-package files under services/core/webapp/patches/ are treated as part of the upstream snapshot unless the update record explicitly marks one as nexo-local.