v0.7.2

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

The v0.7.0 topic-governed content-type contract is not an in-place state
upgrade from an earlier preview. Stop every hub and consolidator, retain the
old state destinations for rollback, configure new empty state-event and
snapshot destinations, then re-register topics and subscriptions. Earlier
preview processes and v0.7.0 processes must never share state destinations,
even though both use schema version 1. See the
installation guide
for the complete transition and rollback procedure.

Starting with v0.6.0, existing v0.5.0 hub configurations must explicitly set
server.auth.mode and operations.auth.mode to none or jwt; omission is a
startup error. The packaged developer configuration uses none. Production
deployments should use jwt; authentication never falls back on JWT failure.

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• Start 0.7.2-SNAPSHOT development by @github-actions[bot] in #45
• chore(deps): bump github.com/twmb/franz-go from 1.22.0 to 1.22.1 by @dependabot[bot] in #47
• Prepare v0.7.2 release by @github-actions[bot] in #48

Full Changelog: v0.7.1...v0.7.2

v0.7.1

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

The v0.7.0 topic-governed content-type contract is not an in-place state
upgrade from an earlier preview. Stop every hub and consolidator, retain the
old state destinations for rollback, configure new empty state-event and
snapshot destinations, then re-register topics and subscriptions. Earlier
preview processes and v0.7.0 processes must never share state destinations,
even though both use schema version 1. See the
installation guide
for the complete transition and rollback procedure.

Starting with v0.6.0, existing v0.5.0 hub configurations must explicitly set
server.auth.mode and operations.auth.mode to none or jwt; omission is a
startup error. The packaged developer configuration uses none. Production
deployments should use jwt; authentication never falls back on JWT failure.

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• Start 0.7.1-SNAPSHOT development by @github-actions[bot] in #36
• chore(deps): bump github.com/lestrrat-go/jwx/v3 from 3.2.0 to 3.3.0 by @dependabot[bot] in #38
• chore(deps): bump docker/setup-buildx-action from 4.3.0 to 4.4.1 by @dependabot[bot] in #39
• chore(deps): bump docker/build-push-action from 7.3.0 to 7.4.0 by @dependabot[bot] in #42
• chore(deps): bump github.com/twmb/franz-go/pkg/kadm from 1.18.0 to 1.19.0 by @dependabot[bot] in #41
• chore(deps): bump lib-websubhub to v0.6.1 by @ayeshLK in #43
• Prepare v0.7.1 release by @github-actions[bot] in #44

Full Changelog: v0.7.0...v0.7.1

v0.7.0

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

The v0.7.0 topic-governed content-type contract is not an in-place state
upgrade from an earlier preview. Stop every hub and consolidator, retain the
old state destinations for rollback, configure new empty state-event and
snapshot destinations, then re-register topics and subscriptions. Earlier
preview processes and v0.7.0 processes must never share state destinations,
even though both use schema version 1. See the
installation guide
for the complete transition and rollback procedure.

Starting with v0.6.0, existing v0.5.0 hub configurations must explicitly set
server.auth.mode and operations.auth.mode to none or jwt; omission is a
startup error. The packaged developer configuration uses none. Production
deployments should use jwt; authentication never falls back on JWT failure.

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• Start 0.6.2-SNAPSHOT development by @github-actions[bot] in #28
• Add configurable structured runtime logging by @ayeshLK in #27
• Govern resource content types by topic by @ayeshLK in #30
• Upgrade supported Go toolchain to 1.26.8 by @ayeshLK in #34
• chore(deps): bump goreleaser/goreleaser-action from 7.2.0 to 7.2.3 by @dependabot[bot] in #32
• chore(deps): bump anchore/sbom-action/download-syft from 0.24.0 to 0.24.2 by @dependabot[bot] in #33
• Prepare v0.7.0 release by @github-actions[bot] in #35

Full Changelog: v0.6.1...v0.7.0

v0.6.1

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

Starting with v0.6.0, existing v0.5.0 hub configurations must explicitly set
server.auth.mode and operations.auth.mode to none or jwt; omission is a
startup error. The packaged developer configuration uses none. Production
deployments should use jwt; authentication never falls back on JWT failure.

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• Start 0.6.1-SNAPSHOT development by @github-actions[bot] in #22
• Improve GitHub product profile by @ayeshLK in #23
• Improve Docker Hub product profiles by @ayeshLK in #24
• Update repository handoff context by @ayeshLK in #25
• Prepare v0.6.1 release by @github-actions[bot] in #26

Full Changelog: v0.6.0...v0.6.1

v0.6.0

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

Starting with v0.6.0, existing v0.5.0 hub configurations must explicitly set
server.auth.mode and operations.auth.mode to none or jwt; omission is a
startup error. The packaged developer configuration uses none. Production
deployments should use jwt; authentication never falls back on JWT failure.

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• Fix release notes cleanliness and safe tag recovery by @ayeshLK in #15
• Start 0.5.1-SNAPSHOT development by @github-actions[bot] in #16
• Update v0.5 release handoff context by @ayeshLK in #17
• Add explicit API authentication modes by @ayeshLK in #18
• Prepare v0.6.0 release by @github-actions[bot] in #21

New Contributors

• @github-actions[bot] made their first contribution in #16

Full Changelog: v0.5.0...v0.6.0

v0.5.0

Important

This is a pre-1.0 developer preview, not a production-readiness claim.

Delivery and compatibility

WebSubHub delivery is at least once. Subscribers must tolerate duplicate
notifications around retries, acknowledgement failures, consumer recovery, and
process restarts. The release does not claim end-to-end exactly-once delivery.

websubhub and websubhub-consolidator use one lockstep product version and
should be rolled out together. Consult the release-specific state and migration
notes before upgrading or rolling back; binary versions alone do not establish
persisted-state compatibility.

Preview limitations

Automatic subscription renewal, lease expiry, ownership transfer and fencing,
event-stream APIs, and complete failure qualification are deferred. macOS
archives are not Apple-notarized and Windows archives are not Authenticode
signed. Checksums, Sigstore bundles, SBOMs, and provenance are provided for the
portable artifacts.

Changes

What's Changed

• chore(deps): bump actions/setup-go from 6.5.0 to 7.0.0 by @dependabot[bot] in #1
• chore(deps): bump actions/checkout from 6.1.0 to 7.0.1 by @dependabot[bot] in #3
• chore(deps): bump github.com/lestrrat-go/jwx/v3 from 3.1.1 to 3.2.0 by @dependabot[bot] in #4
• feat: add consolidator-backed management APIs by @ayeshLK in #6
• Add release distribution foundation by @ayeshLK in #8
• Add Kafka subscription delivery options by @ayeshLK in #10
• Run complete Kafka provider integration suite by @ayeshLK in #12
• Automate reviewed snapshot release lifecycle by @ayeshLK in #13
• Prepare v0.5.0 release by @ayeshLK in #14

New Contributors

• @dependabot[bot] made their first contribution in #1

Full Changelog: https://github.com/ayeshLK/websubhub/commits/v0.5.0