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.5.3 #144

Merged
merged 1 commit into from
Oct 25, 2024
Merged

chore: release v0.5.3 #144

merged 1 commit into from
Oct 25, 2024

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Oct 25, 2024

🤖 New release

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

augurs

0.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)

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.5.2 - 2024-10-25

Other

  • add benchmark for Prophet (#140)

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.5.3 - 2024-10-25

Fixed

  • correctly pass cap_scaled to piecewise_logistic (#142)

Other

  • Remove commented code

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 workspace package version to 0.5.3, ensuring all components are aligned.
    • Introduced a fix for the cap_scaled parameter in the augurs-prophet package.
  • Bug Fixes

    • Resolved an issue with the piecewise_logistic function in the augurs-prophet package.
  • Documentation

    • Updated changelog to reflect changes and improvements in version 0.5.3.

Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

Walkthrough

The pull request introduces version updates in the Cargo.toml file for a workspace, incrementing the package version from 0.5.2 to 0.5.3. All dependencies under the workspace have also been updated to the new version, ensuring consistency across components. Additionally, the changelog for the augurs-prophet package has been updated to reflect the new version and document recent changes, including a fix for the cap_scaled parameter and the removal of commented code.

Changes

File Change Summary
Cargo.toml Updated package version from 0.5.2 to 0.5.3. Updated all workspace dependencies from 0.5.2 to 0.5.3.
crates/augurs-prophet/CHANGELOG.md Added entry for version 0.5.3, detailing a fix for cap_scaled and removal of commented code.

Possibly related PRs

🐇 In the garden where bunnies play,
Versions hop and dance all day.
From 0.5.2 to 0.5.3,
Dependencies align, oh joy to see!
Changelog shines, with fixes bright,
A leap of progress, pure delight! 🌼


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.

@github-actions github-actions bot force-pushed the release-plz-2024-10-25T12-36-20Z branch from 4e706a0 to 899b693 Compare October 25, 2024 12:36
@sd2k sd2k enabled auto-merge (squash) October 25, 2024 12:37
@sd2k sd2k closed this Oct 25, 2024
auto-merge was automatically disabled October 25, 2024 12:37

Pull request was closed

@sd2k sd2k reopened this Oct 25, 2024
@sd2k sd2k enabled auto-merge (squash) October 25, 2024 12:37
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 (1)
crates/augurs-prophet/CHANGELOG.md (1)

18-18: Consider adding PR reference for the commented code removal.

For consistency with other entries and better traceability, consider adding the PR reference where the commented code was removed.

-Remove commented code
+Remove commented code ([#144](https://github.com/grafana/augurs/pull/144))
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f93d596 and 899b693.

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

15-15: LGTM: Version bump to 0.5.3

Version update is consistent with the release objectives and follows semantic versioning.


26-35: LGTM: Consistent dependency version updates

All workspace dependencies are correctly updated to version 0.5.3, maintaining consistency across the project. The path dependencies are properly configured.

Let's verify version consistency across all crates:

✅ Verification successful

✓ Version consistency verified in workspace dependencies

The workspace dependencies in Cargo.toml are correctly configured:

  • All augurs-* crates are set to version 0.5.3, matching the workspace version
  • Path dependencies are correctly specified for all workspace members
  • augurs-testing is intentionally excluded from versioning as a development dependency
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency in all crate Cargo.toml files
# Expected: All versioned crates should be at 0.5.3

# Check versions in all Cargo.toml files under crates/
fd Cargo.toml crates/ --exec rg -A 1 'version = "\d+\.\d+\.\d+"' {}

Length of output: 1055


Script:

#!/bin/bash
# Let's try a different approach to check versions in Cargo.toml files
# First, check the workspace version
echo "=== Workspace Version ==="
rg '^version = ' Cargo.toml

echo -e "\n=== Individual Crate Versions ==="
# Check version field in each crate's Cargo.toml
fd Cargo.toml crates/ -x sh -c 'echo "=== {} ==="; rg "^version = " {}'

echo -e "\n=== Dependency Versions ==="
# Check augurs dependencies in each crate's Cargo.toml
fd Cargo.toml crates/ -x sh -c 'echo "=== {} ==="; rg "^augurs-.*version = " {}'

Length of output: 1521


Script:

#!/bin/bash
# Let's check the workspace members and their version fields in a different way
echo "=== Workspace Members ==="
rg '^\[workspace\.members\]' -A 20 Cargo.toml

echo -e "\n=== Checking Individual Crate Versions ==="
# Use cat instead of rg to see the full content of each Cargo.toml
for crate in $(fd Cargo.toml crates/); do
    echo "=== $crate ==="
    cat "$crate" | rg -A1 '^\[package\]|^version ='
done

Length of output: 3488


Script:

#!/bin/bash
# Let's try one final approach to check version information
echo "=== Workspace Version ==="
rg '^version = ' Cargo.toml

echo -e "\n=== Workspace Dependencies Section ==="
rg '^\[workspace\.dependencies\]' -A 50 Cargo.toml

echo -e "\n=== Package Versions ==="
# Use grep to look specifically for version field after [package] section
for crate in $(fd Cargo.toml crates/); do
    echo "=== $crate ==="
    awk '/\[package\]/{p=1;next} /^\[/{p=0} p&&/^version =/' "$crate"
done

Length of output: 5237

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

10-19: LGTM! Changelog entry follows the Keep a Changelog format.

The new version entry is well-structured with proper sections and includes the correct version comparison link.

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