Current Output :-
This part is missing libraries that cannot be satisfied with any available stage-packages known to snapcraft:
libgdbm.so.5
libreadline.so.7
These dependencies can be satisfied via additional parts or content sharing. Consider validating configured filesets if this dependency was built.
yeah, there is a hack (the ln calls in snapcraft.yaml that work around the versioned dependencies), it should not have any effect beyond that message in the logs … (though it might also not be needed at all anymore, who knows )
if it failed to release you either got an email that states the reason or you can log in to the site above (the old/former store page) and check the results for that package. it will not show up anywhere in the store if it failed to release …
no, the version complaints have nothing to do with releasing … they are just helpful comments for you as a packager in case missing libs cause issues at runtime.
hmm, this is indeed weird, if it successfully produced a .snap package (as your logs show it did), it should show up somewhere either in snapcraft.io/releases or on the dashboard page … not sure whats going on …
yes, obviously … no idea what is wrong there, your built snap should be running through the security checks and then go to the edge channel normally, i have no idea why it does not …