Fix link check test

[rahulpinto19]

Description

Should include a concise description of the changes (bug or feature), it's
impact, along with a summary of the solution

PR Checklist

Thank you for opening a Pull Request! Before submitting your PR, there are a
few things you can do to make sure it goes smoothly:

• Make sure you reviewed
  CONTRIBUTING.md
• Make sure to open an issue as a
  bug/issue
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)
• Make sure to add ! if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[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 introduces significant enhancements to the tool configuration and skill generation processes, alongside expanding Serverless Spark capabilities with new session management tools. It also includes various CI/CD improvements, dependency updates, and testing infrastructure refinements to improve stability and maintainability.

Highlights

• CI/CD Configuration Updates: Modified integration.cloudbuild.yaml to gracefully handle BigQuery and Spanner integration test failures and removed unused environment variables for Healthcare and CockroachDB. The test_with_coverage.sh script was updated to support extra test arguments.
• Enhanced Skill Generation: Refactored skill generation logic to improve flexibility in loading tool configurations (e.g., from files, folders, or prebuilt configs) and added support for custom license headers in generated Node.js scripts. The SKILL.md output now uses a Markdown table for parameters instead of JSON schema.
• New Serverless Spark Session Tools: Introduced serverlesssparkgetsession and serverlesssparklistsessions tools, along with their respective documentation and prebuilt configurations, expanding Serverless Spark management capabilities.
• Tool Annotation Support: Added ToolAnnotations to all MongoDB tools (aggregate, deleteMany, deleteOne, find, findOne, insertMany, insertOne, updateMany, updateOne) to provide semantic metadata like readOnlyHint and destructiveHint.
• Oracle SQL ReadOnly Flag: Implemented a readOnly flag for the oracle-execute-sql tool to control SQL execution behavior, allowing explicit declaration of read-only operations.
• Version Bump and Dependency Updates: Updated the project version from 0.27.0 to 0.28.0 across various configuration and documentation files. Go module dependencies, including OpenTelemetry and filippo.io/edwards25519, were updated, and testcontainers-go/modules/cockroachdb was added.
• Improved Testing Infrastructure: Migrated CockroachDB integration tests to use testcontainers-go for better isolation, adjusted Healthcare DICOM store tests to use dynamically uploaded data, and added a cleanup mechanism for old Postgres test schemas.

Changelog

• Bug Fixes
  • ci: Add path for forked PR unit test runs (#2540) (04dd2a7)
  • Deflake alloydb omni (#2431)
  • docs/adk: Resolve dependency duplication (#2418) (4d44abb)
  • docs/langchain: Fix core at 0.3.0 and align compatible dependencies (#2426) (36edfd3)
  • Enforce required validation for explicit null parameter values (#2519) (d5e9512)
  • oracle: Enable DML operations and resolve incorrect array type error (#2323) (72146a4)
  • server/mcp: Guard nil dereference in sseManager.get (#2557) (e534196), closes #2548
  • tests/postgres: Implement uuid-based isolation and reliable resource cleanup (#2377) (8a96fb1)
  • tests/postgres: Restore list_schemas test and implement dynamic owner (#2521) (7041e79)
  • tests: Resolve LlamaIndex dependency conflict in JS quickstart (#2597) (ac11f5a)

Ignored Files

• Ignored by pattern: .github/workflows/** (7)
  • .github/workflows/deploy_dev_docs.yaml
  • .github/workflows/deploy_previous_version_docs.yaml
  • .github/workflows/deploy_versioned_docs.yaml
  • .github/workflows/docs_preview_deploy.yaml
  • .github/workflows/link_checker.yaml
  • .github/workflows/lint.yaml
  • .github/workflows/tests.yaml
• Ignored by pattern: go.sum (1)
  • go.sum

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a wide range of changes, including new features, significant refactoring, and various fixes. Key additions include the skills-generate command for creating agent skills, support for tool annotations to provide semantic metadata, and new Serverless Spark tools for session management. The PR also refactors the configuration file parsing into a dedicated ToolsFileParser and improves test reliability by using testcontainers for CockroachDB and making other tests self-contained.

My review focuses on the new skills-generate feature, where I've identified a potential regression in how the toolbox binary is located. I've provided a suggestion to address this. The other changes, such as using errors.Join for resource cleanup and updating telemetry attributes, are positive improvements that align with best practices.

_{Note: Security Review did not run due to the size of the PR.}

[gemini-code-assist]

The updated getToolboxPath function in the Node.js script template has a potential regression. It no longer attempts to find the toolbox binary in a local path (../../../toolbox) as a fallback if it's not found in the system's PATH (unless the GEMINI_CLI environment variable is set). The previous implementation handled this fallback gracefully.

This change could cause the generated skill scripts to fail in environments where toolbox is not in the PATH but is available locally relative to the project, which was a supported scenario.

I suggest restoring the fallback behavior to ensure the script is more robust.

function getToolboxPath() {
    if (process.env.GEMINI_CLI === '1') {
        const localPath = path.resolve(__dirname, '../../../toolbox');
        if (fs.existsSync(localPath)) {
            return localPath;
        }
    }
    try {
        const checkCommand = process.platform === 'win32' ? 'where toolbox' : 'which toolbox';
        const globalPath = execSync(checkCommand, { stdio: 'pipe', encoding: 'utf-8' }).trim();
        if (globalPath) {
            return globalPath.split('\n')[0].trim();
        }
    } catch (e) {
        // global path not found, fall back to local path
    }
    const localPath = path.resolve(__dirname, '../../../toolbox');
    if (fs.existsSync(localPath)) {
        return localPath;
    }
    throw new Error("Toolbox binary not found in PATH or locally");
}