Skip to content

Comments

fix: harden 0.4.0 migration for latest Sui/Seal and CI#63

Open
arbuthnot-eth wants to merge 2 commits intoMystenLabs:mainfrom
arbuthnot-eth:fix/sui-seal-0-4-0-ci-node22-upstream-clean
Open

fix: harden 0.4.0 migration for latest Sui/Seal and CI#63
arbuthnot-eth wants to merge 2 commits intoMystenLabs:mainfrom
arbuthnot-eth:fix/sui-seal-0-4-0-ci-node22-upstream-clean

Conversation

@arbuthnot-eth
Copy link

Summary

This PR hardens the 0.4.0 migration for latest Sui/Seal by addressing runtime and API-compatibility gaps discovered during validation.

Fixes #60

Changes

  • Update GitHub Actions workflows to Node 22 (required by @mysten/sui@2.4.0):
    • .github/workflows/ci.yml
    • .github/workflows/npm-publish.yml
  • Add integration coverage to CI localnet flow:
    • run TEST_ENVIRONMENT=localnet pnpm run test:integration
  • Add pre-publish unit-test gate in npm publish workflow.
  • Align script helper with current Sui client typing/API:
    • scripts/utils.ts
    • use ClientWithCoreApi and client.core.signAndExecuteTransaction(...)
    • use client.core.waitForTransaction(...)
  • Enforce engine floor in package metadata:
    • packages/messaging/package.json -> "node": ">=22"
  • Record successful mainnet deployment + CDN manifest:
    • AGENTS.md
    • cdn/messaging-mainnet.json

Validation

  • pnpm -C packages/messaging build
  • pnpm -C packages/messaging lint
  • pnpm -C packages/messaging test:unit
  • pnpm -C scripts exec tsc -p tsconfig.json --noEmit

Integration tests require Docker-capable runtime for testcontainers.

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.

Harden 0.4.0 migration: Node 22 CI + Sui client script compatibility

1 participant