Skip to content

Conversation

@nightfury1204
Copy link
Collaborator

@nightfury1204 nightfury1204 commented Oct 22, 2025

What is the feature/update/fix?

Fix: Redis Version Decimal Parsing Issue

We've fixed an issue where Redis version numbers with decimal points (such as 7.0) were incorrectly being converted to integers (e.g., 7) when specified in the convox.yml. This parsing error would cause deployment failures as the truncated version number was invalid for Redis configuration.

Previously, when specifying a Redis resource version like 7.0, the YAML parser would interpret this as a float and convert it to 7, which is not a valid Redis version. This forced users to wrap version numbers in quotes as a workaround.


How to use it?

You can now specify Redis versions with decimal points directly in your convox.yml without needing quotes:

Before (workaround required):

resources:
  cache:
    type: redis
    options:
      version: "7.0"  # Quotes were required to prevent conversion to 7

After (now works correctly):

resources:
  cache:
    type: redis
    options:
      version: 7.0  # No quotes needed - properly handled as 7.0

Both quoted and unquoted formats will now work correctly:

  • version: 7.0
  • version: "7.0"
  • version: 6.2
  • version: "6.2"

This fix applies to all Redis version specifications and ensures consistent behavior regardless of how you format the version number.


Does it have a breaking change?

There are no breaking changes introduced with this fix. Existing configurations with quoted version numbers will continue to work as before.


Requirements

To use this feature, you must be on at least rack version 20251022194219.

You can check your rack's version with the command convox rack.
Update your rack to the latest version with the command convox rack update.

@nightfury1204 nightfury1204 merged commit 71a835d into staging Oct 22, 2025
1 check was pending
@nightfury1204 nightfury1204 deleted the yaml-resource-version branch October 22, 2025 15:43
@nightfury1204 nightfury1204 mentioned this pull request Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants