Release Notes - v0.1.13

v0.1.13 (May 15, 2026)

Title: Budget safety and Plutus data decode limits

Date: May 15, 2026

Version: v0.1.13

This release delivers focused safety and reliability fixes for evaluation limits and data decoding.

✨ What’s New

• Clarified patch release scope: This patch release does not add new user facing features and instead focuses on correctness and safety fixes.

🔧 Fixes

• Corrected budget overflow handling for expModInteger evaluation: Plutigo now checks expModInteger cost calculations for overflow, returns a budget error instead of corrupting execution budgeting, and prevents invalid negative or overflowed budget charges from changing runtime state.
• Hardened Plutus data decode limits: Plutigo now enforces hard CBOR decode limits for PlutusData, including nesting depth and node count limits, and stops early with explicit errors for oversized or excessively nested inputs instead of consuming excessive resources.

📋 What You Need to Know

• Highlighted safer budget evaluation for integrators: Integrators and evaluators can rely on budget failures surfacing as explicit errors, which keeps execution accounting predictable when extreme inputs trigger overflow conditions.
• Emphasized stronger protection against malformed inputs: Reliability and safety improve when untrusted or malformed data arrives because decoding now stops early instead of consuming excessive resources on oversized or deeply nested inputs.

🙏 Thank You

Thank you for using Plutigo.

---