-
Notifications
You must be signed in to change notification settings - Fork 381
Comparing changes
Open a pull request
base repository: googleapis/python-aiplatform
base: v1.68.0
head repository: googleapis/python-aiplatform
compare: v1.69.0
- 9 commits
- 31 files changed
- 6 contributors
Commits on Sep 24, 2024
-
test: Verify gemini-1.5.pro-002 and gemini-1.5-flash-002 tokenizer in…
… system test PiperOrigin-RevId: 678401729
Configuration menu - View commit details
-
Copy full SHA for c442b92 - Browse repository at this point
Copy the full SHA c442b92View commit details -
Copybara import of the project:
-- 5ec9fa2 by release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>: chore(main): release 1.68.0 -- e380be8 by Yvonne Yu <[email protected]>: Update CHANGELOG.md COPYBARA_INTEGRATE_REVIEW=#4430 from googleapis:release-please--branches--main e380be8 PiperOrigin-RevId: 678408369
Configuration menu - View commit details
-
Copy full SHA for 950fbbc - Browse repository at this point
Copy the full SHA 950fbbcView commit details
Commits on Sep 25, 2024
-
chore: Tokenization - Add gemini-1.5-flash-002 and gemini-1.5-pro-002…
… to the list of supported tokenizers. PiperOrigin-RevId: 678818545
Configuration menu - View commit details
-
Copy full SHA for 44766a0 - Browse repository at this point
Copy the full SHA 44766a0View commit details
Commits on Sep 26, 2024
-
feat: Add rerun method to pipeline job preview client.
PiperOrigin-RevId: 678990608
Configuration menu - View commit details
-
Copy full SHA for 29dec74 - Browse repository at this point
Copy the full SHA 29dec74View commit details
Commits on Sep 30, 2024
-
fix: GenAI - Fixed from_dict methods
The parsing of dictionaries was standardized and improved. Parsing dictionaries via `json_formt.ParseDict` allows automatically handling renamed fields like `type_`, `format_`, `enum_` and also camelCase keys like `minItems` that are often used in Json Schema schemas. The `json_formt.ParseDict` method succeeds in such cases while the Proto Message constructors fail. However there is an issue with enums which makes full migration to `json_schema.ParseDict` non-trivial. Protobuf's ParseDict treats enum names as case sensitive. This is mostly problematic for Shema messages where Python protos use uppercase enum names like `"OBJECT"` while Json Schemas usually use lowercase types like `"object"`. I've created a fix for the protobuf library, but it will take a while before it's released everywhere. So, enums need to be fixed. But such enums can happen in multiple places in a deeply nested dictionary structure. We need to carefully fix all enum casing issues in nested dicts before we can use `ParseDict`. PiperOrigin-RevId: 680480143
Configuration menu - View commit details
-
Copy full SHA for 3090812 - Browse repository at this point
Copy the full SHA 3090812View commit details
Commits on Oct 1, 2024
-
chore: Adds tests for camelCase and snake_case proto field naming.
PiperOrigin-RevId: 680785742
Configuration menu - View commit details
-
Copy full SHA for f6e0a5a - Browse repository at this point
Copy the full SHA f6e0a5aView commit details -
chore: GenAI -
Part.function_call.args
is now a properdict
Fixes #4079 PiperOrigin-RevId: 680833836
Configuration menu - View commit details
-
Copy full SHA for 427bd75 - Browse repository at this point
Copy the full SHA 427bd75View commit details -
chore: Rollback: GenAI -
Part.function_call.args
is now a proper `d……ict` PiperOrigin-RevId: 680894911
Configuration menu - View commit details
-
Copy full SHA for d591101 - Browse repository at this point
Copy the full SHA d591101View commit details -
chore(main): release 1.69.0 (#4456)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Yvonne Yu <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for cbb71cd - Browse repository at this point
Copy the full SHA cbb71cdView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.68.0...v1.69.0