Release strategy has to change.

### Is there an existing issue for this?

- [x] I have searched the existing issues and checked the recent builds/commits

### What problem are you experiencing?

Unfortunately the current release strategy of having only @latest, or @x.y.z is driving everybody in the community crazy.

It used to be that front ends were released maybe every week. Seriously, now it's every few hours in some cases. I really like what you are trying to do, and where you're trying to go. But the constant failure of workflows because of front end updates is driving us bonkers.

### When does this problem occur?

Constant problems with subgraphs, nodes, and my hair due to using us as beta testers for constant front end updates.

### How often do you encounter this problem?

Multiple times per day

### How much does this problem affect your workflow?

Significantly slows down my work

### Current workarounds

Right now, the prevalent method for dealing with this is to find the latest front-end version that doesn't have any problems with the workflows I'm using.

This requires me to step by step, check, change, reload the Fe until it works.

### Ideas for solutions (Optional)

I would like to see a @latest_stable instead of just @latest.

The latest_stable should of course have been thoroughly tested.

### Additional context

If you agree, give a thumbs up!

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-8534-Release-strategy-has-to-change-2fa6d73d365081ab9b7bd660af72b1bd) by [Unito](https://www.unito.io)