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

Closed
wants to merge 1 commit into from
Closed

chore: release v0.5.3 #143

wants to merge 1 commit into from

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

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 and dependencies to version 0.5.3 for improved consistency.
  • Chores

    • Updated changelog to reflect the new version 0.5.3 and document changes, including code cleanup.

Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces updates to the Cargo.toml file, incrementing the workspace package version from 0.5.2 to 0.5.3 and aligning all dependencies to the same version. The dependencies affected include augurs-changepoint, augurs-clustering, augurs-core, augurs-dtw, augurs-ets, augurs-forecaster, augurs-mstl, augurs-outlier, augurs-prophet, and augurs-seasons. Additionally, the changelog for augurs-prophet has been updated to reflect the new version and document the removal of commented code.

Changes

File Change Summary
Cargo.toml - Version updated from 0.5.2 to 0.5.3 for workspace package and all dependencies.
crates/augurs-prophet/CHANGELOG.md - Updated to include version 0.5.3 entry, noting removal of commented code.

Possibly related PRs

  • chore: release #96: Involves a version update in Cargo.toml to increment the version of the workspace package and its dependencies.
  • chore: bump to v0.3.1 #103: Updates the version of the workspace package and its dependencies, similar to the main PR's changes.
  • chore: release v0.4.1 #132: Reflects another version increment for the workspace package and its dependencies, maintaining consistency with the main PR.
  • chore: release v0.4.2 #133: Updates the version of the workspace package and its dependencies, indicating a consistent versioning strategy.
  • chore: release v0.4.3 #134: Continues the pattern of version updates for the workspace package and its dependencies, aligning with the changes in the main PR.
  • chore: release v0.5.0 #137: Marks a version bump for all packages to v0.5.0, consistent with the versioning changes in the main PR.
  • chore: release v0.5.1 #139: Updates the version of the workspace package and its dependencies from 0.5.0 to 0.5.1, reflecting the same versioning approach as in the main PR.

🐰 In the garden where we play,
Versions bloom in bright array.
From 0.5.2 to 0.5.3,
All dependencies in harmony!
Changelog sings of code refined,
A tidy space for joy combined! 🌼


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-25-37Z branch from b38a8aa to 1453603 Compare October 25, 2024 12:35
@sd2k sd2k closed this Oct 25, 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