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

Bump eBUSd version to 24.1.0 #153

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump eBUSd version to 24.1.0 #153

wants to merge 1 commit into from

Conversation

peroo
Copy link

@peroo peroo commented Dec 12, 2024

The eBUSd docker image was recently updated to 24.1, but it's not possible to update in Home Assistant, presumably because the version wasn't bumped.

Resolves #151

Summary by CodeRabbit

  • New Features
    • Updated changelog to include new version entry for EBUSd 24.1.0.
  • Chores
    • Incremented version number in the configuration file from 23.2.6 to 24.1.0.

Copy link

coderabbitai bot commented Dec 12, 2024

Walkthrough

The changes in this pull request involve updating the version information for the EBUSd application. Specifically, a new version entry for EBUSd 24.1.0 has been added to the changelog, along with its corresponding header. Additionally, the version number in the configuration file has been updated from "23.2.6" to "24.1.0". The overall structure and content of both files remain unchanged apart from these version updates.

Changes

File Change Summary
ebusd/CHANGELOG.md Added new version entry ## version: 24.1.0 and section header - EBUSd 24.1.
ebusd/config.yaml Updated version from version: "23.2.6" to version: "24.1.0".

Possibly related PRs

  • Update ebusd to 24.1 #152: The changes in this PR involve updating the version of the ebusd package to 24.1, which is directly related to the version increment in the main PR that updates the changelog and configuration files to reflect the new version 24.1.0.

Suggested reviewers

  • LukasGrebe
  • tjorim

Poem

In the burrow, soft and bright,
A new version hops into sight.
EBUSd's tale, now 24.1,
With changelog updates, the work is done!
Hooray for changes, let’s all cheer,
For every hop brings progress near! 🐇✨


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. (Experiment)
  • @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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1e5293e and 0a389fc.

📒 Files selected for processing (2)
  • ebusd/CHANGELOG.md (1 hunks)
  • ebusd/config.yaml (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
ebusd/CHANGELOG.md

2-2: null
First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🔇 Additional comments (2)
ebusd/config.yaml (1)

2-2: Verify docker image version alignment

The version has been bumped from 23.2.6 to 24.1.0. Let's verify this matches the referenced docker image.

✅ Verification successful

Version alignment confirmed between config and package

The version bump to 24.1.0 in config.yaml aligns correctly with the ebusd package version 24.1-r0 specified in the Dockerfile. The add-on uses the Alpine package repository to install ebusd, and the version numbers match (24.1.x). The image versioning is handled through the Home Assistant build system using the base images defined in build.yaml.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if the docker image for version 24.1.0 exists
# Note: Using GitHub Container Registry (ghcr.io) as specified in the image field

# Check if the image exists for all supported architectures
for arch in armhf armv7 aarch64 amd64 i386; do
  echo "Checking image for $arch..."
  gh api \
    -H "Accept: application/vnd.oci.image.index.v1+json" \
    "/v2/lukasgrebe/ha-addon-ebusd-$arch/tags/list" | \
    jq '.tags[] | select(. == "24.1.0")'
done

Length of output: 2172


Script:

#!/bin/bash
# Let's first check the Dockerfile and config to understand the image reference
echo "=== Checking config.yaml ==="
cat ebusd/config.yaml

echo -e "\n=== Checking Dockerfile ==="
cat ebusd/Dockerfile

echo -e "\n=== Checking build.yaml if exists ==="
cat ebusd/build.yaml 2>/dev/null || echo "build.yaml not found"

Length of output: 3103

ebusd/CHANGELOG.md (1)

2-4: Version consistency verified

The version "24.1.0" is consistently reflected in both config.yaml and CHANGELOG.md.

🧰 Tools
🪛 Markdownlint (0.37.0)

2-2: null
First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

ebusd/CHANGELOG.md Show resolved Hide resolved
Copy link

@ajvdw ajvdw left a comment

Choose a reason for hiding this comment

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

Minor change, ok.

Copy link
Contributor

@pvyleta pvyleta left a comment

Choose a reason for hiding this comment

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

LGTM, but I guess @LukasGrebe needs to approve as well.

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.

How to update the ebusd release image
3 participants