Skip to content

fix: remove 'Alpha' prefix from package name#707

Merged
olavloite merged 1 commit intomainfrom
correct-ado-net-package-name
Feb 25, 2026
Merged

fix: remove 'Alpha' prefix from package name#707
olavloite merged 1 commit intomainfrom
correct-ado-net-package-name

Conversation

@olavloite
Copy link
Collaborator

Remove the 'Alpha' prefix from the package name.

@olavloite olavloite requested review from a team as code owners February 25, 2026 08:48
@olavloite olavloite requested a review from bhatt4982 February 25, 2026 08:48
@gemini-code-assist
Copy link

Summary of Changes

Hello @olavloite, 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 streamlines the package identification by eliminating the 'Alpha' prefix from the project's PackageId. This change ensures a cleaner and more consistent naming convention for the Spanner ADO.NET data provider, aligning it with a more mature release cycle.

Highlights

  • Package Naming: The 'Alpha' prefix has been removed from the PackageId in the spanner-ado-net.csproj file, standardizing the package name.
Changelog
  • spanner-ado-net/spanner-ado-net/spanner-ado-net.csproj
    • Removed 'Alpha' prefix from the PackageId element.
Activity
  • No human activity has been recorded on this pull request since its creation.
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
Collaborator

@bhatt4982 bhatt4982 left a comment

Choose a reason for hiding this comment

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

LGTM...

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 removes the 'Alpha' prefix from the PackageId in spanner-ado-net.csproj. This change is appropriate as it aligns the package identifier with .NET packaging conventions, where pre-release status is typically denoted in the version number, not the package ID. The package's alpha status is still correctly communicated through its version (1.0.0-alpha...) and description. This change also makes the package ID consistent with the component name defined in release-please-config.json, which is used for release tagging. While changing a package ID is a breaking change for existing users, it is acceptable for a package in its alpha stage. No issues were found in the code change.

@olavloite olavloite merged commit 0f02447 into main Feb 25, 2026
19 checks passed
@olavloite olavloite deleted the correct-ado-net-package-name branch February 25, 2026 09:20
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.

3 participants