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.8.0 #200

Closed
wants to merge 1 commit into from
Closed

chore: release v0.8.0 #200

wants to merge 1 commit into from

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Dec 16, 2024

πŸ€– New release

  • augurs: 0.7.0 -> 0.8.0 (βœ“ API compatible changes)
  • augurs-changepoint: 0.7.0 -> 0.8.0
  • augurs-core: 0.7.0 -> 0.8.0 (⚠️ API breaking changes)
  • augurs-clustering: 0.7.0 -> 0.8.0
  • augurs-dtw: 0.7.0 -> 0.8.0
  • augurs-ets: 0.7.0 -> 0.8.0
  • augurs-mstl: 0.7.0 -> 0.8.0
  • augurs-forecaster: 0.7.0 -> 0.8.0 (⚠️ API breaking changes)
  • augurs-outlier: 0.7.0 -> 0.8.0 (βœ“ API compatible changes)
  • augurs-prophet: 0.7.0 -> 0.8.0 (βœ“ API compatible changes)
  • augurs-seasons: 0.7.0 -> 0.8.0

⚠️ augurs-core breaking changes

--- failure module_missing: pub module removed or renamed ---

Description:
A publicly-visible module cannot be imported by its prior path. A `pub use` may have been removed, or the module may have been renamed, removed, or made non-public.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/module_missing.ron

Failed in:
  mod augurs_core::interpolate, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:1

--- failure struct_missing: pub struct removed or renamed ---

Description:
A publicly-visible struct cannot be imported by its prior path. A `pub use` may have been removed, or the struct itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/struct_missing.ron

Failed in:
  struct augurs_core::interpolate::LinearInterpolator, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:41
  struct augurs_core::interpolate::Interpolate, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:71

--- failure trait_missing: pub trait removed or renamed ---

Description:
A publicly-visible trait cannot be imported by its prior path. A `pub use` may have been removed, or the trait itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/trait_missing.ron

Failed in:
  trait augurs_core::interpolate::Interpolatable, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:198
  trait augurs_core::interpolate::InterpolateExt, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:159
  trait augurs_core::interpolate::Interpolater, previously in file /tmp/.tmpDICXAz/augurs-core/src/interpolate.rs:16

⚠️ augurs-forecaster breaking changes

--- failure auto_trait_impl_removed: auto trait no longer implemented ---

Description:
A public type has stopped implementing one or more auto traits. This can break downstream code that depends on the traits being implemented.
        ref: https://doc.rust-lang.org/reference/special-types-and-traits.html#auto-traits
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/auto_trait_impl_removed.ron

Failed in:
  type Forecaster is no longer UnwindSafe, in /tmp/.tmpglQ86A/augurs/crates/augurs-forecaster/src/forecaster.rs:12
  type Forecaster is no longer RefUnwindSafe, in /tmp/.tmpglQ86A/augurs/crates/augurs-forecaster/src/forecaster.rs:12

--- failure enum_missing: pub enum removed or renamed ---

Description:
A publicly-visible enum cannot be imported by its prior path. A `pub use` may have been removed, or the enum itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/enum_missing.ron

Failed in:
  enum augurs_forecaster::transforms::Transform, previously in file /tmp/.tmpDICXAz/augurs-forecaster/src/transforms.rs:37
  enum augurs_forecaster::Transform, previously in file /tmp/.tmpDICXAz/augurs-forecaster/src/transforms.rs:37

--- failure enum_variant_added: enum variant added on exhaustive enum ---

Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/enum_variant_added.ron

Failed in:
  variant Error:Transform in /tmp/.tmpglQ86A/augurs/crates/augurs-forecaster/src/error.rs:26

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/inherent_method_missing.ron

Failed in:
  Forecaster::with_transforms, previously in file /tmp/.tmpDICXAz/augurs-forecaster/src/forecaster.rs:34

--- failure struct_missing: pub struct removed or renamed ---

Description:
A publicly-visible struct cannot be imported by its prior path. A `pub use` may have been removed, or the struct itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.38.0/src/lints/struct_missing.ron

Failed in:
  struct augurs_forecaster::transforms::MinMaxScaleParams, previously in file /tmp/.tmpDICXAz/augurs-forecaster/src/transforms.rs:131
Changelog

augurs

0.8.0 - 2024-12-23

Added

augurs-changepoint

0.7.0 - 2024-11-25

Other

  • update Cargo.toml dependencies

augurs-core

0.8.0 - 2024-12-23

Added

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.7.0 - 2024-11-25

Other

  • update Cargo.toml dependencies

augurs-mstl

0.7.0 - 2024-11-25

Other

  • update Cargo.toml dependencies

augurs-forecaster

0.8.0 - 2024-12-23

Added

Fixed

Other

augurs-outlier

0.8.0 - 2024-12-23

Other

augurs-prophet

0.8.0 - 2024-12-23

Added

Fixed

Other

augurs-seasons

0.7.0 - 2024-11-25

Other

  • update Cargo.toml dependencies


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features

    • Updated workspace package version to 0.8.0.
    • Introduced new transformation functionalities, including Box-Cox and Yeo-Johnson transforms.
    • Added a Forecaster wrapper for Prophet.
    • Included a new JavaScript crate named 'transforms'.
  • Bug Fixes

    • Corrected function usage and documentation links.
  • Documentation

    • Updated changelogs for multiple components to reflect new version entries and changes.
  • Chores

    • Updated dependency versions across the workspace for consistency.

Copy link
Contributor

coderabbitai bot commented Dec 16, 2024

Walkthrough

This pull request focuses on updating the versioning scheme for the Augurs workspace. The workspace package version has been incremented from 0.7.0 to 0.8.0, with all dependencies under [workspace.dependencies] also updated to 0.8.0. Additionally, the changelogs for augurs-forecaster, augurs-outlier, augurs-prophet, augurs-core, and augurs have been revised to reflect new features and dependency updates associated with this version increment.

Changes

File Change Summary
Cargo.toml - Workspace package version updated from 0.7.0 to 0.8.0
- All workspace dependencies updated from 0.7.0 to 0.8.0
crates/augurs-forecaster/CHANGELOG.md - Added new version 0.8.0 entry
- Introduced new transforms and fixed box_cox function
- Restructured transforms into modules
crates/augurs-outlier/CHANGELOG.md - Added new version 0.8.0 entry
- Updated rv dependency from 0.17.0 to 0.18.0
crates/augurs-prophet/CHANGELOG.md - Added new version 0.8.0 entry
- Added Forecaster wrapper for Prophet
- Updated statrs dependency from 0.17.1 to 0.18.0
crates/augurs-core/CHANGELOG.md - Added new version 0.8.0 entry
- Introduced breaking change: transform switched to a trait
crates/augurs/CHANGELOG.md - Added new version 0.8.0 entry
- Introduced breaking change: transform switched to a trait

Possibly related PRs

  • chore: releaseΒ #96: This PR involves a version update in the Cargo.toml file for the Augurs project, similar to the main PR's updates to the versioning scheme for the workspace package and its dependencies.
  • chore: bump to v0.3.1Β #103: This PR also updates the Cargo.toml file, incrementing the version for the workspace package and its dependencies, aligning with the versioning changes in the main PR.
  • chore: release v0.4.1Β #132: Similar to the main PR, this PR updates the Cargo.toml file to reflect a new versioning scheme for the workspace package and its dependencies.
  • chore: release v0.5.0Β #137: This PR updates the Cargo.toml file for the workspace package and its dependencies, similar to the main PR's versioning updates.
  • chore: release v0.6.1Β #151: This PR updates the Cargo.toml file for the workspace package and its dependencies, consistent with the main PR's changes.
  • chore: release v0.6.2Β #156: This PR updates the Cargo.toml file for the workspace package and its dependencies, aligning with the versioning changes in the main PR.
  • chore: release v0.7.0Β #178: This PR updates the Cargo.toml file for the workspace package and its dependencies, which is directly related to the versioning changes in the main PR.

Poem

🐰 Hop, hop, version update time!
Augurs workspace, now so sublime
From 0.7 to 0.8 we leap
Dependencies aligned, no need to weep
A rabbit's versioning dance so fine! πŸš€


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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 0e56162 and 0bb5299.

πŸ“’ Files selected for processing (4)
  • Cargo.toml (2 hunks)
  • crates/augurs-forecaster/CHANGELOG.md (1 hunks)
  • crates/augurs-outlier/CHANGELOG.md (1 hunks)
  • crates/augurs-prophet/CHANGELOG.md (1 hunks)
βœ… Files skipped from review due to trivial changes (1)
  • crates/augurs-outlier/CHANGELOG.md
πŸ”‡ Additional comments (3)
crates/augurs-forecaster/CHANGELOG.md (1)

9-22: LGTM on changelog structure and content

The changelog follows the Keep a Changelog format correctly and includes proper categorization of changes with links to relevant PRs.

Cargo.toml (1)

21-21: LGTM on version updates

The version updates are consistent across the workspace and all augurs-* dependencies, properly aligned with the 0.8.0 release.

Also applies to: 32-41

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

10-22: LGTM on changelog updates

The changelog is well-structured with proper categorization of changes and clear documentation of dependency updates.


### Fixed

- make Transform enum non-exhaustive (#194)
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Breaking change needs more visibility

The Transform enum being marked as non-exhaustive (#194) is a breaking change that requires pattern matching outside the crate to include a wildcard pattern. This should be moved to a "Breaking Changes" section for better visibility.

### Fixed

- make Transform enum non-exhaustive (#194)

+### Breaking Changes
+
+- make Transform enum non-exhaustive (#194) - Pattern matching on Transform enum outside the crate must now include a wildcard pattern
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- make Transform enum non-exhaustive (#194)
### Fixed
### Breaking Changes
- make Transform enum non-exhaustive (#194) - Pattern matching on Transform enum outside the crate must now include a wildcard pattern

@github-actions github-actions bot force-pushed the release-plz-2024-12-16T10-57-12Z branch 11 times, most recently from 8a020d9 to 584cade Compare December 23, 2024 08:30
@github-actions github-actions bot force-pushed the release-plz-2024-12-16T10-57-12Z branch from 584cade to 4859bdf Compare December 23, 2024 08:38
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)
crates/augurs-core/CHANGELOG.md (1)

9-10: Version entry is consistent with main package

The version number, date, and comparison link format are consistent with the main package changelog. However, the same date verification comment applies here.

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 584cade and 4859bdf.

πŸ“’ Files selected for processing (6)
  • Cargo.toml (2 hunks)
  • crates/augurs-core/CHANGELOG.md (1 hunks)
  • crates/augurs-forecaster/CHANGELOG.md (1 hunks)
  • crates/augurs-outlier/CHANGELOG.md (1 hunks)
  • crates/augurs-prophet/CHANGELOG.md (1 hunks)
  • crates/augurs/CHANGELOG.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
  • crates/augurs-outlier/CHANGELOG.md
  • crates/augurs-forecaster/CHANGELOG.md
  • crates/augurs-prophet/CHANGELOG.md
  • Cargo.toml
πŸ”‡ Additional comments (3)
crates/augurs/CHANGELOG.md (2)

14-14: Breaking change is well documented

The breaking change for switching transform to a trait is properly marked and referenced (PR #213). This aligns with the PR objectives and is consistently documented across packages.


10-11: Verify the release date

The changelog entry is dated December 23, 2024, which is in the future. Consider either:

  • Updating to the actual release date when merging
  • Using the placeholder [Unreleased] section until the actual release
βœ… Verification successful

Let me verify if there are any established patterns for release dates in the changelog by checking the existing entries.


Future date in changelog entry needs to be moved to [Unreleased]

The changelog already has an [Unreleased] section, and looking at the previous entries (0.6.0 from Nov 8, 0.5.2 from Oct 25, etc.), all release dates are in the past. The current entry for 0.8.0 should be moved under [Unreleased] until the actual release date.

  • Move the 0.8.0 changes to the [Unreleased] section
  • Remove the future date (2024-12-23)
  • Add the actual release date only when the release is made
🏁 Scripts executed

The following scripts were executed for the analysis:

Error: No shell scripts found


Script:

#!/bin/bash
# Check the content of CHANGELOG.md to analyze date patterns
cat crates/augurs/CHANGELOG.md

Length of output: 1974

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

13-13: Breaking change documentation is consistent

The breaking change for the transform trait is documented identically across packages, maintaining consistency in the release notes.

@sd2k sd2k closed this Dec 23, 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