build(deps): bump @nestjs/microservices from 11.1.12 to 11.1.19#45
build(deps): bump @nestjs/microservices from 11.1.12 to 11.1.19#45dependabot[bot] wants to merge 1 commit intodevelopfrom
Conversation
Bumps [@nestjs/microservices](https://github.com/nestjs/nest/tree/HEAD/packages/microservices) from 11.1.12 to 11.1.19. - [Release notes](https://github.com/nestjs/nest/releases) - [Commits](https://github.com/nestjs/nest/commits/v11.1.19/packages/microservices) --- updated-dependencies: - dependency-name: "@nestjs/microservices" dependency-version: 11.1.19 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
1 similar comment
|
|
Greptile SummaryAutomated Dependabot bump of Confidence Score: 5/5Safe to merge — straightforward patch-level bump with only bug fixes and no breaking changes. Both No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["@nestjs/microservices@11.1.12"] -->|Dependabot bump| B["@nestjs/microservices@11.1.19"]
B --> C["Fix: stack overflow in JsonSocket.handleData()"]
B --> D["Fix: Kafka consumer CRASH event listener"]
B --> E["Fix: NATS serializer packet header preservation"]
Reviews (1): Last reviewed commit: "build(deps): bump @nestjs/microservices ..." | Re-trigger Greptile |
Bumps @nestjs/microservices from 11.1.12 to 11.1.19.
Release notes
Sourced from
@nestjs/microservices's releases.... (truncated)
Commits
6730995chore(release): publish v11.1.19 releasebcc036dMerge pull request #16762 from burhanharoon/fix/kafka-consumer-crash-event-li...d3deafechore: remove redundant comments298857efix(microservices): prevent stack overflow in jsonsocket.handledata()77063fbfix(microservices): use backing field for consumer crash event listener3c1cc5fchore(release): publish v11.1.18 release848a6fbfix(microservices): escape msvc pattern keys9e6774bfix(microservices): preserve packet headers in nats serializer5a05f52chore: update readme447a373chore(release): publish v11.1.17 releaseDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.