Skip to content

feat(marketplace): access matrix, role package, custom policy and OAuth sign-in hooks - #55

Merged
Domantas merged 2 commits into
mainfrom
audit/marketplace-access
Oct 13, 2026
Merged

Domantas merged 2 commits into
mainfrom
audit/marketplace-access

Conversation

@Domantas

Copy link
Copy Markdown
Contributor

What changed

  • @norbix.ai/ts ^4.24.0 (released from sdk-ts PR #91).
  • Hooks for marketplace routes 25–28: useGetMarketplaceIntegrationAccessQuery (provides CodeMarketplace/ACCESS:<int>), useSetMarketplaceIntegrationRoleAccessMutation and useSaveMarketplaceIntegrationCustomAccessMutation (invalidate only that connection's ACCESS:<int>), useStartMarketplaceIntegrationSignInMutation (invalidates nothing; the connection changes after the vendor's callback). Test, delete, function save and function delete also invalidate ACCESS:<int> (the gateway re-syncs the packages after them). README rows.
  • Tests: typecheck, lint clean; vitest 16 files / 365 passed (+10: wire cases through the real SDK for the four routes, tag tests).

Task file: typegen docs/tasks/marketplace-access-sdks.md (branch audit/marketplace-access2). Expected release: v1.15.0 (feat → minor). Additive only.

🤖 Generated with Claude Code

Domantas and others added 2 commits October 13, 2026 16:47
…OAuth sign-in route 28)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…th sign-in hooks

useGetMarketplaceIntegrationAccessQuery provides ACCESS:<int>;
useSetMarketplaceIntegrationRoleAccessMutation and
useSaveMarketplaceIntegrationCustomAccessMutation invalidate only that
connection's matrix. Test, delete, function save and function delete
invalidate it too (the gateway re-syncs the packages after them).
useStartMarketplaceIntegrationSignInMutation (route 28) invalidates
nothing: the connection changes only after the vendor's callback. Wire
cases for the four routes, tag tests, README rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🚀 Release preview

Next version on merge to main: none

semantic-release dry-run output
[1:57:29 PM] [semantic-release] › ℹ  Running semantic-release version 25.0.9
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[1:57:29 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[1:57:30 PM] [semantic-release] › ℹ  This test run was triggered on the branch refs/pull/55/merge, while semantic-release is configured to only publish from main, therefore a new version won’t be published.

If next_version is none, your commits don't trigger a release. Use feat: for minor (breaking changes too, until launch), fix: / perf: for patch.

@Domantas
Domantas merged commit 44efa13 into main Oct 13, 2026
7 checks passed
@Domantas
Domantas deleted the audit/marketplace-access branch October 13, 2026 14:05
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.15.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant