Bump ipywidgets from 7.7.2 to 8.1.7#1
Merged
Conversation
Bumps [ipywidgets](https://github.com/jupyter-widgets/ipywidgets) from 7.7.2 to 8.1.7. - [Release notes](https://github.com/jupyter-widgets/ipywidgets/releases) - [Commits](jupyter-widgets/ipywidgets@7.7.2...8.1.7) --- updated-dependencies: - dependency-name: ipywidgets dependency-version: 8.1.7 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
4 tasks
1 task
tkislan
added a commit
that referenced
this pull request
Jun 29, 2026
The "required + valid-JSON" check for service-account credentials was duplicated across the Cloud SQL, Spanner and BigQuery forms. Extract it into a pure, dependency-free `validateServiceAccountJson()` helper and reuse it in all three forms (both the change and submit handlers). BigQuery keeps its detailed "Invalid JSON: <detail>" message via the helper's `detail` field, so behavior is unchanged everywhere. The helper has no React/localization dependencies, so it is unit-tested in isolation. Addresses finding #1 from the TypeScript code review. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
tkislan
added a commit
that referenced
this pull request
Jun 30, 2026
* feat(integrations): add Cloud SQL integration support
Bump @deepnote/database-integrations from 1.4.3 to 1.5.0, which adds the
`cloud-sql` database integration type, and wire it through the extension
following the convention used by the other integrations:
- Add Cloud SQL to the type-label and icon maps (incl. new cloud-sql.svg)
- Add CloudSqlForm (name + service account JSON, matching the
`{ service_account }` metadata schema) and route to it from
ConfigurationForm
- Surface Cloud SQL in the integration type selector and item label
- Add the corresponding localization keys, strings and webview wiring
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
* fix(integrations): validate service-account input in Cloud SQL and Spanner forms
Addresses CodeRabbit review on the Cloud SQL form, and applies the same fixes
to the Spanner form which shared both issues (BigQueryForm already handled them
correctly):
- Reject whitespace-only service-account JSON on submit. The `required`
attribute on a <textarea> does not trim, so " " passed the browser check
and reached onSave with an effectively blank credential. Submit now treats a
trim-empty value as missing and surfaces a dedicated "required" error.
- Clear the validation error in the reset effect, so switching integrations or
reloading a valid config no longer leaves a stale error that blocks Save.
Adds the corresponding `...ServiceAccountRequired` localization strings + wiring.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
* docs(integrations): document Cloud SQL integration
Add Cloud SQL to specs/INTEGRATIONS_CREDENTIALS.md (supported-types list,
config interface example and the Google Cloud forms section) and bump the
integration count 18 -> 19. Addresses the CodeRabbit "Updates Docs" check.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
* refactor(integrations): extract shared service-account JSON validation
The "required + valid-JSON" check for service-account credentials was
duplicated across the Cloud SQL, Spanner and BigQuery forms. Extract it into a
pure, dependency-free `validateServiceAccountJson()` helper and reuse it in all
three forms (both the change and submit handlers). BigQuery keeps its detailed
"Invalid JSON: <detail>" message via the helper's `detail` field, so behavior is
unchanged everywhere.
The helper has no React/localization dependencies, so it is unit-tested in
isolation. Addresses finding #1 from the TypeScript code review.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
* fix(integrations): require service-account credential to be a JSON object
`validateServiceAccountJson` only checked that `JSON.parse` succeeded, so
`JSON.parse`-valid but non-object payloads (`123`, `"foo"`, `null`, `[]`) passed
validation and could be saved as service accounts, failing only later. Reject
anything that is not a non-null, non-array object. Covers the Cloud SQL, Spanner
and BigQuery forms via the shared helper. Addresses CodeRabbit review feedback.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VuoSZXF8YHsN81Lra45JW
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Bumps ipywidgets from 7.7.2 to 8.1.7.
Release notes
Sourced from ipywidgets's releases.
... (truncated)
Commits
3171b1cUpdate Output Widget.ipynb (#3881)cd81783update image processing example notebok imports and function call (#3896)cecd2b0specify Jupyterlab (version 3.x or above) (#3880)0aa1efbAllowinteractto use basic type hint annotations (#3908)2e15cfcUpdate Widget List.ipynb06ed868Merge pull request #3793 from ferdnyc/mappings-work-again31259caMerge pull request #3801 from warrickball/patch-2dd250bfHandle Notebook 7 in dev install scripta1282ecFix link to "Output widget examples"b6b3051Revert "Add note on removal of mapping types in documentation"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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)