Repository navigation
Conversation
Reading a data row's versions only returned the user's ID, so you had to list every organization user to see who submitted or approved. The API already returns the user (createdBy); the SDK now reads its email, with the masking user emails always get between a workforce provider and the organizations it works for. The Project.label_versions() docstring now also says that a review decision on a whole data row records one version per label on it, all with the same time and reviewer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mnoszczak
requested review from
KeshavSahoo,
apollonin,
gmadaan-hue,
ikerr,
lb-mwetter,
manuaero and
pablito25sp
October 29, 2026 17:09
pawelkozik-labelbox
approved these changes
Oct 29, 2026
kjamrozy
approved these changes
Oct 30, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LabelVersionnow hascreated_by_email, so you can see who submitted or approved without listing every organization user and mapping the IDs yourself. John Bullock hit this while checking an Airbnb data row: he had to build{u.uid: u.email for u in org.users()}.createdBy { email }, which the publicLabelVersiontype has had since Labelbox/intelligence#31624. No API change is needed. The original E2E for that PR read reviewer emails through the same field.@classified, so it is masked the way user emails always are between a workforce provider and the organizations it works for. If the user can't be read, it isNone.Project.label_versions()docstring: a review decision on a whole data row records one version per label on it, all with the same time and reviewer. Filtering bydata_rowon a row with three labels therefore returns three APPROVED versions. The example now printslabel_id, so those don't look like duplicates.Tests:
tests/unit/schema/test_label_version.py(17 passed); ruff and mypy are clean on the changed files.🤖 Generated with Claude Code