release: changelog + version bump to 9.6.0 - #149
Merged
Conversation
The optimizer fix (#146), production-safety hardening (#140), and the installation-guide rework (#136) landed on main since v9.5.0 without the per-merge CHANGELOG/version-bump steps (the #146 merge skipped the gate). This backfills the user-facing CHANGELOG and bumps config.yaml to 9.6.0. MINOR bump: #146 visibly changes optimizer schedules and corrects the savings figures users see (binary store/export, no phantom solar export). Agent/CI/test-infra PRs (#137/#138/#139/#143/#144) are intentionally not in the user-facing changelog; the simulator (#144) is noted as the verification mechanism inside the #146 entry. No code change — CHANGELOG.md + version only. Does NOT tag or release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Why
Eight commits landed on
mainsince v9.5.0, but the CHANGELOG had no entries for them andconfig.yamlwas still9.5.0. The per-merge CHANGELOG/version-bump steps were skipped — notably when #146 merged without going through the gate. This backfills the user-facing changelog and bumps the version.What
CHANGELOG.md— new## [9.6.0]section:assert→SystemConfigurationError, TOU time-parsing (test: add 115 unit tests, remove dead code, fix production bugs #140)bess_manager/config.yaml—9.5.0→9.6.0bess_manager/CHANGELOG.mdis a symlink to root, so it updates automatically.Version rationale — MINOR (9.6.0)
#146 visibly changes optimizer schedules and corrects the savings figures users see (more than a silent patch, but no new user feature).
Intentionally excluded from the user-facing changelog
Agent/CI/test-infra PRs #137, #138, #139, #143, #144. The simulator (#144) is referenced as the verification mechanism inside the #146 entry rather than its own line.
Not in scope
No code change. This PR does not tag or create a release — that happens later, after #146 is validated and the merge gate (#148) is in place.
🤖 Generated with Claude Code