Stable doesn’t mean that it crashes less, but that the features which were “in progress” in dev version are generally available.
Dev version is newer and more advanced but some features can still be WIP.
And a file produce in dev version could but unusable in a previous (stable or dev) version.
“Use it at your own risks” is often used as a warning, even though it could be with lots of bugs fixed.
Note that even so-called (official) development versions can be quite old.
If you want the latest features available, you can use an UNOFFICIAL appimage build that I’m building from the latest commits with the build system we use.
I make it for my own usage and I publish it to avoid others to have to play with Docker and have to reserve gigs of disk space.
Work also in Windows 10/11 with WSL 
Also, with the UNOFFICIAL builds, as it is AppImage v2, you can have several versions in parallel with own .config and .home, it will not mess your config.
And as a general rule of thumb, if you start a project with a specific version, keep it during the production (especially with dev version).
And keep this version just in case if you want to alter the file later.
When it is time to upgrade, check that the file (a copy) can still be opened in the new version before to get rid of it.
Another good reason to use AppImage v2 (UNOFFICIAL yet, official are still in v1)