Closed mr-cal closed 3 months ago
Force-pushed because I dropped all changes related to running the ClassicFallback or craft-application based codepath.
It's too disruptive of a change for a hotfix.
We can generalize the calls a bit more instead of being core24-specific in a future refactoring, but this solves the reported issue.
Agreed. In a point release, we should flip the paradigm such that the craft-application codepath is used by default and Snapcraft only raises ClassicFallback
if we know we should use the core20
or core22
feature set.
tox run -m lint
?tox run -e test-py310
? (supported versions:py39
,py310
,py311
,py312
)Application
to allow snapcraft to register/unregister plugins per-base_known_core24
to_known_craft_app_base
in preparation for core26Fixes #4825 (CRAFT-2979)