rbrooks/Iris-WLED
Watch
1
0
Fork
You've already forked Iris-WLED
 0
Code Issues 21 Pull requests Projects Releases 2 Packages 1 Wiki Activity Actions

Cut the v1.0.0 release #10

New issue
Closed
opened 2026-07-07 16:51:51 +00:00 by claude-bot · 1 comment
claude-bot commented 2026-07-07 16:51:51 +00:00
Contributor
Copy link

Goal

Tag and publish v1.0.0 once all other v1.0.0 issues are closed.

Preconditions

  • CI on Forgejo Actions green
  • Images publishing to the Forgejo registry
  • Release automation in place
  • Expanded test coverage passing
  • All three final QA issues closed
  • Deferred v1 items resolved
  • CHANGELOG.md [1.0.0] section finalized with a release date

Steps

  • git tag v1.0.0 && git push origin v1.0.0
  • Confirm the release workflow builds/pushes images and creates the Forgejo release
  • Smoke-test the published :1.0.0 image

This is the last issue in the v1.0.0 label; closing it means v1 is shipped.

## Goal Tag and publish v1.0.0 once all other `v1.0.0` issues are closed. ## Preconditions - [ ] CI on Forgejo Actions green - [ ] Images publishing to the Forgejo registry - [ ] Release automation in place - [ ] Expanded test coverage passing - [ ] All three final QA issues closed - [ ] Deferred v1 items resolved - [ ] CHANGELOG.md `[1.0.0]` section finalized with a release date ## Steps - [ ] `git tag v1.0.0 && git push origin v1.0.0` - [ ] Confirm the release workflow builds/pushes images and creates the Forgejo release - [ ] Smoke-test the published `:1.0.0` image This is the last issue in the `v1.0.0` label; closing it means v1 is shipped.
claude-bot added this to the v1.0.0 milestone 2026-07-15 15:33:01 +00:00
claude-bot commented 2026-09-01 20:08:41 +00:00
Author
Contributor
Copy link

v1.0.0 is released 🎉

Tagged v1.0.0 at 0251a6a, release job run #224 green on first attempt.

Steps

  • git tag v1.0.0 && git push origin v1.0.0
  • The release workflow built/pushed images and created the Forgejo release
  • Smoke-tested the published :1.0.0 image

The three things that had genuinely never run

The #4 dry run used a pre-release tag, which by design suppresses :latest and {{major}}.{{minor}} and has no matching CHANGELOG section — so it exercised neither the extraction nor those tags. All three ran for real here:

1. All three tags published, pointing at one image:

EXISTS   1.0.0     manifest defb6bd651a55cf3
EXISTS   1.0       manifest defb6bd651a55cf3
EXISTS   latest    manifest defb6bd651a55cf3

2. Release notes came from the CHANGELOG, not the Release v1.0.0 fallback — the full [1.0.0] section, all 30 entries, prerelease: false, draft: false. As expected, the trailing [Unreleased]: / [1.0.0]: link-reference lines land in the body; harmless and standard for the format.

3. Smoke test of the published image, pulled fresh on the dev host with its own data dir and no WLED_HOST:

health: healthy
GET /api/v1/health -> 200
GET /              -> 200
events 2026        : 47      (seeded from a cold start)
digest             : sha256:a58eef27ab6c9abf41e…

Torn down afterwards; the dev deployment was untouched throughout and still runs :main.

Preconditions

  • CI green on Forgejo Actions
  • Images publishing to the Forgejo registry (#3)
  • Release automation in place (#4)
  • Expanded test coverage passing (#5) — 291 backend, 76 frontend, plus E2E
  • All three final QA issues closed — #5, #8 passed; #7 verified leg-by-leg and moved to v1.1.0 for one confirming unattended night
  • Deferred v1 items resolved or explicitly deferred with a rationale
  • CHANGELOG.md [1.0.0] finalised with a release date

One thing to keep in view

v1.0.0 shipped with the roofline install having run one verified night. The scheduler's sunrise-off was broken until today (#106) and is now fixed and verified firing on real hardware — but tonight is the first ordinary unattended cycle. #7 tracks that check; if it surprises us, a patch release is cheap.

Closing. v1.0.0: 27 issues, shipped.

## v1.0.0 is released 🎉 Tagged `v1.0.0` at `0251a6a`, release job [run #224](https://git.rhoving.com/rbrooks/Iris-WLED/actions/runs/224) green on first attempt. ### Steps - [x] `git tag v1.0.0 && git push origin v1.0.0` - [x] **The release workflow built/pushed images and created the Forgejo release** - [x] **Smoke-tested the published `:1.0.0` image** ### The three things that had genuinely never run The #4 dry run used a pre-release tag, which by design suppresses `:latest` and `{{major}}.{{minor}}` and has no matching CHANGELOG section — so it exercised neither the extraction nor those tags. All three ran for real here: **1. All three tags published, pointing at one image:** ``` EXISTS 1.0.0 manifest defb6bd651a55cf3 EXISTS 1.0 manifest defb6bd651a55cf3 EXISTS latest manifest defb6bd651a55cf3 ``` **2. Release notes came from the CHANGELOG**, not the `Release v1.0.0` fallback — the full `[1.0.0]` section, all 30 entries, `prerelease: false`, `draft: false`. As expected, the trailing `[Unreleased]:` / `[1.0.0]:` link-reference lines land in the body; harmless and standard for the format. **3. Smoke test of the published image**, pulled fresh on the dev host with its own data dir and no `WLED_HOST`: ``` health: healthy GET /api/v1/health -> 200 GET / -> 200 events 2026 : 47 (seeded from a cold start) digest : sha256:a58eef27ab6c9abf41e… ``` Torn down afterwards; the dev deployment was untouched throughout and still runs `:main`. ### Preconditions - [x] CI green on Forgejo Actions - [x] Images publishing to the Forgejo registry (#3) - [x] Release automation in place (#4) - [x] Expanded test coverage passing (#5) — 291 backend, 76 frontend, plus E2E - [x] All three final QA issues closed — #5, #8 passed; #7 verified leg-by-leg and moved to v1.1.0 for one confirming unattended night - [x] Deferred v1 items resolved or explicitly deferred with a rationale - [x] `CHANGELOG.md` `[1.0.0]` finalised with a release date ### One thing to keep in view `v1.0.0` shipped with the roofline install having run **one** verified night. The scheduler's sunrise-off was broken until today (#106) and is now fixed and verified firing on real hardware — but tonight is the first ordinary unattended cycle. #7 tracks that check; if it surprises us, a patch release is cheap. Closing. **v1.0.0: 27 issues, shipped.**
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/lock-file-maintenance
v1.1.0
v1.0.0
Labels
Clear labels   
area/ai
AI suggestion pipeline

  
area/backend
FastAPI / Python backend

  
area/frontend
React / Vite frontend

  
area/infra
Docker, deployment, and infrastructure

  
area/scheduler
Scheduler and time envelope

  
area/wled
WLED controller integration

  
good-first-issue
Good for newcomers

  
priority/high
Blocks release or high impact

  
priority/low
Nice to have

  
priority/medium
Should be done soon

  
type/bug
Something isn't working

  
type/chore
Maintenance, release, or housekeeping

  
type/ci-cd
CI/CD pipeline, build, or release automation

  
type/docs
Documentation

  
type/feature
New capability or enhancement

  
type/qa
Testing, validation, or quality assurance

  
v1.0.0
Target release: v1.0.0

  
v1.1.0
Target release: v1.1.0

  
v1.2.0
Target release: v1.2.0

  
v2.0.0
Target release: v2.0.0

No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
Milestone
Clear milestone
No items
No milestone
v1.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Iris-WLED#10
No description provided.