community

Make a saved package public (first community listing), or force-refresh an already-public listing to the current publ...

Make a saved package public (first community listing), or force-refresh an already-public listing to the current published_commit. Default-branch HEAD becomes world-readable and forkable, and the package appears on /community. Prefer packageUpdate with changes.visibility: "public" for the first publish. After that, packagePublishExternalPush / promote auto-advance the listing pin — you do not need a separate republish step. Before calling for a first publish, review the package for overly personal content (package_authoring visibility). If anything looks personal, stop, tell the user, suggest generalizing, and wait for explicit go-ahead. No license, logo, or Intent platform gates. Runtime uses published_commit. Listings owned by anyone are third-party code — review before forking.

Org permission: package:publish.

post/v1/community/listings

Request

  • Base URL: https://api.kody.codes
  • URL: https://api.kody.codes/v1/community/listings
  • Auth: HTTP bearer

Request body

package_idstring required

Saved package id to publish as a public package.

Response

Success.

listing_idstring required
namestring required
kody_idstring required
descriptionstring required
category'integrations' | 'examples' | 'productivity' | 'apps' | 'utilities' | 'other' required
licensestring required
versionstring nullable required

package.json#version from the pinned listing snapshot, or null when the author did not set a string version.

pinned_commitstring required
status'active' | 'delisted' required
public_urlstring required

Canonical shareable user URL ({base}/@{username}/{package-name-leaf}); share this URL with humans.

published_atstring required

Changes

No recorded changes to this operation across all 2 revisions of this API.