Skip to content

Upstream normative change detected #2

Description

@github-actions

A normative file changed upstream. The protocol baseline pinned in
conformance/PROTOCOL_BASELINE no longer matches upstream, and the
difference is in a file that defines behaviour rather than in
implementation or surrounding docs.

Do not advance the baseline without reading the diff. The tracking
policy in conformance/PROTOCOL_BASELINE explains why the pin is held.

Baseline: v1.8.2 @ 05366539
Upstream advanced to 7041032b
CHANGED docs/protocol.md (+19 -2)
CHANGED docs/configuration.md (+33 -5)
CHANGED docs/compatibility.md (+9 -5)
Normative files changed. A human must assess before PROTOCOL_BASELINE is updated.
Inspect the diff:
git -C /home/runner/work/Somewhere-Android/Somewhere-Android/upstream-nowhere diff 05366539 7041032b346d713f3c6bf25db9e3d7b2a41e1315 -- docs/protocol.md
After assessing:
1. re-run scripts/verify-vectors.py to check the fixed vectors still hold;
2. re-run scripts/smoke-local.sh to check end-to-end still works;
3. update UPSTREAM_COMMIT and the notes in PROTOCOL_BASELINE.

Run: https://github.com/NodePassProject/Somewhere-Android/actions/runs/33504105250

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions