build(deps-dev): bump @codama/renderers-rust from 1.2.9 to 3.0.0

[dependabot]

Bumps @codama/renderers-rust from 1.2.9 to 3.0.0.

Release notes

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

v3.0.0

Major Changes

• #92 4af6c06 Thanks @​grod220! - Removed default serde support and replaced kaigan with spl-collections

  BREAKING CHANGES:

  • Generated variable-sized string/vector wrappers now come from spl-collections instead of kaigan. If you have handwritten code that references these generated wrapper types, update those imports and usages after regenerating your client:

    • kaigan::types::RemainderStr -> spl_collections::TrailingStr
    • kaigan::types::RemainderVec<T> -> spl_collections::TrailingVec<T>
    • kaigan::types::U8PrefixString, U16PrefixString, U64PrefixString -> spl_collections::U8PrefixedStr, U16PrefixedStr, U64PrefixedStr
    • kaigan::types::U8PrefixVec<T>, U16PrefixVec<T>, U64PrefixVec<T> -> spl_collections::U8PrefixedVec<T>, U16PrefixedVec<T>, U64PrefixedVec<T>

  • serde is no longer part of the default or recommended generated client surface. The previous default derives on wrapper types were misleading because their serde representation does not match the Borsh/Wincode wire format.

  • If you still want serde derives for a separate JSON representation, you can opt in explicitly via traitOptions as shown below. This does not make the generated types serde-compatible with their Borsh/Wincode wire format, but you can define a handwritten implementation with your own serde mapping as needed.

      traitOptions: {
        baseDefaults: [
          'borsh::BorshSerialize',
          'borsh::BorshDeserialize',

  •   'serde::Serialize',
    

  •   'serde::Deserialize',
      'Clone',
      'Debug',
      'Eq',
      'PartialEq',
    ],
    

  • featureFlags: {

  •   serde: ['serde::Serialize', 'serde::Deserialize'],
    

  • }, }

• #90 f214970 Thanks @​grod220! - Switch generated Rust code from solana_pubkey::Pubkey to solana_address::Address and update the default dependency set to newer Solana 3.x and borsh 1.0 versions. This affects generated program IDs, account/instruction types, PDA helpers, and public key literals, so downstream users may need to update imports and pubkey usage after regenerating clients.

v2.0.1

Patch Changes

• #88 6477636 Thanks @​yihau! - resolve io_other_error and uninlined_format_args warnings

v2.0.0

Major Changes

• #85 44dacca Thanks @​lorisleiva! - Refactor renderVisitor to use crateFolder as its primary argument instead of the generated output path. The generated folder is now derived internally using a new generatedFolder option (defaults to 'src/generated'). Remove the crateFolder option as it is no longer needed.

  BREAKING CHANGES

... (truncated)

Changelog

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

3.0.0

Major Changes

• #92 4af6c06 Thanks @​grod220! - Removed default serde support and replaced kaigan with spl-collections

  BREAKING CHANGES:

  • Generated variable-sized string/vector wrappers now come from spl-collections instead of kaigan. If you have handwritten code that references these generated wrapper types, update those imports and usages after regenerating your client:
    • kaigan::types::RemainderStr -> spl_collections::TrailingStr
    • kaigan::types::RemainderVec<T> -> spl_collections::TrailingVec<T>
    • kaigan::types::U8PrefixString, U16PrefixString, U64PrefixString -> spl_collections::U8PrefixedStr, U16PrefixedStr, U64PrefixedStr
    • kaigan::types::U8PrefixVec<T>, U16PrefixVec<T>, U64PrefixVec<T> -> spl_collections::U8PrefixedVec<T>, U16PrefixedVec<T>, U64PrefixedVec<T>
  • serde is no longer part of the default or recommended generated client surface. The previous default derives on wrapper types were misleading because their serde representation does not match the Borsh/Wincode wire format.
  • If you still want serde derives for a separate JSON representation, you can opt in explicitly via traitOptions as shown below. This does not make the generated types serde-compatible with their Borsh/Wincode wire format, but you can define a handwritten implementation with your own serde mapping as needed.

    traitOptions: {
      baseDefaults: [
        'borsh::BorshSerialize',
        'borsh::BorshDeserialize',
  +     'serde::Serialize',
  +     'serde::Deserialize',
        'Clone',
        'Debug',
        'Eq',
        'PartialEq',
      ],
  +   featureFlags: {
  +     serde: ['serde::Serialize', 'serde::Deserialize'],
  +   },
    }

• #90 f214970 Thanks @​grod220! - Switch generated Rust code from solana_pubkey::Pubkey to solana_address::Address and update the default dependency set to newer Solana 3.x and borsh 1.0 versions. This affects generated program IDs, account/instruction types, PDA helpers, and public key literals, so downstream users may need to update imports and pubkey usage after regenerating clients.

2.0.1

Patch Changes

• #88 6477636 Thanks @​yihau! - resolve io_other_error and uninlined_format_args warnings

2.0.0

Major Changes

• #85 44dacca Thanks @​lorisleiva! - Refactor renderVisitor to use crateFolder as its primary argument instead of the generated output path. The generated folder is now derived internally using a new generatedFolder option (defaults to 'src/generated'). Remove the crateFolder option as it is no longer needed.

  BREAKING CHANGES

  First argument of renderVisitor changed from output path to crate folder. The function now takes the crate folder (where Cargo.toml lives) and derives the generated output path internally.

... (truncated)

Commits

• 0a65cc6 Publish package (#91)
• 4af6c06 Deprecate default serde & add spl-collections (#92)
• f214970 Migrate from solana-pubkey to solana-address (#90)
• a7b322a Publish package (#89)
• 6477636 chore: resolve io_other_error and uninlined_format_args warnings for rust 1.8...
• bcaed69 Publish package (#86)
• 44dacca Refactor renderVisitor to use crateFolder as primary argument (#85)
• f0fbbb0 Sync Cargo.toml when generating code (#70)
• c1bd049 build(deps-dev): bump @​types/node from 25.0.0 to 25.0.1 (#80)
• 1e59964 build(deps): bump the codama group with 5 updates (#79)
• Additional commits viewable in compare view

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)