Skip to content

Associate versions to features in BrushFamily proto.#510

Open
copybara-service[bot] wants to merge 1 commit intomainfrom
test_872916637
Open

Associate versions to features in BrushFamily proto.#510
copybara-service[bot] wants to merge 1 commit intomainfrom
test_872916637

Conversation

@copybara-service
Copy link

@copybara-service copybara-service bot commented Feb 20, 2026

Associate versions to features in BrushFamily proto.

Add descriptors to associate ink.proto.Version values with messages, fields, and enum types in BrushFamily proto. This will be used in a future CL to write consistency tests to ensure all features have a minimum compatible version associated with them. transitive_descriptor_set and options_cc_proto will be used in a future CL.

Version 1.0.0 (stable 1) is being used to represent all the features that were available when Ink 1.0.0 was released (TODO: I think I have this right here, but where can I find the last commit on the C++ side that was included to confirm this?). Everything else is being lumped under the (presumed) next release of Ink, Version 1.1.0-alpha01 (if features get cut or pushed off, we can change them). We don't necessarily need this split, as there is no release of Ink which has versioning set with a maximum allowed version of 1.0.0, so the actual 1.0.0 release will not reject brushes from 1.1.0-alpha01. But, this distinction in the code now has been useful for testing purposes.

@copybara-service copybara-service bot changed the title Add descriptors to associate ink.proto.Version values with messages, fields, and enum types in BrushFamily proto. This will be used in a future CL to write consistency tests to ensure all features have a minimum compatible version associated with them. Add descriptors to associate ink.proto.Version values with messages, fields, and enum types in BrushFamily proto. This will be used in a future CL to write consistency tests to ensure all features have a minimum compatible version associated with them. transitive_descriptor_set and options_cc_proto will be used in a future CL. Feb 23, 2026
Add descriptors to associate ink.proto.Version values with messages, fields, and enum types in BrushFamily proto. This will be used in a future CL to write consistency tests to ensure all features have a minimum compatible version associated with them. `transitive_descriptor_set` and `options_cc_proto` will be used in a future CL.

Version `1.0.0` (stable 1) is being used to represent all the features that were available when Ink `1.0.0` was released (TODO: I think I have this right here, but where can I find the last commit on the C++ side that was included to confirm this?). Everything else is being lumped under the (presumed) next release of Ink, Version `1.1.0-alpha01` (if features get cut or pushed off, we can change them). We don't necessarily need this split, as there is no release of Ink which has versioning set with a maximum allowed version of `1.0.0`, so the actual `1.0.0` release will not reject brushes from `1.1.0-alpha01`. But, this distinction in the code now has been useful for testing purposes.

PiperOrigin-RevId: 872916637
@copybara-service copybara-service bot changed the title Add descriptors to associate ink.proto.Version values with messages, fields, and enum types in BrushFamily proto. This will be used in a future CL to write consistency tests to ensure all features have a minimum compatible version associated with them. transitive_descriptor_set and options_cc_proto will be used in a future CL. Associate versions to features in BrushFamily proto. Feb 25, 2026
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.

1 participant