-
Notifications
You must be signed in to change notification settings - Fork 1
WEEKLY-CHANGELOG for v0.0.5-weekly #210
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,10 +1,9 @@ | ||
| ## Update: Version v0.0.3-weekly (July 7, 2025) | ||
| ## Update: Version v0.0.5-weekly - Released on July 21, 2025 | ||
|
|
||
| Explore what's new in the latest release of our software. | ||
| ### What's New? | ||
| - We've merged a significant update to our CI/CD pipeline. For more details, please refer to [Pull Request #209](https://github.com/getjavelin/javelin-python/issues/209). | ||
|
|
||
| For more details on the changes made in this update, you can view the specific comparisons: | ||
| - To see what's different from the previous weekly version, check out the [comparison with v0.0.2-weekly](https://github.com/getjavelin/javelin-python/compare/v0.0.2-weekly...v0.0.3-weekly). | ||
| - For ongoing developments beyond this release, take a look at the [comparison with our latest work](https://github.com/getjavelin/javelin-python/compare/v0.0.3-weekly...HEAD). | ||
| Stay updated by checking the latest developments on our [GitHub repository](https://github.com/getjavelin/javelin-python). | ||
|
|
||
| --- | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,3 +1,12 @@ | ||||||
| ## Update: Version v0.0.5-weekly - Released on July 21, 2025 | ||||||
|
|
||||||
| ### What's New? | ||||||
| - We've merged a significant update to our CI/CD pipeline. For more details, please refer to [Pull Request #209](https://github.com/getjavelin/javelin-python/issues/209). | ||||||
|
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. For clarity and correctness, the link for a pull request should use the
Suggested change
|
||||||
|
|
||||||
| Stay updated by checking the latest developments on our [GitHub repository](https://github.com/getjavelin/javelin-python). | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| ## Update: Version v0.0.3-weekly (July 7, 2025) | ||||||
|
|
||||||
| Explore what's new in the latest release of our software. | ||||||
|
|
||||||
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.
For clarity and correctness, the link for a pull request should use the
/pull/path instead of/issues/. While GitHub automatically redirects from/issues/to/pull/for pull requests, using the canonical URL is better practice, especially since the text explicitly mentions 'Pull Request'.