fix(deps): update all non-major dependencies - #33
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 14, 2025 22:44
922247e to
52c2da5
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
September 4, 2025 02:46
6bc7907 to
402aeee
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 10, 2025 07:59
bcbc56d to
d43f69e
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 18, 2025 19:48
d3ee846 to
7a5e6c7
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
September 29, 2025 16:07
d44f4ee to
30e3b18
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 8, 2025 23:01
a72e7b8 to
f9dfb70
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 18, 2025 11:10
b03cf4e to
28b741b
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
October 25, 2025 23:53
a777000 to
374f29b
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 3, 2025 23:46
b6bf517 to
0cf4148
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 9, 2025 16:05
55c955f to
3e25681
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 19, 2025 12:00
4409313 to
90eba90
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
December 5, 2025 05:04
101da48 to
4dafd1a
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
January 27, 2026 00:15
10ec692 to
15d7282
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
February 3, 2026 07:40
0f6e079 to
20b6061
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
February 11, 2026 11:40
a96102a to
4ea4901
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
February 20, 2026 16:13
a07ccfd to
421af85
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
March 7, 2026 05:40
afa2547 to
448efc4
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
March 13, 2026 21:29
548f9e1 to
864bafe
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 31, 2026 17:43
864bafe to
603cdac
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
April 20, 2026 18:25
0f03003 to
4ceda27
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 23, 2026 19:40
4ceda27 to
f0e52a7
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
May 6, 2026 20:10
11176bf to
34ebcd9
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 10, 2026 08:09
34ebcd9 to
2124f9f
Compare
Contributor
Author
|
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
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.
This PR contains the following updates:
v5.0.0→v5.1.0v6.1.0→v6.5.03.22.1→3.24.1v5.3.1→v5.3.2v1.20.0→v1.20.10v2.2.0→v2.3.3v2.2.1-0.20260610110527-59c45527ebe4→v2.4.1v1.110.0→v1.123.0v0.27.2→v0.28.0v1.18.0→v1.19.0v2.39.0→v2.40.1v0.41.0→v0.48.0v1.79.3→v1.82.1v0.35.3→v0.36.3v0.35.0→v0.36.3v0.35.3→v0.36.3v0.35.3→v0.36.3v0.23.3→v0.24.1v0.20.0→v0.21.0Release Notes
actions/checkout (actions/checkout)
v5.1.0Compare Source
v5.0.1Compare Source
actions/setup-go (actions/setup-go)
v6.5.0Compare Source
v6.4.0Compare Source
What's Changed
Enhancement
Dependency update
Documentation update
New Contributors
Full Changelog: actions/setup-go@v6...v6.4.0
v6.3.0Compare Source
What's Changed
Full Changelog: actions/setup-go@v6...v6.3.0
v6.2.0Compare Source
What's Changed
Enhancements
Dependency updates
New Contributors
Full Changelog: actions/setup-go@v6...v6.2.0
fkirc/skip-duplicate-actions (fkirc/skip-duplicate-actions)
v5.3.2Compare Source
v5.3.2
crossplane/crossplane-runtime (github.com/crossplane/crossplane-runtime)
v1.20.10Compare Source
What's Changed
Full Changelog: crossplane/crossplane-runtime@v1.20.9...v1.20.10
v1.20.9Compare Source
What's Changed
Full Changelog: crossplane/crossplane-runtime@v1.20.8...v1.20.9
v1.20.8Compare Source
What's Changed
Full Changelog: crossplane/crossplane-runtime@v1.20.6...v1.20.8
v1.20.6Compare Source
What's Changed
Full Changelog: crossplane/crossplane-runtime@v1.20.0...v1.20.6
crossplane/upjet (github.com/crossplane/upjet/v2)
v2.4.1Compare Source
v2.4.0This is a minor release that ships several new configuration and runtime capabilities for upjet-based providers, together with a set of bug fixes and security-relevant dependency updates.
New Features
Runtime Terraform conversions in the CLI-based external client (#683): The Terraform CLI external client now applies the runtime schema conversions (for example, singleton-list-to-embedded-object) that were previously handled only by the no-fork clients. This unblocks CLI-based providers whose reconciliations failed when converting singleton lists to embedded objects.
Separate Terraform import ID via
GetImportIDFn(#677): Added an optionalExternalName.GetImportIDFnfield. When set, upjet uses it to produce the ID passed toterraform import, whileGetIDFncontinues to produce the ID for the refreshed state. This supports providers that store resource IDs in a different format than their import function expects; existing behavior is preserved when it is unset. Fixes #676.Customizable controller setup aggregator & terraformed templates (#693): Added the
config.WithSetupAggregatorTemplateandconfig.WithTerraformedTemplateProviderOptions, allowing providers to override the controller setup aggregator and theresource.Terraformedtemplates used during code generation. The change is backward-compatible and mirrors the existingconfig.WithMainTemplateoption. A newTerraform.ResourceSchematemplate variable is also introduced, supersedingTerraform.SchemaVersionfor terraformed template rendering.Storage version migration support (#588, #711): Added support for automatically migrating stored CRD resources to the current storage version when a CRD's storage version changes, avoiding stale versions lingering in etcd across upgrades. #711 switches this to a dynamic approach that discovers the versions to migrate at runtime instead of relying on static configuration.
Bug Fixes
Fix namespaced conversions resolved from the wrong provider in RoundTrip (#695):
registry.GetConversionsselected between the cluster- and namespaced-scoped providers using the destination object's namespace, which was still empty at the first conversion stage duringRoundTrip, so namespaced resources fell through to the cluster-scoped provider. The namespace is now copied from the source before conversions are resolved, so all conversion stages operate against the correct provider.Fix "unexpected identity change" errors at Observe (Plugin Framework) (#698): Incomplete or invalid resource identities (for example, cached after a failed
Create) could be sent asCurrentIdentityto Terraform'sReadResourceRPC, causing subsequentObservecalls to fail with an "unexpected identity change" diagnostic once the original failure was resolved. Such identities are no longer fed back to the provider, eliminating the spurious errors.Prevent Terraform provider panics when the external resource is not found (#685):
InstanceState'sRawConfigandRawPlanare now populated when a previously cached state had zero-valuedRawConfig/RawPlanbut the external resource is (no longer) found. This prevents the underlying Terraform provider from panicking when it reads those attributes (for example, the Terraform AWS provider's tagging interceptor).Omit XValidation for required fields that have references (#684): When a field is marked required but also has a reference configured, it is satisfiable via its
*Ref/*Selectorfields, so no CELXValidationrequired-parameter rule is emitted for it anymore. This avoids validation errors for fields resolved through references.Do not emit SSA markers on observation (status) fields (#660): Removed the
listType: mapmarkers and injected map-key defaults from generatedstatus.atProviderfields, where server-side apply merge markers do not apply. Fixes #659.Dependency & Security Updates
golang.org/x/netto v0.55.0 (#699) andgoogle.golang.org/grpcto v1.82.1 (#710) to pick up security fixes.What's Changed
Full Changelog: crossplane/upjet@v2.3.0...v2.4.0
databricks/terraform-provider-databricks (github.com/databricks/terraform-provider-databricks)
v1.123.0Compare Source
Important Changes
Removed plan-time
workspace_idreachability validation for unified-providerresources (#5887).
workspace_idreachability and mismatch errors (e.g.workspace_id mismatch,managing workspace-level resources requires a workspace_id) are now reportedwhen the resource is applied instead of during
terraform plan. Plans no longermake workspace-resolution API calls for these checks. This fixes false-positive
plan failures for principals that can manage a resource but cannot call the
workspace
/Meendpoint, and forprovider_config.workspace_idvalues that areonly known after apply (for example a
workspace_idsourced from anotherresource that is created in the same run). For newly-created workspace-level
resources this removes plan-time workspace API calls entirely; existing
resources still refresh at plan (an unavoidable read), which validates the
workspace they already live in.
New Features and Improvements
databricks_recipientsdata source to list Delta Sharing recipient names.trace_locationtodatabricks_mlflow_experimentfor storing experiment traces in a Unity Catalog schema (#5869). The block is immutable (ForceNew);table_prefixis optional and, when omitted, server-defaulted, with the resolved value exposed on the read-onlyeffective_table_prefix.Bug Fixes
VIEWindatabricks_sql_table(#5855). The provider emittedALTER VIEW ... ALTER COLUMN ... COMMENT, which Databricks rejects with aPARSE_SYNTAX_ERROR, leaving the change stuck as a perpetual, un-appliable diff. Column comment changes on views are now applied in place viaCOMMENT ON COLUMN, matching how column comments on tables are updated.databricks_access_control_rule_setdrift detection when allgrant_rulesare removed outside Terraform (#5589).Internal Changes
A provider-level
workspace_idis now consistently validated when aworkspace-level resource acquires its client, regardless of whether the value
came from the resource's
provider_configblock or the provider configuration(#5887).
Previously a workspace-level provider silently ignored a mismatched
provider-level
workspace_idwhen a resource omittedprovider_config. It nowsurfaces a
workspace_id mismatcherror at apply, matching the behavior whenprovider_config.workspace_idis set explicitly. For the common case where theprovider-level
workspace_idmatches the configured workspace (including whenit is auto-resolved from host metadata) there is no change.
v1.122.0Compare Source
New Features and Improvements
databricks_postgres_cdf_config.databricks_postgres_cdf_status.Bug Fixes
VIEWindatabricks_sql_table(#5855). The provider emittedALTER VIEW ... ALTER COLUMN ... COMMENT, which Databricks rejects with aPARSE_SYNTAX_ERROR, leaving the change stuck as a perpetual, un-appliable diff. Column comment changes on views are now applied in place viaCOMMENT ON COLUMN, matching how column comments on tables are updated.v1.121.0Compare Source
Important Changes
databricks_mws_ncc_private_endpoint_rulehas been refactored in this version to fix multiple bugs in its implementation and behavior. Server-populated attributes are now strictly read-only (writes that previously produced perpetual plan drift now error at plan time), plan churn on previously-Optional output fields is eliminated, and the new Plugin Framework implementation (behindDATABRICKS_TF_ENABLED_PF_RESOURCES) polls the rule'sconnection_stateduring Create so a failed or unusable provisioning state surfaces at apply time instead of on the next plan. SeeBreaking ChangesandNew Features and Improvementsbelow for specifics.Breaking Changes
databricks_mws_ncc_private_endpoint_rule(#5819). The attributesrule_id,account_id,endpoint_name,vpc_endpoint_id,connection_state,creation_time,updated_time,deactivated,deactivated_at,error_message, andgcp_endpoint.psc_endpoint_uriare now computed-only and can no longer be set in HCL. They are populated by the server in every API response (andpsc_endpoint_uriis unconditionally overwritten from the cloud-platform truth on every read), and previous releases accepted writes to these attributes silently while the API ignored or overwrote the values, producing perpetual drift on every plan. Configurations that explicitly assigned any of these attributes must remove the assignment; the value is still available in state after apply.New Features and Improvements
databricks_mws_ncc_private_endpoint_ruleis now available behindDATABRICKS_TF_ENABLED_PF_RESOURCES=databricks_mws_ncc_private_endpoint_rule(#5819). Once opted in,terraform applywaits for the rule to leaveCREATINGbefore returning:PENDINGandESTABLISHEDsucceed, while aCREATE_FAILED,REJECTED,DISCONNECTED, orEXPIREDconnection state surfaces as an apply-time error instead of on the next plan. This differs from the SDKv2 implementation, which returns immediately without polling. The Plugin Framework implementation will replace the SDKv2 implementation in a follow-up version.databricks_library,databricks_quality_monitor, anddatabricks_shareresources, and thedatabricks_share,databricks_shares, anddatabricks_volumesdata sources. These resources have been served by the Plugin Framework by default since their migration; the SDKv2 implementations remain only as opt-in fallbacks via theUSE_SDK_V2_RESOURCES/USE_SDK_V2_DATA_SOURCESenvironment variables. Setting either environment variable for any of these names now emits a runtime warning (visible withTF_LOG=WARNor higher), and the SDKv2 implementations will be removed in the next major release of the provider.databricks_ai_search_endpoint.databricks_ai_search_index.clear_cloud_attributes_on_removetodatabricks_cluster(#5812). When set totrue, removing a cloud attributes block (aws_attributes,azure_attributes,gcp_attributes) from the configuration clears it instead of the removal being silently suppressed. The flag defaults tofalse, preserving the existing diff-suppression behavior that prevents perpetual drift from platform-returned cloud attribute defaults. Keeping a block, even partially specified, is unaffected; only removing the whole block clears.Bug Fixes
Documentation
databricks_budgetfor creating budgets to control Genie usage costs (#5817).Exporter
import.shmore safely (#5848).Internal Changes
instance_profilesattribute, and replace it withrolesindatabricks_groupdata source (#5086)v1.120.0Compare Source
New Features and Improvements
Add resource and data source for
databricks_postgres_data_api.Deprecate the SDKv2 fallback implementations of
databricks_library,databricks_quality_monitor, anddatabricks_shareresources, and thedatabricks_share,databricks_shares, anddatabricks_volumesdata sources. These resources have been served by the Plugin Framework by default since their migration; the SDKv2 implementations remain only as opt-in fallbacks via theUSE_SDK_V2_RESOURCES/USE_SDK_V2_DATA_SOURCESenvironment variables. Setting either environment variable for any of these names now emits a runtime warning (visible withTF_LOG=WARNor higher), and the SDKv2 implementations will be removed in the next major release of the provider.Bug Fixes
Fix permanent permissions drift when
user_namecasing indatabricks_permissionsaccess_controlblocks differs from the API response (#5757).Allow setting
user_api_scopes = []ondatabricks_appto disable OBO (On-Behalf-Of) user authorization (#5834).The Apps API omits
user_api_scopesfrom its response when OBO is inactive, so a configured empty list previously failed withProvider produced inconsistent result after apply. The provider now preserves a configured empty list in state, mirroring the reconciliation used bydatabricks_app_space.Internal Changes
v1.119.0Compare Source
Documentation
Internal Changes
v1.118.0Compare Source
New Features and Improvements
databricks_ai_search_endpoint.databricks_ai_search_index.Bug Fixes
Fixed
databricks_instance_poolignoringenable_elastic_disk = falsedue toomitemptyJSON tag, which caused an infinite plan/replace cycle (#5802).Fix
databricks_entitlementsto honorprovider_config { workspace_id }when used with an account-level provider (#5680).Fix spurious
account_iddrift ondatabricks_mws_ncc_private_endpoint_rule(#5347). The backend echoesaccount_idon read; the schema previously marked it as a plainOptionalattribute, so once it landed in state (for example viaterraform import) the next plan reportedaccount_id = "..." -> nulland a subsequent apply failed withcannot update mws ncc private endpoint rule: Update mask must be specified.. Markingaccount_idasComputed(matching the siblingdatabricks_mws_network_connectivity_configresource) preserves the server-provided value across refreshes and eliminates the spurious in-place update.Fixed
databricks_mws_workspacesfailing to updateprivate_access_settings_idand other fields on GCP workspaces (#5430).Documentation
disabledfield totaskblock indatabricks_jobresource, allowing individual tasks to be disabled (#5767).Exporter
v1.117.0Compare Source
Bug Fixes
databricks_external_locationso that creating a resource withenable_file_events = falseis sent in the POST request. Previously the field was silently dropped (Go SDK marshals the bool withomitempty), so the server applied itstruedefault andeffective_enable_file_eventscame backtrue.v1.116.0Compare Source
New Features and Improvements
principal_idargument todatabricks_git_credentialresource, enabling management of Git credentials on behalf of service principals.Bug Fixes
databricks_metastoreso that updatingexternal_access_enabledfromtruetofalseis sent in the PATCH request. Previously the field was silently dropped from the request body, so the change never reached the API.databricks_vector_search_indexhardcoded 15-minute creation timeout: increased default to 75 minutes (consistent withdatabricks_vector_search_endpoint) and made it user-overridable via thetimeoutsblock.databricks_groupdata source (#5679).Documentation
databricks_mws_*resources on GCP require Google-issued OIDC tokens (not Databricks OAuth) (#5654).databricks_vector_search_indexdoc (#5605).principal_idargument fordatabricks_git_credentialresource.Exporter
alert_taskwhen exportingdatabricks_job(#5629).Internal Changes
Add
internal/retrierpackage for unified retry and backoff handling (#5746).Pass
excludedAttributes=entitlementson SCIM/Merequests (#5725).workspace_id(provider attribute andprovider_config.workspace_idblock) now accepts workspace connection IDs in addition to classic numeric workspace IDs. On unified Databricks hosts, the platform gateway disambiguates the value server-side via theX-Databricks-Workspace-Idrequest header. The previous positive-integer validator has been relaxed to require only a non-empty string.Numeric workspace IDs continue to behave exactly as before, including the account-API workspace-deployment lookup. Connection IDs skip that lookup and route directly via the configured host. When the provider is configured at the workspace level (host + token), connection IDs surface a clear error directing the user to reconfigure with account-level credentials, since a workspace-level provider can only operate on a single workspace.
v1.115.0Compare Source
Bug Fixes
Fix
databricks_library,databricks_share, anddatabricks_quality_monitorfailing to decode prior state withError decoding ... from prior state: missing expected {after upgrading from v1.113.0 to v1.114.0 (#5669). Reverts #5582.Fix
databricks_service_principaldata source failing on account-level provider withcannot populate provider_config for service principal: failed to resolve workspace_id(#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_service_principalsdata source failing on account-level provider with the samecannot populate provider_config for service principals: failed to resolve workspace_idregression (#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_mws_workspacesanddatabricks_mws_credentialsdata sources failing on account-level provider withcannot populate provider_config for mws workspaces: failed to resolve workspace_id(#5672). These account-only data sources are now exempted from the post-Read workspace-tracking hook, andprovider_config(which had no effect on them) is now deprecated and will be removed in a future major release.Fix
databricks_disable_legacy_features_settingfailing on account-level provider withcannot populate provider_config for disable legacy features setting: failed to resolve workspace_id: ... Unable to load OAuth Config. This account-only setting is now exempted from the post-Read workspace-tracking hook, and the auto-injectedprovider_configblock is deprecated. The fix is applied at the generic-setting builder level (makeSettingResourceinsettings/generic_setting.go), so any futureaccountSetting-based resource inherits the opt-out automatically.v1.114.2Compare Source
Release v1.114.2
New Features and Improvements
databricks_postgres_branchanddatabricks_postgres_endpointresources viareplace_existing = trueargument.Internal Changes
effective_file_event_queueas computed with diff suppression indatabricks_external_locationto prevent Terraform drift when the Unity Catalog backend returns the server-populated field.v1.114.1Compare Source
Release v1.114.1
Bug Fixes
Rolls back to v1.113.0 as the stable release.
v1.114.0Compare Source
Bug Fixes
Fix
databricks_library,databricks_share, anddatabricks_quality_monitorfailing to decode prior state withError decoding ... from prior state: missing expected {after upgrading from v1.113.0 to v1.114.0 (#5669). Reverts #5582.Fix
databricks_service_principaldata source failing on account-level provider withcannot populate provider_config for service principal: failed to resolve workspace_id(#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_service_principalsdata source failing on account-level provider with the samecannot populate provider_config for service principals: failed to resolve workspace_idregression (#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_mws_workspacesanddatabricks_mws_credentialsdata sources failing on account-level provider withcannot populate provider_config for mws workspaces: failed to resolve workspace_id(#5672). These account-only data sources are now exempted from the post-Read workspace-tracking hook, andprovider_config(which had no effect on them) is now deprecated and will be removed in a future major release.Fix
databricks_disable_legacy_features_settingfailing on account-level provider withcannot populate provider_config for disable legacy features setting: failed to resolve workspace_id: ... Unable to load OAuth Config. This account-only setting is now exempted from the post-Read workspace-tracking hook, and the auto-injectedprovider_configblock is deprecated. The fix is applied at the generic-setting builder level (makeSettingResourceinsettings/generic_setting.go), so any futureaccountSetting-based resource inherits the opt-out automatically.v1.113.0Compare Source
Bug Fixes
Fix
databricks_library,databricks_share, anddatabricks_quality_monitorfailing to decode prior state withError decoding ... from prior state: missing expected {after upgrading from v1.113.0 to v1.114.0 (#5669). Reverts #5582.Fix
databricks_service_principaldata source failing on account-level provider withcannot populate provider_config for service principal: failed to resolve workspace_id(#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_service_principalsdata source failing on account-level provider with the samecannot populate provider_config for service principals: failed to resolve workspace_idregression (#5664). The data source now supports theapifield and skips workspace-tracking when used at account level.Fix
databricks_mws_workspacesanddatabricks_mws_credentialsdata sources failing on account-level provider withcannot populate provider_config for mws workspaces: failed to resolve workspace_id(#5672). These account-only data sources are now exempted from the post-Read workspace-tracking hook, andprovider_config(which had no effect on them) is now deprecated and will be removed in a future major release.Fix
databricks_disable_legacy_features_settingfailing on account-level provider withcannot populate provider_config for disable legacy features setting: failed to resolve workspace_id: ... Unable to load OAuth Config. This account-only setting is now exempted from the post-Read workspace-tracking hook, and the auto-injected `provider_coConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.