The flasher's versions become feed-driven (/releases on the firmware
proxy Worker): config.json's observer entries turn into github release
defs with no embedded filenames, so update-firmware.py would find zero
matches and exit nonzero — remove the call before the config conversion
lands. Changelog notes now ride the release body via a non-fatal
'gh release edit --notes-file firmware-notes.html' in the publish step.
MUST land before the flasher config.json conversion, or the next build
goes red at Update Flasher Config.
Workflow-only commit: pushing this triggers no build.
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.
Flip gen-slim-manifests.py to its new --bin-dir mode (flasher repo PR #1):
the slim OTA manifests are now generated from out/ — the assets actually
uploaded to the release — instead of the config.json entries, which the
/releases feed migration will convert to github release defs. STATIC_PATH
joins the workflow env; it must stay consistent with config.json's
staticPath.
Also add observer-firmware alongside mqtt-bridge-implementation-flex in
both push triggers, ahead of renaming the branch: GitHub does not rewrite
branch filters on rename, and a rename with only the old name in the
filter silently stops production publishing. The old name is dropped once
a publish is verified on the new one.
Workflow-only commit (.github/** is in paths-ignore): pushing this
triggers no build.
Updated the build-observer-firmwares workflow to exclude .partsig files
when uploading release assets. This change prevents issues with the
slim-manifest generator and ensures that only relevant firmware files
are published, improving the integrity of the release process.
Implemented functionality to generate and compare partition-table
signatures during OTA updates. This enhancement ensures that the
target build's partition layout matches the device's actual layout,
improving the reliability of OTA updates and preventing issues
related to partition changes.
Enhanced the firmware versioning system by appending a build number
suffix when available, allowing for better tracking of published builds.
This change improves the OTA update process by providing clearer
versioning information in the embedded firmware string.
Updated the build-observer-firmwares.yml to improve the asset pruning
logic during the release process. The workflow now retains the most
recent build hashes to prevent 404 errors for assets that may still
be requested during build cycles. This change ensures a smoother
release experience by maintaining necessary assets while cleaning
up older ones.
Updated the build-observer-firmwares.yml to improve the handling of rolling releases. The workflow now creates a release only if it doesn't already exist, preventing tag conflicts. Additionally, it uploads build artifacts while replacing existing assets and prunes older assets to maintain a clean release. This change enhances the reliability and efficiency of the release process.
agessaman