Bump version to v0.3.0 #768
Conversation
📝 WalkthroughSummary by CodeRabbitRelease Notes
Summary by CodeRabbit
WalkthroughRepository-wide manifest updates: the "version" field in many package.json files (root, benchmarks, bin, packages/core, packages/jam, packages/workers, etc.) was changed (mostly from 0.2.0 and a few from 0.1.3) to 0.3.0. No dependency, script, or source-code behavior changes except for packages/jam/node/main-fuzz.test.ts, which was modified to parse expected version components from package.json and CURRENT_VERSION instead of using hard-coded literals. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
bin/rpc/package.json (1)
36-36: Consider updating zod to v4 in a future PR.The project currently uses zod 3.25.30, which is outdated. Zod 4 introduces unified error customization, safer number validation (e.g., rejecting infinite values), and performance improvements. This is outside the scope of the current version bump but worth considering for a future enhancement.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (60)
benchmarks/package.json(1 hunks)bin/convert/package.json(1 hunks)bin/ipc2rpc/package.json(1 hunks)bin/jam/package.json(1 hunks)bin/lib/package.json(1 hunks)bin/pvm/package.json(1 hunks)bin/rpc/package.json(1 hunks)bin/tci/package.json(1 hunks)bin/test-runner/package.json(1 hunks)package.json(1 hunks)packages/configs/package.json(1 hunks)packages/core/bytes/package.json(1 hunks)packages/core/codec/package.json(1 hunks)packages/core/collections/package.json(1 hunks)packages/core/concurrent/package.json(1 hunks)packages/core/crypto/package.json(1 hunks)packages/core/erasure-coding/package.json(1 hunks)packages/core/hash/package.json(1 hunks)packages/core/json-parser/package.json(1 hunks)packages/core/listener/package.json(1 hunks)packages/core/logger/package.json(1 hunks)packages/core/mmr/package.json(1 hunks)packages/core/networking/package.json(1 hunks)packages/core/numbers/package.json(1 hunks)packages/core/ordering/package.json(1 hunks)packages/core/pvm-debugger-adapter/package.json(1 hunks)packages/core/pvm-host-calls/package.json(1 hunks)packages/core/pvm-interface/package.json(1 hunks)packages/core/pvm-interpreter-ananas/package.json(1 hunks)packages/core/pvm-interpreter/package.json(1 hunks)packages/core/pvm-program/package.json(1 hunks)packages/core/pvm-spi-decoder/package.json(1 hunks)packages/core/shuffling/package.json(1 hunks)packages/core/trie/package.json(1 hunks)packages/core/utils/package.json(1 hunks)packages/extensions/ipc/package.json(1 hunks)packages/jam/block-json/package.json(1 hunks)packages/jam/block/package.json(1 hunks)packages/jam/config-node/package.json(1 hunks)packages/jam/config/package.json(1 hunks)packages/jam/database-lmdb/package.json(1 hunks)packages/jam/database/package.json(1 hunks)packages/jam/fuzz-proto/package.json(1 hunks)packages/jam/jam-host-calls/package.json(1 hunks)packages/jam/jamnp-s/package.json(1 hunks)packages/jam/node/package.json(1 hunks)packages/jam/safrole/package.json(1 hunks)packages/jam/state-json/package.json(1 hunks)packages/jam/state-merkleization/package.json(1 hunks)packages/jam/state-vectors/package.json(1 hunks)packages/jam/state/package.json(1 hunks)packages/jam/transition/disputes/package.json(1 hunks)packages/jam/transition/package.json(1 hunks)packages/misc/benchmark/package.json(1 hunks)packages/misc/builder/package.json(1 hunks)packages/workers/api-node/package.json(1 hunks)packages/workers/api/package.json(1 hunks)packages/workers/block-generator/package.json(1 hunks)packages/workers/importer/package.json(1 hunks)packages/workers/jam-network/package.json(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
packages/**/package.json
⚙️ CodeRabbit configuration file
packages/**/package.json: Whenever a new package is added, thepackages/README.mdshould be updated accordingly.
packages/**/package.json: Dependencies coming from the workspace (typically the ones starting with@typeberry/)
must use*as version.
Files:
packages/jam/state-merkleization/package.jsonpackages/jam/state-json/package.jsonpackages/jam/state/package.jsonpackages/jam/block/package.jsonpackages/jam/transition/package.jsonpackages/jam/jam-host-calls/package.jsonpackages/core/pvm-interpreter/package.jsonpackages/core/pvm-program/package.jsonpackages/core/erasure-coding/package.jsonpackages/core/ordering/package.jsonpackages/core/numbers/package.jsonpackages/jam/transition/disputes/package.jsonpackages/core/shuffling/package.jsonpackages/core/bytes/package.jsonpackages/core/networking/package.jsonpackages/core/mmr/package.jsonpackages/core/trie/package.jsonpackages/jam/config-node/package.jsonpackages/core/concurrent/package.jsonpackages/workers/api/package.jsonpackages/core/pvm-interface/package.jsonpackages/core/json-parser/package.jsonpackages/core/logger/package.jsonpackages/core/collections/package.jsonpackages/jam/jamnp-s/package.jsonpackages/jam/config/package.jsonpackages/misc/builder/package.jsonpackages/configs/package.jsonpackages/jam/node/package.jsonpackages/core/listener/package.jsonpackages/core/pvm-interpreter-ananas/package.jsonpackages/core/pvm-debugger-adapter/package.jsonpackages/jam/state-vectors/package.jsonpackages/core/crypto/package.jsonpackages/core/pvm-host-calls/package.jsonpackages/jam/safrole/package.jsonpackages/workers/api-node/package.jsonpackages/misc/benchmark/package.jsonpackages/extensions/ipc/package.jsonpackages/core/pvm-spi-decoder/package.jsonpackages/core/hash/package.jsonpackages/jam/block-json/package.jsonpackages/workers/block-generator/package.jsonpackages/workers/importer/package.jsonpackages/jam/fuzz-proto/package.jsonpackages/core/utils/package.jsonpackages/jam/database/package.jsonpackages/workers/jam-network/package.jsonpackages/core/codec/package.jsonpackages/jam/database-lmdb/package.json
🧠 Learnings (6)
📚 Learning: 2025-09-15T14:37:04.214Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 625
File: benchmarks/package.json:8-15
Timestamp: 2025-09-15T14:37:04.214Z
Learning: In the FluffyLabs/typeberry monorepo, the workspace:* protocol does not work for internal typeberry dependencies. The working approach is to use "*" as the version specifier for internal monorepo packages instead of "workspace:*".
Applied to files:
bin/tci/package.jsonpackages/core/pvm-interpreter/package.jsonpackage.jsonpackages/core/pvm-program/package.jsonbin/lib/package.jsonpackages/core/numbers/package.jsonpackages/core/bytes/package.jsonpackages/jam/config-node/package.jsonpackages/workers/api/package.jsonpackages/core/pvm-interface/package.jsonbin/rpc/package.jsonpackages/jam/config/package.jsonpackages/misc/builder/package.jsonpackages/jam/node/package.jsonbin/jam/package.jsonpackages/core/pvm-debugger-adapter/package.jsonpackages/core/pvm-host-calls/package.jsonpackages/workers/api-node/package.jsonpackages/extensions/ipc/package.jsonpackages/jam/fuzz-proto/package.jsonpackages/core/utils/package.jsonpackages/workers/jam-network/package.jsonbin/pvm/package.json
📚 Learning: 2025-06-18T20:35:13.536Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 442
File: packages/core/pvm-debugger-adapter/index.ts:22-40
Timestamp: 2025-06-18T20:35:13.536Z
Learning: The `typeberry/utils` package has browser compatibility issues due to Node.js-specific code like `measure` function using `process.hrtime()` and `testUtils` importing `node:assert`, causing white screens in browser environments.
Applied to files:
bin/tci/package.jsonbin/lib/package.jsonpackages/core/bytes/package.jsonpackages/jam/config-node/package.jsonbenchmarks/package.jsonpackages/misc/builder/package.jsonpackages/jam/node/package.jsonpackages/misc/benchmark/package.jsonpackages/core/hash/package.jsonpackages/core/utils/package.jsonbin/test-runner/package.json
📚 Learning: 2025-05-26T21:31:58.688Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 399
File: .github/workflows/vectors-jamduna.yml:78-78
Timestamp: 2025-05-26T21:31:58.688Z
Learning: In the typeberry project, the npm start script in the test-runner workspace is designed to accept test suite names as arguments (e.g., "jamduna", "w3f"). The command `npm start -w typeberry/test-runner jamduna` is the correct way to run the jamduna test suite, not `npm run jamduna`. This is an architectural design choice where the start script acts as a unified entry point for different test suites.
Applied to files:
package.jsonbin/jam/package.jsonpackages/misc/benchmark/package.jsonpackages/workers/jam-network/package.jsonbin/test-runner/package.json
📚 Learning: 2025-04-24T19:48:31.051Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 351
File: packages/jam/state-merkleization/index.ts:19-37
Timestamp: 2025-04-24T19:48:31.051Z
Learning: In the typeberry codebase, `Bytes` inherits from `BytesBlob`, so a `Bytes` instance can be directly used where a `BytesBlob` is expected without needing conversion.
Applied to files:
packages/core/bytes/package.json
📚 Learning: 2025-06-18T20:35:13.536Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 442
File: packages/core/pvm-debugger-adapter/index.ts:22-40
Timestamp: 2025-06-18T20:35:13.536Z
Learning: The `measure` function in `typeberry/utils/debug.ts` attempts environment detection by checking `process === undefined` but still causes bundling issues because bundlers see the `process.hrtime` reference in the Node.js branch.
Applied to files:
benchmarks/package.jsonpackages/misc/benchmark/package.jsonpackages/core/utils/package.json
📚 Learning: 2025-04-24T19:42:18.083Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 351
File: bin/jam/genesis.ts:7-11
Timestamp: 2025-04-24T19:42:18.083Z
Learning: Error handling for file operations and JSON parsing in the typeberry project is done at a higher level in the call stack rather than within individual utility functions.
Applied to files:
packages/core/json-parser/package.jsonpackages/core/utils/package.json
⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
- GitHub Check: run (22.x)
- GitHub Check: run (22.x)
- GitHub Check: run (22.x)
- GitHub Check: run (22.x)
- GitHub Check: e2e (22.x)
- GitHub Check: test (22.x)
🔇 Additional comments (60)
packages/jam/fuzz-proto/package.json (1)
3-3: Version bump applied correctly.All workspace dependencies (@typeberry/) correctly use "" as the version specifier.
bin/tci/package.json (1)
3-3: Version bump applied correctly.All workspace dependencies use "*" as the version specifier, and external dependencies remain appropriately pinned.
packages/core/json-parser/package.json (1)
3-3: Version bump applied correctly.No dependency changes in this package.
packages/jam/node/package.json (1)
3-3: Version bump applied correctly.All 24 workspace dependencies correctly use "*" as the version specifier.
packages/jam/database-lmdb/package.json (1)
3-3: Version bump applied correctly.All workspace dependencies use "*" as the version specifier, and external dependency (lmdb) is appropriately pinned.
packages/core/numbers/package.json (1)
3-3: Version bump applied correctly.Workspace dependency (@typeberry/utils) correctly uses "*" as the version specifier.
packages/configs/package.json (1)
3-3: Version bump applied correctly.No dependencies in this package.
packages/core/networking/package.json (1)
3-3: Version bump applied correctly.All workspace dependencies use "*" as the version specifier, and external dependencies are appropriately pinned.
packages/core/mmr/package.json (1)
3-3: Version bump looks good. All internal dependencies correctly use*as version specifier.packages/misc/builder/package.json (1)
3-3: Version bump approved. No internal dependencies; external dev dependencies unchanged.packages/jam/block/package.json (1)
3-3: Version bump looks good. All internal dependencies correctly use*as version specifier.packages/core/bytes/package.json (1)
3-3: Version bump approved. All internal dependencies correctly use*as version specifier.packages/core/listener/package.json (1)
3-3: Version bump approved. No dependencies to verify.packages/core/trie/package.json (1)
3-3: Version bump looks good. All internal dependencies correctly use*as version specifier.packages/jam/config-node/package.json (1)
3-3: Version bump approved. All internal dependencies correctly use*as version specifier.packages/workers/api/package.json (1)
3-3: Version bump looks good. All internal dependencies correctly use*as version specifier.packages/extensions/ipc/package.json (1)
3-3: Version bump applied consistently with correct dependency versioning.All internal
@typeberry/*dependencies correctly use*as the version specifier, following the monorepo pattern.packages/workers/jam-network/package.json (1)
3-3: Version bump consistent with workspace dependency pattern.All
@typeberry/*dependencies maintain the*version specifier required for monorepo packages.benchmarks/package.json (1)
3-3: Version bump aligns with monorepo versioning strategy.Internal dependencies correctly use
*, and external packages retain explicit versions.packages/jam/database/package.json (1)
3-3: Version bump follows established monorepo patterns.All workspace dependencies correctly use the
*version specifier.packages/core/hash/package.json (1)
3-3: Version bump applied correctly with proper dependency versioning.Workspace dependencies use
*, and external packages retain pinned versions.packages/jam/jam-host-calls/package.json (1)
3-3: Version bump consistent across workspace dependencies.All internal
@typeberry/*packages correctly use*as the version specifier.package.json (1)
3-3: Root version bump applied.Version updated in sync with workspace packages.
packages/jam/transition/disputes/package.json (1)
3-3: Version bump applied with correct workspace dependency versioning.All
@typeberry/*dependencies consistently use*as the version specifier.packages/core/pvm-debugger-adapter/package.json (1)
3-3: Version bump and dependencies look good.All internal workspace dependencies correctly use
*versioning. No issues identified.Also applies to: 7-17
packages/jam/state-merkleization/package.json (1)
3-3: Version bump complies with workspace guidelines.All internal dependencies correctly use
*versioning.Also applies to: 12-23
bin/pvm/package.json (1)
3-3: Version bump is correct.All workspace dependencies use
*as specified in guidelines.Also applies to: 7-9
packages/core/codec/package.json (1)
3-3: Version bump and dependencies correct.Workspace dependencies consistently use
*versioning.Also applies to: 7-10
packages/core/pvm-interface/package.json (1)
3-3: Version bump to 0.3.0 and dependencies correct.All workspace dependencies use
*as required.Also applies to: 7-8
packages/core/logger/package.json (1)
3-3: Version bump looks good.No dependencies to review; version-only change aligns with PR objective.
packages/core/shuffling/package.json (1)
3-3: Version and dependencies are correct.All internal workspace dependencies correctly use
*versioning.Also applies to: 7-10
packages/jam/safrole/package.json (1)
3-3: Version bump and workspace dependencies are correct.All internal dependencies properly use
*versioning per guidelines.Also applies to: 7-17
packages/core/erasure-coding/package.json (1)
3-3: Version bump and dependencies look good.All internal dependencies correctly use
*as the version specifier, and the version is updated from 0.2.0 to 0.3.0.Also applies to: 14-19
packages/core/collections/package.json (1)
4-4: Version and dependencies correctly updated.All internal dependencies use
*and version bumped to 0.3.0.Also applies to: 7-10
bin/convert/package.json (1)
3-3: Version bump and workspace dependencies are correct.All internal dependencies correctly use
*and version updated to 0.3.0.Also applies to: 16-34
packages/workers/api-node/package.json (1)
3-3: Version bump and workspace dependencies are correct.Version bumped from 0.1.3 to 0.3.0, and all internal dependencies correctly use
*.Also applies to: 10-19
packages/jam/block-json/package.json (1)
3-3: Version and dependencies correctly updated.All internal dependencies use
*and version bumped to 0.3.0.Also applies to: 12-18
packages/core/pvm-host-calls/package.json (1)
3-3: Version bump and workspace dependencies are correct.All internal dependencies correctly use
*and version updated to 0.3.0.Also applies to: 7-15
packages/core/pvm-interpreter-ananas/package.json (1)
3-3: Version bump and workspace dependencies are correct.Version bumped from 0.1.3 to 0.3.0, and all internal dependencies correctly use
*.Also applies to: 8-11
bin/rpc/package.json (1)
3-3: Version bump and workspace dependencies are correct.Version updated to 0.3.0 and all internal dependencies correctly use
*.Also applies to: 20-32
bin/ipc2rpc/package.json (1)
3-3: Version bump looks good.All internal dependencies correctly use
"*"as the version specifier, and external dependencies are appropriately pinned.packages/core/utils/package.json (1)
3-3: Version bump is clean.This package has no dependencies to verify. The version change from 0.2.0 to 0.3.0 is straightforward.
bin/lib/package.json (1)
3-3: Version bump and dependencies look good.All internal
@typeberry/*dependencies correctly use"*"as the version specifier across the comprehensive dependency list.bin/jam/package.json (1)
3-3: Version bump and dependencies are correct.All internal
@typeberry/*dependencies use"*", and the externalminimistpackage is appropriately pinned to version 1.2.8.packages/jam/state-vectors/package.json (1)
3-3: Version bump and dependencies look good.All internal
@typeberry/*dependencies correctly use"*"as the version specifier.bin/test-runner/package.json (1)
3-3: Version bump and dependencies are correct.All internal
@typeberry/*dependencies correctly use"*"as the version specifier, and the externaljson-bigint-patchis appropriately pinned to version 0.0.8.packages/core/concurrent/package.json (1)
3-3: Version bump and dependency are correct.The internal
@typeberry/utilsdependency correctly uses"*"as the version specifier.packages/core/crypto/package.json (1)
3-3: Version bump and dependencies are correct.Internal
@typeberry/*dependencies correctly use"*"as the version specifier, while external dependencies (@noble/ed25519and@typeberry/native) are appropriately pinned to specific versions.packages/core/pvm-program/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/jam/config/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/misc/benchmark/package.json (1)
3-3: Version bump looks good.Workspace dependency uses
*as the version specifier; third-party dependencies remain pinned appropriately.packages/jam/jamnp-s/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/core/pvm-interpreter/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/workers/block-generator/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/core/ordering/package.json (1)
3-3: Version bump looks good.No issues identified.
packages/jam/state/package.json (1)
3-3: Version bump looks good.All workspace dependencies correctly use
*as the version specifier.packages/jam/transition/package.json (1)
3-3: LGTM!Version bump is correct and all workspace dependencies properly use
*as the version specifier per coding guidelines.packages/jam/state-json/package.json (1)
3-3: LGTM!Version bump is correct and all workspace dependencies properly use
*as the version specifier per coding guidelines.packages/workers/importer/package.json (1)
3-3: LGTM!Version bump is correct and all workspace dependencies properly use
*as the version specifier per coding guidelines.packages/core/pvm-spi-decoder/package.json (1)
3-3: LGTM!Version bump is correct and all workspace dependencies properly use
*as the version specifier per coding guidelines.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
packages/jam/node/main-fuzz.test.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.ts
⚙️ CodeRabbit configuration file
**/*.ts: rules from./CODESTYLE.mdshould be adhered to.
**/*.ts: Any function whose documentation mention it must not be used in production code,
can be safely used in*.test.tsfiles. Other usage should be carefuly reviewed
and the comment must explain why it's safe to use there.
**/*.ts:asconversions must not be used. Suggest usingtryAsconversion methods.
**/*.ts: Classes withstatic Codecfield must have private constructor and staticcreatemethod.
**/*.ts: Casting abigint(orU64) usingNumber(x)must have an explanation comment why
it is safe.
**/*.ts: When making changes to code with comments containing links (in classes, constants, methods, etc.)
to graypaper.fluffylabs.dev, ensure those links point to the current version for this update.
Files:
packages/jam/node/main-fuzz.test.ts
🧠 Learnings (1)
📚 Learning: 2025-06-18T20:35:13.536Z
Learnt from: tomusdrw
Repo: FluffyLabs/typeberry PR: 442
File: packages/core/pvm-debugger-adapter/index.ts:22-40
Timestamp: 2025-06-18T20:35:13.536Z
Learning: The `typeberry/utils` package has browser compatibility issues due to Node.js-specific code like `measure` function using `process.hrtime()` and `testUtils` importing `node:assert`, causing white screens in browser environments.
Applied to files:
packages/jam/node/main-fuzz.test.ts
🧬 Code graph analysis (1)
packages/jam/node/main-fuzz.test.ts (4)
packages/core/utils/compatibility.ts (1)
CURRENT_VERSION(19-19)packages/jam/node/main-fuzz.ts (1)
getFuzzDetails(25-31)packages/core/utils/test.ts (1)
deepEqual(43-195)packages/core/numbers/index.ts (1)
tryAsU8(28-31)
🪛 GitHub Actions: Build - Lint & Test
packages/jam/node/main-fuzz.test.ts
[error] 4-4: ESLint: Relative import from another package is not allowed. Use '@typeberry/jam/package.json' instead of '../../../package.json' (import/no-relative-packages)
🪛 GitHub Check: test (22.x)
packages/jam/node/main-fuzz.test.ts
[failure] 4-4:
Relative import from another package is not allowed. Use @typeberry/jam/package.json instead of ../../../package.json
⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: state_transition (22.x)
- GitHub Check: state_transition (22.x)
- GitHub Check: run (22.x)
- GitHub Check: run (22.x)
- GitHub Check: e2e (22.x)
🔇 Additional comments (1)
packages/jam/node/main-fuzz.test.ts (1)
9-10: ****The concern about suffix handling is not applicable.
CURRENT_VERSIONis aGpVersionenum value (e.g., "0.7.2", "0.6.7") which never contains suffixes like "-beta" or "-rc". The enum values are clean semantic versions, so parsing them directly with.split(".")is correct. The.split("-")[0]in production code handlespkg.version(from package.json), which is a different source that may have suffixes—notCURRENT_VERSION.Likely an incorrect or invalid review comment.
|
@fluffylabs-bot benchmark |
|
✅ Benchmark workflow triggered successfully! 🎉 🔗 Check the Actions tab for workflow progress. |
Picofuzz Benchmark Resultsfallback
safrole
storage
storage_light
🤖 Automated benchmark |
View all
Benchmarks summary: 63/63 OK ✅ |
No description provided.