Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.34.0: autoOrient property is needed if the Metadata type is being used #4363

Closed
guyellis opened this issue Apr 4, 2025 · 4 comments
Closed

Comments

@guyellis
Copy link

guyellis commented Apr 4, 2025

Question about an existing feature

What are you trying to achieve?

Upgrade from 0.33.5 to 0.34.0

When you searched for similar issues, what did you find that might be related?

#4248 (Merge autoOrient improvements)

Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question

Image

Please provide sample image(s) that help explain this question

After upgrading from 0.33.5 to 0.34.0 an autoOrient property is needed if the Metadata type is being used. Just confirming that this was intentional and expected?

@lovell
Copy link
Owner

lovell commented Apr 4, 2025

Hello, this has been reported and fixed via #4362. I'll wait overnight to see if anything else urgent turns up before making the (inevitable) patch release.

@lovell lovell added this to the v0.34.1 milestone Apr 4, 2025
@lovell lovell changed the title autoOrient property is needed if the Metadata type is being used v0.34.0: autoOrient property is needed if the Metadata type is being used Apr 4, 2025
@styfle
Copy link
Contributor

styfle commented Apr 7, 2025

@lovell Its been a few days now. Seems like a good time to release a patch when you're available.

@lovell
Copy link
Owner

lovell commented Apr 7, 2025

@styfle I was waiting to see if anything is needed for #4361 but sadly there isn't yet enough detail for someone else to reproduce (if only to check if it might be the same problem discussed here). I note Vercel is mentioned a couple of times so you may want to check to see if there are any support issues internally that relate to this.

@lovell
Copy link
Owner

lovell commented Apr 7, 2025

v0.34.1 now available with the fix, thanks all.

@lovell lovell closed this as completed Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants