Skip to content
Discussion options

You must be logged in to vote

That was a bug that we introduced in v1.2.0 I believe. For now, you could downgrade to v1.1.0 which should solve the issue. We've just merged the bugfix yesterday and will do a beta release later today, which you could test too. Sorry for the trouble.

Replies: 7 comments 6 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
3 replies
@gavspeed
Comment options

@gavspeed
Comment options

@waldekmastykarz
Comment options

Comment options

You must be logged in to vote
3 replies
@gavspeed
Comment options

@waldekmastykarz
Comment options

Answer selected by waldekmastykarz
@gavspeed
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1401 on October 02, 2025 06:06.