ci: drop retired mqtt-bridge-implementation-flex trigger name
The rename to observer-firmware is verified: the rename's own push event ran both workflows on the new name (branch creation bypasses path filters), sync-flasher-content pushed to the flasher repo, and the production publish completed on observer-firmware. The transition dual trigger is no longer needed. Also update the MQTT_INTERNALS.md prose reference to the old branch name. Workflow+docs-only commit: pushing this triggers no build.
This commit is contained in:
1 parent
e06bd756ee
commit
80b4e4051c
3 files changed
+2
-9
No files matched your search
@@ -7,10 +7,6 @@ on:
|
||||
workflow_dispatch:
|
||||
push:
|
||||
branches:
|
||||
# Both names during the flex -> observer-firmware rename: GitHub does not
|
||||
# rewrite branch filters on rename, so the old name is kept until a
|
||||
# publish is verified on the new one (then it gets dropped).
|
||||
- mqtt-bridge-implementation-flex
|
||||
- observer-firmware
|
||||
# Only rebuild firmware when something that affects the binaries changes.
|
||||
# Docs, the changelog, the changelog generator, CI files, and repo-meta
|
||||
|
||||
@@ -14,10 +14,6 @@ on:
|
||||
workflow_dispatch:
|
||||
push:
|
||||
branches:
|
||||
# Both names during the flex -> observer-firmware rename: GitHub does not
|
||||
# rewrite branch filters on rename, so the old name is kept until a
|
||||
# publish is verified on the new one (then it gets dropped).
|
||||
- mqtt-bridge-implementation-flex
|
||||
- observer-firmware
|
||||
paths:
|
||||
- '**.md'
|
||||
|
||||
+2
-1
@@ -81,7 +81,8 @@ default; a newer, longer one is truncated harmlessly.
|
||||
- **`/mqtt_prefs`** — if the file has the version header it is read directly. Otherwise
|
||||
it is a legacy headerless file and its layout is detected by size: pre-slot
|
||||
(`OldMQTTPrefs`), 3-slot (`ThreeSlotMQTTPrefs`), or the 6-slot layout shipped on
|
||||
`mqtt-bridge-implementation-flex` (`Legacy6SlotMQTTPrefs`). Each is field-copied into
|
||||
`observer-firmware` back when it was named `mqtt-bridge-implementation-flex`
|
||||
(`Legacy6SlotMQTTPrefs`). Each is field-copied into
|
||||
the current compact `MQTTPrefs` and re-saved with the version header — which also
|
||||
drops the vestigial `_legacy_*` fields the flex layout carried mid-struct. This is a
|
||||
one-time rewrite; every deployed device performs it on its first boot of versioned
|
||||
|
||||
Reference in new issue
Block a user