Upgrade fog-aliyun to 0.3.10#1606
Merged
aashah merged 1 commit intocloudfoundry:masterfrom May 11, 2020
Merged
Conversation
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/172713125 The labels on this github issue will be updated when the story is started. |
Contributor
|
Hey @xiaozhu36, Looks like a super easy PR to merge, thanks! Quick clarification -- title says 0.3.10, commit says 0.3.9. Should we hold off from merging this until it's updated for 0.3.10? |
Contributor
Author
|
HI @aashah Thanks for your review. I am sorry for the confused commit message and I have corrected it. Please check it again. Thanks. |
Contributor
|
No worries, thanks for updating the PR. Will merge this in then. |
This file contains hidden or 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
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.
The fog-aliyun 0.3.10 aims to fix the issue: fog/fog-aliyun#61 and exlarge the limitation when getting oss objects. The related PRs as following:
fog/fog-aliyun#65
fog/fog-aliyun#64
fog/fog-aliyun#63
fog/fog-aliyun#62
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
masterbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests
I have deploy a whole CF deployment and spring-music app by packing gem fog-aliyun 0.3.10 to Capi-release.