fix: remove 'Alpha' prefix from package name#707
Conversation
Summary of ChangesHello @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 Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
Remove the 'Alpha' prefix from the package name.