Repository navigation
docs: add the @hypercerts-org/api package (Hypercerts API types) - #182
Merged
Merged
Conversation
A release page and component for the npm package, tracked by its @hypercerts-org/api@ tags, next to the service's release notes; a TypeScript example on the API reference page; and a pointer from the SDK page.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@hypercerts-org/api0.1.0 was published to npm on 2026-11-03 (hypercerts-org/api#48, TECH-829): typed query definitions for calling the Hypercerts API with@atproto/lex. The docs did not mention it; the API reference page still said to "use the SDK when available". The service's own release notes stay where they are.lib/release-components.json,docs-sources.yml,pages/releases/api-types.md): the package's changelog (packages/api/CHANGELOG.md), tracked by its@hypercerts-org/api@tags, with its own sidebar badge and release card. The existing "Hypercerts API" page keeps tracking the service (@hypercerts-org/happyview-modules, v0.3.0); the two are released independently from the same repository, which fix: track the API release by its tag prefix, not the repository's latest #181 made possible.pages/reference/services/hypercerts-api.md): a "From TypeScript" section with install and agetActivityexample, the response-validation caveat from the package README (TECH-791), and links to both release pages.docs/remote-markdown.md: eight components, not seven.The example typechecks against the published
@hypercerts-org/api0.1.0,@hypercerts-org/lexicon2.0.0 and@atproto/lex0.4.2, and returned a live activity fromapi.hypercerts.dev. Generating against GitHub shows API v0.3.0 and API types v0.1.0.The "Hypercerts API" page's heading still reads
@hypercerts-org/hypercerts-api, the package's old name: it is the first line of the changelog in the API repository, fixed there separately.pnpm testpasses (82 tests).