Skip to content

Bump dependencies with known vulnerabilities - #7305

Merged
pietern merged 2 commits into
mainfrom
auto/bump-vuln-deps
Nov 3, 2026
Merged

pietern merged 2 commits into
mainfrom
auto/bump-vuln-deps

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Bump dependencies flagged by govulncheck -scan module to their fixed versions.

Each CVE links to its Go advisory page.

  • golang.org/x/crypto → v0.58.1-0.20261009181718-2f1f834330b2 (fixes GO-2026-5932)

Vulnerabilities in the Go standard library are left to the Bump Go toolchain workflow.

If a bump promotes a new direct dependency, double-check its license annotation in go.mod and NOTICE.

@github-actions github-actions Bot added the Dependencies Pull requests that update a dependency file label Nov 3, 2026
@github-actions
github-actions Bot requested a review from a team as a code owner November 3, 2026 05:35
@pietern
pietern enabled auto-merge November 3, 2026 07:23
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 7ac13c7

Run: 41596120955

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 281 15 5:29
✅​ aws-windows-latest-4core-16gb 283 13 7:16
✅​ azure linux-2core-8gb 280 15 5:31
✅​ azure-windows-latest-4core-16gb 282 13 7:08
✅​ gcp linux-2core-8gb 281 15 5:28
✅​ gcp-windows-latest-4core-16gb 283 13 7:02
Top 6 slowest tests (at least 2 minutes):
duration env testname
7:10 aws-windows-latest-4core-16gb TestAccept
7:02 azure-windows-latest-4core-16gb TestAccept
6:56 gcp-windows-latest-4core-16gb TestAccept
4:18 aws linux-2core-8gb TestAccept
4:11 azure linux-2core-8gb TestAccept
4:06 gcp linux-2core-8gb TestAccept

@pietern
pietern added this pull request to the merge queue Nov 3, 2026
Merged via the queue into main with commit 1622bba Nov 3, 2026
36 checks passed
@pietern
pietern deleted the auto/bump-vuln-deps branch November 3, 2026 08:06
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 1622bba

Run: 41600891416

Env ❌​FAIL 🔄​flaky ✅​pass 🙈​skip Time
❌​ aws linux-2core-8gb 2 2 1500 1227 138:36
❌​ aws-windows-latest-4core-16gb 2 1427 1252 150:30
✅​ azure linux-2core-8gb 1351 1279 117:45
🔄​ azure-windows-latest-4core-16gb 4 1272 1304 135:43
✅​ gcp linux-2core-8gb 1338 1284 132:12
✅​ gcp-windows-latest-4core-16gb 1263 1309 134:23
8 interesting tests: 6 flaky, 2 FAIL
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure-windows-latest-4core-16gb
❌​ TestAccept ❌​F ❌​F ✅​p
🔄​ TestAccept/bundle/invariant/delete_idempotent 🔄​f ✅​p ✅​p
🔄​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_table_update_trigger.yml.tmpl/READPLAN= 🔄​f ✅​p ✅​p
🔄​ TestAccept/bundle/invariant/no_drift ✅​p ✅​p 🔄​f
🔄​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN= ✅​p ✅​p 🔄​f
🔄​ TestAccept/bundle/resources/apps/lifecycle-started ✅​p ✅​p 🔄​f
🔄​ TestAccept/bundle/resources/apps/lifecycle-started/DMS= ✅​p ✅​p 🔄​f
❌​ TestAccept/bundle/resources/postgres_projects/factcheck/update_mask_spec ❌​F ❌​F 🙈​s
Top 50 slowest tests (at least 2 minutes):
duration env testname
11:07 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:32 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:00 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:44 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:36 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:34 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:29 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:27 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:26 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:19 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:17 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
8:08 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
7:51 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:36 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:28 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:20 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:18 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
7:11 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:06 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:05 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
6:59 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
6:53 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
6:31 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:29 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:25 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:22 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:21 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:12 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:12 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
5:58 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS=true
5:53 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:51 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
5:34 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:32 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:30 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:23 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=
5:03 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
5:02 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:51 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
4:51 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=true
4:48 gcp linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
4:44 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:38 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
4:37 gcp linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=
4:34 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:28 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:25 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
4:18 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
4:18 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true
4:09 azure linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true

deco-sdk-tagging Bot added a commit that referenced this pull request Nov 4, 2026
## Release v1.24.0

### Notable Changes

 * A variable used as the value of a secret is now sensitive: referencing it from any other field, such as a job parameter or a secret's `comment`, is an error because the value would be used in plain text. Mark other secret-holding variables with `sensitive: true` to get the same protection. ([#7288](#7288))

### CLI

 * Fix `databricks auth login` and `databricks configure` overwriting the parent profile's host and token when saving a profile with a dotted name such as `team.prod` next to an existing `[team]`. ([#7266](#7266))
 * `databricks auth login` and `databricks auth token` now reject the name of an existing profile after "Create a new profile" instead of logging in to that profile. ([#7196](#7196))
 * `databricks auth login` and `databricks auth token` now reject a host that is not a URL with a hostname, such as `/`, `?o=123` or `https://`, instead of falling back to `DATABRICKS_HOST` or failing later. An empty host after "Enter a host URL manually" in the login profile picker no longer starts discovery login. ([#7195](#7195))
 * Prompts that validate their input, such as the `databricks configure` host prompt, no longer open with a red cross before anything is typed. ([#7314](#7314))
 * `databricks ssh connect` now documents `--environment-version` for choosing the serverless environment version, starts a separate default-named server for each version, and rejects the flag together with `--cluster`. Default connection names also include the environment version in their hash, so the default name when `--environment-version` is not specified changes with this release. Configuration associated with the old connection name (secret scope, SSH keys and known hosts in your local `.databricks` folder) will no longer be used and can be safely removed. ([#7310](#7310))

### AI Runtime

 * Show workspace-supported accelerator types in `databricks air run -h config.compute.accelerator_type`. ([#7275](#7275))
 * `air list` now reports `No active runs found.` for an empty active-only result. ([#7276](#7276))
 * Stop printing a retry notice on every `air run --watch`; retries are still reported when they happen. ([#7270](#7270))

### Bundles

 * Fix `bundle plan` reporting an update to an app's `config.env` values on every run, which also redeployed the app on every `bundle deploy`. The Apps API returns environment variable names only, so `value` and `value_from` are no longer compared against the remote deployment. ([#7326](#7326))
 * Add the `data_quality_monitors` resource for data quality monitors on Unity Catalog schemas and tables (direct engine only). ([#7094](#7094))
 * `bundle deploy` now asks for confirmation before recreating or deleting a Feature View, and `bundle deploy` and `bundle destroy` warn that FeatureSpecs using a Feature View are not checked. ([#7164](#7164))
 * Accept grant `privileges` values that the SDK enum does not list yet: `bundle validate` no longer warns (or errors under `--strict`) on them, and the PyDABs `Privilege` enum accepts unknown strings instead of raising. The JSON schema and PyDABs still advertise the known values for completion. ([#7315](#7315))
 * Add the `materialization_sets` resource, which materializes Feature Store Feature Views to offline and online stores. ([#7164](#7164))
 * Detect notebooks with the same rule as the workspace: a `.py`, `.sql`, `.scala` or `.r` file is a notebook when its first line contains `Databricks notebook source`, for example after a byte order mark. Previously such a file was tracked as a plain file, so removing it locally left the remote notebook behind. ([#7290](#7290))
 * Add `sensitive: true` for bundle variables. A variable used as the value of a secret is sensitive by default. `bundle validate -o json` redacts only sensitive variables instead of every string variable, and a sensitive variable can only be referenced from a sensitive resource field (such as a secret's `value`) or from another sensitive variable. ([#7288](#7288))

### Dependency Updates

 * Bump dependencies with known vulnerabilities. ([#7305](#7305))
 * Bump dependencies with known vulnerabilities. ([#7327](#7327))
 * Update the Go SDK to [v0.191.1](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.191.1). ([#7277](#7277))
 * Update the Go SDK to [v0.193.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.193.0). ([#7303](#7303))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants