singhvishalkr opened a new pull request, #1130: URL: https://github.com/apache/pulsar-site/pull/1130
## Scope Closes apache/pulsar#23554, closes apache/pulsar#23383. The Pulsar Kafka wrapper artifacts (`pulsar-client-kafka`, `pulsar-client-kafka-original`) live in the separate [apache/pulsar-adapters](https://github.com/apache/pulsar-adapters) repo, and the last released version on Maven Central is [`2.11.0`](https://repo1.maven.org/maven2/org/apache/pulsar/pulsar-client-kafka/) (March 2023). The docs use the `@pulsar:version@` build-time placeholder for the adapter `<version>` though, so on the 3.x / 4.x docs pages the pom snippet renders as e.g. `<version>3.3.1</version>` or `<version>4.2.x</version>` -- artifacts that do not exist. Users copy-paste the snippet and hit `Could not find artifact org.apache.pulsar:pulsar-client-kafka:pom:4.2.x`. ## Changes For every docs version where the placeholder would have resolved to a non-existent adapter release: - Hard-code both artifact versions to `2.11.0` instead of `@pulsar:version@`. - Add a Docusaurus `:::note` admonition at the top of the page explaining the release lag (adapter repo is separate, 2.11.0 is the last release, pin to it even on modern brokers). Files touched (8 total): - `docs/adaptors-kafka.md` (current / next docs) - `versioned_docs/version-3.0.x/adaptors-kafka.md` - `versioned_docs/version-3.1.x/adaptors-kafka.md` - `versioned_docs/version-3.2.x/adaptors-kafka.md` - `versioned_docs/version-3.3.x/adaptors-kafka.md` - `versioned_docs/version-4.0.x/adaptors-kafka.md` - `versioned_docs/version-4.1.x/adaptors-kafka.md` - `versioned_docs/version-4.2.x/adaptors-kafka.md` I intentionally did **not** touch `versioned_docs/version-2.11.x/...` and earlier -- the placeholder correctly resolves to a version that was actually released for those docs. ## Verification - Maven Central search for `org.apache.pulsar:pulsar-client-kafka`: latest `v` is `2.11.0` ([search.maven.org](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-kafka)). - `apache/pulsar-adapters` tags: newest release tag is `v2.11.0`; subsequent activity is only `v3.0.0-candidate-*` (never promoted to a release). - Follow-up releases of the adapter would just flip `2.11.0` back to a placeholder -- this PR is not prescriptive about future releases, only about today's reality. Single concern on scope: I left 3.3.x / 4.0.x / 4.1.x copies patched too. Happy to narrow to `docs/` + `version-4.2.x` if maintainers prefer a tighter blast radius. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
