Skip to content

Upgrade ScalaPB to 1.0.0-alpha.3 to support protobuf 28#836

Open
jchyb wants to merge 1 commit intotypelevel:mainfrom
jchyb:protobuf-28
Open

Upgrade ScalaPB to 1.0.0-alpha.3 to support protobuf 28#836
jchyb wants to merge 1 commit intotypelevel:mainfrom
jchyb:protobuf-28

Conversation

@jchyb
Copy link

@jchyb jchyb commented Mar 12, 2026

In the new ScalaPB, symbols are returned with root prefixes and (for scala 3) and using keywords are inserted. Because of that, related tests were adjusted and we filter out _root_ from packages (since it's an illegal name there).

This is part PR, part question, since I realize there's an alpha in the version name - is it possible to merge this? Or merge into some branch and release via some separate/temporary version scheme?

The reason for needing this is that there is some incompatibility when migrating a project to Bazel 8, caused by a necessary rules_java upgrade, which itself enforces a newer protobuf version. Regardless of the reason, I think it would be helpful to get this in.

In the new ScalaPB, symbols are returned with _root_ prefixes and (for
scala 3) and `using` keywords are inserted. Because of that, related
tests were adjusted and we filter out _root_ from packages
(since it's an illegal name there).
@ahjohannessen
Copy link
Collaborator

ahjohannessen commented Mar 13, 2026

prefixing generated with _root_ seems harmless at first sight, but switching to "1.0.0-alpha.3" is probably not what users want on v3.0.x.

You could ask @thesamet what the plans are for releasing 1.0.0 and what that entails.

via some separate/temporary version scheme?

Perhaps a more practical approach would be to maintain your own fork until 1.0.0 is released. I am happy to merge things that do not break existing code, but I am not going to maintain more than necessary, e.g. a separate branch.

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