Skip to content

Conversation

@filipecabaco
Copy link
Member

What kind of change does this PR introduce?

handle tuple errors

@vercel
Copy link

vercel bot commented Jun 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
realtime-demo ⬜️ Ignored (Inspect) Visit Preview Jun 6, 2025 11:56am

@coveralls
Copy link

coveralls commented Jun 2, 2025

Coverage Status

coverage: 83.849% (-0.1%) from 83.98%
when pulling f9f9309 on fix/handle-tuple-errors
into b6e6858 on main.

@filipecabaco filipecabaco force-pushed the fix/handle-tuple-errors branch 2 times, most recently from 32f0f41 to 1ade961 Compare June 5, 2025 14:13
@filipecabaco filipecabaco force-pushed the fix/handle-tuple-errors branch 2 times, most recently from 682d9cf to 24abbc4 Compare June 6, 2025 11:41
@filipecabaco filipecabaco force-pushed the fix/handle-tuple-errors branch from 24abbc4 to f9f9309 Compare June 6, 2025 11:56
@filipecabaco filipecabaco merged commit 6daea67 into main Jun 9, 2025
5 of 7 checks passed
@filipecabaco filipecabaco deleted the fix/handle-tuple-errors branch June 9, 2025 10:18
@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.36.12 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants