Skip to content
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

deps: Update github.com/jen20/awspolicyequivalence #9139

Merged
merged 1 commit into from
Sep 29, 2016

Conversation

jen20
Copy link
Contributor

@jen20 jen20 commented Sep 29, 2016

This fixes a bug in the upstream library where different casing of effect values were not treated as equivalent.

This fixes a bug in the upstream library where different casing of
`effect` was not treated as equivalent.
@stack72
Copy link
Contributor

stack72 commented Sep 29, 2016

LGTM!

@jen20 jen20 merged commit 200daa9 into master Sep 29, 2016
@jen20 jen20 deleted the deps-update-policy-equivalence branch September 29, 2016 22:05
@ghost
Copy link

ghost commented Apr 21, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants