Skip to content

build(deps): Bump the uv group with 4 updates - #37

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/uv/uv-5c20d0e3e0
Nov 19, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
dependabot/uv/uv-5c20d0e3e0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor

Bumps the uv group with 4 updates: pandas, ty, pulumi and pulumi-datarobot.

Updates pandas from 3.1.0 to 3.1.1

Release notes

Sourced from pandas's releases.

pandas 3.1.1

We are pleased to announce the release of pandas 3.1.1. This is a patch release in the 3.1.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.1.x series upgrade to this version.

See the full whatsnew for a list of all the changes.

The release can be installed from PyPI:

python -m pip install --upgrade pandas==3.1.*

Or from conda-forge

conda install -c conda-forge pandas=3.1

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

Commits
  • 3dcc6fb RLS: 3.1.1
  • 01560e3 Backport PR #71896 on branch 3.1.x (DOC: cleanup 3.1.1 whatsnew) (#71898)
  • 49709c4 [backport 3.1.x] BUG: ffill/bfill on Arrow arrays without NA returns a view o...
  • 55089f8 Backport PR #71025 on branch 3.1.x (BUG: \s and \S in str regex methods missi...
  • eea23d0 Backport PR #71782 on branch 3.1.x (BUG: py.path.local treated as an open buf...
  • e427eb5 [backport 3.1.x] DOC: avoid system-ui in default font-family for the docs (re...
  • 3120a57 Backport PR #71572 on branch 3.1.x (BLD: don't include moments_simd.hpp in mo...
  • 378620e Backport PR #71865 on branch 3.1.x (REGR: ensure map() with datetime-like dty...
  • ceca8cb Backport PR #71495 on branch 3.1.x (BUG: support python-dateutil 3.0 tzfile (...
  • 68fc76e Backport PR #71661 on branch 3.1.x (CI: Remove install requirement-dev.txt sm...
  • Additional commits viewable in compare view

Updates ty from 0.0.94 to 0.0.97

Release notes

Sourced from ty's releases.

0.0.97

Release Notes

Released on 2026-11-04.

Bug fixes

  • Apply a cycle iteration cutoff across type inference (#30010)
  • Cap the size of inferred bytes literals during concatenation (#29942)
  • Django: support ForeignKey and OneToOneField as primary keys (#29785)
  • Fix a call hierarchy panic when expanding outgoing calls (#29964)
  • Handle decorators that replace overrides of final methods (#29961)
  • Ignore an empty VIRTUAL_ENV (#29973)
  • Preserve narrowed type variables in union inference (#29989)

Diagnostic improvements

  • Lower severity of diagnostics on recoverable invalid globs (#29946)
  • Rename unresolved-import to import-not-found (#29960)

Other changes

  • Document baseline support (#4897)
  • Document third-party library support. (#4879)
  • Pydantic: Respect extra-field configuration on settings models (#29902)
  • Reuse matching constraints at branch joins (#29875)
  • Reuse normalization of wide unions (#29874)
  • Skip empty diagnostic context for overloaded callables (#29959)
  • Speed up comparisons of deeply nested tuples (#29933)
  • Update PyCharm setup instructions for 2026.2 (#4914)

Contributors

Install ty 0.0.97

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ty/releases/download/0.0.97/ty-installer.sh | sh

... (truncated)

Changelog

Sourced from ty's changelog.

0.0.97

Released on 2026-11-04.

Bug fixes

  • Apply a cycle iteration cutoff across type inference (#30010)
  • Cap the size of inferred bytes literals during concatenation (#29942)
  • Django: support ForeignKey and OneToOneField as primary keys (#29785)
  • Fix a call hierarchy panic when expanding outgoing calls (#29964)
  • Handle decorators that replace overrides of final methods (#29961)
  • Ignore an empty VIRTUAL_ENV (#29973)
  • Preserve narrowed type variables in union inference (#29989)

Diagnostic improvements

  • Lower severity of diagnostics on recoverable invalid globs (#29946)
  • Rename unresolved-import to import-not-found (#29960)

Other changes

  • Document baseline support (#4897)
  • Document third-party library support. (#4879)
  • Pydantic: Respect extra-field configuration on settings models (#29902)
  • Reuse matching constraints at branch joins (#29875)
  • Reuse normalization of wide unions (#29874)
  • Skip empty diagnostic context for overloaded callables (#29959)
  • Speed up comparisons of deeply nested tuples (#29933)
  • Update PyCharm setup instructions for 2026.2 (#4914)

Contributors

0.0.96

Released on 2026-11-03.

Bug fixes

  • Fix a panic when checking protocols involving runtime type aliases (#29840)
  • Preserve Pydantic field metadata in quoted annotations (#29851)
  • Resolve class-local names in generic type aliases (#29915)

... (truncated)

Commits

Updates pulumi from 3.273.0 to 3.274.0

Release notes

Sourced from pulumi's releases.

v3.274.0

3.274.0 (2026-11-03)

Features

  • [cli/policy] Add pulumi policy get to show a policy pack's policies #25297
  • [cli/policy] Add --output json to pulumi policy publish, enable, disable, rm and validate-config, and print the updated policy group after enable and disable #25347
  • [cli/policy] Add --stack-rule and --account-rule to pulumi policy group new and edit, and show match rules in policy group console output #25345
  • [cli/policy] Add pulumi stack policy ls to list the policy groups and policy packs that apply to a stack #25345
  • [auto] Add schema commands to the generated automation APIs for NodeJS, Python and Go #25058
  • [auto] Add org usage commands to the generated automation APIs for NodeJS, Python and Go #25059
  • [auto] Add api commands to the generated automation APIs for NodeJS, Python and Go #25060
  • [auto] Add org audit-log commands to the generated automation APIs for NodeJS, Python and Go #25062
  • [cli/policy] Add pulumi policy issue edit to set the status, priority and assignee of a policy issue #25334
  • [cli/policy] Add filter and sort flags to pulumi policy issue ls, and add pulumi policy issue export #25333
  • [sdkgen/go] Generate <Resource>Exists functions that check whether a resource with a given ID exists without adopting it into the stack #25326
  • [programgen/go] Support resourceExists in generated Go programs #25326
  • [sdkgen/python] Generate static exists methods that check whether a resource with a given ID exists without adopting it into the stack #25336
  • [programgen/python] Support resourceExists in generated Python programs #25336

Bug Fixes

  • [cli] Normalize backend URLs when logging in with OIDC #25477
  • [sdk/python] Explain how to install missing Python dependencies when uv package discovery requires packaging #25495
  • [sdk/nodejs] Restrict @opentelemetry/api to 1.9.x so package managers such as bun and pnpm no longer install 1.10.0, which the OpenTelemetry SDK 2.x packages do not support #25444
  • [cli] Document PULUMI_FALLBACK_TO_STATE_SECRETS_MANAGER as the fix for secret decryption errors when running from a workspace without local stack configuration, such as the Automation API or a saved update plan applied from a different directory #24535
  • [cli/stack] Load the --copy-config-from stack before pulumi stack init creates the new stack, so a source stack that does not exist no longer leaves an empty stack behind #25421
  • [cli/config] Write block-style YAML when a CLI edit adds the first entry to an empty {} mapping in a stack or project file, instead of keeping the mapping on one line, as pulumi env set does #25415
  • [cli] Report that Pulumi ESC requires Pulumi Cloud before attempting login on DIY backends #25338
  • [engine] Preserve snapshot integrity when a protected resource has multiple pending-delete copies of its parent #25384
  • [pcl] Send the parent, version and pluginDownloadUrl invoke options to the engine #25403
  • [pcl] Fix hideDiffs to resolve both resource input and output properties #25450
  • [engine] Use the explicit provider of a custom parent for an invoke that sets no provider #25403
  • [cli/env] Show only environment change requests in pulumi env change-request commands #25443
  • [pcl] Report a diagnostic instead of panicking when a block that requires labels has none #25445
  • [engine] Fix invokes and calls of extension packages #25478
  • [sdk/python] Select the provider for pulumi.runtime.exists_resource from its options and parent when no resource is given #25336
  • [sdk/python] Fix RecursionError after creating many dynamic resources in one process #25492
  • [cli] Print a message when the CLI downloads a language runtime #25512

Improvements

  • [cli/policy] Show each group's mode and Insights account count in pulumi policy group ls, including new mode and numAccounts keys in its JSON output #25345
  • [cli/policy] Point agents to pulumi policy group get, pulumi stack policy ls and pulumi policy issue ls after pulumi policy group ls #25345
  • [cli] Add credentials helpers for backend selection, HTTP authentication, and cloud credentials #25260
  • [cli] Point AI agents that call policy endpoints through pulumi api to the matching pulumi policy command #25455
  • [cli/policy] Add --closed to pulumi policy issue ls, and show priority, assignee, policy group and policy remediation details in pulumi policy issue get #25295
  • [sdkgen] Reject schema property names that contain no ASCII letters, and warn on property names that collide after reduction to lower-case ASCII letters and digits #25292
  • [sdk/go] Take the ID passed to Context.ExistsResource as a StringInput, since it is an import ID rather than a resource ID #25326
  • [sdk/go] Add config.Value.ToCoercedObject, which returns a value with the typing Map.Set applies below the top level of a --path key #25377

... (truncated)

Changelog

Sourced from pulumi's changelog.

3.274.0 (2026-11-04)

Features

  • [cli/policy] Add pulumi policy get to show a policy pack's policies #25297
  • [cli/policy] Add --output json to pulumi policy publish, enable, disable, rm and validate-config, and print the updated policy group after enable and disable #25347
  • [cli/policy] Add --stack-rule and --account-rule to pulumi policy group new and edit, and show match rules in policy group console output #25345
  • [cli/policy] Add pulumi stack policy ls to list the policy groups and policy packs that apply to a stack #25345
  • [auto] Add schema commands to the generated automation APIs for NodeJS, Python and Go #25058
  • [auto] Add org usage commands to the generated automation APIs for NodeJS, Python and Go #25059
  • [auto] Add api commands to the generated automation APIs for NodeJS, Python and Go #25060
  • [auto] Add org audit-log commands to the generated automation APIs for NodeJS, Python and Go #25062
  • [cli/policy] Add pulumi policy issue edit to set the status, priority and assignee of a policy issue #25334
  • [cli/policy] Add filter and sort flags to pulumi policy issue ls, and add pulumi policy issue export #25333
  • [sdkgen/go] Generate <Resource>Exists functions that check whether a resource with a given ID exists without adopting it into the stack #25326
  • [programgen/go] Support resourceExists in generated Go programs #25326
  • [sdkgen/python] Generate static exists methods that check whether a resource with a given ID exists without adopting it into the stack #25336
  • [programgen/python] Support resourceExists in generated Python programs #25336

Bug Fixes

  • [cli] Normalize backend URLs when logging in with OIDC #25477
  • [sdk/python] Explain how to install missing Python dependencies when uv package discovery requires packaging #25495
  • [sdk/nodejs] Restrict @opentelemetry/api to 1.9.x so package managers such as bun and pnpm no longer install 1.10.0, which the OpenTelemetry SDK 2.x packages do not support #25444
  • [cli] Document PULUMI_FALLBACK_TO_STATE_SECRETS_MANAGER as the fix for secret decryption errors when running from a workspace without local stack configuration, such as the Automation API or a saved update plan applied from a different directory #24535
  • [cli/stack] Load the --copy-config-from stack before pulumi stack init creates the new stack, so a source stack that does not exist no longer leaves an empty stack behind #25421
  • [cli/config] Write block-style YAML when a CLI edit adds the first entry to an empty {} mapping in a stack or project file, instead of keeping the mapping on one line, as pulumi env set does #25415
  • [cli] Report that Pulumi ESC requires Pulumi Cloud before attempting login on DIY backends #25338
  • [engine] Preserve snapshot integrity when a protected resource has multiple pending-delete copies of its parent #25384
  • [pcl] Send the parent, version and pluginDownloadUrl invoke options to the engine #25403
  • [pcl] Fix hideDiffs to resolve both resource input and output properties #25450
  • [engine] Use the explicit provider of a custom parent for an invoke that sets no provider #25403
  • [cli/env] Show only environment change requests in pulumi env change-request commands #25443
  • [pcl] Report a diagnostic instead of panicking when a block that requires labels has none #25445
  • [engine] Fix invokes and calls of extension packages #25478
  • [sdk/python] Select the provider for pulumi.runtime.exists_resource from its options and parent when no resource is given #25336
  • [sdk/python] Fix RecursionError after creating many dynamic resources in one process #25492
  • [cli] Print a message when the CLI downloads a language runtime #25512

Improvements

  • [cli/policy] Show each group's mode and Insights account count in pulumi policy group ls, including new mode and numAccounts keys in its JSON output #25345
  • [cli/policy] Point agents to pulumi policy group get, pulumi stack policy ls and pulumi policy issue ls after pulumi policy group ls #25345
  • [cli] Add credentials helpers for backend selection, HTTP authentication, and cloud credentials #25260
  • [cli] Point AI agents that call policy endpoints through pulumi api to the matching pulumi policy command #25455
  • [cli/policy] Add --closed to pulumi policy issue ls, and show priority, assignee, policy group and policy remediation details in pulumi policy issue get #25295
  • [sdkgen] Reject schema property names that contain no ASCII letters, and warn on property names that collide after reduction to lower-case ASCII letters and digits #25292
  • [sdk/go] Take the ID passed to Context.ExistsResource as a StringInput, since it is an import ID rather than a resource ID #25326
  • [sdk/go] Add config.Value.ToCoercedObject, which returns a value with the typing Map.Set applies below the top level of a --path key #25377
  • [cli] Highlight backtick-quoted commands in CLI error messages #25432

... (truncated)

Commits
  • e6e7c7a Harvest propertyDependencies from OutputValue inputs on RegisterResource (#25...
  • a6cbe45 Point agents from pulumi api to the dedicated policy commands (#25455)
  • 263beaa tag sdk and pkg at the same time (#25527)
  • 1757c69 Add pulumi policy issue edit (#25334)
  • 521f2ed Add policy issue filters and policy issue export (#25333)
  • 8035c09 Clean up some property maps in testing code (#25525)
  • 689c528 Update Python and Node.js dependencies and lockfiles (#25425)
  • d2c8c7e Report language runtime downloads to the user (#25512)
  • 2962400 Restore the pickler methods patched when serializing Python dynamic providers...
  • eb15060 Remove the unused SourceResourceMonitor interface (#25498)
  • Additional commits viewable in compare view

Updates pulumi-datarobot from 0.13.0 to 0.14.0

Release notes

Sourced from pulumi-datarobot's releases.

v0.14.0

Upstream provider changes

terraform-provider-datarobot v0.13.0 → v0.14.0

v0.14.0 — 2026-10-28

Added
  • datarobot_registered_model_from_external: a Registered Model for a model that runs outside of DataRobot, created through POST /modelPackages/fromJSON/ from target, model_description, datasets, timeseries, text_generation and geospatial_monitoring, with optional model_id, tags and use_case_ids. How a change is applied depends on what changes:
    • name, description, version_name and model_description.description are updated in place on the Registered Model or its latest version. Removing model_description.description creates a new version, because the API cannot clear it in place.
    • target.type, target.name, target.class_names, adding or removing timeseries, setting or removing timeseries.series_column_name, and changing timeseries.datetime_column_name, datetime_column_format, forecast_distances_time_unit or forecast_distances replace the Registered Model, because DataRobot rejects a new version that differs from the previous one in these.
    • Any other change creates a new version of the Registered Model.
    • Checked at plan time, as DataRobot checks them on create: target.name is required unless target.type is AgenticWorkflow or MCP, and is required for every target type when datasets has training or holdout data, by catalog or version ID; an AgenticWorkflow target refuses dataset IDs, timeseries and geospatial_monitoring.
    • Import reads the model package fields from the latest version, so the first plan after an import does not replace the Registered Model. Values DataRobot uses by default when they are left out are imported as unset, and use_case_ids is not imported.
  • datarobot_workload has a computed placements attribute: the Enclaves the Workload runs on, with enclave_id, enclave and region, as the platform reports them. With enclave_selection_policy = "availability", it names the Enclave the scheduler chose. It is empty for a Workload outside any Enclave and is known only after apply when artifact_id or runtime changes, since the rollout that follows can move the Workload.
  • datarobot_custom_metric accepts geospatial_segment_attribute, the name of the column that contains geospatial values, serialized as geospatialSegmentAttribute on POST /deployments/{deploymentId}/customMetrics/. It must be a segment attribute of the Deployment, segment analysis must be enabled on the Deployment, and the corresponding feature must be of geospatial type. The API accepts it on create only, so changing it replaces the Custom Metric.
  • The attribute is required when is_geospatial is true and rejected when it is false, checked at plan time. The API does not enforce this on create: a geospatial Custom Metric with no attribute is accepted, but it has no column to read geospatial values from and, because the attribute cannot be changed in place, can only be fixed by replacing it. A configuration that already sets is_geospatial = true without the attribute now fails to plan until the attribute is set.
Changed
  • Built with Go 1.27.3, fixing a govulncheck advisory in Go 1.27.2's crypto/x509: certificate verification now refuses intermediate certificates that are known to be compromised, also on systems whose trust store has not been updated.
Fixed
  • datarobot_registered_model and datarobot_registered_model_from_leaderboard clear the Registered Model's description when description is removed or set to "". Formerly, the update left the description out of the request, so DataRobot kept the old value, the next refresh read it back, and every plan showed the same update again. The same applied when the description was set outside Terraform on a Registered Model whose configuration has none.
  • datarobot_registered_model_from_leaderboard no longer crashes the provider on an update that neither creates a new version nor sets version_name, such as changing name or description with version_name left out of the configuration. The update now keeps the latest version's name.
  • datarobot_artifact refuses an image_uri on a container built from source before anything is created. Such a configuration failed apply with Provider produced inconsistent result after apply once the artifact existed, and under Pulumi showed a diff on every preview. After upgrading, remove image_uri from such containers: plan and destroy refuse the configuration until then, and the built value stays in state.
  • A locked artifact with source.wait_for_build = false is refused at plan time, with or without image_uri. The platform locks an artifact only once its build has completed, so the apply failed after creating the artifact. When status comes from a variable, this check now waits for it instead of assuming locked.
  • A sidecar's image_uri no longer keeps the primary container's image_uri at its previous build in the plan, which failed the apply after a source change. A change that creates a new version of such an artifact now rebuilds the primary image, as it already did without a sidecar.
  • A datarobot_artifact destroy that the platform refuses with 409 Conflict because workloads still use its version or repository now names those workloads, with their ID, name and status. A workload that an earlier version left out of state after it failed to start could block every destroy, and the platform's error did not say which workload to delete.
  • The deployment unit tests no longer hang or fail when the whole pkg/provider suite runs. Fixes made to tests: TestUnitDeploymentModelReplacementSuccess, TestUnitDeploymentModelReplacementMismatch, TestWaitForDeploymentStatusErroredIncludesLogsAndUIURL and TestWaitForDeploymentStatusErroredLogRetrievalFailure. This changes tests only; the provider's behavior is unchanged.
  • Docs: the datarobot_workload page has a "Failed applies" section, and the datarobot_artifact page says what a create that fails partway leaves behind, under Terraform and under Pulumi. Neither engine rolls completed resources back: an artifact created before a datarobot_workload the platform refuses stays in state, the retry reuses it without another upload or build, and terraform destroy removes it.
  • datarobot_artifact removes a file deleted from source.dir from the catalog when the directory has no sync state yet, as in a fresh clone or a CI checkout (.datarobot/workload/ is git-ignored); the file used to stay in the catalog and reach the image build, or was downloaded back when the catalog had moved on. After upgrading, the first apply that syncs such a checkout removes every catalog file that is not in source.dir, including files .drignore excludes, and names them in a warning, so the checkout must hold every file the image needs.
  • An apply retried after a failed image build builds again when the sync finds the catalog already matching source.dir, instead of recording the source over the failed build.

Full upstream diff: datarobot-community/terraform-provider-datarobot@v0.13.0...v0.14.0

Pulumi SDK surface

Diff of the generated schema.json — what actually reached the SDKs.

New resources (1)

  • datarobot:index/registeredModelFromExternal:RegisteredModelFromExternal

Changed resources (2)

  • datarobot:index/customMetric:CustomMetric
    • new inputs: geospatialSegmentAttribute

... (truncated)

Changelog

Sourced from pulumi-datarobot's changelog.

[0.14.0] - 2026-10-29

Upstream provider changes

terraform-provider-datarobot v0.13.0 → v0.14.0

v0.14.0 — 2026-10-28

Added
  • datarobot_registered_model_from_external: a Registered Model for a model that runs outside of DataRobot, created through POST /modelPackages/fromJSON/ from target, model_description, datasets, timeseries, text_generation and geospatial_monitoring, with optional model_id, tags and use_case_ids. How a change is applied depends on what changes:
    • name, description, version_name and model_description.description are updated in place on the Registered Model or its latest version. Removing model_description.description creates a new version, because the API cannot clear it in place.
    • target.type, target.name, target.class_names, adding or removing timeseries, setting or removing timeseries.series_column_name, and changing timeseries.datetime_column_name, datetime_column_format, forecast_distances_time_unit or forecast_distances replace the Registered Model, because DataRobot rejects a new version that differs from the previous one in these.
    • Any other change creates a new version of the Registered Model.
    • Checked at plan time, as DataRobot checks them on create: target.name is required unless target.type is AgenticWorkflow or MCP, and is required for every target type when datasets has training or holdout data, by catalog or version ID; an AgenticWorkflow target refuses dataset IDs, timeseries and geospatial_monitoring.
    • Import reads the model package fields from the latest version, so the first plan after an import does not replace the Registered Model. Values DataRobot uses by default when they are left out are imported as unset, and use_case_ids is not imported.
  • datarobot_workload has a computed placements attribute: the Enclaves the Workload runs on, with enclave_id, enclave and region, as the platform reports them. With enclave_selection_policy = "availability", it names the Enclave the scheduler chose. It is empty for a Workload outside any Enclave and is known only after apply when artifact_id or runtime changes, since the rollout that follows can move the Workload.
  • datarobot_custom_metric accepts geospatial_segment_attribute, the name of the column that contains geospatial values, serialized as geospatialSegmentAttribute on POST /deployments/{deploymentId}/customMetrics/. It must be a segment attribute of the Deployment, segment analysis must be enabled on the Deployment, and the corresponding feature must be of geospatial type. The API accepts it on create only, so changing it replaces the Custom Metric.
  • The attribute is required when is_geospatial is true and rejected when it is false, checked at plan time. The API does not enforce this on create: a geospatial Custom Metric with no attribute is accepted, but it has no column to read geospatial values from and, because the attribute cannot be changed in place, can only be fixed by replacing it. A configuration that already sets is_geospatial = true without the attribute now fails to plan until the attribute is set.
Changed
  • Built with Go 1.27.3, fixing a govulncheck advisory in Go 1.27.2's crypto/x509: certificate verification now refuses intermediate certificates that are known to be compromised, also on systems whose trust store has not been updated.
Fixed
  • datarobot_registered_model and datarobot_registered_model_from_leaderboard clear the Registered Model's description when description is removed or set to "". Formerly, the update left the description out of the request, so DataRobot kept the old value, the next refresh read it back, and every plan showed the same update again. The same applied when the description was set outside Terraform on a Registered Model whose configuration has none.
  • datarobot_registered_model_from_leaderboard no longer crashes the provider on an update that neither creates a new version nor sets version_name, such as changing name or description with version_name left out of the configuration. The update now keeps the latest version's name.
  • datarobot_artifact refuses an image_uri on a container built from source before anything is created. Such a configuration failed apply with Provider produced inconsistent result after apply once the artifact existed, and under Pulumi showed a diff on every preview. After upgrading, remove image_uri from such containers: plan and destroy refuse the configuration until then, and the built value stays in state.
  • A locked artifact with source.wait_for_build = false is refused at plan time, with or without image_uri. The platform locks an artifact only once its build has completed, so the apply failed after creating the artifact. When status comes from a variable, this check now waits for it instead of assuming locked.
  • A sidecar's image_uri no longer keeps the primary container's image_uri at its previous build in the plan, which failed the apply after a source change. A change that creates a new version of such an artifact now rebuilds the primary image, as it already did without a sidecar.
  • A datarobot_artifact destroy that the platform refuses with 409 Conflict because workloads still use its version or repository now names those workloads, with their ID, name and status. A workload that an earlier version left out of state after it failed to start could block every destroy, and the platform's error did not say which workload to delete.
  • The deployment unit tests no longer hang or fail when the whole pkg/provider suite runs. Fixes made to tests: TestUnitDeploymentModelReplacementSuccess, TestUnitDeploymentModelReplacementMismatch, TestWaitForDeploymentStatusErroredIncludesLogsAndUIURL and TestWaitForDeploymentStatusErroredLogRetrievalFailure. This changes tests only; the provider's behavior is unchanged.
  • Docs: the datarobot_workload page has a "Failed applies" section, and the datarobot_artifact page says what a create that fails partway leaves behind, under Terraform and under Pulumi. Neither engine rolls completed resources back: an artifact created before a datarobot_workload the platform refuses stays in state, the retry reuses it without another upload or build, and terraform destroy removes it.
  • datarobot_artifact removes a file deleted from source.dir from the catalog when the directory has no sync state yet, as in a fresh clone or a CI checkout (.datarobot/workload/ is git-ignored); the file used to stay in the catalog and reach the image build, or was downloaded back when the catalog had moved on. After upgrading, the first apply that syncs such a checkout removes every catalog file that is not in source.dir, including files .drignore excludes, and names them in a warning, so the checkout must hold every file the image needs.
  • An apply retried after a failed image build builds again when the sync finds the catalog already matching source.dir, instead of recording the source over the failed build.

Full upstream diff: datarobot-community/terraform-provider-datarobot@v0.13.0...v0.14.0

Pulumi SDK surface

Diff of the generated schema.json — what actually reached the SDKs.

New resources (1)

  • datarobot:index/registeredModelFromExternal:RegisteredModelFromExternal

Changed resources (2)

  • datarobot:index/customMetric:CustomMetric

... (truncated)

Commits
  • 0afefbf Upgrade terraform-provider-datarobot to v0.14.0 (#406)
  • cc38b13 Bump the github-actions-minor-patch group with 5 updates (#405)
  • 8870318 Bump the gomod-minor-patch group across 2 directories with 1 update (#404)
  • 80e463e Bump the github-actions-minor-patch group with 3 updates (#403)
  • f4c459d Bump the gomod-minor-patch group across 2 directories with 1 update (#402)
  • See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the uv group with 4 updates: [pandas](https://github.com/pandas-dev/pandas), [ty](https://github.com/astral-sh/ty), [pulumi](https://github.com/pulumi/pulumi) and [pulumi-datarobot](https://github.com/datarobot-community/pulumi-datarobot).


Updates `pandas` from 3.1.0 to 3.1.1
- [Release notes](https://github.com/pandas-dev/pandas/releases)
- [Commits](pandas-dev/pandas@v3.1.0...v3.1.1)

Updates `ty` from 0.0.94 to 0.0.97
- [Release notes](https://github.com/astral-sh/ty/releases)
- [Changelog](https://github.com/astral-sh/ty/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ty@0.0.94...0.0.97)

Updates `pulumi` from 3.273.0 to 3.274.0
- [Release notes](https://github.com/pulumi/pulumi/releases)
- [Changelog](https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md)
- [Commits](pulumi/pulumi@v3.273.0...v3.274.0)

Updates `pulumi-datarobot` from 0.13.0 to 0.14.0
- [Release notes](https://github.com/datarobot-community/pulumi-datarobot/releases)
- [Changelog](https://github.com/datarobot-community/pulumi-datarobot/blob/main/CHANGELOG.md)
- [Commits](datarobot-community/pulumi-datarobot@v0.13.0...v0.14.0)

---
updated-dependencies:
- dependency-name: pandas
  dependency-version: 3.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: uv
- dependency-name: ty
  dependency-version: 0.0.97
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: uv
- dependency-name: pulumi
  dependency-version: 3.274.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv
- dependency-name: pulumi-datarobot
  dependency-version: 0.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Dependency update, usually opened by Dependabot. label Nov 19, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) November 19, 2026 11:08

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@github-actions
github-actions Bot merged commit 5ad8c38 into main Nov 19, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency update, usually opened by Dependabot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant