Repository navigation
api: build on lexicon 2.0.0 and start releasing @hypercerts-org/api - #48
Merged
kristoferlund merged 1 commit intoNov 3, 2026
Conversation
…rcerts-org/api - Both packages move to @hypercerts-org/lexicon 2.0.0 (same Lexicons as 1.6.0); vendor/ is gone, and a test checks that the client and the server modules pin the same version. - The generator points record imports at the package root paths, re-exports top-level namespaces from the root, and resolves every path through the lexicon package's exports. - @hypercerts-org/api is no longer private or ignored by Changesets, with a changeset for its first release (0.1.0).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: ffa08d7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
❌ The last analysis has failed. |
kristoferlund
deleted the
kristofer/tech-829-publish-the-first-version-of-hypercerts-orgapi-to-npm
branch
November 3, 2026 09:08
Merged
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.
TECH-829. Moves the repository to the published
@hypercerts-org/lexicon2.0.0 and makes@hypercerts-org/apireleasable, so its first version can go to npm.What changes
happyview-modules/andpackages/api/pin@hypercerts-org/lexicon2.0.0, andvendor/(the packed pre-release tarball) is gone. 2.0.0 has the same Lexicons as 1.6.0:pnpm docs:syncchanged only the pinned version strings, no schema snapshot. The server modules' validation is unchanged, so there is no changeset for them.packages/apiandhappyview-modulespin different lexicon versions, so the client's record types always describe what the server validates.@hypercerts-org/lexicon/<nsid path>instead of/records/<nsid path>. Top-level namespaces the tree re-exports (com,pub) come from the package root (export { com } from "@hypercerts-org/lexicon"), because 2.0 exports./com/*but not./com. Every path is now resolved through the lexicon package's exports rather than checked on disk, which is how this was caught: the type check failed, the generator had not.@hypercerts-org/apiis no longerprivateor in the Changesetsignorelist, and has a minor changeset for its first release (0.0.0 to 0.1.0)./recordsor vendored tarball),.changeset/README.md, and the changesets skill.Before merging the Release PR
Merging this PR only updates the open Release PR. Publishing happens when that Release PR is merged, and needs a Trusted Publisher for
@hypercerts-org/apion npmjs.com (repositoryhypercerts-org/api, workflowrelease.yml). If npm only allows that for an existing package, an owner of the@hypercerts-orgscope publishes 0.1.0 by hand first.The Release PR (#44) also carries the pending
@hypercerts-org/happyview-modules0.3.0 release, so merging it releases both.Verification
packages/api:pnpm check(freshness, lint, format, typecheck, build, tests) andpnpm check:package(packs, installs with lexicon 2.0.0 from npm, Node import, TypeScript consumer, Vite bundle) pass.happyview-modules:check:generated,lint:js,typecheckpass;test:unitpasses except the Luacheck test, because Luacheck is not installed locally (CI has it).