Skip to content

Update Typesense from 29.0 to 30.1#5

Open
shaheemMPM wants to merge 1 commit into
railwayapp-templates:mainfrom
shaheemMPM:update/typesense-30.1
Open

Update Typesense from 29.0 to 30.1#5
shaheemMPM wants to merge 1 commit into
railwayapp-templates:mainfrom
shaheemMPM:update/typesense-30.1

Conversation

@shaheemMPM

Copy link
Copy Markdown
Contributor

Updates the Typesense Docker image from 29.0 to 30.1 (latest stable).

What changed

  • Dockerfile line 8: typesense/typesense:29.0typesense/typesense:30.1

What's in 30.x

  • 30.0: MMR search diversity, global synonyms, enhanced JOINs, union search improvements, IPv6 support
  • 30.1: Bug fix for search latency metric overflow in stats.json

Docker image typesense/typesense:30.1 is available with multi-arch support (amd64 + arm64).

30.1 is the latest stable release. Includes MMR search diversity, global synonyms, enhanced JOINs, and IPv6 support (30.0) plus a latency metric bug fix (30.1).
@sameerkumar18

Copy link
Copy Markdown

@brody192 any update/thoughts on this?

@brody192

brody192 commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Have you confirmed that the service will still deploy after this change?

@sameerkumar18

Copy link
Copy Markdown

@brody192 I personally have not -- just looking to get to the latest typesense versions because it contains bug fixes that our customers have started reporting, particularly around handing special characters in substring searches

Maybe @shaheemMPM ?

@brody192

brody192 commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Unfortunately, I don't have the cycles right now to test the upgrade path, so it would be much appreciated if you where able to show me there are no issues when bumping this image.

@sameerkumar18

Copy link
Copy Markdown

@brody192

Copy link
Copy Markdown
Contributor

Thank you. I would need some confirmation on the above before merging this.

@sameerkumar18

Copy link
Copy Markdown

@shaheemMPM I saw you have the latest Typesense version in your fork

Were you able to still deploy the service on Railway after this change? Any issues you observed?

@sameerkumar18

sameerkumar18 commented Apr 9, 2026

Copy link
Copy Markdown

@brody192 I ended up forking the repo to run v30.1 myself.
Here's the Railway service running forked v30.1
Screenshot 2026-04-09 at 9 36 58 AM

I can confirm the service deploys after this change -- but what I've not tried is copying/cloning the Railway volume to replicate the production data behaviour - but so far looks good to me.
Any thoughts?

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.

3 participants