Release v1.2.0 - #238
Merged
Merged
Conversation
Ashex
approved these changes
Aug 3, 2026
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@hypercerts-org/lexicon@1.2.0
Minor Changes
#236
5439b36Thanks @Ashex! - Addapp.certified.graph.entityFollow, a follow record for non-account entities.subjectis an open union currently offering onlyapp.certified.defs#recordSubject(a record referenced by AT-URI without a CID, so the follow survives updates to the referenced record); account follows remain inapp.certified.graph.follow. The new collection is also added to theapp.certified.authWritepermission set so it is grantable alongside the other Certified records.#222
fa1c29aThanks @aspiers! - Add three permission-set lexicons —org.hypercerts.authWrite,org.hyperboards.authWrite, andapp.certified.authWrite— each granting create/update/delete over every record collection in its namespace.A permission set lets any AT Protocol app request a whole bundle of
repo:scopes with a singleinclude:<nsid>OAuth scope, instead of enumerating each collection by hand. The user's PDS resolves and expands the set during the OAuth grant; the same published set can also be consumed by services (e.g. the Certified group service) when expanding API-key scopes.There are three sets rather than one because the spec requires it: a permission set "is limited to expressing permissions that reference resources under the same NSID namespace as the set itself" and "can not address 'sibling groups' or 'parents'".
org.hypercerts,org.hyperboards, andapp.certifiedare separate namespace authorities, so they cannot be combined in a single set — an app needing more than one requests eachinclude:scope.Permission sets are published as-is (they are the source of truth for what gets published to AT Protocol) but have no TypeScript shape —
lex gen-apicannot generate code forpermission-setdefs. They are therefore excluded from the codegen globs (gen-api/gen-md/gen-ts) and fromgenerated/exports.ts, while still shipping as raw lexicon JSON.Collection lists are enumerated explicitly because the spec forbids wildcards inside a permission set; they must be kept in sync as record types are added. See
docs/design/permission-sets.md.The generated
SCHEMAS.mdreference now renders permission-set entries (title, detail, and the resource/collections/actions each set grants) instead of leaving them as empty sections.