1

Metadata-Settings

Jonathan Miller edited this page 2026-06-20 17:21:42 +00:00

Table of Contents

• Metadata Settings
• API
• Key Changes (v1.27.0)
• Web UI

Metadata Settings

Per-repo identity, governance, and build metadata stored in the database.

API

• GET /api/v1/repos/{owner}/{repo}/metadata — read settings
• PUT /api/v1/repos/{owner}/{repo}/metadata — update (merge semantics, only provided fields change)

Key Changes (v1.27.0)

• Endpoint renamed from /manifest to /metadata
• package_type renamed to extension_type
• display_name is now read-only — computed as {ExtensionType} - {Name} (e.g. Package - MokoSuiteBackup)
• .mokogitea/manifest.xml file is no longer used — metadata is API-only

Web UI

Settings are also available in the repo Settings → Metadata tab. The web form supports: name, org, description, license, platform, extension type, and entry point.

Pages

• API-Reference
• Home
• License-Management
• Metadata-API
• Metadata-Settings
• README
• api
  • Branch-Protection-API
  • Custom-Fields-API
  • Project-API
  • Security-API
  • org-branch-protection-api
  • project-api
• features
  • Custom-Fields
  • Custom-Statuses
  • Issue-Priorities
  • Issue-Types
  • MCP-Server
  • Security-Scanning
  • Well-Known-Tabs
  • Wiki-Folders
  • cdn
  • issue-management
  • manifest-settings
  • security-scanning
• manifest-api
• operations
  • README
  • branding
  • deployment
  • roadmap