v1.3.3 (2025-09-14)

Enhancements

• DebugAndLog: The environment variable AWS_LAMBDA_LOG_LEVEL is now checked as well for setting logging level. LOG_LEVEL has priority. (v1.3.2)
• DebugAndLog: The log level environment variable now accepts strings as well as numbers ERROR, WARN, INFO, MSG, DIAG, DEBUG or 0, 1, 2, 3, 4, 5 respectively.

Fixes

• DebugAndLog: Environment and Logging Level value checks are fixed (v1.3.2)

v1.3.2 (2025-09-12)

Enhancements

• DebugAndLog: The environment variable AWS_LAMBDA_LOG_LEVEL is now checked as well for setting logging level. LOG_LEVEL has priority.

Fixes

• DebugAndLog: Environment and Logging Level value checks are fixed

v1.3.0 (2025-07-16)

Enhancements

• Removed AWS SDK V2 support which closes issue-213. AWS SDK V2 was for versions of Node 16 and under, and since they are no longer supported Lambda runtimes, support has been removed from cache-data.

Fixes

• Addressed deprecation warnings (handled by Amazon Q Developer):
  • Eliminated Warning:
    • [email protected] - From aws-sdk v2 (removed aws-sdk v2)
  • Remaining Warning (unavoidable):
    • [email protected] - From sinon dependency (external package)

v1.2.10 (2025-07-15)

Enhancements

• Added check for CACHE_DATA_ environment variables during init so they don't need to be set during Cache initialization. (Closes issue-212)
• Cleaner documentation, CloudFormation templates, and code now that defaults and environment variables can be used.
• Added ability to pass an array of objects to new Connections(connections) to make it easy when importing a connections file

Fixes

• Addressed deprecation warnings (handled by Amazon Q Developer):
  • Eliminated Warnings:
    • @extra-number/[email protected] - REMOVED by eliminating lambda-tester
    • [email protected] (2 instances) - REMOVED by eliminating lambda-tester
  • Remaining Warnings (unavoidable):
    • [email protected] - From sinon dependency (external package)
    • [email protected] - From aws-sdk v2 (required for compatibility)
• Fixed variable misname in cache S3 init from v1.2.6
• Fixed to check for environment variable CACHE_DATA_AWS_X_RAY_ON from v1.2.6

The querystring warning will be addressed when aws-sdk v2 compatibility is removed from cache-data. (Required for Node <18 which is no longer available as a Lambda runtime.) Opened issue-213

AI Usage Note

Amazon Q Developer was used to generate tests to ensure backward compatibility, no breaking changes were introduced, and enhancements work as expected. It was used for some additional code generation and reviewed by a human for accuracy.

v1.2.9 (2025-07-15)

Enhancements

• Added check for CACHE_DATA_ environment variables during init so they don't need to be set during Cache initialization. (Closes issue-212)
• Cleaner documentation, CloudFormation templates, and code now that defaults and environment variables can be used.
• Added ability to pass an array of objects to new Connections(connections) to make it easy when importing a connections file

Fixes

• Addressed deprecation warnings (handled by Amazon Q Developer):
  • Eliminated Warnings:
    • @extra-number/[email protected] - REMOVED by eliminating lambda-tester
    • [email protected] (2 instances) - REMOVED by eliminating lambda-tester
  • Remaining Warnings (unavoidable):
    • [email protected] - From sinon dependency (external package)
    • [email protected] - From aws-sdk v2 (required for compatibility)
• Fixed variable misname in cache S3 init from v1.2.6
• Fixed to check for environment variable CACHE_DATA_AWS_X_RAY_ON from v1.2.6

The querystring warning will be addressed when aws-sdk v2 compatibility is removed from cache-data. (Required for Node <18 which is no longer available as a Lambda runtime.) Opened issue-213

AI Usage Note

Amazon Q Developer was used to generate tests to ensure backward compatibility, no breaking changes were introduced, and enhancements work as expected. It was used for some additional code generation and reviewed by a human for accuracy.

v1.2.8 (2025-07-15)

Enhancements

• Added check for CACHE_DATA_ environment variables during init so they don't need to be set during Cache initialization. (Closes issue-212)
• Cleaner documentation, CloudFormation templates, and code now that defaults and environment variables can be used.

Fixes

• Addressed deprecation warnings (handled by Amazon Q Developer):
  • Eliminated Warnings:
    • @extra-number/[email protected] - REMOVED by eliminating lambda-tester
    • [email protected] (2 instances) - REMOVED by eliminating lambda-tester
  • Remaining Warnings (unavoidable):
    • [email protected] - From sinon dependency (external package)
    • [email protected] - From aws-sdk v2 (required for compatibility)
• Fixed variable misname in cache S3 init from v1.2.6
• Fixed to check for environment variable CACHE_DATA_AWS_X_RAY_ON from v1.2.6

The querystring warning will be addressed when aws-sdk v2 compatibility is removed from cache-data. (Required for Node <18 which is no longer available as a Lambda runtime.) Opened issue-213

AI Usage Note

Amazon Q Developer was used to generate tests to ensure backward compatibility, no breaking changes were introduced, and enhancements work as expected. It was used for some additional code generation and reviewed by a human for accuracy.

v1.2.5 Environment Variable Updates

• Updated suggested Lambda environment variables to uppercase: CACHE_DATA_
• Added check for environment variable DEPLOY_ENVIRONMENT among the current list of variables checked to determine the environment.

v1.2.3 Updated References

No code changes, just documentation changes to update references to the new repository.

v1.2.2 New release under 63Klabs

Update package.json

v1.2.1 Moving to 63Klabs

Still managed by @chadkluck but moving to an organizational structure.