Skip to content

Conversation

@sigmaaa
Copy link
Collaborator

@sigmaaa sigmaaa commented Apr 25, 2025

Description

Please include a summary of the change and which issue is fixed.

Fixes # (IEP-XXX)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • ESP-IDF Version:
  • OS (Windows,Linux and macOS):

Dependent components impacted by this PR:

  • Component 1
  • Component 2

Checklist

  • PR Self Reviewed
  • Applied Code formatting
  • Added Documentation
  • Added Unit Test
  • Verified on all platforms - Windows,Linux and macOS

Summary by CodeRabbit

  • Chores
    • Updated version numbers from 3.3.0 to 3.4.0 across plugin, feature, product, and build configuration files. No functional changes introduced.

@sigmaaa sigmaaa self-assigned this Apr 25, 2025
@coderabbitai
Copy link

coderabbitai bot commented Apr 25, 2025

Walkthrough

This change updates the version numbers from 3.3.0 to 3.4.0 in several project files, including the branding bundle manifest, feature descriptor, Maven POM configuration, and product descriptor. No other modifications or functional changes are introduced; only the version attributes and metadata are incremented to reflect the new release.

Changes

Files Change Summary
bundles/com.espressif.idf.branding/META-INF/MANIFEST.MF Updated bundle version from 3.3.0.qualifier to 3.4.0.qualifier.
features/com.espressif.idf.feature/feature.xml Updated feature version attribute from 3.3.0.qualifier to 3.4.0.qualifier.
releng/com.espressif.idf.configuration/pom.xml Updated Maven property espressif-ide-release-version from 3.3.0 to 3.4.0.
releng/com.espressif.idf.product/idf.product Updated product version attribute from 3.3.0 to 3.4.0.

Possibly related PRs

Suggested reviewers

  • AndriiFilippov
  • kolipakakondal
  • alirana01

Poem

Version numbers hop and leap,
From three-point-three to four they creep.
Bundles, features, products too,
All refreshed with something new.
A rabbit stamps this tidy feat—
Release is ready, crisp and neat!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e0537d2 and ce30c9a.

📒 Files selected for processing (4)
  • bundles/com.espressif.idf.branding/META-INF/MANIFEST.MF (1 hunks)
  • features/com.espressif.idf.feature/feature.xml (1 hunks)
  • releng/com.espressif.idf.configuration/pom.xml (1 hunks)
  • releng/com.espressif.idf.product/idf.product (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_macos
  • GitHub Check: build
🔇 Additional comments (4)
releng/com.espressif.idf.configuration/pom.xml (1)

13-13: Upgrade project release version
The <espressif-ide-release-version> property is correctly bumped to 3.4.0, keeping the POM aligned with the new release cycle.

bundles/com.espressif.idf.branding/META-INF/MANIFEST.MF (1)

5-5: Update bundle version qualifier
The Bundle-Version has been updated to 3.4.0.qualifier, ensuring the branding plugin metadata matches the new IDE release.

releng/com.espressif.idf.product/idf.product (1)

4-4: Synchronize product version
The root <product> element’s version attribute is correctly updated to 3.4.0, aligning the product descriptor with other component versions.

features/com.espressif.idf.feature/feature.xml (1)

5-5: Bump feature descriptor version
The feature’s version attribute is updated to 3.4.0.qualifier, matching the release versioning scheme used elsewhere.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in 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
Collaborator Author

@sigmaaa sigmaaa left a comment

Choose a reason for hiding this comment

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

Self reviewed

Copy link
Collaborator

@kolipakakondal kolipakakondal left a comment

Choose a reason for hiding this comment

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

LGTM

@kolipakakondal kolipakakondal merged commit 0345b84 into master Apr 25, 2025
2 of 5 checks passed
@kolipakakondal kolipakakondal deleted the bump_v3.4.0 branch April 25, 2025 08:45
@coderabbitai coderabbitai bot mentioned this pull request Jul 24, 2025
5 tasks
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.

3 participants