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.9.1 #249

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: release v0.9.1 #249

wants to merge 1 commit into from

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Jan 30, 2025

🤖 New release

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


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features

    • Introduced JavaScript support in the Prophet module to enhance forecasting interactions.
    • Enabled customizable parameter settings in the Outlier module for improved tuning.
  • Chores

    • Upgraded all modules to version 0.9.1 for uniformity and enhanced reliability.
    • Updated underlying dependencies to maintain optimal system performance.

Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

Walkthrough

This pull request involves a version update for the Augurs project, incrementing the main package and its dependencies from version 0.9.0 to 0.9.1. The changes primarily affect the CHANGELOG.md and Cargo.toml files, with specific notes about updating the ureq dependency from version 2.10.1 to 3.0.0 and the wasmtime dependency from version 28 to 29. A new section has been added for the augurs-outlier module, documenting its version update to 0.9.1 and the addition of setters for parameters.

Changes

File Change Summary
CHANGELOG.md - Added new section for augurs-prophet v0.9.1
- Updated ureq dependency from 2.10.1 to 3.0.0
- Updated wasmtime dependency from 28 to 29
- Added new section for augurs-outlier v0.9.1 with setters for parameters
Cargo.toml - Updated workspace package version to 0.9.1
- Updated versions of multiple dependencies (augurs-*) to 0.9.1

Possibly related PRs

  • chore: release v0.4.3 #134: The changes in the main PR are related to the updates in the Cargo.toml file for versioning and dependencies, which also appear in the retrieved PR's updates to the same file.
  • chore: release v0.6.3 #166: The changes in the main PR are related to the updates in the Cargo.toml file for dependency versioning, which also appear in the retrieved PR's updates to the same file for version increments across multiple modules.
  • chore: release v0.8.1 #224: The changes in the main PR are related to the updates in the Cargo.toml file for the augurs-prophet and augurs-outlier modules, which also appear in the retrieved PR's updates for the same modules.

Poem

🐰 Hop, hop, version bump we go!
Augurs dancing, versions in tow
From zero-nine-zero to zero-nine-one
Dependencies aligned, our work is done
Ureq and Wasmtime, all in sight! 🚀

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.

🪧 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 generate docstrings to generate docstrings for this 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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e493801 and bffccfd.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms (23)
  • GitHub Check: windows (windows-latest, x86)
  • GitHub Check: macos (macos-14, aarch64)
  • GitHub Check: windows (windows-latest, x64)
  • GitHub Check: macos (macos-13, x86_64)
  • GitHub Check: linux (ubuntu-22.04, ppc64le)
  • GitHub Check: musllinux (ubuntu-22.04, armv7)
  • GitHub Check: linux (ubuntu-22.04, s390x)
  • GitHub Check: musllinux (ubuntu-22.04, aarch64)
  • GitHub Check: linux (ubuntu-22.04, armv7)
  • GitHub Check: musllinux (ubuntu-22.04, x86)
  • GitHub Check: Clippy
  • GitHub Check: linux (ubuntu-22.04, aarch64)
  • GitHub Check: Test Book
  • GitHub Check: Tests
  • GitHub Check: musllinux (ubuntu-22.04, x86_64)
  • GitHub Check: linux (ubuntu-22.04, x86)
  • GitHub Check: Rustfmt
  • GitHub Check: linux (ubuntu-22.04, x86_64)
  • GitHub Check: Check
  • GitHub Check: Run benchmarks
  • GitHub Check: JS tests
  • GitHub Check: Python tests
  • GitHub Check: Prophet WASMStan component
🔇 Additional comments (1)
Cargo.toml (1)

21-21: LGTM! Version bump aligns with release objectives.

The patch version increment (0.9.0 -> 0.9.1) follows semantic versioning conventions.

Comment on lines +32 to +41
augurs-changepoint = { version = "0.9.1", path = "crates/augurs-changepoint" }
augurs-clustering = { version = "0.9.1", path = "crates/augurs-clustering" }
augurs-core = { version = "0.9.1", path = "crates/augurs-core" }
augurs-dtw = { version = "0.9.1", path = "crates/augurs-dtw" }
augurs-ets = { version = "0.9.1", path = "crates/augurs-ets" }
augurs-forecaster = { version = "0.9.1", path = "crates/augurs-forecaster" }
augurs-mstl = { version = "0.9.1", path = "crates/augurs-mstl" }
augurs-outlier = { version = "0.9.1", path = "crates/augurs-outlier" }
augurs-prophet = { version = "0.9.1", path = "crates/augurs-prophet" }
augurs-seasons = { version = "0.9.1", 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

Missing changelog entries for version 0.9.1

While all packages are being updated to version 0.9.1 in Cargo.toml, only augurs-prophet has a corresponding changelog entry. Please add changelog entries for version 0.9.1 in:

  • Root CHANGELOG.md for all updated packages
  • Package-specific CHANGELOG.md files in:
    • crates/augurs-changepoint/
    • crates/augurs-clustering/
    • crates/augurs-core/
    • crates/augurs-dtw/
    • crates/augurs-ets/
    • crates/augurs-forecaster/
    • crates/augurs-mstl/
    • crates/augurs-outlier/
    • crates/augurs-seasons/
🔗 Analysis chain

LGTM! Dependency versions are consistently updated.

All internal workspace dependencies are correctly updated to match the new version 0.9.1, maintaining consistency across the project.

Let's verify that each updated package has corresponding changelog entries:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for changelog entries for each updated package

# List of packages to check
packages=(
  "augurs-changepoint"
  "augurs-clustering"
  "augurs-core"
  "augurs-dtw"
  "augurs-ets"
  "augurs-forecaster"
  "augurs-mstl"
  "augurs-outlier"
  "augurs-prophet"
  "augurs-seasons"
)

echo "Checking for changelog entries in version 0.9.1..."

for pkg in "${packages[@]}"; do
  echo "Checking $pkg..."
  
  # Check main CHANGELOG.md
  if rg -q "## \[0\.9\.1\]" "CHANGELOG.md"; then
    rg -A 10 "## \[0\.9\.1\]" "CHANGELOG.md"
  fi
  
  # Check package-specific CHANGELOG.md
  if [ -f "crates/$pkg/CHANGELOG.md" ]; then
    if rg -q "## \[0\.9\.1\]" "crates/$pkg/CHANGELOG.md"; then
      rg -A 10 "## \[0\.9\.1\]" "crates/$pkg/CHANGELOG.md"
    fi
  fi
done

Length of output: 2663


Script:

#!/bin/bash
# Check existence and content of changelog files

# First check root CHANGELOG.md
echo "=== Root CHANGELOG.md ==="
if [ -f "CHANGELOG.md" ]; then
    echo "Found root CHANGELOG.md"
    head -n 20 "CHANGELOG.md"
else
    echo "No root CHANGELOG.md found"
fi

echo -e "\n=== Package CHANGELOGs ==="
for pkg in augurs-{changepoint,clustering,core,dtw,ets,forecaster,mstl,outlier,prophet,seasons}; do
    echo -e "\n--- $pkg ---"
    if [ -f "crates/$pkg/CHANGELOG.md" ]; then
        echo "Found CHANGELOG.md"
        head -n 20 "crates/$pkg/CHANGELOG.md"
    else
        echo "No CHANGELOG.md found"
    fi
done

Length of output: 10414

@github-actions github-actions bot force-pushed the release-plz-2025-01-30T17-54-45Z branch from bffccfd to 5992142 Compare January 30, 2025 18:02
@github-actions github-actions bot force-pushed the release-plz-2025-01-30T17-54-45Z branch 2 times, most recently from f3b19cc to 80d9ea5 Compare March 4, 2025 09:16
@github-actions github-actions bot force-pushed the release-plz-2025-01-30T17-54-45Z branch from 80d9ea5 to ecf6c82 Compare March 6, 2025 12:40
@github-actions github-actions bot force-pushed the release-plz-2025-01-30T17-54-45Z branch from ecf6c82 to 47fb6a1 Compare March 12, 2025 17:40
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

🧹 Nitpick comments (1)
CHANGELOG.md (1)

10-16: Review the 'augurs-prophet' Changelog Section

The new changelog entry for augurs-prophet is clear and follows the expected format—with a version bump to 0.9.1, a proper comparison link, and a correctly formatted release date. The sub-section "Other" neatly groups the additional changes like the JS bindings and dependency updates.

Nitpick: The static analysis tool suggests using "Others" instead of "Other" for the sub-heading. Please verify if the project’s changelog style requires the plural form. If so, consider applying the following small diff:

-### Other
+### Others
🧰 Tools
🪛 LanguageTool

[misspelling] ~12-~12: It seems that the plural noun “others” fits better in this context.
Context: ...ugurs-prophet-v0.9.1) - 2025-03-12 ### Other - Add JS bindings for Prophet make_futu...

(OTHER_OTHERS)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ecf6c82 and 47fb6a1.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • Cargo.toml
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[misspelling] ~12-~12: It seems that the plural noun “others” fits better in this context.
Context: ...ugurs-prophet-v0.9.1) - 2025-03-12 ### Other - Add JS bindings for Prophet make_futu...

(OTHER_OTHERS)

🔇 Additional comments (1)
CHANGELOG.md (1)

17-21: Approve the 'augurs-outlier' Changelog Entry

The entry for augurs-outlier is well-structured. It correctly displays the version update and clearly identifies the addition of setters for parameters under the "Added" sub-heading. The compare link and date are consistent with the rest of the changelog.

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