Skip to content

feats

Latest

Choose a tag to compare

@gaurav-gogia gaurav-gogia released this 28 Jun 00:26
03b5547

Release summary

v2.1.0 moves Mutant forward in four major ways:

  1. The language now supports more application-level constructs such as structs,
    enums, loops, float literals, and field access.
  2. The standard library/runtime now includes broader builtins for filesystem,
    HTTP, networking, DB access, command execution, and Lua-driven workflows.
  3. The security model is materially stronger, with anti-debugging, sandbox
    detection, anti-tamper probing, secure memory primitives, and upgraded
    crypto/signing paths.
  4. The build and packaging story is simpler for maintainers because release
    generation now has Go-only scripts for Windows and Unix-like environments.

What is new in v2.1.0

Language features

  • Struct declarations and struct literals
  • Enum declarations
  • for loops
  • break and continue
  • Float support
  • Field expressions and related parser/compiler support

Runtime and builtins

  • Filesystem builtins
  • HTTP builtins
  • Networking builtins
  • DB builtins
  • Command execution builtin
  • Lua execution builtin and runtime support
  • Security status builtin
  • Additional collection and output helpers

Security improvements

  • Cross-platform anti-debug support
  • Sandbox detection updates
  • Anti-tamper probing
  • Stronger cryptographic plumbing and signing flow
  • Secure memory handling
  • Security diagnostics and telemetry support

Tooling and release engineering

  • Go-only release build scripts
  • Release asset generation support
  • Updated build instructions in README

Breaking-change and compatibility notes

  • Release generation flow has changed, so maintainers should use the new scripts
  • Security behavior is stricter and may surface different runtime outcomes in
    constrained or instrumented environments
  • Projects depending on older assumptions about bytecode, packaging, or runtime
    behavior should be retested
  • Existing .mu artifacts should be validated against the current toolchain
    before claiming backward compatibility