Release 1.0 - why not?

[derberg]

Is there any reason why not release v1 "tomorrow" (like merge next into master)

• We publish release candidates for like almost over 2y I think
• But still master is default branch that people read
• CI/CD issues occur as only master get updates automatically. This causes maintenance issues and hiccups (like /rtm do not work)

cc codeowners @magicmatatjahu @fmvilas

---

Is there anyone having an argument against it?

[fmvilas]

Nope. All for it 👍

[magicmatatjahu]

yeah, We can publish :)

[GreenRover]

I would love this to!

[jonaslagoni]

The playground is currently not working on next, I have tried to fix it for a week now, but this obscure react-app-rewired and it's build system is just not playing ball at all...

[jonaslagoni]

The playground is currently not working on next, I have tried to fix it for a week now, but this obscure react-app-rewired and it's build system is just not playing ball at all...

It's funny, as soon as I write this, I re-tested an implementation I did last week, and now everything magically works...

Checkout #763

[jonaslagoni]

After playground is fixed I would release the library as v1 for sure 👍

[derberg]

once we have #767 merged, I think we are ready to go with v1 release

[derberg]

@magicmatatjahu @fmvilas #764 is ready for final review. Merge conflicts solved. Playground works. Tests pass. I think we are ready to go. In case of issues, we can always do a followup fixes 🤷🏼

[derberg]

it is out https://github.com/asyncapi/asyncapi-react/releases/tag/v1.0.1