Skip to content

Vendor & publish consumed snapshots (TapirXL, Viper) #191

Description

@xnorkl

Parent: #187 — Pillar A

Goal

Bring the consumed upstream contracts (TapirXL, Viper) into the registry as versioned packages.

Acceptance criteria

  • TapirXL upload-vector.vrl + golden vendored as a versioned package with source URL + fetch timestamp
  • Viper OpenAPI vendored as a versioned package with source URL + fetch timestamp
  • A documented refresh procedure exists for intentional updates
  • If an upstream source is unreachable in CI, the job fails loudly rather than publishing a stale or empty package

Notes

Metadata

Metadata

Assignees

Labels

ci/cdconsumersenhancementNew feature or requestepic:contract-infraChild of the contract distribution/CDC EPICneeds-refinementIssue requires a refinement session before sprint planningrefinedPassed Definition of Ready

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions