Repository navigation
Conversation
Tracks contract revision 61610853b4 of polymorfa/polymorfa#887. Renames the --owner value, profile key, principal type, output fields, SDK credential and client names, help text, README, skills and tests. No aliases or shims. Regenerates contracts/cli-reference.json.
|
Warning Review limit reachedThe included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 28 minutes. View limit details
|
Codex Review Summary: ✅ CompletedThis 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: 5f63032bb5
ℹ️ 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".
| 'team', | ||
| 'project', | ||
| ]) | ||
| if (Object.keys(value).some((key) => !profileKeys.has(key))) return false |
There was a problem hiding this comment.
When upgrading with an existing config containing organization or owner: 'organization', the renamed validator rejects previously valid version-1 and version-2 profiles as having an invalid shape. validateConfig still accepts those config versions but performs no migration, so one legacy profile prevents the entire config from loading, breaking profile-backed commands and even auth login and auth logout, which also load it first. Normalize the legacy field and owner value to their team equivalents before applying the new validation.
Useful? React with 👍 / 👎.
Renames "organization" to "team" across the CLI. Greenfield: no deprecated aliases or shims.
Tracks contract revision
61610853b4of polymorfa/polymorfa#887.Depends on the polymorfa/sdks team-rename PR (
organizationApiKey→teamApiKey,OrganizationClient→TeamClient,organizations→teams,validateOrganizationApiKey→validateTeamApiKey,ClientInstance<'organization'>→ClientInstance<'team'>).Must merge after #887 and the SDK PR.
package.jsonstill pins the current published@polymorfa/sdk; it must be bumped to the SDK release that carries the rename before this merges. Nothing is published here.Renamed surface
--owner organization→--owner team(every command that takes--owner; value choices are nowproject|team)organization→teamprincipalTypeorganization_key→team_key,organizationId→teamId, resource ownerorganization→teamorganizationId→teamIdorganizationApiKey→teamApiKeyorg_*→team_*POLYMORFA_API_KEY), so none changed.Kept (not the tenant):
message send contact --organization(vCardORG:company field), npm/GitHub organization wording ininternal/npm-prerelease.md,.orgURLs.Reference artifact
contracts/cli-reference.jsonregenerated (npm run docs:reference, 381 commands) for the docs app'ssync-cli-reference.mjs.Five-part assessment
teamId,team_key,bansafe_team_suspended,teamsroutes through the SDK.contracts/abprops-capabilities.jsonupdated for the renamed error code.docs/and the reference artifact. The public Mintlify CLI reference in polymorfa/polymorfa syncs fromcontracts/cli-reference.jsonafter this merges; not yet synced.Verification
tsctypecheck,eslint .,prettier --check: cleanvitest run: 1169/1169 pass (with--maxWorkers=3 --testTimeout=30000; the default run shows load-related 5s timeouts on a busy machine)npm run docs:reference: regeneratedverify:browser,verify:bundled-runtime,npm pack,audit:prod, and a build against the real renamed SDK release.\borg(anization)?s?\b|orgId|organizationId|organization_api_key|ORG_KEY|--org\b: remaining hits are only the vendor/non-tenant items listed above plus.orgURLs (registry.npmjs.org).Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Contract and dependency status (2026-11-12)
devasa3db53e74c6e24507ca01e2ff6ecba19358422c7. Its specs are identical to contract revisionf180dc1ee2.mainas6f4afba13d48ba55356def32b6aa1aa2f169f5a7.@polymorfa/sdk, which still exports the organization names (validateOrganizationApiKey,Client<'organization'>). No SDK release with the team names exists yet. The nightly publish (publish-dev.yml) builds only after staging acceptance passes for the API commit pinned in the SDK'scontracts/source.json, which needs #887 deployed to staging. Once a nightly0.x.y-dev.<timestamp>is published, bump the exact@polymorfa/*versions here, rerun CI, and merge.