Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request automates the release of Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
9fba16b to
25608b5
Compare
There was a problem hiding this comment.
Code Review
This pull request is an automated release PR for version 0.14.0. The changes correctly update the version across Cargo.toml, Cargo.lock, and package.json, and update the CHANGELOG.md. I've added one comment regarding the clarity of the changelog entry, as the new feature described doesn't seem to be implemented in the related +upload helper command, which could cause confusion for users.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request, generated by the Changesets release action, prepares for the release of version 0.14.0. The changes include updating the version number in Cargo.toml, Cargo.lock, and package.json, and moving the release notes for the new --upload-content-type feature into CHANGELOG.md. The changes are consistent with an automated release process. No issues were found in the submitted changes.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #475 +/- ##
=======================================
Coverage 67.81% 67.81%
=======================================
Files 38 38
Lines 17136 17136
=======================================
Hits 11621 11621
Misses 5515 5515 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
25608b5 to
82b13d5
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request is an automated release generated by the Changesets action. It correctly bumps the package version to 0.14.0, updates the CHANGELOG.md with the recent feature additions and bug fixes, and adjusts version numbers in Cargo.toml, Cargo.lock, and package.json. The changes are consistent and appropriate for a release. I found no issues to report.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@googleworkspace/cli@0.14.0
Minor Changes
dc561e0: Add
--upload-content-typeflag and smart MIME inference for multipart uploadsPreviously, multipart uploads used the metadata
mimeTypefield for both the Drivemetadata and the media part's
Content-Typeheader. This made it impossible to uploada file in one format (e.g. Markdown) and have Drive convert it to another (e.g. Google Docs),
because the media
Content-Typeand the targetmimeTypemust differ for import conversions.The new
--upload-content-typeflag allows setting the mediaContent-Typeexplicitly.When omitted, the media type is now inferred from the file extension before falling back
to the metadata
mimeType. This matches Google Drive's model where metadatamimeTypeis the target type (what the file should become) while the media
Content-Typeis thesource type (what the bytes are).
This means import conversions now work automatically:
Patch Changes
ReaderStreaminstead of being read entirely into memory, reducing memory usage from O(file_size) to O(64 KB).