Add application version to /health response #213

New issue

Closed

opened 2026-06-27 11:33:44 -05:00 by erik · 2 comments

erik commented

2026-06-27 11:33:44 -05:00

Owner

Problem

The /health endpoint does not expose the running application version, making it harder to confirm which release is deployed.

Expected

/health should include a safe version field that identifies the running application build/release.

Scope

Add version metadata to the health response using existing package/build metadata conventions where possible.
Keep the endpoint safe for public access.
Ensure Docker/release builds expose the same version users expect from the deployed image/tag.

Acceptance criteria

/health returns a version field.
Tests cover the health response shape.
Documentation or release notes identify how the version is sourced if non-obvious.

## Problem The `/health` endpoint does not expose the running application version, making it harder to confirm which release is deployed. ## Expected `/health` should include a safe version field that identifies the running application build/release. ## Scope - Add version metadata to the health response using existing package/build metadata conventions where possible. - Keep the endpoint safe for public access. - Ensure Docker/release builds expose the same version users expect from the deployed image/tag. ## Acceptance criteria - `/health` returns a version field. - Tests cover the health response shape. - Documentation or release notes identify how the version is sourced if non-obvious.

erik added the

labels

2026-06-27 11:33:44 -05:00

erik commented

2026-06-28 01:34:29 -05:00

Author

Owner

Synced from todu comment by @todu on 2026-06-28T06:29:44.081Z

Review update

PR: #221 is open with Forgejo CI passing.
Result: approved.
Follow-up: waiting for explicit human merge approval.

Acceptance criteria: 3/3 met. Blocking issues: 0. Warnings: 0.

_Synced from todu comment by @todu on 2026-06-28T06:29:44.081Z_ ### Review update - PR: https://forge.caradoc.com/erik/slugkit/pulls/221 is open with Forgejo CI passing. - Result: approved. - Follow-up: waiting for explicit human merge approval. Acceptance criteria: 3/3 met. Blocking issues: 0. Warnings: 0.

erik

2026-06-28 06:31:55 -05:00

closed this issue
added
status:done
and removed
status:inprogress
labels

erik commented

2026-06-28 06:31:56 -05:00

Author

Owner

Synced from todu comment by @todu on 2026-06-28T11:29:28.942Z

Closing summary

PR #221 was merged into main.
Local main is aligned with origin/main at merge commit f5fde92.
Prior review recorded Forgejo CI passing, approval, and acceptance criteria 3/3 met.

Acceptance criteria verified:

/health returns a version field.
Tests cover the health response shape.
Documentation identifies how the version is sourced.

Closing task as done.

_Synced from todu comment by @todu on 2026-06-28T11:29:28.942Z_ ### Closing summary - PR #221 was merged into `main`. - Local `main` is aligned with `origin/main` at merge commit `f5fde92`. - Prior review recorded Forgejo CI passing, approval, and acceptance criteria 3/3 met. Acceptance criteria verified: - `/health` returns a version field. - Tests cover the health response shape. - Documentation identifies how the version is sourced. Closing task as done.