-
Notifications
You must be signed in to change notification settings - Fork 18
[DRAFT] Proposed Python release changes, partial #680
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
Conversation
@lucasmcdonald3, I noticed you are updating the smithy model files. |
Detected changes to the release files or to the check-files action |
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
@lucasmcdonald3, I noticed you are updating the smithy model files. |
Detected changes to the release files or to the check-files action |
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
@lucasmcdonald3, I noticed you are updating the smithy model files. |
Detected changes to the release files or to the check-files action |
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
@lucasmcdonald3, I noticed you are updating the smithy model files. |
Detected changes to the release files or to the check-files action |
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
Description of changes:
Changes from ESDK release process
validate
tests involve installing the package from PyPI and running tests against the published package.validate
tested against a downstream dependency (busy-engineers-guide), but not every MPL subproject has a separate downstream dependency. Only the MPL-Core does. For the MPL-Core, this will also test against the ESDK as a downstream dependency.I only made changes for MPL-Core and Primitives as a proof of concept for other subprojects.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.