Publish immutable API contract artifacts from releases #300
No reviewers
Labels
No labels
activitypub
admin
api
architecture
articles
auth
bug
cleanup
cli
comments
compatibility
config
contacts
content
database
deployment
design
dev-env
diagnostics
docs
documentation
email
enhancement
feature
federation
feed
health
homepage
implementation
integration
logging
mastodon
media
navigation
npm-packages
openapi
opengraph
packages
passkeys
preview
priority:high
priority:low
priority:medium
production
proof
proxy
public-routes
public-ui
release
safety
slug-api
slug-auth
slug-core
slug-federation
slug-media
slug-template
social
sources
status:active
status:canceled
status:done
status:inprogress
status:waiting
syndication
tailwind
template
test
web
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit!300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/task-c934d36b-contract-publication"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
API releases currently have an authoritative packaged specification but no durable public version archive. Download the published package from npm, verify tarball integrity and its exact contract artifact/digest, and commit reference files to the independent
api-contract-archivebranch after normal API release publication. Add a dedicated workflow for the initial package 0.2.0 publication and safe retries without another npm release.Prior versions remain intact. Changed specification bytes under an existing version are rejected; identical retries and later packages carrying the same contract preserve the original manifest/provenance. The public website reads this branch without management credentials. This is coordinated with the Slugkit.com exact-version API/documentation change. Older packages without versioned artifacts are unsupported, as clarified by the human; tests use subsequent-release fixtures, never fake published versions.
Validation: complete
./scripts/pre-pr.shpassed, including build, formatting, lint, types and 1,236 tests across workspaces. New deterministic archive coverage verifies retention, first-publication provenance, identical retry, changed-byte rejection and identity/digest validation. Integration and visual tests remain local-only. The initial real Actions publication will be verified after human-approved merge; no manual publication workaround is used.Task: task-c934d36b. Publication and rollout policy:
docs/api-contract-archive.md.Independent review
ffc3b0372c443c8619fd68fb0afd7f3c678f7700: approved, no actionable findings or warnings.715307233414dd64c4ea1ed2b4d4a437853dd9db: changes requested. Explicitly wire the existing short-lived Actions token into both the dedicated archive publication step and the normal API release archive step, consistent with existing repository release workflows.Coordinated independent review approved
ff2bb09d83c11508448521793a8ba05236f50613: approved. The sole prior finding is resolved by explicitly supplying the existing short-lived Actions token to both publication steps. Current-head CI run 518 passed, and full local pre-PR verification passed again (1,236 tests).ffc3b0372c443c8619fd68fb0afd7f3c678f7700: approved. Current-head CI run 47 and complete local verification (356 tests) passed. The independent reviewer confirmed the unchanged approved head./api/v1is unavailable locally; live preservation verification remains pending deployment.