toki/nexo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nexo/services/push-proxy/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

1.2 KiB
Raw Blame History

Mattermost Push Proxy Upstream

services/push-proxy/ is derived from the mattermost-push-proxy repository.

  • Source: https://github.com/mattermost/mattermost-push-proxy.git
  • Branch: master
  • Snapshot commit: 7852e23b8f7786d7ff1ad5062aa0a9424babd84f
  • Snapshot date: 2026-05-30
  • Snapshot source: /config/workspace/mattermost/mattermost-push-proxy/
  • Snapshot target: /config/workspace/nexo/services/push-proxy/

Tracking Mode

Current choice: source snapshot plus nexo-owned runtime image build.

Use the source snapshot as the primary baseline because nexo needs reproducible image builds, local smoke validation, and an explicit place to review FCM/APNs delivery behavior. Do not treat push-proxy as image-only while local runtime images are built from this workspace.

Image-only tracking is only a future candidate if nexo no longer needs local source-level validation, no nexo-local patch is present, and runtime image provenance can still be tied to a specific upstream commit or release artifact.

Keep nexo-specific changes outside this snapshot where possible. If a local patch is unavoidable, record its path, reason, rebase risk, and validation evidence in this file before merging the snapshot update.