Skip to content

fix: light up a peer's own other-slot chip for dynamic TG activity too - #69

Merged
ce5rpy merged 2 commits into
masterfrom
develop
Jul 31, 2026
Merged

fix: light up a peer's own other-slot chip for dynamic TG activity too#69
ce5rpy merged 2 commits into
masterfrom
develop

Conversation

@ce5rpy

@ce5rpy ce5rpy commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Release PR: develop -> master. Includes the dynamic TG own-other-slot chip display fix (#68).

ce5rpy and others added 2 commits July 31, 2026 07:33
peer_downlink_display_slots()/_peer_subscribed_to_tg() only checked
TS1_STATIC/TS2_STATIC OPTIONS lists, so a peer with a TG active only via
a dynamic UA session (SINGLE=0/1) on the other slot never got its own
TX-style chip lit there, and dual-slot chip updates missed dynamic-only
subscriptions. Mirrors the server-side dual-slot delivery fix (PR #66/#67
in new-adn-server) on the monitor's display side.
fix: light up a peer's own other-slot chip for dynamic TG activity too
@github-actions

Copy link
Copy Markdown
Contributor

Release PR — merge method

Commits listed on this PR: 2 (file diff may be smaller — that is normal when squash releases stacked up).

Required

Merge with Create a merge commit. Do not use Squash and merge.

Why

  • Squash on master creates new commit SHAs; develop keeps the original squash commits from feature PRs.
  • The next release PR then lists old fixes again even though master already has them.
  • Merge commit keeps the same SHAs on both branches; CI fast-forwards develop to master after chore(release) — no force-push, local git pull on develop still works.

One-time cleanup

If this PR lists commits from earlier releases (2.0.4, 2.0.5, …), merge once with merge commit; post-release sync realigns develop with master automatically.

@ce5rpy
ce5rpy merged commit 6d42fd0 into master Jul 31, 2026
2 checks passed
@ce5rpy
ce5rpy deleted the develop branch July 31, 2026 11:45
@ce5rpy
ce5rpy restored the develop branch July 31, 2026 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant