chore: safeguard all packages as pre-release#15
Conversation
Summary of ChangesHello, 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 introduces changes to safeguard all language packages by explicitly marking them as pre-release. This measure prevents accidental stable releases while the repository is still under active development, ensuring that consumers are aware of the experimental nature of the current builds. The changes involve adjusting version numbers in various project files and updating the automated release configuration. 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request correctly sets up pre-releases for all packages by updating version strings and configuring release-please. The changes are consistent across different languages. I've found one potential issue with the .release-please-manifest.json file that could cause problems with the release automation. My suggestion aims to align the manifest with the new pre-release versions you've set in the code.
aepfli
force-pushed
the
chore/pre-release-safeguard
branch
from
d7cdccc to
8108d18
Compare
- Rust: 0.1.0 → 0.1.0-alpha.0 (Cargo.toml + python/Cargo.toml) - Python: 0.1.0 → 0.1.0.dev0 (PEP 440) - JavaScript: 0.1.0 → 0.1.0-alpha.0 - .NET: added <Version>0.1.0-alpha.0</Version> - Java: already 0.1.0-SNAPSHOT (no change) - Go: version via git tags only (no change) Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…s pre-release - Set prerelease: true and prerelease-type: alpha on root Rust package - Add Java (maven), Python, Go, JavaScript (node), .NET (simple) packages - Each package includes full changelog-sections config - Updated .release-please-manifest.json with initial versions for all packages Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aepfli
force-pushed
the
chore/pre-release-safeguard
branch
from
8108d18 to
3fb2f0c
Compare
1 participant
Closes #14
Marks all language packages as pre-release to prevent accidental stable releases while the repository is still in active development.
Changes
Version strings
0.1.0→0.1.0-alpha.00.1.0→0.1.0.dev0(PEP 440)0.1.0→0.1.0-alpha.0<Version>0.1.0-alpha.0</Version>0.1.0-SNAPSHOT✅release-please
prerelease: trueon the root Rust packagerelease-please-config.json.release-please-manifest.jsonwith initial versions for all packages