Repository navigation
Publish real creation timestamps in /v1/models - #24
Merged
Merged
Conversation
Marketen
approved these changes
Nov 16, 2026
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.
Regular models in
GET /v1/modelsalways returnedcreated: 0, preventing clients from sorting the catalog by when models were added. Carry Metering'screated_atthrough the runtime client and domain model, then publish its Unix timestamp in the existingcreatedfield.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