Update repository references for rename to ably-pubsub-java

[umair-ably]

Do not merge until the repository is renamed ably-java → ably-pubsub-java, in the programme's rename freeze window. Merging early points javadoc.yml and features.yml at the ably-sdk-builds-ably-pubsub-java IAM role, whose OIDC trust is bound to the new repository name, so the credential step would fail; and the release.yaml repository guard would skip every run. Conversely, once the rename happens the old role name stops matching and the old guard skips, so this is a same-window change in both directions.

Sibling of ably-pubsub-ruby#457, ably-dotnet#1332, ably-python#682 and ably-js#2298. It only updates strings inside the repo; it does not rename anything.

What changed

• .github/workflows/javadoc.yml — role-to-assume → ably-sdk-builds-ably-pubsub-java. The role is provisioned by infrastructure#13005 (merged 2026-09-01); infrastructure#13054 adds the ID-qualified OIDC subject GitHub uses for repos renamed after 2026-07-15.
• .github/workflows/features.yml — repository-name: ably-pubsub-java.
• .github/workflows/release.yaml — if: github.repository == 'ably/ably-pubsub-java'. ⚠️ This guard silently skips the Maven Central release job on a mismatch, so it must flip in the same window as the rename.
• gradle.properties — POM_URL, POM_SCM_URL, POM_SCM_CONNECTION, POM_SCM_DEV_CONNECTION, POM_LICENSE_URL. These are published into the POM on Maven Central, so the next release advertises the new repo. GROUP/artifact coordinates untouched.
• README.md — licence badge and GitHub Issues link.
• CONTRIBUTING.md — issue link, the two IDE "select ably-java/…" checkout-path steps, and the release-workflow link.
• overview.html — source-code link on the Javadoc front page.

Deliberately left as-is

• ably-java/<version> agent identifier and the pubsub-adapter tests asserting on it — a registered identifier, not a repository reference. The family rename to ably-pubsub-java lands on the split branch ([Split 2/3] Add io.ably.pubsub:device and :server door packages with side-declaring agents #1233), gated on ably-common#361.
• Maven coordinates io.ably:ably-java — README badges/links, deploy/check-archives.sh path. Artifact IDs, not the repo.
• CHANGELOG.md, issue/PR links in code comments and tests, .claude/skills prose, and the ably-java-secring.gpg example filename — history / local names; GitHub's redirect covers the links.
• Maven Central publishing authenticates with Sonatype credentials in repo secrets, not OIDC, so nothing to rebind registry-side. Secrets carry over with the rename.

Post-rename verification

• git ls-remote from an existing checkout and web redirects for repo / a PR / a file permalink.
• check.yml matrix green.
• javadoc.yml and features.yml runs: AWS credential step succeeds and the upload lands at sdk.ably.com/builds/ably/ably-pubsub-java/main/… (the upload failure mode is silent).
• release.yaml dispatched on the latest release tag reaches the "Compare version with tag" step (proves the repository guard) — cancel before publish, or wait for the next real release.
• Merge main into integration/v2 and the integration/split-* chain, which carry their own copies of the workflows.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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

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