-
Notifications
You must be signed in to change notification settings - Fork 33
Comparing changes
Open a pull request
base repository: microsoftgraph/msgraph-sdk-java-core
base: v3.1.3
head repository: microsoftgraph/msgraph-sdk-java-core
compare: v3.1.4
- 10 commits
- 11 files changed
- 4 contributors
Commits on Feb 19, 2024
-
chore(deps): bump dawidd6/action-download-artifact from 3.1.0 to 3.1.1
Bumps [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/dawidd6/action-download-artifact/releases) - [Commits](dawidd6/action-download-artifact@v3.1.0...v3.1.1) --- updated-dependencies: - dependency-name: dawidd6/action-download-artifact dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Configuration menu - View commit details
-
Copy full SHA for 4020b30 - Browse repository at this point
Copy the full SHA 4020b30View commit details -
Merge pull request #1516 from microsoftgraph/dependabot/github_action…
…s/dawidd6/action-download-artifact-3.1.1 chore(deps): bump dawidd6/action-download-artifact from 3.1.0 to 3.1.1
Configuration menu - View commit details
-
Copy full SHA for dde3ec2 - Browse repository at this point
Copy the full SHA dde3ec2View commit details
Commits on Feb 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 2c168c7 - Browse repository at this point
Copy the full SHA 2c168c7View commit details -
The test UploadResponseHandlerTest#getUploadSessionOnProgressingUpload mimicked a server response with a 200/OK response code. In the REST reference (https://learn.microsoft.com/en-us/graph/api/driveitem-createuploadsession?view=graph-rest-1.0#upload-bytes-to-the-upload-session) it is stated that the response code for uploading more bytes to the upload session is 202/Accepted. The bug in #1517 is fixed. Previously the method UploadResponseHandler#handleResponse handled differently the response in these two cases: - response code 200/OK - all other cases Now the same method handles differently the response in these two cases: - response code 200/OK or 201/Created - all other cases Everything works if the REST reference is corrected and: - 200/OK is returned when an item is updated, 201/Created is returned when an item is Created - 202/Accepted is returned when more bytes are requested
Configuration menu - View commit details
-
Copy full SHA for dc45304 - Browse repository at this point
Copy the full SHA dc45304View commit details -
Test fix and updating releases
- Updated the patch version in gradle.properies - Updated changelog.md and readme.md with the new patch version - Bumped kiota dependencies to 1.0.3 - Fixed the test UploadSliceRequestTest.putReturnsExpectedUploadSession which did not respect the response descripted in the REST reference
Configuration menu - View commit details
-
Copy full SHA for 2c1684d - Browse repository at this point
Copy the full SHA 2c1684dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3be4c4b - Browse repository at this point
Copy the full SHA 3be4c4bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3482361 - Browse repository at this point
Copy the full SHA 3482361View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4cb7c3b - Browse repository at this point
Copy the full SHA 4cb7c3bView commit details -
- fixes NRP in large file upload
Signed-off-by: Vincent Biret <vibiret@microsoft.com>
Configuration menu - View commit details
-
Copy full SHA for 9d368ce - Browse repository at this point
Copy the full SHA 9d368ceView commit details -
Merge pull request #1518 from kekolab/dev
Fix for issue 1517 and correction of two tests not respecting the REST reference (impacted by the fix)
Configuration menu - View commit details
-
Copy full SHA for 93ea88a - Browse repository at this point
Copy the full SHA 93ea88aView 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 v3.1.3...v3.1.4