-
Notifications
You must be signed in to change notification settings - Fork 1
WEEKLY-CHANGELOG for v0.0.2-weekly #203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,31 +1,8 @@ | ||
| ## Version v0.0.1-weekly - June 30, 2025 | ||
| # Update v0.0.2-weekly - June 30, 2025 | ||
|
|
||
| ### Bug Fixes | ||
| - Improved the README file for better formatting and clarity. | ||
| - Updated route models to enhance performance. For more details, see [Issue #198](https://github.com/getjavelin/issues/198). | ||
| - Upgraded Python version and OpenTelemetry dependencies for better stability. See [Issue #191](https://github.com/getjavelin/issues/191). | ||
| - Corrected the region configuration from west to east-1 for the Bedrock client. Refer to [Issue #192](https://github.com/getjavelin/issues/192). | ||
| - Modified SDK calls to prevent failures in end-to-end testing. Check [Issue #179](https://github.com/getjavelin/issues/179). | ||
| - Fixed the removal of duplicate event registrations. More info at [Issue #178](https://github.com/getjavelin/issues/178). | ||
| - Updated installation instructions and metadata in the pyproject.toml file. | ||
| - Changed the base URL to accept environment variables and corrected AWS Bedrock documentation links. | ||
| - Supported Python libraries with updated formatting and linting tools. | ||
| - Implemented security enhancements by using API keys in requests. | ||
| - Merged several improvements for streamlined code examples. | ||
| We're excited to share the latest updates in our v0.0.2-weekly release. For a detailed look at the changes between this and our previous release, please visit our [GitHub page](https://github.com/getjavelin/compare/v0.0.1-weekly...v0.0.2-weekly). | ||
|
|
||
| ### New Features | ||
| - Added and updated scripts for universal endpoints. Details in [Issue #195](https://github.com/getjavelin/issues/195). | ||
| - Introduced image generation capabilities with unified endpoints, see [Issue #193](https://github.com/getjavelin/issues/193). | ||
| - Implemented standalone Guardrail methods with rigorous model validation. More at [Issue #189](https://github.com/getjavelin/issues/189). | ||
| - Updated Bedrock and OpenAI clients for enhanced tracing and request handling. | ||
| - Added sample scripts and examples for LLM provider functionality, including OpenAI and Gemini integrations. | ||
| - Expanded CLI capabilities for Javelin SDK, improving user accessibility. | ||
| - Introduced OpenTelemetry tracing with comprehensive support for various AI clients. | ||
|
|
||
| ### Pull Request Merges | ||
| A series of pull requests were successfully merged to improve the platform’s code quality, security, and functionality. Key pull requests include enhancements to the continuous integration process, updates to existing features, and bug resolutions. For specific PRs, see the links in the changelog above. | ||
|
|
||
| For ongoing updates beyond this release, please refer to [Unreleased Changes](https://github.com/getjavelin/compare/v0.0.1-weekly...HEAD). | ||
| Stay tuned for more updates in the upcoming releases! | ||
|
|
||
| --- | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,11 @@ | ||
| # Update v0.0.2-weekly - June 30, 2025 | ||
|
|
||
| We're excited to share the latest updates in our v0.0.2-weekly release. For a detailed look at the changes between this and our previous release, please visit our [GitHub page](https://github.com/getjavelin/compare/v0.0.1-weekly...v0.0.2-weekly). | ||
|
Comment on lines
+1
to
+3
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This new changelog entry for I recommend adopting the detailed format used for |
||
|
|
||
| Stay tuned for more updates in the upcoming releases! | ||
|
|
||
| --- | ||
|
|
||
| ## Version v0.0.1-weekly - June 30, 2025 | ||
|
|
||
| ### Bug Fixes | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new changelog format for v0.0.2-weekly is much less informative than the previous format. A changelog should ideally provide a summary of user-facing changes, such as bug fixes and new features, rather than just linking to a GitHub compare page. This makes it easier for users to understand what's new in the release.
Additionally, the heading has changed from
## Version v...(H2) to# Update v...(H1). It's common practice to use a consistent heading level and structure for versions.Could we restore a more detailed format, similar to the previous version's entry? For example:
Since this PR is auto-generated, the release pipeline script might need to be updated to produce more descriptive changelogs.