Skip to content

SG-43798 Bump vendored tk-core to v0.23.10#159

Open
stevelittlefish wants to merge 1 commit into
masterfrom
sg-43798-bump-tk-core-v0.23.10
Open

SG-43798 Bump vendored tk-core to v0.23.10#159
stevelittlefish wants to merge 1 commit into
masterfrom
sg-43798-bump-tk-core-v0.23.10

Conversation

@stevelittlefish

@stevelittlefish stevelittlefish commented Jul 20, 2026

Copy link
Copy Markdown

Summary

Runs tk_core_update.sh v0.23.10 to vendor the tk-core release that removes Python 3.7 support (SG-43667 / tk-core#1107). This:

  • Bumps the version guard in python/tk-core/python/tank/__init__.py from a Python 3.7 hard-block to 3.9.
  • Removes the vendored requirements/3.7/ directory.

Scope

Intentionally does not add minimum_python_version to the top-level info.yml — that's tracked separately in SG-42460, which has its own revert history (PR #148 broke auto-update) and needs careful validation on its own.

Test plan

  • Confirmed python/tk-core/python/tank/__init__.py guard now reads sys.version_info < (3, 9)
  • Confirmed python/tk-core/requirements/3.7/ is gone
  • Sanity-imported the vendored tank module on Python 3.9 - succeeds
  • Full desktop startup smoke test recommended before merge

Part of epic SG-36195.

🤖 Generated with Claude Code

Runs tk_core_update.sh v0.23.10 to vendor the tk-core release that
removes Python 3.7 support (SG-43667/#1107). This brings the
version guard in python/tk-core/python/tank/__init__.py from a
3.7 hard-block to 3.9, and removes the vendored requirements/3.7/
directory.

Note: v0.23.10 is currently a GitHub pre-release (QA in progress).
tk_core_update.sh clones directly off the git tag and doesn't care
about that flag, so this is safe to prep now, but this branch
shouldn't be released until tk-core is confirmed/promoted.

Scope intentionally excludes adding minimum_python_version to the
top-level info.yml - that's tracked separately in SG-42460, which
has its own history of breaking auto-update and needs its own
careful validation.
@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 10.30%. Comparing base (a2eacff) to head (544cdb7).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #159   +/-   ##
=======================================
  Coverage   10.30%   10.30%           
=======================================
  Files          13       13           
  Lines         582      582           
=======================================
  Hits           60       60           
  Misses        522      522           
Flag Coverage Δ
Linux 9.96% <100.00%> (ø)
Python-3.10 10.30% <100.00%> (ø)
Python-3.11 10.30% <100.00%> (ø)
Python-3.13 10.30% <100.00%> (ø)
Python-3.9 10.30% <100.00%> (ø)
Windows 9.79% <100.00%> (ø)
macOS 9.62% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@stevelittlefish
stevelittlefish requested a review from a team July 20, 2026 14:32

@julien-lang julien-lang left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but I don't see the changes from python-api?

@stevelittlefish

Copy link
Copy Markdown
Author

Looks good but I don't see the changes from python-api?

Does this need to be resolved now? If so I can do another tk-core release but it's time consuming.

@carlos-villavicencio-adsk

Copy link
Copy Markdown
Contributor

Does this need to be resolved now? If so I can do another tk-core release but it's time consuming.

It depends of the purpose of this release. If it's about releasing the 3.7 end of support, I believe we should include python-api.

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.

3 participants