8000 Fix bad module dep version in 5.10 by luispadron · Pull Request #2780 · swiftlang/swift-syntax · GitHub
[go: up one dir, main page]

Skip to content

Fix bad module dep version in 5.10 #2780

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

Conversation

luispadron
Copy link

This was using the wrong versions for apple_support. We don't need a new tag here as we'll be patching the bazel-central-registry but fixing in case there is another 5.10 patch

@keith
Copy link
Member
keith commented Aug 6, 2024

@swift-ci please test

@ahoppen ahoppen requested a review from bnbarham August 6, 2024 22:34
@ahoppen ahoppen merged commit cdd571f into swiftlang:release/5.10 Aug 8, 2024
3 checks passed
@bnbarham
Copy link
Contributor
bnbarham commented Aug 8, 2024

@luispadron / @keith is there anyway that we can check these earlier? 5.10 was released a while back now, did something else change that needed these to be patched?

@keith
Copy link
Member
keith commented Aug 8, 2024

we technically didn't need the change here unless there was going to be other natural 5.10 releases

@bnbarham
Copy link
Contributor
bnbarham commented Aug 8, 2024

we technically didn't need the change here unless there was going to be other natural 5.10 releases

I was more talking about the other change rather than this one. And doesn't hurt to have this in just in case we do.

@keith
Copy link
Member
keith commented Aug 8, 2024

sorry which one do you mean? the 6.x one? FWIW something did change with these rules, repos have to declare compatibility on the new version of rules_swift since there were breaking changes, so it wasn't that swift-syntax changed, but if a repo that consumes it wants to use a newer version of rules_swift it would have failed w/o this change. These can technically be patched in the bazel-central-registry repo instead of pushed here, but on main it's nice to land to reduce the patching that has to happen there, and make it easier for folks to test dev versions

@bnbarham
Copy link
Contributor
bnbarham commented Aug 8, 2024

sorry which one do you mean?

#2766

so it wasn't that swift-syntax changed, but if a repo that consumes it wants to use a newer version of rules_swift it would have failed w/o this change

Ah I see, good to know. Thanks.

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.

4 participants
0