Antonin Stefanutti

+1 It'd be useful to have a warning in the release notes so existing users can adjust their existing deployment if needed.

Interesting, I wonder why #1574 did not work this time 🤔.

Now that @kevin85421 has created the [ray-operator/v1.1.0-rc.1](https://github.com/ray-project/kuberay/releases/tag/ray-operator%2Fv1.1.0-rc.1) tag, here is what I have: ``` $ go list -m github.com/ray-project/kuberay/[email protected] github.com/ray-project/kuberay/ray-operator v1.1.0-rc.0 ``` I see the release workflow run successfully this...

@Fiona-Waters and I faced a similar issue, this time when the AppWrapper contains an item, that has the same name as an existing resource of the same kind in another...

👋🏼 It's seems it's in great shape. Could that awesome work be merged🙏🏼? It'd be great for users to adopt it, and eventually report any issues / improvements iteratively.

I confirm it's been fixed with recent versions of Chrome. Thanks.

> The `kamel kit delete` completion already exists : the command only shows non-platform kits. Is this behavior something that should evolve to all kits (even the platform ones) for...

Decktape relies on the global `Reveal` variable and expect it to exist, as documented in https://revealjs.com/initialization/. That being said, I've tested it by exporting the demo presentation from https://denehyg.github.io/reveal.js-menu and...

I've given this another try and it still works with the demo presentation https://denehyg.github.io/reveal.js-menu. The most likely explanation is a difference between your presentation and the demo one w.r.t. initialising...

Hi @nicojs, I remember some issues with `npm install` and `package-lock.json`, which led to changing to using `npm-shrinkwrap.json`: https://github.com/astefanutti/decktape/issues/136#issuecomment-392725841. We can certainly re-assess what's the best option.