Make changes to typescript to trigger new tag

[olaservo]

Description

The previous changes made to these servers didn't trigger a new version getting published yet.

For server-redis the appears to be because I only changed the package.json, and it appears that the automatic publish script is only checking for .ts and .py changes. For server-memory its still a little more vague to me why it hasn't been published yet since the last update to the server.

I changed the server versions to match the npm version but I'm not 100% sure if this is the expected convention. If we want to keep the server version as-is, I can find something else to change.

Server Details

• Server: server-redis, server-memory
• Changes to: Version within server itself

How Has This Been Tested?

In the process of testing a locally built version to understand any unintentional impact of changing server versions. Will take this out of draft when done testing.

Breaking Changes

None

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

[olaservo]

Closing in favor of new PR since I see other issues with this server during testing