chore: bump message broker version - #1243
Merged
Merged
Conversation
TCMeldrum
requested review from
simonfernandes
and removed request for
a team
October 29, 2025 11:03
simonfernandes
approved these changes
Oct 29, 2025
bolmsten
approved these changes
Oct 29, 2025
TCMeldrum
enabled auto-merge (squash)
October 29, 2025 11:58
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
3 participants
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.
Description
This PR updates the version of the message broker in our backend service.
Motivation and Context
The message broker version upgrade is necessary to keep our application up-to-date with the latest improvements and bug fixes. This aligns with our continuous efforts to ensure the stability and efficiency of our application, and to provide the best experience for our users.
Changes
The major changes in this PR are as follows:
@user-office-software/duo-message-brokeris updated from1.6.0to1.8.0in bothpackage.jsonandpackage-lock.jsonfiles.package-lock.jsonto match the new version of the message broker.These changes ensure that our application will use the updated version of the message broker.
How Has This Been Tested?
Fixes Jira Issue
https://jira.esss.lu.se/browse/
Depends On
Tests included/Docs Updated?