Skip to content

Publish real creation timestamps in /v1/models - #24

Merged
hcastc00 merged 1 commit into
mainfrom
fix/model-catalog-created-timestamps
Nov 16, 2026
Merged

hcastc00 merged 1 commit into
mainfrom
fix/model-catalog-created-timestamps

Conversation

@hcastc00

@hcastc00 hcastc00 commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Regular models in GET /v1/models always returned created: 0, preventing clients from sorting the catalog by when models were added. Carry Metering's created_at through the runtime client and domain model, then publish its Unix timestamp in the existing created field.

Missing dates from older Metering versions still serialize as 0, preserving compatibility during rollout. The existing public catalog remains the source for the landing page.

Companion Nexus change: https://github.com/dappnode/dappnode-nexus/pull/162

Deploy the companion Metering change first to supply creation dates.

Validation

  • Gateway handler, Metering client, application service, and domain tests passed.
  • Regression assertions cover runtime JSON date mapping, the public Unix timestamp, and the zero fallback for missing dates.
  • Gateway Docker build passed.
  • Live local verification confirmed populated timestamps through the database → Metering → gateway → landing path.

@hcastc00
hcastc00 merged commit 3934992 into main Nov 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants