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 #154

Closed
wants to merge 1 commit into from
Closed

chore: release v0.6.2 #154

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-09

Fixed

  • use OUT_DIR instead of CARGO_MANIFEST_DIR

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 of the workspace package and all dependencies to 0.6.2, ensuring consistency across the application.
  • Bug Fixes

    • Enhanced build process for augurs-prophet by utilizing OUT_DIR, improving compatibility with build systems.
  • Documentation

    • Updated changelog for augurs-prophet to reflect recent changes and improvements.

Copy link
Contributor

coderabbitai bot commented Nov 9, 2024

Walkthrough

The pull request involves updates to the Cargo.toml file, primarily focusing on incrementing the version of the workspace package and all listed dependencies from 0.6.1 to 0.6.2. Additionally, the changelog for the augurs-prophet project has been updated to reflect the new version, detailing changes in the build process. These modifications ensure that all components within the workspace are aligned in their versioning, contributing to consistent dependency management.

Changes

File Change Summary
Cargo.toml Updated workspace package version from 0.6.1 to 0.6.2. All dependencies updated to 0.6.2.
crates/augurs-prophet/CHANGELOG.md Added entry for version 0.6.2, detailing build process changes; previous versions documented.

Possibly related PRs

🐰 In the meadow, we hop with glee,
Versions rising, as bright as can be!
Dependencies dance, all in a line,
With 0.6.2, everything's fine!
Changelog updated, our tales we share,
In the world of code, we show we care! 🌼✨


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: 1

🧹 Outside diff range and nitpick comments (1)
crates/augurs-prophet/CHANGELOG.md (1)

12-14: Consider adding more context to the changelog entry.

While the fix is correctly categorized, consider expanding the description to include:

  • Why the change from CARGO_MANIFEST_DIR to OUT_DIR was necessary
  • What issues this change resolves
  • The impact of this change on the build process

This additional context would be valuable for future maintainers.

 ### Fixed
 
-use OUT_DIR instead of CARGO_MANIFEST_DIR
+use OUT_DIR instead of CARGO_MANIFEST_DIR for build artifacts to ensure correct
+placement of compiled files and compatibility with cargo's build system
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2bf1f2b and 1df53eb.

📒 Files selected for processing (2)
  • Cargo.toml (2 hunks)
  • crates/augurs-prophet/CHANGELOG.md (1 hunks)
🔇 Additional comments (2)
Cargo.toml (1)

21-21: LGTM: Workspace version update is correct.

Version bump from 0.6.1 to 0.6.2 aligns with the release objectives.

crates/augurs-prophet/CHANGELOG.md (1)

10-11: LGTM: Version entry follows the standard format.

The version number, comparison link, and date are correctly formatted according to Keep a Changelog conventions.

Comment on lines +32 to +41
augurs-changepoint = { version = "0.6.2", path = "crates/augurs-changepoint" }
augurs-clustering = { version = "0.6.2", path = "crates/augurs-clustering" }
augurs-core = { version = "0.6.2", path = "crates/augurs-core" }
augurs-dtw = { version = "0.6.2", path = "crates/augurs-dtw" }
augurs-ets = { version = "0.6.2", path = "crates/augurs-ets" }
augurs-forecaster = { version = "0.6.2", path = "crates/augurs-forecaster" }
augurs-mstl = { version = "0.6.2", path = "crates/augurs-mstl" }
augurs-outlier = { version = "0.6.2", path = "crates/augurs-outlier" }
augurs-prophet = { version = "0.6.2", path = "crates/augurs-prophet" }
augurs-seasons = { version = "0.6.2", path = "crates/augurs-seasons" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Note: augurs-testing dependency is missing version specification

The verification revealed that while most augurs-* dependencies are correctly updated to version 0.6.2, the augurs-testing crate is specified with only a path and no version:

augurs-testing = { path = "crates/augurs-testing" }

For consistency with other workspace dependencies, it should also include the version "0.6.2".

🔗 Analysis chain

LGTM: Dependency versions are consistently updated.

All augurs-* dependencies have been correctly updated to version 0.6.2, maintaining consistency across the workspace.

Let's verify that no dependencies were missed in this update:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any augurs-* dependencies that might still reference version 0.6.1

# Test: Search for any remaining 0.6.1 versions in Cargo.toml files
# Expect: No matches as all should be updated to 0.6.2
echo "Checking for any remaining 0.6.1 versions..."
rg '"0.6.1"' -g 'Cargo.toml'

# Test: Verify all augurs-* crates in workspace are included in dependencies
# Expect: All workspace crates should have corresponding dependency entries
echo "Checking for any missing augurs-* crates..."
fd '^augurs-.*' crates -t d -x echo "Checking if {} is in dependencies..." \; -x rg "{}" Cargo.toml

Length of output: 1693

@sd2k sd2k closed this Nov 9, 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