Skip to main content

v1.14.1

Discover the new features, logic changes, bug fixes, breaking changes, and known issues and limitations in this Piiano Vault release.

New features

Logic change

  • Vault now enforces a maximum length for LONG_TEXT and JSON data types. See data types for more details.

Breaking changes

  • Vault no longer enforces Access Reason by default for new and existing vaults. You can switch enforcement on using PVAULT_SERVICE_FORCE_ACCESS_REASON;
  • ⚠️ If you're using LONG_TEXT or JSON data types that exceed 5MB in size, an action is required:
    • For self-hosted Vaults: Increase the PVAULT_DB_MAX_BLOB_LENGTH environment variable to accommodate your maximum blob size.
    • For Vault SaaS: Please contact us to adjust your Vault configuration.

Bug fixes

  • Vault now enforces anti-tampering on more internal components.
  • CLI commands that prompts for interactive user confirmation now respects Ctrl-C signals.
  • Vault returns now a clear error for an IAM error where an IAM user is added in different casing than an existing IAM user.
  • Fixed a bug that caused the uniqueness constraint not to be removed after updating a collection.
note

This release includes a minor change in Vault's anti-tampering signatures. If you run multiple instances and want to run this release alongside the previous one, you must remove anti-tampering enforcement for that transition time. Set the PVAULT_FEATURES_ANTI_TAMPERING environment variable to log or off on the existing instances before upgrading to this version. Restore the enforcement when all Vault instances are running this release.