v2.1.0 - Change default to LEAKPROOF "disabled"

🚀 Version 2.1.0

⚙ Changes:

• Configurable LEAKPROOF Attribute: Shifted the default stance on the LEAKPROOF attribute from always enabled to optional. This adjustment allows users to evaluate their security requirements and operational context to decide whether to activate the LEAKPROOF setting. It moves towards accommodating various deployment scenarios, from dedicated servers to cloud-based environments, including Google Cloud Platform (GCP), Microsoft Azure, and Amazon Web Services (AWS), where the need for superuser rights can vary/are limited.

---

📝 Migration Guide from nanoid() Version 2.0.0 to 2.1.0:

Transitioning to version 2.1.0 involves assessing your current nanoid() function usage against your specific operational and security needs. Follow these steps to ensure a smooth migration:

1. Review and Decide on the LEAKPROOF Setting: Assess whether the LEAKPROOF attribute is necessary for your specific use case. If your environment requires strict security measures, you can keep it. Otherwise, you can now easily adjust this setting for enhanced compatibility with your deployment environment.

2. Update the nanoid() function: To disable the LEAKPROOF attribute, modify the function definition by commenting out or removing the LEAKPROOF line. You can make use of the nanoid.sql file and execute it.

Note: Prioritize testing any configuration changes in a controlled environment before applying them to your production systems. Additionally, ensure up-to-date backups to safeguard against data loss or configuration issues during the transition process — otherwise, this can be quite a career-limiting move.

---

Full Changelog: 2.0.0...2.1.0