Skip to content

build(deps-dev): bump @codama/renderers-js from 1.7.0 to 2.0.2#268

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/codama/renderers-js-2.0.2
Open

build(deps-dev): bump @codama/renderers-js from 1.7.0 to 2.0.2#268
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/codama/renderers-js-2.0.2

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 18, 2026

Bumps @codama/renderers-js from 1.7.0 to 2.0.2.

Release notes

Sourced from @​codama/renderers-js's releases.

v2.0.2

Patch Changes

v2.0.1

Patch Changes

  • #121 1944b95 Thanks @​lorisleiva! - Fix the generated plugin instruction type to use ReturnType<typeof instructionFunction> instead of manually constructing the return type, and make payer default values optional in the plugin's instruction input type.

v2.0.0

Major Changes

  • #114 9ac7e22 Thanks @​lorisleiva! - Remove the generated shared.ts file from the output. Helper types and functions such as ResolvedAccount, InstructionWithByteDelta, and getAccountMetaFactory are now imported from @solana/kit/program-client-core.

    BREAKING CHANGES

    • The shared folder is no longer generated. Any imports from generated/shared should be updated to import from @solana/kit/program-client-core.
    • The getAccountMetaFactory function now requires the account name as the first argument.
    • The ResolvedAccount type has been replaced with ResolvedInstructionAccount.
    • The expectSome function has been replaced with getNonNullResolvedInstructionInput.
    • The expectAddress function has been replaced with getAddressFromResolvedInstructionAccount.
    • The expectTransactionSigner function has been replaced with getResolvedInstructionAccountAsTransactionSigner.
    • The expectProgramDerivedAddress function has been replaced with getResolvedInstructionAccountAsProgramDerivedAddress.
  • #117 b9d76cd Thanks @​lorisleiva! - Replace the useGranularImports boolean option with a new kitImportStrategy option that accepts 'granular', 'preferRoot' (default), or 'rootOnly'. This provides finer control over how generated code imports from @solana/kit versus granular packages like @solana/addresses or @solana/codecs-strings. The new 'preferRoot' default imports from @solana/kit when possible but falls back to granular packages for symbols not exported from the root entrypoint. The 'rootOnly' strategy exclusively uses @solana/kit (including subpath exports like @solana/kit/program-client-core).

    BREAKING CHANGES

    • The useGranularImports option has been removed. Use kitImportStrategy: 'granular' instead of useGranularImports: true, and kitImportStrategy: 'rootOnly' instead of useGranularImports: false.
    • The default import behavior has changed from resolving everything to @solana/kit to 'preferRoot', which falls back to granular packages for symbols not available on the root @solana/kit entrypoint (e.g. @solana/program-client-core).
  • #118 4902cfe Thanks @​lorisleiva! - Refactor renderVisitor to accept packageFolder as its primary argument instead of the generated output path. The generated folder is now derived from the package folder using the new generatedFolder option (defaults to 'src/generated'). The syncPackageJson option now defaults to true and no longer requires a separate packageFolder option.

    BREAKING CHANGES

    renderVisitor first argument changed. The first argument is now the package folder (where package.json lives) instead of the direct path to the generated output directory.

    - const visitor = renderVisitor('clients/js/src/generated', { packageFolder: 'clients/js' });
    + const visitor = renderVisitor('clients/js');

    packageFolder option removed. It is no longer needed since the package folder is now the primary argument.

    syncPackageJson now defaults to true. Previously it defaulted to false and required packageFolder to be set.

    - renderVisitor('clients/js/src/generated', { packageFolder: 'clients/js', syncPackageJson: true });
    + renderVisitor('clients/js');

... (truncated)

Changelog

Sourced from @​codama/renderers-js's changelog.

2.0.2

Patch Changes

2.0.1

Patch Changes

  • #121 1944b95 Thanks @​lorisleiva! - Fix the generated plugin instruction type to use ReturnType<typeof instructionFunction> instead of manually constructing the return type, and make payer default values optional in the plugin's instruction input type.

2.0.0

Major Changes

  • #114 9ac7e22 Thanks @​lorisleiva! - Remove the generated shared.ts file from the output. Helper types and functions such as ResolvedAccount, InstructionWithByteDelta, and getAccountMetaFactory are now imported from @solana/kit/program-client-core.

    BREAKING CHANGES

    • The shared folder is no longer generated. Any imports from generated/shared should be updated to import from @solana/kit/program-client-core.
    • The getAccountMetaFactory function now requires the account name as the first argument.
    • The ResolvedAccount type has been replaced with ResolvedInstructionAccount.
    • The expectSome function has been replaced with getNonNullResolvedInstructionInput.
    • The expectAddress function has been replaced with getAddressFromResolvedInstructionAccount.
    • The expectTransactionSigner function has been replaced with getResolvedInstructionAccountAsTransactionSigner.
    • The expectProgramDerivedAddress function has been replaced with getResolvedInstructionAccountAsProgramDerivedAddress.
  • #117 b9d76cd Thanks @​lorisleiva! - Replace the useGranularImports boolean option with a new kitImportStrategy option that accepts 'granular', 'preferRoot' (default), or 'rootOnly'. This provides finer control over how generated code imports from @solana/kit versus granular packages like @solana/addresses or @solana/codecs-strings. The new 'preferRoot' default imports from @solana/kit when possible but falls back to granular packages for symbols not exported from the root entrypoint. The 'rootOnly' strategy exclusively uses @solana/kit (including subpath exports like @solana/kit/program-client-core).

    BREAKING CHANGES

    • The useGranularImports option has been removed. Use kitImportStrategy: 'granular' instead of useGranularImports: true, and kitImportStrategy: 'rootOnly' instead of useGranularImports: false.
    • The default import behavior has changed from resolving everything to @solana/kit to 'preferRoot', which falls back to granular packages for symbols not available on the root @solana/kit entrypoint (e.g. @solana/program-client-core).
  • #118 4902cfe Thanks @​lorisleiva! - Refactor renderVisitor to accept packageFolder as its primary argument instead of the generated output path. The generated folder is now derived from the package folder using the new generatedFolder option (defaults to 'src/generated'). The syncPackageJson option now defaults to true and no longer requires a separate packageFolder option.

    BREAKING CHANGES

    renderVisitor first argument changed. The first argument is now the package folder (where package.json lives) instead of the direct path to the generated output directory.

    - const visitor = renderVisitor('clients/js/src/generated', { packageFolder: 'clients/js' });
    + const visitor = renderVisitor('clients/js');

    packageFolder option removed. It is no longer needed since the package folder is now the primary argument.

    syncPackageJson now defaults to true. Previously it defaulted to false and required packageFolder to be set.

    - renderVisitor('clients/js/src/generated', { packageFolder: 'clients/js', syncPackageJson: true });

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Feb 18, 2026
@github-actions github-actions bot enabled auto-merge (squash) February 18, 2026 09:14
github-actions[bot]
github-actions bot previously approved these changes Feb 18, 2026
Bumps [@codama/renderers-js](https://github.com/codama-idl/renderers-js) from 1.7.0 to 2.0.2.
- [Release notes](https://github.com/codama-idl/renderers-js/releases)
- [Changelog](https://github.com/codama-idl/renderers-js/blob/main/CHANGELOG.md)
- [Commits](codama-idl/renderers-js@v1.7.0...v2.0.2)

---
updated-dependencies:
- dependency-name: "@codama/renderers-js"
  dependency-version: 2.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/codama/renderers-js-2.0.2 branch from a675058 to bf2bc2c Compare February 19, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

Comments