Repository navigation
fix: track the API release by its tag prefix, not the repository's latest - #181
Merged
Merged
Conversation
…test hypercerts-org/api now releases two packages, and GitHub marks the npm package @hypercerts-org/api@0.1.0 as the repository's latest release. A source with releaseTagPrefix now takes the newest stable release with that prefix from the release list. The API page tracks @hypercerts-org/happyview-modules@.
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/api now releases two packages: the server modules (
@hypercerts-org/happyview-modules@0.3.0) and the npm package@hypercerts-org/api@0.1.0, both released on 2026-11-03. GitHub marks only one release per repository as "latest", currently@hypercerts-org/api@0.1.0, so docs generation would fail on the API source: it read/releases/latestand expected the server modules' tag.lib/external-docs-snapshot.js: a source withreleaseTagPrefixnow takes the newest stable (not draft, not prerelease) release with that prefix from the repository's release list. A repository with no releases is still "unreleased"; one whose releases include none with the prefix is an error, so a wrong prefix cannot silently show "unreleased". Sources without a prefix still use/releases/latest.docs-sources.yml: the API source tracks@hypercerts-org/happyview-modules@, the tag prefix since the rename in client: add @hypercerts-org/api with record types from @hypercerts-org/lexicon/records api#45 (follow-up to fix: read the API changelog from happyview-modules/ #180).pnpm testpasses (81 tests). Generating against GitHub shows the API at v0.3.0 and the Lexicons at v2.0.0.The
@hypercerts-org/apinpm package itself has no page on the docs site yet; that is separate.