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(main): release tempo 1.1.1 #125

Merged
merged 1 commit into from
Mar 7, 2025

Conversation

cedricziel
Copy link
Owner

@cedricziel cedricziel commented Dec 10, 2024

🤖 I have created a release beep boop

1.1.1 (2025-03-07)

Bug Fixes

  • bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo (#117) (b4b88c2)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Chores

    • Upgraded the application version to 1.1.1, ensuring consistent improvements across configurations.
  • Bug Fixes

    • Updated a key network dependency to enhance performance and reliability, addressing a reported issue.

@cedricziel cedricziel force-pushed the release-please--branches--main--components--tempo branch from f298f64 to 163c33c Compare December 10, 2024 11:06
@cedricziel cedricziel force-pushed the release-please--branches--main--components--tempo branch from 163c33c to f843e75 Compare December 18, 2024 11:26
Copy link

coderabbitai bot commented Dec 18, 2024

Walkthrough

This pull request involves a minor version update for the "tempo" component across multiple configuration files. The version has been incremented from 1.1.0 to 1.1.1, which includes a dependency update for the tarampampam/curl package from version 8.10.1 to 8.11.0. The changes are consistent across the .release-please-manifest.json, tempo/CHANGELOG.md, and tempo/config.yaml files, indicating a coordinated version bump.

Changes

File Change Summary
.release-please-manifest.json Updated "tempo" dependency version from 1.1.0 to 1.1.1
tempo/CHANGELOG.md Added new version entry 1.1.1 with bug fix for tarampampam/curl dependency update
tempo/config.yaml Updated version from 1.1.0 to 1.1.1

Poem

🐰 Hop, hop, version bump today!
Curl dependency finds its way
One-point-one-one, a tiny leap
Tempo's progress, smooth and neat
Rabbit's code dance, light and fleet! 🚀


🪧 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

@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)
tempo/CHANGELOG.md (1)

8-10: Maintain consistent list style

For consistency with other entries in the changelog, consider using a dash (-) instead of an asterisk (*) for the list item.

-* bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
+- bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
🧰 Tools
🪛 Markdownlint (0.37.0)

10-10: Expected: dash; Actual: asterisk
Unordered list style

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b35ed8d and f843e75.

📒 Files selected for processing (3)
  • .release-please-manifest.json (1 hunks)
  • tempo/CHANGELOG.md (1 hunks)
  • tempo/config.yaml (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • .release-please-manifest.json
  • tempo/config.yaml
🧰 Additional context used
🪛 Markdownlint (0.37.0)
tempo/CHANGELOG.md

10-10: Expected: dash; Actual: asterisk
Unordered list style

(MD004, ul-style)

🔇 Additional comments (2)
tempo/CHANGELOG.md (2)

5-7: LGTM: Version entry follows conventional format

The version entry is properly formatted with the correct version number, comparison link, and release date.


Line range hint 1-11: LGTM: Changelog structure is well-maintained

The changelog maintains proper chronological order and consistent formatting across versions. The new entry is correctly placed and includes all necessary references.

🧰 Tools
🪛 Markdownlint (0.37.0)

10-10: Expected: dash; Actual: asterisk
Unordered list style

(MD004, ul-style)

@cedricziel cedricziel force-pushed the release-please--branches--main--components--tempo branch from f843e75 to ef732ac Compare March 7, 2025 21:52
Copy link

@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)
tempo/CHANGELOG.md (1)

5-11: New Version Entry and Dependency Update Noted

The new changelog entry for version 1.1.1 added on 2025-03-07 correctly reflects the dependency update (tarampampam/curl from 8.10.1 to 8.11.0) tied to issue #117 with the associated commit reference. This provides clear traceability and context for the bug fix in this release.

Style Note:
The bullet point on line 10 uses an asterisk (*), whereas the markdownlint static analysis recommends using a dash (-) for unordered lists. For consistency across the document, consider updating the bullet style as shown in the diff below:

-* bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
+ - bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

10-10: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f843e75 and ef732ac.

📒 Files selected for processing (3)
  • .release-please-manifest.json (1 hunks)
  • tempo/CHANGELOG.md (1 hunks)
  • tempo/config.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .release-please-manifest.json
  • tempo/config.yaml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
tempo/CHANGELOG.md

10-10: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

@cedricziel cedricziel force-pushed the release-please--branches--main--components--tempo branch from ef732ac to 7b04f5d Compare March 7, 2025 21:55
Copy link

@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)
tempo/CHANGELOG.md (1)

8-10: Consider updating the bullet style for consistency.
The bug fix list item uses an asterisk (*), but the markdown lint hint suggests using dashes (-) for unordered lists. To align with the expected style and maintain consistency across the changelog, consider updating the bullet marker.

Example Diff:

-* bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
+- bump tarampampam/curl from 8.10.1 to 8.11.0 in /tempo ([#117](https://github.com/cedricziel/ha-addons/issues/117)) ([b4b88c2](https://github.com/cedricziel/ha-addons/commit/b4b88c25ceb716263c58311083c25b7ab762fbf7))
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

10-10: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ef732ac and 7b04f5d.

📒 Files selected for processing (3)
  • .release-please-manifest.json (1 hunks)
  • tempo/CHANGELOG.md (1 hunks)
  • tempo/config.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • tempo/config.yaml
  • .release-please-manifest.json
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
tempo/CHANGELOG.md

10-10: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

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

5-6: New version entry added successfully.
The new entry for [1.1.1](https://github.com/cedricziel/ha-addons/compare/tempo-1.1.0...tempo-1.1.1) with the release date 2025-03-07 is clearly delineated and follows the established format.

@cedricziel cedricziel merged commit 3b40e6e into main Mar 7, 2025
20 checks passed
@cedricziel cedricziel deleted the release-please--branches--main--components--tempo branch March 7, 2025 22:02
@cedricziel
Copy link
Owner Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant