Skip to content

feat: release 2.4 - #61

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

feat: release 2.4#61
ce5rpy merged 2 commits into
masterfrom
develop

Conversation

@ce5rpy

@ce5rpy ce5rpy commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • OpenBridge page shows keepalive connected status (flag, online/offline dot) from server dashboard_state.
  • Stream chip debounce raised to 0.5s on the OpenBridge view.

ce5rpy and others added 2 commits July 13, 2026 23:14
Map dashboard_state connected into CTABLE, show country flag and online/offline
dot before each OBP name, and raise stream chip debounce to 0.5s.
feat: OBP keepalive status on OpenBridge page
@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 fac80a5 into master Jul 15, 2026
2 checks passed
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