analysis: Bump org.eclipse.tracecompass.analysis.profiling.core version

[PatrickTasse]

What it does

analysis: Bump org.eclipse.tracecompass.analysis.profiling.core version

How to test

Check for no API errors

Follow-ups

N/A

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the instructions in this template

Summary by CodeRabbit

• Chores
  • Version bumped from 2.6.1 to 2.7.0, reflecting documentation updates across the profiling analysis core module. All internal documentation references updated to reflect the new version.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version bump and documentation maintenance for the profiling analysis bundle. Bundle version incremented from 2.6.1.qualifier to 2.7.0.qualifier, with corresponding @since tag updates in related Javadoc annotations across multiple source files.

Changes

Cohort / File(s)	Summary
Version bump analysis/org.eclipse.tracecompass.analysis.profiling.core/META-INF/MANIFEST.MF	Bundle-Version header updated from 2.6.1.qualifier to 2.7.0.qualifier
Documentation updates analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/callstack/CallStackAnalysis.java, CallStackStateProvider.java, InstrumentedCallStackAnalysis.java	@since tags updated from 2.6 to 2.7 in Javadoc for ANNOTATIONS field and addMarker method

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

All changes are non-functional: a single version string update and repetitive Javadoc tag maintenance. No logic modifications, behavioral changes, or risk factors present.

Poem

🐰 Hop, hop—version grows from two-point-six,
To seven-oh, we've got our mix!
A bump, a tag, documentation's bright,
The bundle springs forward, everything's tight! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change—bumping the version of org.eclipse.tracecompass.analysis.profiling.core from 2.6.1 to 2.7.0 across manifest and @SInCE tags.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 477ab7c and 21f9b74.

📒 Files selected for processing (4)

• analysis/org.eclipse.tracecompass.analysis.profiling.core/META-INF/MANIFEST.MF (1 hunks)
• analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/callstack/CallStackAnalysis.java (1 hunks)
• analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/callstack/CallStackStateProvider.java (1 hunks)
• analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/instrumented/InstrumentedCallStackAnalysis.java (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build / build
• GitHub Check: build / build
• GitHub Check: build / build

🔇 Additional comments (4)

analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/callstack/CallStackAnalysis.java (1)

57-62: LGTM!

The @since tag update from 2.6 to 2.7 correctly aligns with the bundle version bump to 2.7.0.qualifier.

analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/instrumented/InstrumentedCallStackAnalysis.java (1)

70-75: LGTM!

The @since tag update is consistent with the bundle version bump and mirrors the same update in CallStackAnalysis.java.

analysis/org.eclipse.tracecompass.analysis.profiling.core/META-INF/MANIFEST.MF (1)

6-6: LGTM!

The minor version bump from 2.6.1 to 2.7.0 follows OSGi semantic versioning conventions for backward-compatible API additions. The @since 2.7 tags in the Java source files are correctly aligned with this bundle version.

analysis/org.eclipse.tracecompass.analysis.profiling.core/src/org/eclipse/tracecompass/analysis/profiling/core/callstack/CallStackStateProvider.java (1)

281-290: LGTM!

The @since tag update for addMarker(ITmfEvent) is consistent with the bundle version bump to 2.7.0.qualifier.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}