Java README Maven install snippet is stuck at 1.0.5-01; release sed regex can't match numeric qualifiers

[HoneyTyagii]

Summary

java/README.md advertises 1.0.5-01 in its Maven install snippet. java/pom.xml is on
1.0.10-preview.2-SNAPSHOT. Anyone following the primary Java install path gets a version
several releases behind.

It is not a one-off stale string: the release workflow tries to rewrite that snippet on every
release and silently fails to match it, so it stays wrong until the regex is fixed.

The inconsistency

Same "Installation" section, two different versions for one artifact:

Location	Version
java/README.md:35 (Maven)	1.0.5-01
java/README.md:42 (Gradle)	1.0.9-preview.2-01
java/pom.xml:10 (authoritative)	1.0.10-preview.2-SNAPSHOT

CHANGELOG.md:85 dates java/v1.0.5-01 to 2026-07-01; the newest Java entry is
java/v1.0.6 at line 67.

Root cause

.github/workflows/java-publish-maven.yml:204-205:

sed -i "s|<version>[0-9][0-9]*\.[0-9][0-9]*\.[0-9][0-9]*\(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)*</version>|<version>${VERSION}</version>|g" README.md
sed -i "s|copilot-sdk-java:[0-9][0-9]*\.[0-9][0-9]*\.[0-9][0-9]*\(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)*|copilot-sdk-java:${VERSION}|g" README.md

The qualifier group \(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)* requires a qualifier to start with a
letter and contain a .N part. -01 satisfies neither, so:

1. Sed #1 cannot match <version>1.0.5-01</version> (after 1.0.5 it needs </version>,
   finds -01). The Maven snippet has never been bumped.
2. Sed Fix snapshot filename collisions on case-insensitive filesystems #2 matches only the copilot-sdk-java:1.0.9-preview.2 prefix and leaves -01 in place,
   carrying it forward each release. That is where 1.0.9-preview.2-01 came from; it is a sed
   artifact, not a real coordinate.

The workflow's own validator at line 178,
^[0-9]+\.[0-9]+\.[0-9]+(-(preview|(beta-)?java(-preview)?)\.[0-9]+)?$, rejects -01
versions, so this pipeline cannot even emit the coordinates its docs advertise.

Reproduction

Run those two seds with VERSION="1.0.11-preview.1" over the repo's real version strings.
Actual output (GNU sed, verified locally):

<version>1.0.5-01</version>                   <- unchanged, bug 1
<version>1.0.11-preview.1</version>           <- correctly rewritten
copilot-sdk-java:1.0.11-preview.1-01          <- stray -01 survives, bug 2

Expected: line 1 rewritten, line 3 without the trailing -01.

Why CI misses it

• java/src/test/java/com/github/copilot/DocumentationSamplesTest.java reads README.md and
  jbang-example.java (documentationFiles(), lines 132-138) but only asserts
  setOnPermissionRequest usage. No version assertion exists anywhere.
• .github/workflows/java-smoke-test.yml:55 builds from source and consumes the local
  SNAPSHOT, so it never resolves the README's pinned release version.
• No workflow compiles or runs jbang-example.java; jbang is never installed in CI.

Suggested fix

1. Widen the qualifier group to accept numeric-only qualifiers, e.g.
   \(-[a-z0-9][a-z0-9.-]*\)\?, and anchor the copilot-sdk-java: replacement so it consumes
   the whole coordinate. Re-test against the SNAPSHOT lines too: the comment at lines 206-208
   shows the snapshot seds depend on the release seds matching first.
2. Drop the -01 suffixes; use versions the line 178 validator accepts.
3. Add a CI guard asserting documented coordinates match java/pom.xml.
   DocumentationSamplesTest already loads both files.

Also in that section: duplicate ### Gradle headings at java/README.md:39 and :65 (the root
README.md:27 anchor can only reach the first), and lines 65-70 say "latest release from Maven
Central" while showing a -SNAPSHOT.

Not verified

No network access here, so which versions actually exist on Maven Central is unconfirmed.
Everything else is backed by repo files at main plus the local sed run.

[github-actions]

Investigation findings

Label applied: bug — the reported behavior is a genuine defect.

What I investigated

• java/README.md lines 30–71 (Maven and Gradle install snippets)
• java/pom.xml line 10 (authoritative version)
• .github/workflows/java-publish-maven.yml lines 201–216 (the sed update logic)

What I found

The issue report is accurate. I reproduced both sed failures locally:

Bug 1 — <version>1.0.5-01</version> is completely unchanged by sed line 204:

sed -i "s|<version>[0-9][0-9]*\.[0-9][0-9]*\.[0-9][0-9]*\(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)*</version>|..."

The qualifier group \(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)* requires the qualifier to start with a letter ([a-z]) and contain a dot followed by digits. -01 starts with a digit, so it never matches. The Maven snippet has been frozen at 1.0.5-01 ever since that suffix was introduced.

Bug 2 — copilot-sdk-java:1.0.9-preview.2-01 (sed line 205) matches only the copilot-sdk-java:1.0.9-preview.2 portion and replaces it, leaving the trailing -01. This produces bogus coordinates like copilot-sdk-java:1.0.11-preview.1-01 on every subsequent release.

Both bugs verified with GNU sed against the actual strings in the repo.

Root cause summary

The release workflow's sed regexes use \(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)* to match version qualifiers. This pattern cannot match numeric-only qualifiers (e.g., -01). As a result:

1. The Maven XML snippet is never updated.
2. The Gradle snippet accumulates a stale -01 suffix on each release pass.

The workflow's own version validator (line 177) also rejects -01-style versions, meaning the documented coordinates are not even valid inputs to the pipeline.

Additional issues confirmed

• Duplicate ### Gradle headings at java/README.md:39 and :65
• Lines 65–70 describe "latest release from Maven Central" but show a -SNAPSHOT version

Suggested fix

Widen the qualifier group to include numeric-only qualifiers, e.g. change \(-[a-z][a-z0-9-]*\.[0-9][0-9]*\)* to \(-[a-z0-9][a-z0-9.-]*\)\? (or equivalent), and verify all four sed lines match before the next release.

Generated by Bug Handler for #2209 · sonnet46 26.4 AIC · ⌖ 5.37 AIC · ⊞ 5.9K · ◷