chore: v2.7.4 - #191
Merged
Merged
chore: v2.7.4#191
Conversation
SIMUT_VERSION 2.7.3 -> 2.7.4, and everything that names the current release catches up: CHANGELOG (en, pt-BR), the three READMEs, both user manuals, the docs index, the landing page in its three languages, and the product manual (chapters 1, 3, 4, 5, 6, 8, 9, 13, 14, 26, 28 and 30, appendix C), regenerated. v2.7.4 is #175 (a sensor scan no longer breaks a hardware-I2C BMP280), #182 (four settings nothing reads no longer restart), #184 and #190 (the touch panel's routes and its Configuration section leave the alpha and the Air), #181 (dead code), the build configurator (#185-#188), and the feature-model groundwork (#168-#174, #180). The manuals gain what those changed: - chapter 5: the configuration groups (`logging` and `display_pin` have no field left, `sensing` is only the DS18B20 resolution; Amostra (ms) and Registro Local save without a restart); the Touch Calibration section only on the release. The page has seven sections, not six: the list had missed v2.7.3's Restart; - chapter 6: the sample interval's restart column; the scan hands the hardware-I2C pins back, but GP16 still is not, so the restart advice stays; - chapter 26: the alpha and the Air have 54 routes, not 56 (on the bench, the eight panel and TLS routes answer 404 with no session, like an unknown path); the panel-only rows are marked; `logging` and `display_pin` leave the restart classes; - chapter 3 gains a section on the build configurator; chapter 30's row for the touch reset on an alpha now says the section is not there. Stale before this release, fixed here: - the landing page's third release card still said "On main - next release" about v2.7.2's Air clock and telemetry batches. It is gone, and a v2.7.4 card leads; - the READMEs said the alpha's 16x2 LCD had never been on glass. It was, today (below). They also counted 410 host test cases in 7 suites; CI runs 420 in 8 (185+63+33+45+40+16+9+29). The pt-BR and es-ES security sections said 61 routes, 51 gated; check_authz.py counts 62 and 52; - ConfigApply.h: four enum comments described fields #182 moved out (CFG_NET's "HTTPS", CFG_SENSING's cadence, and CFG_LOGGING and CFG_PIN, which have no field left). Comment-only, same line count: the release and alpha .uf2 built before and after the edit are byte-identical (afa40005, ceda033a); - flash_budget.json: #181 and #184 moved 'measured' without moving 'measured_at_commit', which still described #175. Flash, all six built locally at this commit: used 997,980 release, 1,003,380 test, 1,011,036 test_https, 1,000,156 asserts, 963,308 alpha, 1,003,144 air, every one within budget. 'measured' moves for test only (+8, #190's re-stamp of the pages); budgets unchanged. Against the published v2.7.3 .bin: release -240 B, alpha and air the same size to the byte. The configurator's base sizes (feature_costs.json) are these same figures. Bench (details in the CHANGELOG): the release candidate, built from main before #190. The test image passed the web suite 87/0, the console modes, five sensors, a scan with the BMP280 still reading 90 s later, the rehearsed commit, both touch-panel routes and a panel capture. The release image ran 10 min with no restart. Air and alpha booted with five sensors. The version bump was flashed: the console and the login page say 2.7.4. On the alpha with an HD44780 16x2 wired in parallel, the maintainer confirmed on the glass the boot screen with the version and the progress bar, the connected screen with the IP, and the sensor carousel with the slot and the Wi-Fi level. #190's alpha image passed 11/11 on /config. Gates run locally: scan_secrets, gen_logcodes --check, check_authz, check_license, check_angulo, check_fsguard, check_air_consistency, gen_features --check, check_features, check_feature_sprawl, test_configurator_rules, test_build_custom, test_configurator_page, test_webui_feature_routes, test_h5_day_merge, build_manual --check (1,732 internal links, none broken), and the eight native suites (420). The landing page's scripts parse, and every data-i18n key has a pt and an es entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jq4auDQppGzmAx1gLKn1z3
The changelog's groundwork paragraph named #168-#174 and #180 and left out three merged since v2.7.3 that belong there: the sensor families made switchable in the panel's code (#176, #178) and each feature's savings measured and held nightly (#179). #177 and #183 are documentation and a comment, with nothing to report. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jq4auDQppGzmAx1gLKn1z3
MODELO_DE_RECURSOS.md quotes the product manual's chapter 9 twice (R-R2 and the net.ap_auto row). The first was updated with the manual; this is the second, still saying 'v2.7.1 a v2.7.3'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jq4auDQppGzmAx1gLKn1z3
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.
What
SIMUT_VERSION2.7.3 → 2.7.4. Everything that names the current release catches up:What v2.7.4 ships
What the manuals gain
logginganddisplay_pinhave no field left, andsensingis only the DS18B20 resolution.logginganddisplay_pinleave the restart classes.Stale before this release, fixed here
check_authz.pycounts 62 and 52.ConfigApply.h. Four enum comments described fields that chore: P0 stop four dead config fields from forcing a needless reboot #182 moved out:CFG_NETstill said HTTPS,CFG_SENSINGstill named the cadence, andCFG_LOGGINGandCFG_PINhave no field left. The fix touches comments only, on the same number of lines: the release and alpha.uf2built before and after are byte-identical (afa40005,ceda033a).flash_budget.json. chore: P0 remove dead code — unregistered staging selftest + unreachable stats screen #181 and feat: P2 routes seam — /api/themes and /api/reset_touch_cal register TFT-only #184 movedmeasuredwithout movingmeasured_at_commit, which still described fix: a sensor scan no longer breaks a hardware-I2C BMP280/BME280 #175.Flash
All six images were built locally at this commit, and each is within its budget.
measuredmoves for test only: +8, from fix: the touch-calibration section only on images with a touch panel #190 re-stamping the pages..bin: the release is 240 B smaller, and the alpha and the Air are the same size to the byte.feature_costs.json) are these same figures.Bench
The release candidate was built from
mainbefore #190./config11/11Found on the bench and pre-existing: #189 (a chunked reply occasionally loses its framing; v2.7.3 does the same). It is listed under Known.
Gates run locally
scan_secrets,gen_logcodes --check,check_authz,check_license,check_angulo,check_fsguard,check_air_consistency,gen_features --check,check_features,check_feature_sprawl,test_configurator_rules,test_build_custom,test_configurator_page,test_webui_feature_routes,test_h5_day_merge.build_manual --check: 1,732 internal links, none broken.data-i18nkey has a pt and an es entry.After merge
gh release create v2.7.4 --target main.release-ota.ymlbuilds and attaches the images.verify_release.py: first against v2.7.3, as a negative control that must mismatch, then against v2.7.4..uf2on the bench.🤖 Generated with Claude Code
https://claude.ai/code/session_01Jq4auDQppGzmAx1gLKn1z3