First vault added to release a new apiVersion is always endorsed
Closed this issue · 1 comments
saltyfacu commented
What's your issue about?
The vault that is used to create a new release using YRegistry.newRelease(0x...) is automatically endorsed and shown on Yearn's main site in the production tab.
Steps to reproduce
Create a new release using YRegistry.newRelease(0x...) with any vault.
What is expected to happen.
It's expected to create a new release and add the vault to the registry.
What actually happens.
It creates a new release, adds the vault to the registry, and endorses it automatically.
Notes
It's not always that the first vault of a new release is production-ready. So we need a way to create a new release, add a vault, and test it accordingly.
fubuloubu commented
Closing in favor of yearn/yearn-vaults#179