Skip to content

ready for 3.0.0 release#1956

Merged
haifeng-jin merged 1 commit intomasterfrom
release
Nov 12, 2025
Merged

ready for 3.0.0 release#1956
haifeng-jin merged 1 commit intomasterfrom
release

Conversation

@haifeng-jin
Copy link
Collaborator

No description provided.

@haifeng-jin haifeng-jin merged commit 205af5b into master Nov 12, 2025
7 checks passed
@haifeng-jin haifeng-jin deleted the release branch November 12, 2025 02:47
@gemini-code-assist
Copy link

Summary of Changes

Hello @haifeng-jin, I'm Gemini Code Assist1! 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 marks the official release of version 3.0.0 by updating the project's version number. It significantly enhances the documentation by introducing new tutorials for structured data classification and regression, and by standardizing the Keras backend configuration across all Jupyter notebooks. Additionally, existing tutorials have been refined for clarity and conciseness, improving the overall user experience and ease of understanding.

Highlights

  • Version Update: The project version has been officially updated from '3.0.0dev' to '3.0.0', signaling a stable release.
  • Keras Backend Configuration: All Jupyter notebooks now explicitly set the Keras backend to 'torch' using !export KERAS_BACKEND="torch", ensuring consistent execution environments for tutorials.
  • New Structured Data Tutorials: Two new comprehensive tutorial notebooks, structured_data_classification.ipynb and structured_data_regression.ipynb, have been added to guide users through structured data tasks.
  • Documentation Refinements: Existing tutorial notebooks have been streamlined by removing redundant 'Data Format' sections and simplifying data loading/preprocessing examples, while also updating references to include new structured data components.
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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request prepares for the 3.0.0 release by updating the version number and making significant updates to the documentation notebooks. This includes adding new tutorials for structured data classification and regression, and cleaning up existing ones. The changes are generally good, but I've found a recurring issue across all updated and new notebooks where an environment variable is set incorrectly. I've provided suggestions to fix this in each affected file.

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

},
"outputs": [],
"source": [
"!export KERAS_BACKEND=\"torch\"\n",

Choose a reason for hiding this comment

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

high

The !export command in a Jupyter cell only sets the environment variable for the subshell of that specific command and does not persist for the notebook's kernel. To set the environment variable for the entire notebook session, you should use the %env magic command.

Suggested change
"!export KERAS_BACKEND=\"torch\"\n",
"%env KERAS_BACKEND=torch\n",

@codecov
Copy link

codecov bot commented Nov 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0b2c363) to head (97f5ea6).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #1956   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           49        49           
  Lines         2317      2317           
=========================================
  Hits          2317      2317           
Flag Coverage Δ
unittests 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant