Skip to content
Open
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ jobs:
# This puts Katana in the path for integration tests.
- name: Download Katana for integration tests
run: |
curl -L https://github.com/dojoengine/katana/releases/download/v1.7.0/katana_v1.7.0_linux_amd64.tar.gz -o katana.tar.gz;
curl -L https://github.com/dojoengine/katana/releases/download/v1.7.1/katana_v1.7.1_linux_amd64.tar.gz -o katana.tar.gz;
tar -C /usr/local/bin -xzf katana.tar.gz

- run: |
Expand Down
10 changes: 5 additions & 5 deletions .tool-versions
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
scarb 2.13.1
starknet-foundry 0.51.0
scarb 2.15.0
starknet-foundry 0.55.0
cairo-profiler 0.9.0
katana 1.7.0
torii 1.8.3
sozo 1.8.0
katana 1.7.1
torii 1.8.14
sozo 1.8.6
Comment on lines +1 to +6
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.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

scarb 2.15.0 release Cairo compatibility

💡 Result:

Scarb v2.15.0 (released Dec 19, 2025) bundles Cairo compiler v2.15.0—so its “Cairo compatibility” is Cairo 2.15.0 (that’s the compiler version Scarb uses for builds/tests/docs generation, etc.). [1]

Scarb’s install docs also list 2.15.0 as the stable Scarb version (with prebuilt binaries), consistent with that release. [2]

Sources: [1] [2]


🌐 Web query:

starknet-foundry 0.55.0 release

💡 Result:

Starknet Foundry v0.55.0 (snforge/sncast) release highlights:

  • Forge (snforge)

    • Changed: minimal recommended Scarb version bumped to 2.13.1 (from 2.12.2). [1]
    • Changed: snforge_scarb_plugin now errors on unexpected named args for #[available_gas], #[fork], #[fuzzer], #[should_panic], #[test_case]. [1]
    • Fixed: fuzz output now displays byte arrays with non‑printable characters correctly. [1]
    • Deprecation notice: last release that publishes snforge_std_deprecated; migrate to snforge_std. [1][2]
  • Cast (sncast)

    • Added: network field can be configured in snfoundry.toml. [1]
    • Changed: --network can be used with --add-profile. [1]

Notes on library versions:

  • Docs show using snforge_std = "0.55.0" in Scarb.toml (should match your installed snforge version). [3]
  • snforge_std_deprecated 0.55.0 is published on Scarbs, marked deprecated (and is being discontinued after this). [2]

Sources: [1] [2] [3]


🌐 Web query:

katana 1.7.1 Starknet release

💡 Result:

  • There is no Dojo Starknet sequencer release called katana 1.7.1 in the official Dojo toolchain docs—Dojo’s recommended .tool-versions examples show sozo 1.7.1 but katana 1.7.0. [1]
  • Starknet compatibility: Dojo v1.7.x (including Katana 1.7.0) was aligned with Starknet 0.14.0 and adds/stabilizes support for Starknet RPC 0.9 across the stack (including Katana). [2][3]
  • Starknet 0.14.0 mainnet date: September 1, 2025. [2]

Sources
[1] Dojo Installation Guide (example .tool-versions: sozo 1.7.1, katana 1.7.0)
[2] Dojo 1.7 Upgrading Guide (Starknet 0.14.0 + RPC 0.9; mainnet date)
[3] Dojo GitHub releases (v1.7.x notes referencing Starknet 0.14 / RPC 0.9)


🌐 Web query:

torii 1.8.14 release

💡 Result:

I couldn’t find any “Torii” project that has a 1.8.14 release.

The most common “Torii” packages/repositories I can locate have different version lines:

  • Ember.js addon torii (npm): latest is 1.0.0 (recently published; repo is adopted-ember-addons/torii). [1]
  • Torii-HDL (PyPI): latest is 0.8.1 (Aug 3, 2025). [2]

If you tell me which Torii you mean (e.g., a GitHub repo link or language/ecosystem), I can pull the exact 1.8.14 release notes for that specific project.

Sources: [1] [2]


🌐 Web query:

sozo 1.8.6 release

💡 Result:

Sozo v1.8.6 (tag: sozo/v1.8.6, published Jan 29, 2026 on GitHub) adds Starknet network utility commands (e.g., fetch blocks / tx hashes, etc.) that work without requiring a Dojo or Scarb project. Use sozo starknet --help (or sozo sn --help) to see the new subcommands. [1]

Changes included

Full diff: sozo/v1.8.5...sozo/v1.8.6 [1]

Sources: [1] (github.com)

Citations:


🌐 Web query:

Torii Starknet Dojo tool version

💡 Result:

  • Latest Torii (Dojo/Starknet indexer) release: v1.8.10 (released Nov 24, 2025) [1]
  • Docs context: the Dojo Book page for Torii is currently shown under Dojo v1.7.0 docs [2]
  • Example .tool-versions from Dojo install guide: torii 1.8.3 (sample config, not necessarily the latest) [3]

How to confirm what you have installed locally: run torii --version. [2]

Sources: [1] GitHub releases list for dojoengine/torii; [2] Dojo Book “Torii” page; [3] Dojo installation guide.


🏁 Script executed:

# Check if torii is mentioned anywhere in the repository
rg -i "torii" --type txt --type toml --type json -A 2 -B 2

Repository: dojoengine/dojo

Length of output: 2800


ohayo sensei — Two tool versions don't exist; this will break CI.

katana 1.7.1 does not exist—Dojo official .tool-versions examples use katana 1.7.0.
torii 1.8.14 does not exist—latest released version is torii 1.8.10 (Nov 24, 2025).

Scarb 2.15.0, starknet-foundry 0.55.0, and sozo 1.8.6 are valid and available. Correct the katana and torii versions to avoid installation failures.

🤖 Prompt for AI Agents
In @.tool-versions around lines 1 - 6, Update the invalid tool versions in the
.tool-versions entry: replace the non-existent "katana 1.7.1" with "katana
1.7.0" and replace the non-existent "torii 1.8.14" with the latest released
"torii 1.8.10" so CI tool installation uses valid versions; ensure the lines
mentioning katana and torii are updated exactly (e.g., the "katana" and "torii"
entries).

Loading
Loading