chore(release): bump version to v3.3.0

[kolipakakondal]

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
  • Upgraded the product version to 3.3.0 across multiple areas, ensuring consistent and up-to-date branding and release configurations.

[coderabbitai]

Walkthrough

This pull request updates version numbers across several project configuration files. The manifest file for the branding bundle, the feature XML, the POM property, and the product XML are updated to reflect the new version 3.3.0 (or 3.3.0.qualifier where applicable). The changes are limited to version increments with no alterations to the underlying structure or logic of the files.

Changes

File(s)	Change Summary
bundles/.../MANIFEST.MF features/.../feature.xml	Updated version attributes from 3.2.0.qualifier to 3.3.0.qualifier in both the bundle manifest and the feature XML.
releng/.../pom.xml releng/.../idf.product	Updated <espressif-ide-release-version> in the POM and the <product> version attribute in the product file from 3.2.0 to 3.3.0; also removed a redundant closing tag.

Possibly related PRs

• fix: bump version to 3.1.0 #1044: Updated the manifest's Bundle-Version from 3.0.0.qualifier to 3.1.0.qualifier, which is similar to the current version bump.

Suggested reviewers

• sigmaaa
• AndriiFilippov

Poem

I'm a little rabbit, hopping through the code,
Versions jump ahead in every vibrant node.
From 3.2 to 3.3, a gentle change unfolds,
In XML and manifests, the story now is told.
With a twitch and a hop, I celebrate this version road!
🐇🥕

---

📜 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 e60d439 and 6da9313.

📒 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)

✅ Files skipped from review due to trivial changes (2)

• features/com.espressif.idf.feature/feature.xml
• bundles/com.espressif.idf.branding/META-INF/MANIFEST.MF

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build
• GitHub Check: build_macos

🔇 Additional comments (2)

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

4-4: Version update looks good!

The product version has been correctly updated to 3.3.0, aligning with the PR objective.

releng/com.espressif.idf.configuration/pom.xml (1)

13-13: Version property update looks good!

The espressif-ide-release-version property has been correctly updated to 3.3.0, maintaining consistency with the product version.

---

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