fix: bump version to v3.6.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
  • Updated version numbers across product, feature, and bundle metadata from 3.5.0 to 3.6.0.

[coderabbitai]

Walkthrough

This change updates version numbers from 3.5.0 to 3.6.0 across multiple project metadata files, including the OSGi bundle manifest, Eclipse feature descriptor, Maven POM, and product XML. No functional, structural, or public API changes are introduced.

Changes

Files	Change Summary
bundles/com.espressif.idf.branding/META-INF/MANIFEST.MF	Incremented Bundle-Version from 3.5.0 to 3.6.0
features/com.espressif.idf.feature/feature.xml	Updated feature version from 3.5.0 to 3.6.0
releng/com.espressif.idf.configuration/pom.xml	Updated Maven property espressif-ide-release-version from 3.5.0 to 3.6.0
releng/com.espressif.idf.product/idf.product	Updated product version from 3.5.0 to 3.6.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: updating to 3.4.0v #1206: Also updates version numbers in the same set of files for an incremental version bump.
• fix: bump version to 3.1.0 #1044: Performs analogous version bump changes in the Espressif IDF branding bundle and related files.
• chore(release): bump version to v3.3.0 #1153: Increments version numbers in the same files for the Espressif IDF Eclipse plugin.

Suggested reviewers

• alirana01

Poem

A hop, a skip, a version jump,
From five to six, we thump-thump-thump!
No code to tweak, no tests to run,
Just numbers rising, isn’t this fun?
With every bump, a carrot’s cheer—
Onward, upward, year by year!
🥕✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 660afae and 2992d9f.

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

🔇 Additional comments (4)

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

13-14: No stale 3.5.0 references found
The repository-wide search returned zero occurrences of the old version string. All 3.5.0 literals have been updated.

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

5-6: Bundle version updated – looks good

The bundle version now matches the new release. No further action required.

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

5-6: Feature version aligned with release

Version increment is correct and consistent with the bundle and product descriptors.

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

4-5: Product version updated – consistent across artefacts

The product descriptor now reflects 3.6.0; this keeps update-site and installer metadata in sync.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch v3.6.0_bump

---

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

• 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate unit tests to generate unit tests 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.