ci: Improve the Release Process Allowing to have Release Candidates #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also add rc/* branch to allow to have prereleases before actually releasing. Add cargo verify-project to ensure the project is in a good state. Signed-off-by: Eden Reich <eden.reich@gmail.com>
Signed-off-by: Eden Reich <eden.reich@gmail.com>
…on and error handling Signed-off-by: Eden Reich <eden.reich@gmail.com>
There was a problem hiding this comment.
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (3)
.github/workflows/release.yml:36
- Verify that the email address 'eden.reich@gmail.com' is the intended email for the GitHub Actions Bot.
git config --global user.email 'eden.reich@gmail.com'
.releaserc.yaml:14
- [nitpick] The type 'impr' might be a typo for 'improvement'. Please ensure it is consistently used across the codebase.
- { type: "impr", release: "patch" }
.releaserc.yaml:31
- [nitpick] The section for 'refactor' is labeled as '♻️ Improvements'. This might be confusing as 'refactor' typically means code changes that don't affect functionality. Consider renaming it to avoid confusion.
- { type: "refactor", section: "♻️ Improvements" }
edenreich
deleted the
ci/improve-the-release-process-allowing-to-have-rcs
branch
github-actions bot
pushed a commit
that referenced
this pull request
Feb 8, 2025
## [0.7.1-rc.1](0.7.0...0.7.1-rc.1) (2025-02-08) ### ♻️ Improvements * Remove tool_calls from Message struct and update related tests ([265bdec](265bdec)) ### 👷 CI * Improve the Release Process Allowing to have Release Candidates ([#3](#3)) ([b97e5da](b97e5da)) ### 📚 Documentation * Remove unnecessary code block from README.md ([dcb7c26](dcb7c26))
|
🎉 This PR is included in version 0.7.1-rc.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
edenreich
added a commit
that referenced
this pull request
Feb 10, 2025
* chore(release): 🔖 0.7.1-rc.1 [skip ci] ## [0.7.1-rc.1](0.7.0...0.7.1-rc.1) (2025-02-08) ### ♻️ Improvements * Remove tool_calls from Message struct and update related tests ([265bdec](265bdec)) ### 👷 CI * Improve the Release Process Allowing to have Release Candidates ([#3](#3)) ([b97e5da](b97e5da)) ### 📚 Documentation * Remove unnecessary code block from README.md ([dcb7c26](dcb7c26)) * fix: Enhance Tool and ToolFunction structures with description and parameters updates, use JSON raw value for now Signed-off-by: Eden Reich <eden.reich@gmail.com> * chore(release): 🔖 0.7.1-rc.2 [skip ci] ## [0.7.1-rc.2](0.7.1-rc.1...0.7.1-rc.2) (2025-02-09) ### 🐛 Bug Fixes * Enhance Tool and ToolFunction structures with description and parameters updates, use JSON raw value for now ([cdf6eca](cdf6eca)) * refactor: Remove ToolParameterType and ToolParameter structs to simplify code Will be using regular JSON for this part. Signed-off-by: Eden Reich <eden.reich@gmail.com> * refactor: Rename parameters to arguments in ToolFunctionResponse and update ToolCallResponse structure Signed-off-by: Eden Reich <eden.reich@gmail.com> * chore(release): 🔖 0.7.1-rc.3 [skip ci] ## [0.7.1-rc.3](0.7.1-rc.2...0.7.1-rc.3) (2025-02-09) ### ♻️ Improvements * Remove ToolParameterType and ToolParameter structs to simplify code ([0e4d1b4](0e4d1b4)) * Rename parameters to arguments in ToolFunctionResponse and update ToolCallResponse structure ([3f36c5f](3f36c5f)) * feat: Add optional tool_call_id to Message struct and update serialization tests Signed-off-by: Eden Reich <eden.reich@gmail.com> * chore(release): 🔖 0.8.0-rc.1 [skip ci] ## [0.8.0-rc.1](0.7.1-rc.3...0.8.0-rc.1) (2025-02-09) ### ✨ Features * Add optional tool_call_id to Message struct and update serialization tests ([d51e911](d51e911)) * test: Add assertion for tool_calls length in response test Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Improve the docs for Tool-Use, update it Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Enhance InferenceGatewayAPI docblocks with additional error handling and return details Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Remove redundant whitespace in InferenceGatewayAPI documentation Signed-off-by: Eden Reich <eden.reich@gmail.com> * refactor: Initialize the client with tools optionally This way I don't need to reference None in cases where tools is not needed. It simplifies the usage of generate_content function. Signed-off-by: Eden Reich <eden.reich@gmail.com> * refactor: Implement Default trait for Message and MessageRole structs This makes the code looks more readable, devs should not be concerns with tool_call_id by setting it to None if they not necessarily using tools, it's only valid for MessageRole of type Tool. Signed-off-by: Eden Reich <eden.reich@gmail.com> * refactor: Use in the tests two different conventions to see what's possible with_tools could be defined on initialization for all subsequent generate_content requests or for a particular request. Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Update the example in the README.md Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Resort functions examples, healthcheck is less important so put it at the bottom Signed-off-by: Eden Reich <eden.reich@gmail.com> * docs: Improve the example by mentioning the workflow of messages exchange Signed-off-by: Eden Reich <eden.reich@gmail.com> * chore(release): 🔖 0.8.0-rc.2 [skip ci] ## [0.8.0-rc.2](0.8.0-rc.1...0.8.0-rc.2) (2025-02-10) ### ♻️ Improvements * Implement Default trait for Message and MessageRole structs ([cb43ca8](cb43ca8)) * Initialize the client with tools optionally ([9c56170](9c56170)) * Use in the tests two different conventions to see what's possible ([eef16e8](eef16e8)) ### 📚 Documentation * Enhance InferenceGatewayAPI docblocks with additional error handling and return details ([b666c33](b666c33)) * Improve the docs for Tool-Use, update it ([9e5f5da](9e5f5da)) * Improve the example by mentioning the workflow of messages exchange ([ef474b4](ef474b4)) * Remove redundant whitespace in InferenceGatewayAPI documentation ([422e857](422e857)) * Resort functions examples, healthcheck is less important so put it at the bottom ([e6eb55d](e6eb55d)) * Update the example in the README.md ([0fda0dc](0fda0dc)) ### ✅ Miscellaneous * Add assertion for tool_calls length in response test ([4edcd4b](4edcd4b)) --------- Signed-off-by: Eden Reich <eden.reich@gmail.com>
github-actions bot
pushed a commit
that referenced
this pull request
Feb 10, 2025
## [0.8.0](0.7.0...0.8.0) (2025-02-10) ### ✨ Features * Tool-Use functions call ([#4](#4)) ([efd8e6b](efd8e6b)), closes [#3](#3) ### ♻️ Improvements * Remove tool_calls from Message struct and update related tests ([265bdec](265bdec)) ### 👷 CI * Improve the Release Process Allowing to have Release Candidates ([#3](#3)) ([b97e5da](b97e5da)) ### 📚 Documentation * Remove unnecessary code block from README.md ([dcb7c26](dcb7c26))
|
🎉 This PR is included in version 0.8.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Improve the Release Process Allowing to have Release Candidates.
Also the releases will be attached to the PR's which is nice to track the progress.