Add API metadata route #30
Labels
No labels
activitypub
admin
api
articles
auth
bug
cleanup
cli
comments
compatibility
config
contacts
database
deployment
design
dev-env
docs
documentation
email
enhancement
feature
federation
feed
homepage
implementation
integration
media
openapi
priority:high
priority:low
priority:medium
proof
public-routes
public-ui
release
safety
social
sources
status:active
status:canceled
status:done
status:inprogress
status:waiting
syndication
tailwind
template
test
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Implement the Slugkit API metadata route so clients can discover API version, implementation identity, and OpenAPI location.
Spec:
docs/specs/01-meta-route.mdRequirements
/api/v1exactly as documented in the spec.slugCLI can use the response before attempting authenticated operations.Acceptance criteria
200with the documented JSON shape.Dependencies
Synced from todu comment by @todu on 2026-05-22T16:15:12.424Z
PR Review: Approved
PR: #51
Summary
Reviewed PR #51 at commit
5d42adf. The PR adds the API metadata route as a small bootstrap slice:GET /api/v1/metareturns site, API, and software metadata; base/openapi URLs are derived from the request origin; site identity comes fromsiteConfig; the route is documented in OpenAPI asmeta.get; and tests cover the response shape plus absence of an ad hoc capability matrix.Acceptance Criteria
200with the documented JSON shape.make check,./scripts/pre-pr.sh, manual/api/v1/metasmoke, and Forgejo CI all passed.Blocking Issues
None.
Warnings
None.
Verdict
Approved for merge.
Synced from todu comment by @todu on 2026-05-22T16:27:46.141Z
Closing Summary
PR #51 merged: #51
Acceptance criteria evidence:
200with the documented JSON shape: met —GET /api/v1/metareturns site, API, and software objects.api.versionand request-origin-derivedapi.openapiUrl.capabilitiesproperty./metais documented withoperationId: "meta.get".make check,./scripts/pre-pr.sh, PR CI, and main push CI passed.Readiness: READY