-
Notifications
You must be signed in to change notification settings - Fork 55
LCORE-544: Bump-up to version 0.2.0 #435
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,4 +9,4 @@ | |
| # [tool.pdm.version] | ||
| # source = "file" | ||
| # path = "src/version.py" | ||
| __version__ = "0.1.3" | ||
| __version__ = "0.2.0" | ||
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.
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.
💡 Verification agent
🧩 Analysis chain
Pin to 0.2.0 is fine; consider linking the badge to “latest” to avoid future drift, and verify the 0.2.0 tag exists.
Keeping the badge image as “latest tag” while the link points to a fixed tag means every release requires touching this line. Linking to “releases/latest” avoids that churn. Also, please ensure the 0.2.0 release/tag is already published before merging.
Apply if you prefer a stable link to the latest release page:
Run to verify the tag exists:
🏁 Script executed:
Length of output: 348
Release tag “0.2.0” not found – please publish before merging
Our verification against the GitHub Releases API returned a 404 for tag 0.2.0, which means the badge link will be broken until the tag is actually created. Please ensure the
0.2.0release (and corresponding tag) is published before merging this change.• Location: README.md, line 9
• Current badge/link:
Optional: to avoid manual updates on future releases, you can point the link at the “latest” endpoint instead:
This ensures the badge always links to the newest release, preventing future churn.
🤖 Prompt for AI Agents