[stable] Prepare 1.66.0 release#105563
Conversation
|
Need to finish the PR by backporting the release notes, will do so later today. Do not merge yet. |
This comment has been minimized.
This comment has been minimized.
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
@bors r+ p=1000 |
|
@pietroalbini Just checking if you plan to accept or reject #104650 for backport? To be clear, I don't think that PR is required. The current builds seem to be working ok with xcode 14. The only reason I suggest it is because Apple documents it as not being supported, so we don't know what consequences there might be. It may also be a little strange to switch from 13 to 14 (in 1.66) and then back to 13 in 1.67. There are also a few other nominated (though not approved) PRs. |
|
⌛ Testing commit 61b1219 with merge ea14e00d83d87da23ceeb514d9c7186c6e7f83d9... |
|
@bors r- retry Yielding to the beta PR while we decide on last minute backports. |
|
Added backports for:
@bors r+ p=1000 rollup=never |
|
⌛ Testing commit 61b1219 with merge 955121c4905d97ce2ee3c9969e7857fd6dc134cf... |
|
|
|
@BlackHoleFox See my comment at #105563 (comment). I still lightly recommended it since Apple documents it as not being supported. #105123 is not necessary because the regression did not happen in beta. |
|
@ehuss ahh, ok, many thanks for clearing that up. My brain skipped thinking about the past beta for some reason. I'm lined up with your thoughts on XCode 13 though. |
|
💔 Test failed - checks-actions |
Include is there only for the effect executing the rule. The file is not intended to be remade successfully to be actually included.
|
@bors r+ |
Sorry, I forgot to tag that for beta-nominated. |
|
☀️ Test successful - checks-actions |
This PR prepares the artifacts for the 1.66.0 release. The following PRs have been backported:
FILE_ID_BOTH_DIR_INFOwill be aligned #104558#in rust code blocks #105539r? @ghost