feat!: public release #271
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
moorec-aws
force-pushed
the
public-release
branch
from
893afbc to
b91b784
Compare
jericht
previously approved these changes
Mar 31, 2024
moorec-aws
force-pushed
the
public-release
branch
from
b91b784 to
ef68cb6
Compare
ddneilson
previously approved these changes
Apr 1, 2024
moorec-aws
force-pushed
the
public-release
branch
2 times, most recently
from
103c4e3 to
c79a920
Compare
moorec-aws
force-pushed
the
public-release
branch
from
cfa5d87 to
0d1d642
Compare
Signed-off-by: Charles Moore <[email protected]>
moorec-aws
force-pushed
the
public-release
branch
from
0d1d642 to
a66ecfd
Compare
marofke
approved these changes
Apr 1, 2024
jusiskin
approved these changes
Apr 1, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem/requirement? (What/Why)
We're about to publicly release this library. We need to prep the build process for that.
What was the solution? (How)
Bump to boto3 to
1.34.75and deadline-test-fixtures to0.6.0Update the build script to no longer define a PIP_INDEX_URL -- the environment variable
that we used to interface with our internal repository during private development.
Update the code quality check to pull deps from the public PyPI, so
that we're testing as customers would use it.
Use the public PyPI in the release flows since all deps are now
available publicly. This ensures that the artifact we release can be
built & used by anyone using PyPI.
What is the impact of this change?
Release readiness
How was this change tested?
Tests will not pass until boto3 1.34.75 is released
Was this change documented?
No
Is this a breaking change?
No, but it is being marked as one to force a minor version bump when we release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.