Skip to content

Remove deprecated update_progress / increment_progress#43

Merged
snopoke merged 1 commit intomainfrom
sk/remove-deprecated-progress
May 5, 2026
Merged

Remove deprecated update_progress / increment_progress#43
snopoke merged 1 commit intomainfrom
sk/remove-deprecated-progress

Conversation

@snopoke
Copy link
Copy Markdown
Collaborator

@snopoke snopoke commented May 5, 2026

Summary

  • Remove Task.update_progress and Task.increment_progress (both DeprecationWarning'd to be removed in v1.7.0; package is now on 1.7.0)
  • Update tests to call update_value / increment_value directly and rename test functions
  • Drop a now-redundant duplicate test_increment_value

Migration

The replacements are signature-compatible:

task.update_progress(value, value_step=..., rate_limit=...)  → task.update_value(value, value_step=..., rate_limit=...)
task.increment_progress(amount)                              → task.increment_value(amount)

This is a breaking change; the next release should be v1.8.0.

Test plan

  • pytest tests/test_sdk.py — 14/14 pass
  • No remaining references to update_progress / increment_progress

🤖 Generated with Claude Code

These were marked for removal in v1.7.0, but the package shipped 1.7.0
with them still in place. Removing them now (next release will be 1.8.0
since this is a breaking change). Callers should migrate to
update_value / increment_value, which have been the recommended methods
for several releases.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@snopoke snopoke merged commit 3741de3 into main May 5, 2026
3 of 6 checks passed
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