Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: BabelQueue/babelqueue-java-pulsar
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.2.0
Choose a base ref
...
head repository: BabelQueue/babelqueue-java-pulsar
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.3.0
Choose a head ref
  • 2 commits
  • 14 files changed
  • 1 contributor

Commits on Oct 26, 2026

  1. Release v1.3.0 (ADR-0037) (#3) 

    * Settle unsupported Pulsar schema versions on first delivery (ADR-0037)

An unreadable bq-schema-version is no longer nacked forever: the consumer acks, writes the raw body to <queue>.dlq, or leaves it unsettled when the write fails, per broker-bindings 5.7. Pin conformance v1.8.0 and run version_gate_pulsar.

* Release v1.3.0
    @muhammetsafak
    muhammetsafak authored Oct 26, 2026
    Configuration menu
    Copy the full SHA
    e207dce View commit details
    Browse the repository at this point in the history

  2. Pin the release workflow to conformance v1.8.0 (#) 

    release.yml still verified the vendored suite against 1.7.0 while ci.yml had moved to 1.8.0, so the v-tag release stopped before publishing.
    @muhammetsafak
    muhammetsafak authored Oct 26, 2026
    Configuration menu
    Copy the full SHA
    9a44cde View commit details
    Browse the repository at this point in the history
Loading