-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fix: OPTIC-104: Fixing packages #4749
Merged
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
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
✅ Deploy Preview for heartex-docs canceled.
|
Codecov ReportPatch has no changes to coverable lines. 📢 Thoughts on this report? Let us know!. |
farioas
approved these changes
Sep 15, 2023
16 tasks
shayantabatabaee
pushed a commit
to shayantabatabaee/label-studio
that referenced
this pull request
Sep 19, 2023
* fix: OPTIC-104: Fixing packages * fix: OPTIC-104: Narrowing allowed protobuf versions for compatibility * fix: OPTIC-104: Using archive instead of VCS for drf-yasf requirement * fix: OPTIC-104: Trying VCS without -e flag * fix: OPTIC-104: Adding -e flag back * fix: OPTIC-104: Making google-api-core version looser * fix: OPTIC-104: Testing freeze from previous release * fix: OPTIC-104: Removing duplicate requirements * fix: OPTIC-104: Using wheel for drf-yasg * fix: OPTIC-104: Fixing deps * fix: OPTIC-104: Adding package name * fix: OPTIC-104: Bringing back original reqs with @ * fix: OPTIC-104: Narrowing protobuf again * fix: OPTIC-104: Bumping google-api-core dep +1 patch * fix: OPTIC-104: Making google-api-core >= instead of hard pin * fix: OPTIC-104: Adding newline to bust cache * fix: OPTIC-104: Hard pinning grpc * fix: OPTIC-104: Softening google deps * fix: OPTIC-104: removing duplicate req * fix: OPTIC-104: making sure google packages stay major-stable * feat: OPTIC: Forcing rebuild * fix: OPTIC-104: Decreasing dep versions * fix: OPTIC-104: Pinning google packs to versions that worked before * fix: OPTIC-104: Trying windows build without pip cache * fix: OPTIC-104: Trying different runner version * fix: OPTIC-104: Bringing newest runner back. Quoting version * fix: OPTIC-104: More quotes * fix: OPTIC-104: Removing Python 3.10 and 3.11 tests from windows --------- Co-authored-by: Wesley Lima <[email protected]>
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.
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
(link to issue, supportive screenshots etc.)
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)