Skip to content

deps: update Zaino pin to zingolabs/zaino#1238#482

Merged
nuttycom merged 1 commit into
mainfrom
bump/zaino
Jun 17, 2026
Merged

deps: update Zaino pin to zingolabs/zaino#1238#482
nuttycom merged 1 commit into
mainfrom
bump/zaino

Conversation

@nullcopy

@nullcopy nullcopy commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Bumps the temporary Zaino git pin from zingolabs/zaino#1200 to the latest commit on the rc-0.4.0 branch (zingolabs/zaino#1238), which speeds up finalised-state sync and the v1.1->v1.2 migration. This remains a temporary pin and should be moved to the 0.4.0 release tag once it is published (see #471).

The pin bumped zaino-fetch to 0.2 and zaino-state to 0.3, so the workspace dependency requirements are updated to match. Adapts the embedded indexer setup to two upstream API changes:

  • ChainIndexConfig was renamed to BlockCacheConfig (same constructor signature).
  • DatabaseConfig gained a sync_write_batch_bytes field, which is unused in our ephemeral-mode configuration; inherit Zaino's default.

Closes COR-1360

Bumps the temporary Zaino git pin from zingolabs/zaino#1200 to the
latest commit on the rc-0.4.0 branch (zingolabs/zaino#1238), which
speeds up finalised-state sync and the v1.1->v1.2 migration. This
remains a temporary pin and should be moved to the `0.4.0` release tag
once it is published (see #471).

The pin bumped `zaino-fetch` to 0.2 and `zaino-state` to 0.3, so the
workspace dependency requirements are updated to match. Adapts the
embedded indexer setup to two upstream API changes:

- `ChainIndexConfig` was renamed to `BlockCacheConfig` (same
  constructor signature).
- `DatabaseConfig` gained a `sync_write_batch_bytes` field, which is
  unused in our ephemeral-mode configuration; inherit Zaino's default.

Co-Authored-By: Claude <noreply@anthropic.com>
@linear

linear Bot commented Jun 17, 2026

Copy link
Copy Markdown

COR-1360

@nullcopy nullcopy marked this pull request as ready for review June 17, 2026 16:19

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Zallet’s temporary git pin of the Zaino indexer to a newer commit on the rc-0.4.0 branch, and adjusts the wallet’s dependency constraints and embedded indexer configuration to match upstream API changes.

Changes:

  • Bumped the pinned Zaino git revision and aligned workspace versions for zaino-fetch (0.2) and zaino-state (0.3).
  • Updated embedded indexer configuration to use BlockCacheConfig and to accommodate the new DatabaseConfig field via defaults.
  • Refreshed supply-chain exemptions and changelog entry to reflect the new pin/branch.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
zallet/src/components/chain.rs Adapts to Zaino API rename (ChainIndexConfigBlockCacheConfig) and updates DatabaseConfig construction.
supply-chain/config.toml Updates cargo-deny exemptions for the newly pinned Zaino crate versions/revision.
CHANGELOG.md Updates the release notes to reference the new Zaino pre-release pin.
Cargo.toml Updates workspace dependency requirements and the [patch.crates-io] git pin rev/comment for Zaino crates.
Cargo.lock Locks the new Zaino git revision and updated crate versions.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@nuttycom nuttycom left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@nuttycom nuttycom merged commit 2374db9 into main Jun 17, 2026
28 checks passed
nullcopy pushed a commit that referenced this pull request Jun 17, 2026
@nuttycom nuttycom deleted the bump/zaino branch June 17, 2026 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants