[jiangxt2]

Pull request

What changes were proposed in this pull request?

• Advance the reactor revision to 2.6.0-SNAPSHOT after the verified publication of Pista 2.5.0.
• Record the dated 2.5.0 changelog entry and open a new Unreleased section.
• Point users to the stable download and distinguish published support from development snapshots.
• Reuse RC Submitter evidence for matching downloaded artifacts; reserve additional consumer tests for concrete coverage gaps.

Why are the changes needed?

Development builds need a distinct version after the stable release. Documentation must reflect the published distribution and avoid repeating runtime validation for the same verified artifact.

Related issues

None.

Does this PR introduce any user-facing change?

Source builds use 2.6.0-SNAPSHOT. Stable downloads remain at 2.5.0. Runtime baselines, historical introduced-version annotations, configuration and execution behavior remain unchanged.

How was this patch tested?

• Inspected the root POM and all reactor module POMs: the revision is 2.6.0-SNAPSHOT, child versions inherit the revision, and runtime baselines are preserved.
• python3 -B scripts/check_public_content.py, python3 -B scripts/check_language.py, python3 -B scripts/check_markdown.py and python3 -B scripts/check_public_license.py passed.
• git diff --check and static review of the complete change passed.

The change is limited to release metadata and documentation; no runtime behavior changes.

[greptile-apps]

Confidence Score: 4/5

[Low impact] Documentation and version bump for next development cycle.

The PR appears safe to merge, with a non-blocking gap in the documented release checks.

Findings

1.  Release checks lose coverage ▶

Fix with agent prompt

### Issue 1
docs/releases.md:69-71
The new reuse rule drops two checks that the consumer smoke previously required. `PistaFunctionSubmitterIT` submits console output without checking its contents, and no submission test checks that a required output failure makes the job fail. `BatchSubmitterIT.submit` only checks for a successful exit.

Because extra tests are now required only for gaps caused by distribution or entry-point changes, these existing gaps can go unchecked in future releases. Reuse evidence for covered behavior, but retain focused checks for output contents and required-output failures.

```suggestion
Reuse successful RC Submitter IT evidence for covered behavior when it exercised
the same Assembly JAR and the downloaded hashes match. Run focused consumer smoke
checks for behavior that evidence does not cover, including Spark-native output
contents and required-output failure propagation. Also check any concrete runtime
coverage gaps caused by distribution or entry-point changes.
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Advances development builds to 2.6.0-SNAPSHOT and records 2.5.0 as the stable release.

• Source builds use 2.6.0-SNAPSHOT while the changelog records the 2.5.0 release.
• Users can tell the stable 2.5.0 release from development builds.
• Future release instructions reuse matching evidence and reserve extra smoke tests for coverage gaps.

_{Reviews (1) · Last reviewed commit: "Prepare master for Pista 2.6.0 developme..." · Reviewed by Greptile}

[greptile-apps]

Release checks lose coverage

The new reuse rule drops two checks that the consumer smoke previously required. PistaFunctionSubmitterIT submits console output without checking its contents, and no submission test checks that a required output failure makes the job fail. BatchSubmitterIT.submit only checks for a successful exit.

Because extra tests are now required only for gaps caused by distribution or entry-point changes, these existing gaps can go unchecked in future releases. Reuse evidence for covered behavior, but retain focused checks for output contents and required-output failures.

Suggested change

	Reuse successful RC Submitter IT evidence when it exercised the same Assembly JAR
	and the downloaded hashes match. A separate consumer smoke is needed only when
	distribution or entry-point changes leave a concrete runtime coverage gap.
	Reuse successful RC Submitter IT evidence for covered behavior when it exercised
	the same Assembly JAR and the downloaded hashes match. Run focused consumer smoke
	checks for behavior that evidence does not cover, including Spark-native output
	contents and required-output failure propagation. Also check any concrete runtime
	coverage gaps caused by distribution or entry-point changes.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/releases.md
Line: 69-71

Comment:
**Release checks lose coverage**

The new reuse rule drops two checks that the consumer smoke previously required. `PistaFunctionSubmitterIT` submits console output without checking its contents, and no submission test checks that a required output failure makes the job fail. `BatchSubmitterIT.submit` only checks for a successful exit.

Because extra tests are now required only for gaps caused by distribution or entry-point changes, these existing gaps can go unchecked in future releases. Reuse evidence for covered behavior, but retain focused checks for output contents and required-output failures.

```suggestion
Reuse successful RC Submitter IT evidence for covered behavior when it exercised
the same Assembly JAR and the downloaded hashes match. Run focused consumer smoke
checks for behavior that evidence does not cover, including Spark-native output
contents and required-output failure propagation. Also check any concrete runtime
coverage gaps caused by distribution or entry-point changes.
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!