It will be deleted again once a proper release is out

Cool, is there any plan on when this will happen?

Once everything passes 😅

Yeah that makes sense 😉 I was planning on migrating from 0.6.0 to 0.7.0, but it is a lot of effort with forced down time, so if possible I would like to immediately jump to 0.8.0. Is this more of an hours/days/weeks thing?

probably hours

Perfect, thanks!

yeah no new migrations added since 0.7

Hurray!

The pre release was successful, but the real release failed Working on it today

Cheers! Good luck

Ah so it was only the post-release task failing, the release is there: https://github.com/ory/keto/releases/tag/v0.8.0-alpha.0

Hi Patrik! So I just released the SDKs were released a week or so ago. I noticed that the ActionEnum for patching code generation is broken.

/// <summary>action</summary>
/// <value>action</value>
[JsonConverter(typeof (StringEnumConverter))]
public enum ActionEnum
{
  /// <summary>
  /// Enum InsertDelete for value: [[[[[[[[[[insert delete]]]]]]]]]]
  /// </summary>
  [EnumMember(Value = "[[[[[[[[[[insert delete]]]]]]]]]]")] InsertDelete = 1,
}

This is what got generated

yes, there was a problem with the spec generation

We have decided to stay on 0.7.0 for now, so this is not blocking us specifically

👍 there will be a release soonish anyways

Hi again! Don't mind me reusing this chat all the time 🙂

What if I do mind? 😉 The metadata part of the API is actually not its own endpoint but on both read and write. This is just a way to make it possible to use the SDK on both endpoints. Sorry for the confusion, we will restructure the SDK soon to be easier to understand...

I see! Thanks for the quick reply

np