chore: release v0.6.3

[sd2k]

🤖 New release

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

Changelog

augurs

0.6.0 - 2024-11-08

Added

• add wasmtime based optimizer for dependency-free Rust impl

augurs-changepoint

0.6.3 - 2024-11-18

Other

• update Cargo.toml dependencies

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.6.3 - 2024-11-18

Other

• update Cargo.toml dependencies

augurs-mstl

0.6.3 - 2024-11-18

Other

• update Cargo.toml dependencies

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.3 - 2024-11-18

Other

• Fix broken intra-doc link in wasmstan module

augurs-seasons

0.6.3 - 2024-11-18

Other

• update Cargo.toml dependencies

---

This PR was generated with release-plz.

Summary by CodeRabbit

• New Features

  • Updated the workspace package and all related dependencies to version 0.6.3 for improved functionality and performance.

• Bug Fixes

  • Resolved a broken intra-doc link in the wasmstan module within the augurs-prophet project.

• Documentation

  • Updated changelogs for multiple components to reflect the new version and dependency updates, adhering to Semantic Versioning guidelines.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve updating the version of the workspace package and its dependencies in the Cargo.toml file from 0.6.2 to 0.6.3. This version increment applies to multiple dependencies, ensuring uniformity across the workspace. Additionally, corresponding changelog entries have been added to document this version update for several crates, maintaining adherence to the "Keep a Changelog" format and Semantic Versioning guidelines.

Changes

File Path	Change Summary
Cargo.toml	Updated workspace package version from 0.6.2 to 0.6.3 and all dependencies to 0.6.3.
crates/augurs-changepoint/CHANGELOG.md	Added entry for version 0.6.3 noting dependency updates in Cargo.toml.
crates/augurs-ets/CHANGELOG.md	Added entry for version 0.6.3 noting dependency updates in Cargo.toml.
crates/augurs-mstl/CHANGELOG.md	Added entry for version 0.6.3 noting dependency updates in Cargo.toml.
crates/augurs-seasons/CHANGELOG.md	Added entry for version 0.6.3 noting dependency updates in Cargo.toml.
crates/augurs-prophet/CHANGELOG.md	Added entry for version 0.6.3 noting a fix for a broken intra-doc link.

Possibly related PRs

• chore: release #96: Involves a version bump for the Cargo.toml file and its dependencies, similar to the main PR.
• chore: bump to v0.3.1 #103: Updates the Cargo.toml file, incrementing the version from 0.3.0 to 0.3.1, aligning with the main PR's objective.
• chore: release v0.4.1 #132: Version updates from 0.4.0 to 0.4.1 for the workspace and dependencies relate to the versioning strategy discussed in the main PR.
• chore: release v0.4.2 #133: Updates the workspace version from 0.4.1 to 0.4.2, reflecting a consistent versioning approach.
• chore: release v0.5.1 #139: Updates the workspace version from 0.5.0 to 0.5.1, aligning with the main PR's objective.
• chore: release v0.5.3 #144: Involves updating the workspace version from 0.5.2 to 0.5.3, related to the main PR's focus.
• chore: release v0.6.0 #148: Updates the workspace version from 0.5.4 to 0.6.0, reflecting the same versioning strategy.
• chore: release v0.6.1 #151: Version increment from 0.6.0 to 0.6.1 is consistent with the main PR's focus on updating versions.
• chore: release v0.6.2 #156: Updates the workspace version from 0.6.1 to 0.6.2, aligning with the main PR's objective of maintaining consistent versioning.

🐰 "In the meadow where bunnies play,
Versions rise on this fine day.
From 0.6.2 to 0.6.3,
All dependencies in harmony!
Changelogs dance, updates sing,
A joyful hop in the spring!" 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b096edb and 0247422.

📒 Files selected for processing (6)

• Cargo.toml (2 hunks)
• crates/augurs-changepoint/CHANGELOG.md (1 hunks)
• crates/augurs-ets/CHANGELOG.md (1 hunks)
• crates/augurs-mstl/CHANGELOG.md (1 hunks)
• crates/augurs-prophet/CHANGELOG.md (1 hunks)
• crates/augurs-seasons/CHANGELOG.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (6)

• Cargo.toml
• crates/augurs-changepoint/CHANGELOG.md
• crates/augurs-ets/CHANGELOG.md
• crates/augurs-mstl/CHANGELOG.md
• crates/augurs-prophet/CHANGELOG.md
• crates/augurs-seasons/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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.