Skip to content
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

Closed
wants to merge 1 commit into from
Closed

chore: release v0.6.2 #155

wants to merge 1 commit into from

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Nov 9, 2024

🤖 New release

  • augurs: 0.6.1 -> 0.6.2
  • augurs-changepoint: 0.6.1 -> 0.6.2
  • augurs-core: 0.6.1 -> 0.6.2
  • augurs-clustering: 0.6.1 -> 0.6.2
  • augurs-dtw: 0.6.1 -> 0.6.2
  • augurs-ets: 0.6.1 -> 0.6.2
  • augurs-mstl: 0.6.1 -> 0.6.2
  • augurs-forecaster: 0.6.1 -> 0.6.2
  • augurs-outlier: 0.6.1 -> 0.6.2
  • augurs-prophet: 0.6.1 -> 0.6.2 (✓ API compatible changes)
  • augurs-seasons: 0.6.1 -> 0.6.2
Changelog

augurs

0.6.0 - 2024-11-08

Added

  • add wasmtime based optimizer for dependency-free Rust impl

augurs-changepoint

0.5.1 - 2024-10-24

Other

  • define lints in Cargo.toml instead of each crate's lib.rs (#138)

augurs-core

0.5.1 - 2024-10-24

Other

  • define lints in Cargo.toml instead of each crate's lib.rs (#138)

augurs-clustering

0.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)

augurs-dtw

0.6.0 - 2024-11-08

Added

  • [breaking] split JS package into separate crates (#149)

augurs-ets

0.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)

augurs-mstl

0.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)

augurs-forecaster

0.5.1 - 2024-10-24

Other

  • define lints in Cargo.toml instead of each crate's lib.rs (#138)

augurs-outlier

0.5.1 - 2024-10-24

Other

  • define lints in Cargo.toml instead of each crate's lib.rs (#138)

augurs-prophet

0.6.2 - 2024-11-10

Fixed

  • use OUT_DIR instead of CARGO_MANIFEST_DIR

Other

  • Add Prophet WASM example (#152)

augurs-seasons

0.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features

    • Updated version to 0.6.2, enhancing overall functionality.
    • Introduced a new example for Prophet in WebAssembly (WASM).
  • Bug Fixes

    • Improved build process by utilizing OUT_DIR for better compatibility.
  • Documentation

    • Changelog updated to reflect changes and enhancements in version 0.6.2.

Copy link
Contributor

coderabbitai bot commented Nov 9, 2024

Walkthrough

The changes in this pull request primarily involve updates to the Cargo.toml file, where the workspace package version has been incremented from 0.6.1 to 0.6.2. All related dependencies, specifically the augurs-* crates, have also been updated to the new version 0.6.2. Additionally, the changelog for the augurs-prophet crate has been modified to reflect the new version and document recent fixes and enhancements.

Changes

File Change Summary
Cargo.toml Updated workspace package version from 0.6.1 to 0.6.2. Updated dependencies from 0.6.1 to 0.6.2 for augurs-changepoint, augurs-clustering, augurs-core, augurs-dtw, augurs-ets, augurs-forecaster, augurs-mstl, augurs-outlier, augurs-prophet, and augurs-seasons.
crates/augurs-prophet/CHANGELOG.md Added entry for version 0.6.2 detailing changes made, including build process updates and new examples.

Possibly related PRs

🐇 "In the meadow, we hop with glee,
Versions updated, oh what a spree!
From 0.6.1 to 0.6.2,
All dependencies, fresh and new.
Changelog shines with tales to tell,
In our code, all is well!" 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 933b04e and b6665da.

📒 Files selected for processing (2)
  • Cargo.toml (2 hunks)
  • crates/augurs-prophet/CHANGELOG.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • Cargo.toml
  • crates/augurs-prophet/CHANGELOG.md

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

📥 Commits

Reviewing files that changed from the base of the PR and between 39e1cc0 and 7e05ebd.

📒 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

@sd2k sd2k closed this Nov 9, 2024
@sd2k sd2k reopened this Nov 9, 2024
@github-actions github-actions bot force-pushed the release-plz-2024-11-09T15-10-30Z branch from 7e05ebd to 933b04e Compare November 10, 2024 09:08
@github-actions github-actions bot force-pushed the release-plz-2024-11-09T15-10-30Z branch from 933b04e to b6665da Compare November 10, 2024 09:37
@sd2k sd2k closed this Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant