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

Cherrypick editions fixes to 27.x #17019

Merged
merged 4 commits into from
Jun 4, 2024
Merged

Cherrypick editions fixes to 27.x #17019

merged 4 commits into from
Jun 4, 2024

Conversation

mkruskal-google
Copy link
Member

No description provided.

Since the fixed/overridable split can occur whenever a feature is introduced or removed, we need to include those editions in the resulting compiled defaults.  This does bug only affects edition 2024 and later, where features may be removed or introduced in isolation.

PiperOrigin-RevId: 638903990
If a plugin doesn't support a feature used by a proto file, we can't trust any errors reported by that plugin.  We should always report these types of errors first.  There could be cases where the plugin doesn't correctly specify its support when it hits an error though, so we should *also* report any plugin errors to avoid masking them.

PiperOrigin-RevId: 639984803
@mkruskal-google mkruskal-google added the back-port Cherrypick PRs to release branches label Jun 4, 2024
@mkruskal-google mkruskal-google requested review from a team as code owners June 4, 2024 16:00
@mkruskal-google mkruskal-google requested review from haberman and removed request for a team June 4, 2024 16:00
PiperOrigin-RevId: 639885959
@mkruskal-google mkruskal-google merged commit 368b9b2 into 27.x Jun 4, 2024
175 checks passed
@mkruskal-google mkruskal-google deleted the cp-27 branch June 4, 2024 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-port Cherrypick PRs to release branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants