FAQ and troubleshooting

Platform spec article

FAQ and troubleshooting

Back to pckg client contract ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0001-hub-authority Hub authority Accepted

   Hub authority

   Context

   One client story.

   Decision

   Hub owns HTTP and auth.

   Consequences

   Extension defers.

   Verification anchors

   beskid_pckg; pckgClient.

   Open full ADR page

2. 0002-registry-assigned-versions Registry versions Accepted

   Registry versions

   Context

   Manual semver drift.

   Decision

   Registry-assigned publish versions in routine flows.

   Consequences

   UI shows server version.

   Verification anchors

   publish API tests.

   Open full ADR page

Articles

• Contracts and edge cases Registry client guarantees and failure modes. article Standard
• Design model Conceptual model for the Beskid pckg registry client (`beskid_pckg`). article Standard
• Examples Example `beskid pckg` invocations and configuration. article Standard
• FAQ and troubleshooting Common pckg client and registry issues. article Standard
• Flow and algorithm Pack, upload, and query flows for the pckg registry client. article Standard
• Verification and traceability Tests and traceability for the pckg client contract. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 3 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  pckg client contract

  Parent feature hub

401 / MissingAuthToken

Set BESKID_PCKG_API_KEY or bearer token. For multi-registry setups, ensure .beskid/pckg/repositories.json keys match Workspace.proj registry alias names.

Pack missing docs on pckg site

Run beskid doc --project ... before pack so .beskid/docs/api.json exists. Server ingestion (PackagePublishDocumentation) treats that tree as first-class.

Template pack rejected

Verify project.type = Template, .beskid/template.json (beskid.template.v1), and packageKind: template in generated package.json.

Wrong package version after publish

Registry assigns versions in normal flows—do not expect local project.version alone to drive the published label. Query the server for the assigned version summary.

Local dev server URL

Default http://127.0.0.1:8082 matches typical compose bindings; override with BESKID_PCKG_URL for remote hosts.