Skip to content

Bump dependencies with known vulnerabilities - #7327

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 or by GitHub repository security advisories to their fixed versions.

Each advisory links to its advisory page.

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 15:40

@pietern pietern left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bumps otel to v1.47.0 for GHSA-q7gw-24fr-5p69, the first bump from the new repository-advisory scan (#7320).

@pietern
pietern enabled auto-merge November 3, 2026 15:41
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: d196f46

Run: 41666875019

Env 🔄​flaky ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 271 15 10:59
🔄​ aws-windows-latest-4core-16gb 1 272 13 9:20
🔄​ azure linux-2core-8gb 1 269 15 13:03
✅​ azure-windows-latest-4core-16gb 272 13 8:18
🔄​ gcp linux-2core-8gb 1 270 15 12:06
🔄​ gcp-windows-latest-4core-16gb 1 272 13 8:15
Test Name aws-windows-latest-4core-16gb azure linux-2core-8gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
🔄​ TestSyncFullFileSync ✅​p ✅​p ✅​p 🔄​f
🔄​ TestSyncIncrementalFileSync 🔄​f ✅​p ✅​p ✅​p
🔄​ TestSyncIncrementalSyncFileToPythonNotebook ✅​p 🔄​f ✅​p ✅​p
🔄​ TestSyncNestedFolderSync ✅​p ✅​p 🔄​f ✅​p
Top 15 slowest tests (at least 2 minutes):
duration env testname
7:35 gcp-windows-latest-4core-16gb TestAccept
7:18 azure-windows-latest-4core-16gb TestAccept
7:10 aws-windows-latest-4core-16gb TestAccept
4:16 gcp linux-2core-8gb TestAccept
4:06 azure linux-2core-8gb TestAccept
4:06 aws linux-2core-8gb TestAccept
3:45 gcp linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
3:29 aws-windows-latest-4core-16gb TestLock
3:19 gcp-windows-latest-4core-16gb TestFilerRecursiveDelete/workspace_files
2:53 azure-windows-latest-4core-16gb TestImportDirDoesNotOverwrite
2:43 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir
2:08 azure-windows-latest-4core-16gb TestSyncFullFileSync
2:07 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:07 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsDelete
2:00 gcp-windows-latest-4core-16gb TestImportDirWithOverwriteFlag

@pietern
pietern added this pull request to the merge queue Nov 3, 2026
Merged via the queue into main with commit ff13d1d Nov 3, 2026
36 checks passed
@pietern
pietern deleted the auto/bump-vuln-deps branch November 3, 2026 16:28
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.

3 participants