chore(licensing): bump tifffile to 2026.5.2 in LICENSE-binary-python#4855
Merged
bobbai00 merged 3 commits intoMay 3, 2026
Merged
Conversation
Drift detected by the nightly strict-mode license-binary checker: LICENSE-binary claimed 2026.4.11, bundled was 2026.5.2 (transitive calver bump pulled in via scikit-image). Closes apache#4854 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bobbai00
added
the
release/v1.1.0-incubating
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4855 +/- ##
============================================
+ Coverage 43.36% 43.67% +0.30%
- Complexity 2036 2090 +54
============================================
Files 957 957
Lines 34077 34417 +340
Branches 3753 3785 +32
============================================
+ Hits 14777 15030 +253
- Misses 18509 18593 +84
- Partials 791 794 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
aglinxinyuan
approved these changes
May 3, 2026
Yicong-Huang
pushed a commit
that referenced
this pull request
May 3, 2026
…4855) ### What changes were proposed in this PR? Bump `tifffile` from `2026.4.11` to `2026.5.2` in `amber/LICENSE-binary-python` so it matches the version actually bundled in the runtime image. One-line change. ### Any related issues, documentation, discussions? Closes #4854 The drift is transitive: `tifffile` is pulled in by `scikit-image`, which is declared in `amber/operator-requirements.txt`. PR-time builds tolerate transitive calver bumps via `--ignore-transitive-version`; the nightly strict run is what flagged it. Once this PR merges, the next nightly run will auto-close the tracking issue. ### How was this PR tested? ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-7) (backported from commit 37d1341) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Backport to |
bobbai00
added a commit
that referenced
this pull request
May 4, 2026
### What changes were proposed in this PR? Bump `pytz` from `2026.1.post1` to `2026.2` in `amber/LICENSE-binary-python` so the manifest matches the runtime image's bundled version. One-line change. ### Any related issues, documentation, discussions? Closes #4905. Same pattern as the earlier `tifffile` drift (#4855) — transitive calver bump that strict mode catches. ### How was this PR tested? Drift signature from the strict-mode run: \`\`\` DRIFT (transitive) Python packages — claimed versions differ from bundled: ~ pytz: LICENSE-binary=2026.1.post1 bundled=2026.2 \`\`\` PR-time check on this PR runs with `--ignore-transitive-version` and should pass; the next strict-mode run on `main` post-merge confirms the fix end-to-end. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Yicong-Huang
pushed a commit
that referenced
this pull request
May 4, 2026
### What changes were proposed in this PR? Bump `pytz` from `2026.1.post1` to `2026.2` in `amber/LICENSE-binary-python` so the manifest matches the runtime image's bundled version. One-line change. ### Any related issues, documentation, discussions? Closes #4905. Same pattern as the earlier `tifffile` drift (#4855) — transitive calver bump that strict mode catches. ### How was this PR tested? Drift signature from the strict-mode run: \`\`\` DRIFT (transitive) Python packages — claimed versions differ from bundled: ~ pytz: LICENSE-binary=2026.1.post1 bundled=2026.2 \`\`\` PR-time check on this PR runs with `--ignore-transitive-version` and should pass; the next strict-mode run on `main` post-merge confirms the fix end-to-end. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-7) (backported from commit 4d6b96a) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yangzhang75
pushed a commit
to yangzhang75/texera
that referenced
this pull request
Jun 22, 2026
…pache#4855) ### What changes were proposed in this PR? Bump `tifffile` from `2026.4.11` to `2026.5.2` in `amber/LICENSE-binary-python` so it matches the version actually bundled in the runtime image. One-line change. ### Any related issues, documentation, discussions? Closes apache#4854 The drift is transitive: `tifffile` is pulled in by `scikit-image`, which is declared in `amber/operator-requirements.txt`. PR-time builds tolerate transitive calver bumps via `--ignore-transitive-version`; the nightly strict run is what flagged it. Once this PR merges, the next nightly run will auto-close the tracking issue. ### How was this PR tested? ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yangzhang75
pushed a commit
to yangzhang75/texera
that referenced
this pull request
Jun 22, 2026
…e#4906) ### What changes were proposed in this PR? Bump `pytz` from `2026.1.post1` to `2026.2` in `amber/LICENSE-binary-python` so the manifest matches the runtime image's bundled version. One-line change. ### Any related issues, documentation, discussions? Closes apache#4905. Same pattern as the earlier `tifffile` drift (apache#4855) — transitive calver bump that strict mode catches. ### How was this PR tested? Drift signature from the strict-mode run: \`\`\` DRIFT (transitive) Python packages — claimed versions differ from bundled: ~ pytz: LICENSE-binary=2026.1.post1 bundled=2026.2 \`\`\` PR-time check on this PR runs with `--ignore-transitive-version` and should pass; the next strict-mode run on `main` post-merge confirms the fix end-to-end. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
3 participants
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.
What changes were proposed in this PR?
Bump
tifffilefrom2026.4.11to2026.5.2inamber/LICENSE-binary-pythonso it matches the version actually bundled in the runtime image. One-line change.Any related issues, documentation, discussions?
Closes #4854
The drift is transitive:
tifffileis pulled in byscikit-image, which is declared inamber/operator-requirements.txt. PR-time builds tolerate transitive calver bumps via--ignore-transitive-version; the nightly strict run is what flagged it. Once this PR merges, the next nightly run will auto-close the tracking issue.How was this PR tested?
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (claude-opus-4-7)