Skip to content
Discussion options

You must be logged in to vote

We ended up rolling back the release was had (so an earlier release is currently the latest). Perhaps this 'removal' of a previously published release has a downstream effect that we didn't understand / anticipate and this is the cause... We are planning to publish an updated 1.2 release later today, so that may resolve the issue.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@carbonga
Comment options

@carbonga
Comment options

Answer selected by carbonga
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