-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat!: validate devel bases #302
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! Some minor comments but I agree with the overall direction
would love to get input from the rest of the team (since this was originally my suggestion). Since I'm gone for the rest of the week whatever you agree to do is fine with me.
Signed-off-by: Callahan Kovacs <[email protected]>
Signed-off-by: Callahan Kovacs <[email protected]>
744ebf4
to
da273cb
Compare
Signed-off-by: Callahan Kovacs <[email protected]>
Signed-off-by: Callahan Kovacs <[email protected]>
- allow multiple OSs to register devel bases - raise an exception if the base alias cannot be decoded Signed-off-by: Callahan Kovacs <[email protected]>
Signed-off-by: Callahan Kovacs <[email protected]>
Signed-off-by: Callahan Kovacs <[email protected]>
Signed-off-by: Callahan Kovacs <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
- make error message more generic - move warning message to Project Signed-off-by: Callahan Kovacs <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice thanks
This is a partial revert of 'aeae554 feat!: validate devel bases (#302)'. The base validation is not reverted, but there is now a default implementation for `Project._providers_base()` such that applications do not need to subclass the Project model. Signed-off-by: Callahan Kovacs <[email protected]>
This is a partial revert of 'aeae554 feat!: validate devel bases (#302)'. The base validation is not reverted, but there is now a default implementation for `Project._providers_base()` such that applications do not need to subclass the Project model. Signed-off-by: Callahan Kovacs <[email protected]>
This is a partial revert of 'aeae554 feat!: validate devel bases (#302)'. The base validation is not reverted, but there is now a default implementation for `Project._providers_base()` such that applications do not need to subclass the Project model. Signed-off-by: Callahan Kovacs <[email protected]>
This is a partial revert of 'aeae554 feat!: validate devel bases (#302)'. The base validation is not reverted, but there is now a default implementation for `Project._providers_base()` such that applications do not need to subclass the Project model. Signed-off-by: Callahan Kovacs <[email protected]>
tox
?Upstream
build-base
devel
validation for all *craft applications. This draft treatsdevel
as the devel base, but I will update this to26.04 before this PR can land24.10 when it is available.Downstream integrations:
Fixes #298
(CRAFT-2675)