Deprecate per-task actions#53
Merged
Merged
Conversation
Mirrors server-side deprecation (taskbadger/taskbadger#404). Emits a DeprecationWarning on the write paths; reads and the API are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (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
1 participant
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.
Client-side counterpart to the server deprecation in taskbadger/taskbadger#404, which retires per-job action config in favour of project-level actions. The write paths still work; this just surfaces the deprecation to SDK users ahead of removal.
Passing
actions=tocreate_task/update_task(and thereforeTask.create/Task.update/Task.add_actions) now emits aDeprecationWarning. The warning fires from the twosdk.pywrite functions so every caller is covered exactly once — no duplicate warnings from the wrapper methods. CLI--actionhelp text and docstrings are flagged too.No behavior change: reads, the
Actionclass, and the requests sent to the API are untouched.