Repository navigation
Add team-owned Library sourcing and tracking - #117
Merged
Merged
Conversation
…urces # Conflicts: # docs/LIBRARIES.md
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1017aedc55
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…urces # Conflicts: # apps/api/src/libraries/service.ts
…am-library-sources
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.
Team Libraries can now import and track public GitHub skills under team ownership. Another current curator can continue a source lineage after its initiating curator leaves. Libraries sharing a lineage retain independent adopted versions and notification audiences.
The change keeps importing, instance review, publication, adoption, and local installation separate. Team writes require current authority and MFA; imports retain author-role and token-scope checks. Revoked release grants are not recreated implicitly. Tracking pauses when no eligible curator remains and requires explicit resumption.
Team audience settings preserve existing Bundle owner access and management. Library-specific access and save operations still enforce the team switches, with sharing settings locked before Library writes.
Migration
0034_team_library_ownership.sqladds team ownership while preserving personal records, immutable attribution, and reserved orphaned slugs. Deployments must apply the migration before serving this code. There is no ownership transfer, private GitHub authentication, automatic local update, or scanner-policy change.Verification:
npm run check(1,206 tests), the full disposable Postgres suite (245 tests), eight production-wiring browser tests, and a real team browser/API/Postgres/CLI journey.main, including GitHub source authentication and workspace scopes, is integrated. Required GitHub Node 22/24 and CodeQL checks validate the final integrated head before merge.The deterministic source fixture verifies workflow behavior; it does not establish approval or compatibility of arbitrary upstream packages.