Repository navigation
Conversation
## Summary Restores the `CHANGELOG.md` entry for 1.79.1, which shipped nine fixes and recorded none of them. ## Type of Change - [ ] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Refactoring (no functional changes) - [ ] CI/CD or infrastructure change ## Related Issues Part of #1112. The generator fix itself landed in #1113. ## Changes Made 1.79.1 was released while `conventional-changelog-conventionalcommits` was pinned two majors ahead of the renderer, so its notes rendered as a bare heading. Its tag is published and no generator revisits an existing tag, so the entry is reconstructed by hand from the `v1.79.0..v1.79.1` commit range. It is written in the format semantic-release produces, verified against the 1.79.3 dry run that ran after the pin fix: scope-then-subject ordering, `* **scope:** subject ([#pr](...)) ([sha](...))`, and the same compare link in the heading. Nine `fix` commits, covering replacement risk, SMART observed thresholds, notifications, scheduled reports and the dashboard temperature chart. Only 1.79.1 is backfilled. The other 27 empty entries between 1.69.0 and 1.79.2 stay as they are and remain described in #1112; this is the release whose missing content prompted the investigation. ## Testing - [ ] I have tested this locally - [ ] I have added/updated tests that prove my fix/feature works - [ ] All existing tests pass Documentation only, no code paths touched. The entry was generated from `git log v1.79.0..v1.79.1` rather than transcribed, so the SHAs and PR numbers come from the range itself. ## Checklist - [x] My code follows the project's code style - [x] I have performed a self-review of my code - [x] I have commented my code where necessary (particularly complex areas) - [x] I have updated the documentation if needed - [x] My changes generate no new warnings - [x] No console.log, debug statements, or commented-out code ## Additional Notes `@semantic-release/changelog` prepends new entries directly under the file title, so a future release inserts above this block and will not disturb it. Review: not required (documentation only, no behaviour change, trivially reversible).
## Summary `deploy-beta.yml` now stamps the same OCI labels as the Docker workflow, so `beta` and `beta-omnibus` always carry `org.opencontainers.image.revision`. This applies the #1052 fix for `develop` to the beta workflow. ## Type of Change - [x] CI/CD or infrastructure change ## Related Issues Same race as #1052, for the beta channel. No issue filed. ## Changes Made - Add a `docker/metadata-action@v6` step (`id: meta`) before the beta build, configured like `deploy-testing.yml`. - Pass `labels: ${{ steps.meta.outputs.labels }}` to `docker/build-push-action`. ## Testing - [ ] I have tested this locally - [ ] I have added/updated tests that prove my fix/feature works - [ ] All existing tests pass `actionlint .github/workflows/deploy-beta.yml` passes, and the file parses as YAML. The workflow runs only on a push to `beta`. This PR changes no tag names, platforms or cache scopes. Evidence for the problem: on 2026-11-05, Zeus pulled `beta-omnibus` after #1114 merged (`8500fbc3`). `docker image inspect` showed an empty `org.opencontainers.image.revision`, although both Publish Beta Image and Docker succeeded for that commit. ## Additional Notes Review: required (a workflow change that takes effect on merge with no separate deploy step). `deploy-beta.yml` is identical on `develop`, `master` and `beta`. The fix reaches the beta workflow only after the next promotion to `master` and the `master` into `beta` sync. Co-authored-by: Claude Opus 5.5 <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
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.
Product changes
Summary
None.
Reason
This promotion carries two
developcommits tomaster, and neither changes user-facing behaviour.CHANGELOG.mdentry for 1.79.1, so the next release ships with that history in place. 1.79.1 recorded none of its nine fixes, because it was released while the conventional-commits preset was pinned two majors ahead of the notes renderer. The generator fix promoted in release: restore changelog bodies and add a release dry run #1115 is already confirmed working: a dry run frommasterresolved 1.79.3 and rendered its commits as bullets, the first populated notes since 1.68.0. The entry documents releases that already shipped.deploy-beta.ymlnow stamps the same OCI labels as the Docker workflow, so thebetaandbeta-omnibusimages always carryorg.opencontainers.image.revision. This is the ci: stamp OCI labels on the testing image #1052 fix fordevelop, applied to the beta channel. It joined this promotion after it was opened, because the head isdevelop. It takes effect onbetabuilds after the nextmasterintobetasync.Validation
git log v1.79.0..v1.79.1rather than transcribed, and written in the format the 1.79.3 dry run proved the tooling now emits: scope-then-subject ordering, commit links, pull request links.actionlintclean, CI green (17 pass, 1 skipped), independent review SHIP at42f9adbe. It changes no tags, platforms or cache scopes.Follow-up
masteronce this merges.