[kristoferlund]

Bumps the pinned @hypercerts-org/lexicon from 1.5.0 to 1.6.0, so the API validates records against the current lexicons. Implements TECH-822.

Merging and deploying: Karma, please. Merging alone does not change the running indexer; the bundle has to be reinstalled into the HappyView instance with pnpm install:api and an admin token. Kristofer has not worked with the deployed instance yet, so this PR leaves both the merge and the reinstall to Karma.

What 1.6.0 changes for the API

From the 1.6.0 changelog, all additive or loosening:

• an optional langs field (BCP-47 language tags) on several records;
• an optional app.certified.signature.defs#createdVia signature;
• funding receipts may omit amount and currency;
• description changes on attachments and funding receipts.

No Lua handler or query Lexicon reads a receipt's amount or currency (the API serves the record unchanged), so no handler changes are needed. Validation accepts records using the new fields; no record that validated against 1.5.0 is rejected.

Changes

• api/package.json: @hypercerts-org/lexicon 1.5.0 → 1.6.0, and the lockfile.
• pnpm docs:sync: explorer Lexicon snapshots, docs/openapi.json and coverage.json. In the OpenAPI contract only two record descriptions and the source version change.
• .agents/skills/hypercerts-api/references/openapi.json: the same two description changes.
• Changeset: minor for @hypercerts-org/hypercerts-api.

Why now

api#45 (@hypercerts-org/api) takes its record types from @hypercerts-org/lexicon/records (hypercerts-lexicon#270, to be released as 1.7.0). That release changes no Lexicon JSON, so after this PR the indexer validates against the same lexicons the client types are generated from. Moving to 1.7.0 later is a version number only. Independent of #45 and #270.

Verification

Server generated-source check, lint, typecheck and unit tests pass (except the Luacheck test, which needs Luacheck installed locally; CI runs it). Explorer tests pass; changeset status and the frozen-lockfile install are clean. HTTP tests run in CI.

Confidence Score: 5/5

The PR appears safe to merge; no blocking issues remain.

Summary

Updates the server’s pinned @hypercerts-org/lexicon from 1.5.0 to 1.6.0.

• Profiles and claim records can include language tags and app signatures.
• Attachments can describe account updates and when material was captured.
• Funding receipts can describe payment chains and omit unknown amounts.

_{Reviews (2) · Last reviewed commit: "api: validate against @hypercerts-org/le..." · Reviewed by Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
api-endpoints	Ready	Preview	Nov 2, 2026 6:49am UTC

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: bd2e86aa-79ea-48bd-8610-0ab92685de1d

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[changeset-bot]

🦋 Changeset detected

Latest commit: b6ae142

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hypercerts-org/happyview-modules	Minor

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​hypercerts-org/​lexicon@​1.5.0 ⏵ 1.6.0			+1	+1

View full report

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud