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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Freeze v3.50.1 for release #11704

Merged
merged 1 commit into from Dec 21, 2022
Merged

ci: Freeze v3.50.1 for release #11704

merged 1 commit into from Dec 21, 2022

Conversation

iwahbe
Copy link
Member

@iwahbe iwahbe commented Dec 21, 2022

No description provided.

@iwahbe iwahbe self-assigned this Dec 21, 2022
@iwahbe iwahbe added impact/no-changelog-required This issue doesn't require a CHANGELOG update kind/engineering Work that is not visible to an external user labels Dec 21, 2022
@pulumi-bot
Copy link
Contributor

Changelog

[uncommitted] (2022-12-21)

@iwahbe
Copy link
Member Author

iwahbe commented Dec 21, 2022

bors r+

bors bot added a commit that referenced this pull request Dec 21, 2022
11704: ci: Freeze v3.50.1 for release r=iwahbe a=iwahbe



Co-authored-by: Ian Wahbe <ian@wahbe.com>
@bors
Copy link
Contributor

bors bot commented Dec 21, 2022

Timed out.

@iwahbe
Copy link
Member Author

iwahbe commented Dec 21, 2022

bors retry

bors bot added a commit that referenced this pull request Dec 21, 2022
11431: Bumps grpcio to version 1.50 r=kpitzen a=kpitzen

Currently, pinning to a version of grpcio <1.50 can cause build errors on newer versions of python+pip - the existing setup.py install method of building libararies is being deprecated and wheels are not being backported for older versions of grpcio.  Since this change is a no-op as far as our python proto clients are concerned, it feels safe to bump to a version that will be supported going forward

<!--- 
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

Fixes #11276 

Though this change doesn't result in guaranteed Python 3.11 support, it should allow users of Python 3.11 to at least install Pulumi successfully without Deprecation warnings etc.  grpcio 1.4X does not ship 3.11-compatible wheels, so users are starting to see errors when installing Pulumi - bumping to this version also does not change our existing proto clients in Python, so feels like a relatively safe change.

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->


11704: ci: Freeze v3.50.1 for release r=iwahbe a=iwahbe



Co-authored-by: Kyle Pitzen <kyle.pitzen@gmail.com>
Co-authored-by: Ian Wahbe <ian@wahbe.com>
@bors
Copy link
Contributor

bors bot commented Dec 21, 2022

This PR was included in a batch that was canceled, it will be automatically retried

@RobbieMcKinstry
Copy link
Contributor

@iwahbe I learned recently you can add priority to merges like this (i.e. ones you don't want to fail because they're in a batch with bad PRs).

bors r+ p=100

@bors
Copy link
Contributor

bors bot commented Dec 21, 2022

Already running a review

@iwahbe
Copy link
Member Author

iwahbe commented Dec 21, 2022

@iwahbe I learned recently you can add priority to merges like this (i.e. ones you don't want to fail because they're in a batch with bad PRs).

bors r+ p=100

馃 It looks like bors saw that.

@RobbieMcKinstry
Copy link
Contributor

Yeah, which is weird because I'm certain I read in the docs that commands to bors must be prefixes on comments.

@bors
Copy link
Contributor

bors bot commented Dec 21, 2022

Build succeeded:

@bors bors bot merged commit faff418 into master Dec 21, 2022
@bors bors bot deleted the iwahbe/freeze-3.50.1 branch December 21, 2022 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update kind/engineering Work that is not visible to an external user
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants