Please avoid posting a new thread as we will lose the context of what happened before, instead replying to the existing ones.
My guess would be the store-side linter just got an upgrade to include that check, the problem might be the content interface shouldn’t be used that way without vetting its usage first.
My guess would be you haven’t complied to the previous reviewer’s request:
and thus the review task is simply being moved out of the review queue at the moment.
what to do to avoid this delay when a new version needs to be released.
You should apply for vetting the lxqt-support content snap interface’s usage as according to the following section of Process for aliases, auto-connections and tracks | Snapcraft documentation :
content - the base declaration defines that snaps that plugs the content interface will auto-connect with other snaps from the same publisher. Global auto-connect for content providers is allowed only under certain circumstances
- Rationale: because there is no tight coupling or dependency graphs between the provider and the consumer, there are no guarantees that a providing snap cannot break consuming snaps. Publishers are expected to manage breaking changes with their snaps, but are not generally expected to be concerned about others’ snaps
- Reference:
Library content interface needs special vetting as it must follow a certain interface naming requirement to ensure API compatibility, e.g. lxqt-support-2-core24