* Integrate new reporting reasons
* Update bnn to BNR, prefix all with reason* to match previous
* Remap deprecations
* Update naming, add notes about Bluesky-only reasons
* Update reason
* Move new defs to tools.ozone namespace
* Add ozone lexicons to app view
* Copy known values to merge defs
* Update comments
* Add reasonAppeal to new ozone namespace defs
* Changeset
* ❇️ Support new reporting categories in ozone (#3974)
* ✨ Validate report reason using labeler service profile
* ✅ Rename test
* :rotating_lights: Fix lint issue
* ✨ Use both appeal reason type for materialized views
* ✨ Add old to new reason mapping for fallback
* ✅ Update test snapshot
* :rotating_lights: Fix lint issue
* 🧹 Cleanup
* :rotating_lights: Fix lint issue
* ✨ Adjust report reason tagging
* 📝 Additional comment for new migration
---------
Co-authored-by: Foysal Ahamed <foysal@blueskyweb.xyz>
* Allow unexpected error to go through when fetching permission sets
* Log `cid` as string after succesful lexicon resolution
* Log `cid` and `uri` as string on successful lexicon resolution
* Export constants and type assertion utilities
* Add permission set support to oauth provider
* improve permission set parsing
* Rename `PermissionSet` to `ScopePermissions`
* Improve performance of NSID validation
* Add support for `permission-set` in lexicon document
* Validate NSID syntax using `@atproto/syntax`
* Export all types used in public interfaces (from `lexicon-resolver`)
* Small performance improvement
* Rework scope parsing utilities to work with Lexicon defined permissions
* file rename
* fixup! Rework scope parsing utilities to work with Lexicon defined permissions
* removed outdated comment
* removed outdated comment
* fix comment typo
* Improve `SimpleStore` api
* permission-set NSID auth scopes
* Remove dev dependency on dev-env
* fix build script
* pnpm-lock
* Improve fetch-node unicast protection
* Explicitly set the `redirect: "follow"` `fetch()` option
* Add delay when building oauth-provider-ui in watch mode
* Remove external dependencies from auth-scopes
* Add customizable lexicon authority to pds (for dev purposes)
* fix pds migration
* update permission-set icon
* Add support for `include:` syntax in scopes
* tidy
* Renaming of "resource" concept to better reflect the fact that not all oauth scope values are about resources
* changeset
* ui improvmeents
* i18n
* ui imporvements
* add `AtprotoAudience` type
* Enforce proper formatting of audience (atproto supported did + fragment part)
* tidy
* tidy
* tidy
* fix ci ?
* ci fix ?
* tidy ?
* Apply consistent outline around focusable items
* Use `inheritAud: true` to control `aud` inheritance
* Update packages/oauth/oauth-provider/src/lexicon/lexicon-manager.ts
Co-authored-by: devin ivy <devinivy@gmail.com>
* Review comments
* Add `nsid` property to `LexiconResolutionError`
* improve nsid validation
* i18n
* Improve oauth scope parsing
* Simplify lex scope parsing
* tidy
* docs
* tidy
* ci
* Code simplification
* tidy
* improve type safety
* improve deps graph
* naming
* Improve tests and package structure
* Improve error when resolving a non permission-set
* improve nsid parsing perfs
* benchmark
* Refactor ozone and lexicon into using a common service profile mechanism
* improve perfs
* ci fix (?)
* tidy
* Allow storage of valid lexicons in lexicon store
* Improve handling of lexicon resolution failures
* review comment
* Test both regexp and non regexp based nsid validation
* properly detect presence of port number in https did:web
* Re-enable logging of `safeFetch` requests
* tidy
---------
Co-authored-by: devin ivy <devinivy@gmail.com>
* Support multiple redirect URIs for @atproto/oauth-client-browser
* For redirect_uri callback parameter type
* fix-type-error
* Do not fail if the client can't figure out which redirect uri was used (and only one is available)
---------
Co-authored-by: Emelia Smith <ThisIsMissEm@users.noreply.github.com>
* @atproto/lexicon: relax validation of lexicon documents to allow unknown fields
* changeset
* remove field from lexiconDoc validation, no longer necessary
* Remore requirement for JWK to define either `use` or `key_ops`
* Prevent inconsistent use of `use` and `key_ops` in JWK
* docs
* review comments
* comment
