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

fix(codegen): use specific smithy-cli version in protocol-test-codegen #3054

Merged
merged 1 commit into from
Nov 22, 2021

Conversation

gosar
Copy link
Contributor

@gosar gosar commented Nov 22, 2021

Looks like a miss in earlier PR which locked the versions centrally.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@gosar gosar requested a review from a team as a code owner November 22, 2021 21:46
@gosar gosar changed the title Fix locking smithy-cli version in protocol-test-codegen fix(codegen): fix locking smithy-cli version in protocol-test-codegen Nov 22, 2021
@trivikr trivikr changed the title fix(codegen): fix locking smithy-cli version in protocol-test-codegen fix(codegen): use specific smithy-cli version protocol-test-codegen Nov 22, 2021
@trivikr trivikr changed the title fix(codegen): use specific smithy-cli version protocol-test-codegen fix(codegen): use specific smithy-cli version in protocol-test-codegen Nov 22, 2021
@trivikr trivikr merged commit ba14b3c into aws:main Nov 22, 2021
@gosar gosar deleted the smithy-version branch November 22, 2021 23:06
@github-actions
Copy link

github-actions bot commented Dec 7, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants