Skip to content

RCF Protocol v1.3.0 β€” The Integrity Release πŸ›‘οΈβš‘

Choose a tag to compare

@aliyevaladddin aliyevaladddin released this 12 Apr 04:35
· 232 commits to main since this release

RCF Protocol v1.3.0 β€” The Integrity Release πŸ›‘οΈβš‘

We are proud to announce the release of v1.3.0, a major milestone where the RCF Protocol achieves full technical parity between the TypeScript and Python SDKs. This release focuses on architectural stability, audit transparency, and advanced heuristic detection.

πŸš€ Key Improvements

⚑ TypeScript SDK (rcf-protocol)

  • ESM Modernization: Fully migrated to a native ESModules architecture (NodeNext). This ensures compatibility with the latest Node.js environments and high-performance execution.
  • Intelligent Scanner: The core heuristic engine now accurately detects interfaces, abstract classes, types, and arrow functions, ensuring no logic remains unprotected.
  • CI/CD Stability: Resolved package-lock.json synchronization issues to ensure reliable, error-free builds via npm ci.

🐍 Python SDK (rcf-cli)

  • Full Parity: The scanner module now utilizes the same high-fidelity heuristics as the TypeScript implementation.
  • Enhanced Audit Engine: The audit command has been upgraded to the SHA-256 v1.3 standard for creating tamper-proof cryptographic snapshots of project logic.
  • Test Integrity: Updated the internal test suite (pytest) to align with the stricter v1.3 compliance detection rules.

πŸ€– CI/CD Infrastructure

  • Selective Publishing: Implemented path-based triggers. Updating code in the TypeScript SDK will no longer trigger redundant Python builds, and vice versa.
  • Manual Control: Integrated workflow_dispatch into GitHub Actions, allowing developers to manually trigger independent package releases with a single click.

πŸ“¦ Installation

Node.js (NPM)

npm install -g rcf-protocol