Thanks Nathan This is most likely because of the recent changes to the snap refresh API that added, for by-revision refreshes, the effective-channel (with the least risky channel that contained the requested revision) data in responses. Previously effective-channel was only present in by-channel refreshes and I assume snapd's messaging did not have to deal with that possibility and assumed that effective-channel will differ from the tracking one when that tracking one was closed.
We probably don't need any Store side changes here, but let's wait for snapd's response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074361 Title: Channel latest/stable for chromium is closed; temporarily forwarding to candidate. To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2074361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
