Repository navigation
Prepare 3.1.17 source identity and release checkpoint - #289
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare the next stable version without creating its tag, draft release, release workflow run, service deployment or device flash.
3.1.17and current-main custom identity to3.1.17-main-custom.v3.1.16; no nonexistentv3.1.17ref is exposed.Integration Baseline
All six requested PRs are merged: #276, #277, #283, #284, #285 and #288. #217 and #209 remain excluded.
The actual merged baseline is
dcb53ac6687d8b7c4a6197a4aee5210e57160814. Its treeaee36574dcb7f63088bba42d718735041ad70d31exactly matches the isolated six-PR validation tree. #284's resolved head passed combined standard/grinder/LittleFS, Energy, native, Python/Worker/configurator and minimal-custom checks (runs 44732476358, 44732476401 and 44732476345).Validation
3.1.17source bump. Includes 150 drift cases, tare/ADC/grinder, charger/Energy, App Text deadlines and real U8g2 layout, menu/navigation/AceButton, About and release/nightly contracts.3.1.17-main-customwhile retaining old versions/default.Stop Boundary
Do not tag or release from this PR. The intended later release is
v3.1.17withprevious_tag=v3.1.16.Tag-specific custom support and public-default activation are prepared as held draft follow-ups #290 and #291; neither is merged.
3.1.17-customsupport requires the real approved tag; default activation additionally requires publication and service readiness. Historical refs/recovery assets must remain intact.Production signing, hosted main/tagged artifact identity, exact-candidate hardware/OTA acceptance and publication approval remain explicit gates in the checkpoint. Secret/variable names were verified, not their private values or production signing behavior. No ESP-IDF library rebuild or flashing was performed locally.
Final Pre-Tag Freeze
1efca39865dea78c7da0b15c845da6ab30228e8f, treed96f10609e0ffcb075b673e7e89ab9aaecb5c935. The reviewed preparation tree exactly matches it.FW: 3.1.17, revision1efca3). They are not official signed release artifacts and were not flashed.v3.1.17tag must target the approved main SHA above, not either rollout draft. The latest actual release remainsv3.1.16.Stopped before any tag, draft release, release workflow dispatch, firmware publication, Worker deployment or hardware flash. Normal automatic Pages deployment followed the main merges without activating v3.1.17. Real-tag validation, production signing/hosted-artifact acceptance and exact-candidate physical acceptance remain explicit gates. No additional source commit is needed just to record this evidence.