Repository navigation
fix(deps): update dependency io.namastack:namastack-outbox-starter-jdbc to v1.11.1 - #324
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
renovate
Bot
force-pushed
the
renovate/namastackversion
branch
from
October 8, 2026 12:34
5e0e7ea to
992bdab
Compare
renovate
Bot
force-pushed
the
renovate/namastackversion
branch
from
October 10, 2026 01:54
992bdab to
7f3acb3
Compare
renovate
Bot
force-pushed
the
renovate/namastackversion
branch
from
October 20, 2026 11:51
7f3acb3 to
b5c7b49
Compare
Contributor
|
This pull request has been inactive for 14 days and has been marked as stale. Please rebase, resolve any conflicts, and update the PR if it is still intended to be merged. It will be automatically closed in 7 days if there is no further activity. |
renovate
Bot
force-pushed
the
renovate/namastackversion
branch
from
November 10, 2026 20:52
b5c7b49 to
22875e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.1.0→1.11.1Release Notes
namastack/namastack-outbox (io.namastack:namastack-outbox-starter-jdbc)
v1.11.1: Namastack Outbox v1.11.1What's New
More Reliable Record Processing (#525, #529)
Records with identical creation timestamps now have a deterministic order, so a failed or retry-delayed delivery continues to block later deliveries under strict ordering. Record IDs break timestamp ties; they do not define producer commit order. Concurrent scheduling on MySQL and MariaDB no longer uses the update-before-insert path that could cause gap-lock deadlocks.
Responsive Metrics During Database Outages (#516)
Outbox state gauges now read cached values collected in the background. Slow or unavailable databases no longer block the metrics scrape and hide unrelated application metrics. A new
outbox.metrics.collection.last.success.timestampgauge reports the last fully successful collection.What's Changed
mongo:9.0.4by @rolandbeisel in #571 and #572.Upgrade Notes
Application and Persistence
Upgrade all Namastack Outbox modules together, preferably through
io.namastack:namastack-outbox-bom:1.11.1. Mixing the new core with an older persistence module can leave the required repository methods unavailable.No database schema or index migration is required. Persisted payloads and record fields are unchanged, and pending records remain readable. Producer and handler API signatures are unchanged.
Metrics and Alerts
Existing metric names and tags are retained. State gauges now refresh in the background every 15 seconds by default; readings expire after 60 seconds. Before the first successful reading, after a failed collection, or after expiry, the affected gauge reports
NaNinstead of zero. Review alerts and dashboards that relied on immediate readings or treated zero as the database-failure value.Configure collection with
namastack.outbox.observability.metrics.refresh-intervalandmax-age. Setnamastack.outbox.observability.metrics.enabled=falseto disable state gauges and their background queries; observation-based timers remain enabled.🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.11.0...v1.11.1
v1.11.0: Namastack Outbox v1.11.0What's Changed
Dependency Updates
Other Changes
Full Changelog: namastack/namastack-outbox@v1.10.1...v1.11.0
v1.10.1: Namastack Outbox v1.10.1What's Changed
Bug Fixes
Dependency Updates
Full Changelog: namastack/namastack-outbox@v1.10.0...v1.10.1
v1.10.0: Namastack Outbox v1.10.0What's Changed
New Features
Documentation
Dependency Updates
Other Changes
Full Changelog: namastack/namastack-outbox@v1.9.0...v1.10.0
v1.9.0What's New
Stable Handler IDs and Aliases (GH-420, #442)
Handlers can now define deployment-stable canonical IDs through
@OutboxHandler(id, aliases)orOutboxHandlerIdentity. Lookup-only aliases support pending records during handler renames and rolling deployments while preserving backward compatibility with generated IDs.Safer Handler Registration (GH-420, #442)
Annotation- and interface-based handlers can coexist as distinct methods in the same bean. Handler discovery now validates declarations and ID collisions before installing canonical and alias routes atomically, preventing partially registered configurations at startup.
What's Changed
OutboxFailureContextdocumentation to uselastFailure,recordId,recordKey, and the current failure-state properties by @Alek96 in #439Security
🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.8.1...v1.9.0
v1.8.1: Namastack Outbox v1.8.1What's New
Spring Boot 4.1.1 Support GH-431
Updated the Spring Boot baseline from 4.1.0 to 4.1.1, providing compatibility with the latest Spring Boot maintenance release.
Stable IDs for Lambda Handlers (GH-427 / #428)
Interface-based lambda handlers now use their Spring bean names instead of generated JVM lambda class names. This provides stable handler IDs across application restarts and prevents invalid legacy aliases from being registered for lambda handlers.
What's Changed
Breaking Changes
Security
Full Changelog: namastack/namastack-outbox@v1.8.0...v1.8.1
v1.8.0: Namastack Outbox v1.8.0What's New
Fully Configurable JDBC Table Names (#408)
JDBC users can now customize the base names of all outbox tables through
namastack.outbox.jdbc.table-names.record,namastack.outbox.jdbc.table-names.instance, andnamastack.outbox.jdbc.table-names.partition. The existing schemaname and table prefix settings continue to apply, and advanced users can now register a custom
JdbcTableNameResolverbean for complete control over generated table names. This improves support for organization-specific database naming
standards, including uppercase or otherwise constrained identifiers.
What's Changed
in #408
io.awspring.cloud:spring-cloud-aws-starter-snsfrom 4.0.2 to 4.1.0 in SNS examples by dependabot[bot]in #410
io.awspring.cloud:spring-cloud-aws-dependenciesfrom 4.0.2 to 4.1.0 by dependabot[bot]in #409
org.postgresql:postgresqlin the PostgreSQL example to 42.7.13 by dependabot[bot]in #403
in #401
in #400
Breaking Changes
None.
Security
shell-quotefrom 1.8.4 to 1.10.0 in the documentation site dependency tree by dependabot[bot]in #413
body-parserfrom 1.20.5 to 1.20.6 in the documentation site dependency tree by dependabot[bot]in #412
in #411
websocket-driverfrom 0.7.4 to 0.7.5 in the documentation site dependency tree by dependabot[bot]in #407
in #406
🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.7.1...v1.8.0
v1.7.3: Namastack Outbox v1.7.3What's New
Spring Boot 4.1.1 Support (GH-432)
Updated the Spring Boot baseline from 4.1.0 to 4.1.1, including build support for validating upcoming Spring snapshot releases.
Stable IDs for Spring Modulith Lambda Handlers (GH-427 / #428)
Spring Modulith externalizer lambdas now use stable Spring bean names instead of generated JVM lambda class names. This resolves the integration issue reported in spring-projects/spring-modulith#1777 and ensures reliable handler lookup across application restarts.
What's Changed
Breaking Changes
namastackKafkaOutboxExternalizernamastackJmsOutboxExternalizernamastackRabbitOutboxExternalizernamastackSpringMessagingOutboxExternalizerThis change addresses the unstable lambda handler IDs reported in spring-projects/spring-modulith#1777, which could prevent persisted outbox records from being matched to their Spring Modulith externalizer after an application restart.
Spring Modulith Handler ID Migration
Stop outbox processing and back up the database. Identify the generated handler IDs currently associated with each Spring Modulith externalizer and replace them with the corresponding stable ID listed above.
For relational databases, first inspect the existing IDs:
Then migrate each affected externalizer:
Verify that no pending records reference the old generated IDs before starting the application with version 1.7.3.
Full Changelog: namastack/namastack-outbox@v1.7.2...v1.7.3
v1.7.2: Namastack Outbox v1.7.2What's Changed
io.awspring.cloud:spring-cloud-aws-starter-snsfrom 4.0.2 to 4.1.0 in SNS examples by dependabot[bot] in #410io.awspring.cloud:spring-cloud-aws-dependenciesfrom 4.0.2 to 4.1.0 by dependabot[bot] in #409org.postgresql:postgresqlin the PostgreSQL example to 42.7.13 by dependabot[bot] in #403Breaking Changes
Security
🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.7.1...v1.7.2
v1.7.1: Namastack Outbox v1.7.1What's New
What's Changed
OutboxHandlerDescriptor,OutboxHandlerKind,findAllHandlerDescriptors(), andfindHandlerDescriptorById()for registered handler diagnostics by Roland Beisel in #392OutboxInstanceRegistryuses the dedicatedoutboxHeartbeatScheduler, preventing heartbeat starvation during long-running outbox tasks by Aleksander Zamojski in #396max-retriesand the documented capped retry schedule match by Roland Beisel in #3971.7.1by Roland Beisel in #3999.6.0for the root project and examples by dependabot[bot] in #390 and #391com.vanniktech.maven.publishfrom0.36.0to0.37.0by dependabot[bot] in #394qs,shell-quote,dompurify,launch-editor,undici, andws, by dependabot[bot] in #384 and #393a437aeeBreaking Changes
Security
dompurifyto3.4.11,undicito7.28.0, andwsto7.5.11. These updates affect the documentation build/runtime dependencies, not the published Namastack Outbox runtime artifacts.🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.7.0...v1.7.1
v1.7.0: Namastack Outbox v1.7.0What's New
Spring Boot 4.1.0 compatibility (GH-385)
Spring Boot dependencies were updated to 4.1.0. The JPA module now includes MySQL and MariaDB Hibernate dialect compatibility for schema validation so shipped
LONGTEXToutbox schemas continue to validate with Hibernate's nationalized long text mapping under Spring Boot 4.1.0.Spring Modulith integration guide and example (GH-294)
Namastack Outbox now includes a Spring Modulith integration guide, a dedicated Modulith example project, and smoke coverage for the example. The documentation explains how to use Namastack Outbox as the transactional outbox behind Modulith-style applications, including event publication precedence, retry behavior, observability, and Kafka-backed externalization.
Namastack Outbox BOM (GH-382, #383)
A new
namastack-outbox-bommodule centralizes versions for all Namastack Outbox artifacts. Gradle and Maven users can now import the BOM once and declare individual outbox modules without repeating the version. The README, quickstart, examples, Modulith example, and performance-test modules were updated to use the BOM-based setup.Unified observability module (GH-229, #363)
A new
namastack-outbox-observabilitymodule combines tracing and metrics around Micrometer Observation. It adds process and schedule observations, timer metrics, logical channel tagging, instance-level metrics, and updated observability documentation. The oldernamastack-outbox-metricsandnamastack-outbox-tracingmodules are now deprecated in favor of this module.Performance test suite and tuning guide (GH-377, #378)
A new
namastack-outbox-performance-testmodule provides producer/consumer tooling, Docker Compose infrastructure, Prometheus/Grafana monitoring, SQL setup, report generation, and repeatable commands for measuring outbox throughput and backlog behavior. The docs now include a performance tuning reference with generated report assets.RabbitMQ publisher confirms and send diagnostics (GH-371, #380)
RabbitMQ publishing now uses a dedicated publisher that waits for correlated publisher confirms, reports nacks/timeouts/interruption as
RabbitOutboxSendException, and can optionally fail processing when messages are returned as unroutable. Rabbit configuration metadata and docs were updated for the new confirm and unroutable-message settings.Retry state in handler metadata (GH-364, #365)
OutboxRecordMetadatanow exposesfailureCount,attempt, andisRetry, allowing regular handlers to react differently on first delivery versus retry attempts. Retry policy exception matching also inspects the full cause chain forretryOnandnoRetryOnrules.Package-private Java annotated handlers (GH-381, #379)
Annotated handler discovery now supports package-private Java methods and fallback/retryable annotated methods, improving Java ergonomics without requiring every handler method to be public.
Example smoke tests (GH-298, #297)
Example projects now include smoke tests and a dedicated GitHub Actions workflow to verify the examples. The examples also share centralized Gradle version-catalog setup for Namastack Outbox and Testcontainers dependencies.
What's Changed
namastack-outbox-bomand updated docs/examples to consume Namastack modules through the BOM by Roland Beisel in #383namastack-outbox-observabilitymodule and deprecated legacy metrics/tracing modules by Roland Beisel in #363OutboxRecordMetadataand documented handler access to delivery state by Roland Beisel in #365Breaking Changes
spring.rabbitmq.publisher-confirm-type=correlated; Rabbit auto-configuration now validates this because outbox processing depends on broker acceptance. Ifnamastack.outbox.rabbit.fail-on-unroutable=trueis enabled, also configurespring.rabbitmq.publisher-returns=trueandspring.rabbitmq.template.mandatory=true.New Contributors
🙏 Contributors
Special thanks to everyone who contributed to this release:
Full Changelog: namastack/namastack-outbox@v1.6.0...v1.7.0
v1.6.0: Namastack Outbox v1.6.0What's New
JPA Schema Validation and DDL Compatibility Improvements (GH-288, GH-289)
This release introduces comprehensive JPA schema validation tests for all supported databases and
fixes DDL compatibility issues for
OutboxRecordEntity.payloadandOutboxRecordEntity.context.These fields now use Hibernate's dialect-aware large Unicode text mapping, resolving validation
failures and mismatches with shipped DDL schemas—especially for Oracle, SQL Server, MySQL, MariaDB,
and H2. See the detailed migration and impact notes below.
Impact
ddl-auto=noneddl-auto=validateand new schemaddl-auto=validateand existing schemaDatabase Notes
NCLOBcolumns now validate correctly.TEXTcolumns now validate correctly.contextshould beNVARCHAR(MAX)instead ofVARCHAR(MAX).payloadandcontextshould beLONGTEXT CHARACTER SET utf8mb4.payloadandcontextshould beLONGTEXT CHARACTER SET utf8mb4.payloadandcontextshould beCLOB.Migration Scripts
SQL Server
MySQL
MariaDB
H2
What's Changed
issues by @rolandbeisel in #289
in #291
New Contributors
🙏 Contributors
Special thanks to all contributors who made this release possible:
Full Changelog: namastack/namastack-outbox@v1.5.0...v1.6.0
v1.5.0: Namastack Outbox v1.5.0What's New
MongoDB support (GH-188)
Added full MongoDB persistence support for the outbox pattern. The new
namastack-outbox-mongodbandnamastack-outbox-starter-mongodbmodules provide a complete MongoDB-backed implementation including record, instance, and partition assignment repositories, auto-configuration, and schema setup. MongoDB transaction management is enabled by default.Thanks to @Stellarhold170NT for this contribution.
Handler-level
supportshook for filtering outbox records (GH-274)Introduced a
supports(payload, metadata)method onOutboxHandler, allowing handlers to opt out of record creation for specific payloads before they are scheduled. This enables conditional outbox record filtering at the handler level. The default implementation returnstruefor full backward compatibility.Time-based properties as
java.time.Duration(GH-267)All time-based configuration properties now accept
java.time.Durationvalues (e.g.,PT5S,10s), improving consistency and readability.Thanks to @dagframstad for this contribution.
Row mappers extracted to repositories (GH-272)
JDBC row mappers have been moved into the repository layer, improving modularity and testability. Thanks to @dagframstad for this contribution.
What's Changed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.