-
Notifications
You must be signed in to change notification settings - Fork 8
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
chore: release v0.6.2 #155
Conversation
WalkthroughThe changes in this pull request primarily involve updates to the Changes
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
crates/augurs-prophet/CHANGELOG.md (2)
14-14
: Consider adding more context about the OUT_DIR fix.While the fix is documented, it would be helpful to briefly explain why this change was necessary and its impact. For example, mention if it resolves any specific build issues or improves compatibility.
-use OUT_DIR instead of CARGO_MANIFEST_DIR +use OUT_DIR instead of CARGO_MANIFEST_DIR for improved build reproducibility
18-18
: Consider adding a link to the WASM example.The addition of the Prophet WASM example is well documented with the PR reference. Consider adding a direct link to the example in the repository to help users find it quickly.
-Add Prophet WASM example ([#152](https://github.com/grafana/augurs/pull/152)) +Add Prophet WASM example ([#152](https://github.com/grafana/augurs/pull/152)) - [View Example](https://github.com/grafana/augurs/tree/main/examples/prophet-wasm)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
Cargo.toml
(2 hunks)crates/augurs-prophet/CHANGELOG.md
(1 hunks)
🔇 Additional comments (3)
Cargo.toml (3)
21-21
: LGTM: Version bump to 0.6.2
Version update aligns with the release objectives.
21-21
: Verify versioning strategy for breaking changes
The PR objectives mention breaking changes in augurs-dtw
(splitting of JavaScript package into separate crates). According to semver, breaking changes typically warrant a major version bump (1.0.0) rather than a minor version bump (0.6.2).
Let's check the changelog for versioning rationale:
#!/bin/bash
# Description: Look for changelog entries about breaking changes
# Test: Search for changelog entries mentioning breaking changes
# Expect: Documentation of breaking changes and versioning decision
rg -i "breaking|change" CHANGELOG.md
Also applies to: 35-35
32-41
: LGTM: Consistent dependency version updates
All augurs-* dependencies are correctly updated to match the workspace version 0.6.2.
Let's verify that all augurs-* dependencies are consistently versioned:
✅ Verification successful
Dependencies are correctly versioned and aligned with workspace version
The verification confirms that:
- All augurs-* dependencies in Cargo.toml are consistently set to version "0.6.2"
- The workspace.package.version is also set to "0.6.2"
- There are no augurs-* dependencies with different versions
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify all augurs-* dependencies are at version 0.6.2
# Test: Search for any augurs-* dependencies not at version 0.6.2
# Expect: No output (all versions should be 0.6.2)
rg 'augurs-[a-z]+.*version = "(?!0\.6\.2)' Cargo.toml
Length of output: 170
Script:
#!/bin/bash
# Let's try a different approach to verify the versions
# First, let's check if there are any augurs-* dependencies with different versions
rg 'augurs-.*version.*=.*"[^"]*"' Cargo.toml
# Also check workspace members to ensure consistency
rg '\[workspace\]' -A 20 Cargo.toml
# And check individual crate versions in their respective Cargo.toml files
fd Cargo.toml -t f -p 'crates/augurs-*/'
Length of output: 1358
7e05ebd
to
933b04e
Compare
933b04e
to
b6665da
Compare
🤖 New release
augurs
: 0.6.1 -> 0.6.2augurs-changepoint
: 0.6.1 -> 0.6.2augurs-core
: 0.6.1 -> 0.6.2augurs-clustering
: 0.6.1 -> 0.6.2augurs-dtw
: 0.6.1 -> 0.6.2augurs-ets
: 0.6.1 -> 0.6.2augurs-mstl
: 0.6.1 -> 0.6.2augurs-forecaster
: 0.6.1 -> 0.6.2augurs-outlier
: 0.6.1 -> 0.6.2augurs-prophet
: 0.6.1 -> 0.6.2 (✓ API compatible changes)augurs-seasons
: 0.6.1 -> 0.6.2Changelog
augurs
augurs-changepoint
augurs-core
augurs-clustering
augurs-dtw
augurs-ets
augurs-mstl
augurs-forecaster
augurs-outlier
augurs-prophet
augurs-seasons
This PR was generated with release-plz.
Summary by CodeRabbit
New Features
0.6.2
, enhancing overall functionality.Bug Fixes
OUT_DIR
for better compatibility.Documentation
0.6.2
.