chore: version packages

[github-actions]

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

@github-tools/sdk@1.17.0

Minor Changes

• #158 5df1f13 Thanks @HugoRCD! - Mint Vercel Connect tokens per tool call, for the call's target repository. This covers GitHub Apps installed on several accounts.

  • connect on githubExtension accepts a (ctx, call) => params resolver, where call is { toolName, input, owner?, repo? }. owner / repo are the tool's inputs after context defaults, and are undefined for tools without a repository target (search, gists, notifications). The static shape and the connect.subject resolver keep working unchanged.
  • New perRepository(params?) in @github-tools/sdk/connect: connect: perRepository() mints each token with authorizationDetails: [{ type: 'github_app_installation', org: owner, repositories: [repo] }], and falls back to the static params for calls without a repository target. It works with githubExtension, connectGithubTools, and connectGithubToken. Using it from an eve agent requires @github-tools/sdk as a direct dependency.
  • connectGithubTools / connectGithubToken accept a (call) => params resolver as connect / params. Scopes still derive from preset / include / exclude unless the resolved params set scopes. Connect caches tokens per connector and params, so calls on the same repository reuse one token.
  • Token providers (GithubTokenInput) now receive an optional GithubTokenCall argument on every tool call, from both createGithubTools and the eve runtime. Existing () => Promise<string> providers are unaffected.
  • CONNECT_INSTALLATION_REQUIRED names the target account ("The connector's GitHub App is not installed on ") when the token targets an org or repository owner.

@github-tools/eve-extension@0.8.0

Minor Changes

• #158 5df1f13 Thanks @HugoRCD! - Mint Vercel Connect tokens per tool call, for the call's target repository. This covers GitHub Apps installed on several accounts.

  • connect on githubExtension accepts a (ctx, call) => params resolver, where call is { toolName, input, owner?, repo? }. owner / repo are the tool's inputs after context defaults, and are undefined for tools without a repository target (search, gists, notifications). The static shape and the connect.subject resolver keep working unchanged.
  • New perRepository(params?) in @github-tools/sdk/connect: connect: perRepository() mints each token with authorizationDetails: [{ type: 'github_app_installation', org: owner, repositories: [repo] }], and falls back to the static params for calls without a repository target. It works with githubExtension, connectGithubTools, and connectGithubToken. Using it from an eve agent requires @github-tools/sdk as a direct dependency.
  • connectGithubTools / connectGithubToken accept a (call) => params resolver as connect / params. Scopes still derive from preset / include / exclude unless the resolved params set scopes. Connect caches tokens per connector and params, so calls on the same repository reuse one token.
  • Token providers (GithubTokenInput) now receive an optional GithubTokenCall argument on every tool call, from both createGithubTools and the eve runtime. Existing () => Promise<string> providers are unaffected.
  • CONNECT_INSTALLATION_REQUIRED names the target account ("The connector's GitHub App is not installed on ") when the token targets an org or repository owner.

Patch Changes

• Updated dependencies [5df1f13]:
  • @github-tools/sdk@1.17.0