Skip to content
Beskid The Beskid Book

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

18.1 The pckg CLI

Pack and upload flows through beskid pckg—not a second package manager hiding in the bushes.

The pckg CLI

import { Aside } from ‘@astrojs/starlight/components’;

beskid pckg is the toolchain entry for registry operations: credential configuration, artifact packing, upload, and related workflows implemented in the beskid_pckg crate and the pckg registry service.

Commands you will actually use

Section titled “Commands you will actually use”
Terminal window
beskid pckg configure --api-key "$BESKID_PCKG_API_KEY"
beskid pckg whoami
beskid pckg pack --package acme.math --source . --output acme.math.bpk
beskid pckg upload acme.math --artifact acme.math.bpk

What happens during upload

Section titled “What happens during upload”
  1. beskid pckg pack — collects source, generates API docs for library packages, selects an exact semantic version, and assembles the .bpk artifact
  2. beskid pckg upload — reads that version from artifact-root package.json and streams version, checksum, and artifact bytes to POST /api/packages/<name>/versions
  3. Server-side validation — manifest integrity, checksum match, review/moderation policy enforcement
  4. Catalog update — version appears in search and listing endpoints; project fetch/lock flows can resolve it

The registry does not assign a different version during upload. Package/version coordinates are immutable: publish a new artifact version instead of replacing existing bytes.

Authentication

Section titled “Authentication”

beskid pckg loads credentials from, in order:

  1. --bearer-token / --api-key CLI flags (highest priority)
  2. BESKID_PCKG_TOKEN / BESKID_PCKG_API_KEY environment variables
  3. .beskid/pckg/repositories.json (written by beskid pckg configure)

Publisher operations (upload, yank, unyank) require a valid publish-scoped credential.

See also

Section titled “See also”