New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdated package notifications make me do work #1367
Comments
Yep it will be great to have something like this. We will have more secure snaps |
It would be great if the versions in stable/candidate/beta channels can rebuild themselves with the respective configuration... |
Thanks for bringing this to our attention, as this involves a wider conversation with other teams related to the snap development. Would you be able to post this as a new thread in the forum? |
I've made a thread on the forum https://forum.snapcraft.io/t/outdated-package-notifications-make-me-do-work/8813 |
Thanks for posting the message on the forum, we will make sure any decisions made that affects snapcraft.io will be taken in consideration to improve the platform. |
Snap packages are being built automatically for me by both Launchpad and build.snapcraft.io. The outdated package notifications are great, but would be even better if they actually triggered the build and pushed the snap to configured channels, rather than just nag me to do it manually (which gets pushed to the bottom of my queue, as step one is remembering where the source was setup).
The text was updated successfully, but these errors were encountered: