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

Allow publisher to put downgraded crates into gradle.properties #3317

Conversation

ysaito1001
Copy link
Contributor

Motivation and Context

We are currently in a circumstance where we need to publish 0.60.1 unstable runtime crates even though 0.61.0 were published to crates.io in the previous release.

Description

This PR allows publisher to specify downgraded runtime crate versions in gradle.properties via the --allow-downgrade flag and updates a script upgrade-gradle-properties to use that flag. This is a bare minimum change in that we could update a release workflow to have a new checkbox whether we allow downgrade or not and thread through that value to the upgrade-gradle-properties script, instead of directly specifying like so.

Testing

Added unit tests for publisher and manually ran publisher upgrade-runtime-crates-version with --allow-downgrade to check the functionality.


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

@ysaito1001
Copy link
Contributor Author

Closing this on behalf of PR3316

@ysaito1001 ysaito1001 closed this Dec 13, 2023
Copy link

A new generated diff is ready to view.

  • No codegen difference in the AWS SDK
  • No codegen difference in the Client Test
  • No codegen difference in the Server Test
  • No codegen difference in the Server Test Python
  • No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

@ysaito1001 ysaito1001 deleted the ysaito/allow-publisher-to-downgrade branch January 24, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants