2026-04-13 Custom DC stable release

[gmechali]

Highlights

• [Vis Tools] Delete old, old Map Tool by @juliawu in [Vis Tools] Delete old, old Map Tool #6165, [Vis Tools] Delete old, old Timeline Tool #6168 and [Vis Tools] Remove /tools/visualization #6170
• Update webdriver recordings by @nick-nlb in Update webdriver recordings #6169
• [v0/v1 migration] Replace /v1/variable/search by @nick-nlb in [v0/v1 migration] Replace /v1/variable/search #6140
• [Ranking Page][Ranking Tile] Add pagination to the ranking tile by @juliawu in [Ranking Page][Ranking Tile] Add pagination to the ranking tile #6147
• Upgrade google-adk from 1.18.0 to 1.28.1. by @nick-nlb in Upgrade google-adk from 1.18.0 to 1.28.1. #6172
• Bump setuptools from 66.1.1 to 78.1.1 in /server by https://github.com/dependabot[bot] in Bump setuptools from 66.1.1 to 78.1.1 in /server #6173

Resources - REMOVE BEFORE MERGING

• Diff links to help with writing highlights:
  • Mixer: datacommonsorg/mixer@f8a47a4...00b8206
  • Import: datacommonsorg/import@1e14cdc...fced75e
• Website changes are listed on this page.
• If you're unsure what affects custom DC, please message the team.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request prepares the Custom Data Commons for a stable release by integrating V2 API features, enhancing UI components with pagination, and performing necessary dependency updates. It also streamlines the codebase by removing deprecated visualization tools and updating feature flag configurations to enable new functionality in production and staging environments.

Highlights

• Feature Flag Updates: Enabled 'enable_gemini_3_flash' and 'use_v2_api' across multiple environments to support new NL detection and V2 REST API features.
• Ranking Tile Pagination: Added pagination support to the ranking tile component, allowing users to load more entries dynamically.
• V2 API Integration: Introduced V2 Stat Var search logic and fallback mechanisms for custom Data Commons, including new API endpoints and ancestor resolution.
• Dependency Upgrades: Upgraded several core dependencies including google-adk, fastapi, pydantic, and google-genai to their latest stable versions.
• Code Cleanup: Removed legacy visualization tool components and associated webdriver tests as part of the stable release cleanup.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the Data Commons tools by introducing V2 stat var search logic, turning down the old visualization tool in favor of standardized versions, and adding pagination support to ranking tiles. Backend updates include dependency upgrades and a new V2-based implementation for retrieving variable ancestors. Feedback highlights high-severity issues, including an undefined logger variable in the Python code and missing dependencies in a React useEffect hook that could prevent data from refreshing. Additionally, the new table footer implementation in the ranking units requires structural corrections to avoid breaking the layout.

[gemini-code-assist]

The variable logger is not defined in this scope. Based on the imports at the top of the file (from server.lib import log), you should use log.error instead to log the detected cycle.

Suggested change

	logger.error(f"Cycle detected in StatVar hierarchy at {selected_parent}")
	log.error(f"Cycle detected in StatVar hierarchy at {selected_parent}")

[gemini-code-assist]

The useEffect hook is missing parentPlace and enclosedPlaceType in its dependency array. These variables are used inside the effect to determine if a new data fetch is required (via currentFetchProps). Without them in the dependency array, the tile will not refresh when the user selects a different place or place type.

    parentPlace,
    enclosedPlaceType,
    props.facetSelector,
  ]);

[gemini-code-assist]

The footer row structure is incorrect. footerColSpan is calculated as the total number of columns in the table. By placing the footer content in one td and then adding another td with colSpan={footerColSpan}, the row ends up having 1 + footerColSpan columns, which exceeds the table's column count and will break the layout. It should be a single td spanning all columns.

Suggested change

	<td>{props.tableFooter}</td>
	<td colSpan={footerColSpan}></td>
	<td colSpan={footerColSpan}>{props.tableFooter}</td>

[gemini-code-assist]

The footer row structure is incorrect here as well. It should use a single td with colSpan={footerColSpan} to correctly span the entire table width.

Suggested change

	<td>{props.tableFooter}</td>
	<td colSpan={footerColSpan}></td>
	<td colSpan={footerColSpan}>{props.tableFooter}</td>