chore(deps): update deadline requirement from <0.59,>=0.55.1 to >=0.55.1,<0.60

[dependabot]

Updates the requirements on deadline to permit the latest version.

Release notes

Sourced from deadline's releases.

0.59.0 (2026-06-17)

BREAKING CHANGES

• Farms are now supported across all Deadline Cloud regions. A farm is identified by (region, farm_id) rather than a farm_id in a single globally-fixed region. List operations (like list_farms) now fan out calls to every region and aggregate results, each annotated with its region. The farm list CLI output now includes a region field before farmId. (#1202)

Features

• Added use_deadline_cloud_v2_channel keyword argument to SubmitJobToDeadlineDialog and SharedJobSettingsWidget. When enabled, the deadline-cloud-v2 Conda channel is prepended ahead of the default deadline-cloud channel in the queue environment's CondaChannels parameter, keeping deadline-cloud as a fallback. (#1211)

Changelog

Sourced from deadline's changelog.

0.59.0 (2026-06-17)

BREAKING CHANGES

• Farms are now supported across all Deadline Cloud regions. A farm is identified by (region, farm_id) rather than a farm_id in a single globally-fixed region. List operations (like list_farms) now fan out calls to every region and aggregate results, each annotated with its region. The farm list CLI output now includes a region field before farmId. (#1202)

Features

• Added use_deadline_cloud_v2_channel keyword argument to SubmitJobToDeadlineDialog and SharedJobSettingsWidget. When enabled, the deadline-cloud-v2 Conda channel is prepended ahead of the default deadline-cloud channel in the queue environment's CondaChannels parameter, keeping deadline-cloud as a fallback. (#1211)

0.58.0 (2026-06-10)

BREAKING CHANGES

• Dropped support for Python 3.8. The minimum supported Python version is now 3.9. Users running Python 3.8 must upgrade their Python installation. (#1200)

Features

• When running deadline bundle gui-submit, the Host Requirements tab now correctly populates from the job template's hostRequirements instead of always defaulting to "Run on all available worker hosts". (#1198)
• When no default farm or queue is configured, the CLI and GUI submit dialog now automatically select the farm/queue if only one is available to the user, removing the need to manually configure defaults in single-farm/queue setups. (#1015)

Bug Fixes

• Fixed an issue where some internal boto clients were missing the default client config, causing user-agent attribution (app/deadline-client version, submitter, and CLI command name) to be absent from certain API calls (attachment downloads/uploads and log queries). (#1197)

0.57.4 (2026-06-08)

Features

• When no default farm or queue is configured, the CLI and GUI submit dialog now automatically select the farm/queue if only one is available to the user. If multiple exist, the existing behavior is preserved. (#1015)
• The Monitor's session_id is now read from ~/.deadline/config and included in telemetry events for cross-component correlation with Monitor and CTDX sessions. (#1184)

0.57.3 (2026-06-01)

Features

• Added a preGUI submission hook phase, allowing custom logic to run before the submission GUI is displayed. (#1178)

Bug Fixes

• Fixed an issue in the submission UI where timeout validation errors would flash while still editing days/hours/minutes fields. Errors now only appear after focus leaves the entire timeout row, and clear immediately when the value becomes valid. (#1180)

0.57.2 (2026-05-25)

Features

• Telemetry error events now include sanitized stack traces to help improve diagnostics. Stack traces are sanitized using an allowlist-based approach and do not include exception messages. (#1080)

0.57.1 (2026-05-18)

Bug Fixes

• Environment hooks now correctly receive the job bundle directory instead of the hooks directory. Previously, HookManager.execute_pre_submission_hooks() was overwriting metadata.job_bundle_dir with the hooks directory path for environment hooks (DEADLINE_HOOKS_DIR). (#1162)
• Pre-submission hooks can now modify the template and priority fields. Previously, only attachments.assetReferences changes from hook output were applied. (#1162)

0.57.0 (2026-05-08)

BREAKING CHANGES

• The deadline job download-output command now supports storage profile path mapping, which may change download destination paths when a storage profile is configured. Users relying on the previous raw path behavior should review their download scripts. (#1029)

Features

• Added deadline job download-input CLI command that downloads job input files (job attachments) with optional glob-style --include filtering, --match-paths-by (JOB/LOCAL) storage profile path mapping, JSON output, and conflict resolution options. (#1154)
• Added --include / -i repeatable option to deadline job download-output, allowing you to download specific files using glob patterns or relative paths instead of all job outputs. Multiple patterns are OR'd. Without --include, all outputs download as before. (#1108)
• Added storage profile path mapping support to deadline job download-output, enabling automatic path translation between job and local filesystem paths. (#1029)
• Added two new workstation configuration settings: settings.max_retries_per_task (default: 5) and settings.max_failed_tasks_count (default: 20). These defaults are used when submitting jobs via CLI, API, or GUI when no explicit value is provided and the job bundle doesn't specify them. (#1150)
• Removed the hard dependency on AWS STS. Authentication status checks now use deadline:ListFarms instead of sts:GetCallerIdentity, avoiding slow timeouts and hard failures on networks that block STS. (#1147)

... (truncated)

Commits

• d6a49ff chore(release): 0.59.0 (#1214)
• 405029c revert: "chore(release): 0.59.0 (#1209)" (#1213)
• a74f967 feat: Append deadline-cloud-v2 to the conda queue environment for migration. ...
• 7c2b5c2 fix(test): dismiss Firefox welcome dialog in Linux DCM e2e test (#1212)
• c6f2a53 chore(release): 0.59.0 (#1209)
• 848af18 fix(test): update integ test assertions for multi-region farm list output (#1...
• 09488f5 feat!: support farms across all Deadline Cloud regions (#1202)
• a96b9ac chore: make API change detection use all as the public surface (#1203)
• 3aa01f5 chore(release): 0.58.0 (#1205)
• 905e99f chore(release): 0.57.4 (#1196)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[karthikbekalp]

Closing this PR in favor of: #467

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.