Skip to content

Commit 1b98bd7

Browse files
committed
docs(changelog): cut 0.29.0
Records what v0.28.1..HEAD actually contains: a health check that could not see the failure it existed to report, a shutdown that ended the process before its hooks ran, a validate that returned 0 on a broken config and never looked at the jobs, and a job the scheduler had refused being counted as scheduled. Minor rather than patch. No commit declares a break, but three changes alter behaviour a user can be relying on: validate now exits non-zero, validate now checks the jobs, and /health can answer degraded. The lead paragraph names all three. Version comes from the tag via GoReleaser, so there is no version file to raise. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
1 parent a666a06 commit 1b98bd7

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

CHANGELOG.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10+
## [0.29.0] - 2026-08-03
11+
12+
A release about ofelia telling the truth about itself. A job the scheduler
13+
refused was reported as scheduled, `/health` claimed health it had never
14+
established, `validate` returned success on a config it had not checked, and
15+
shutdown ended the process before the hooks that stop the web server had run.
16+
Each of those looked fine from the outside, which is what made them worth
17+
fixing.
18+
19+
Three changes alter behaviour you may be relying on. `ofelia validate` now
20+
exits non-zero when validation fails, so a pipeline step that silently passed
21+
will start failing — that is the point, but check yours before upgrading. That
22+
same command now also validates the jobs, so a config that passed before may
23+
not. And `/health` can now answer `degraded`; `/ready` is unchanged and still
24+
answers 200 for it.
25+
1026
### Added
1127

1228
- **`ofelia validate` now validates the jobs, not just the `[global]` section.** It checked global keys and stopped there, so a `[job-run]` without an `image` or a `[job-exec]` without a `container` passed the gate and then failed on every tick at runtime. Each job type is now checked for the fields its runtime actually requires, and the schedule and command are required everywhere ([#778](https://github.com/netresearch/ofelia/pull/778)).

0 commit comments

Comments
 (0)