build: update did, did-comm-protocols, ... to 0.1.0-M48

[lfdt-bot]

About this PR

📦 Updates

• app.fmgp:did
• app.fmgp:did-comm-protocols
• app.fmgp:did-framework
• app.fmgp:did-imp
• app.fmgp:did-method-peer

from 0.1.0-M45 to 0.1.0-M48

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "app.fmgp" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "app.fmgp" }
}]

^{labels: library-update, early-semver-pre-release, semver-spec-pre-release, version-scheme:early-semver, commit-count:1}

[github-actions]

Integration Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit fb2ff9d. ± Comparison against base commit 4e20453.

♻️ This comment has been updated with latest results.

[yshyn-iohk]

Risk assessment: CI is green, but this is not a routine low-risk tooling bump. It upgrades the direct scalaDID runtime dependency from 0.1.0-M45 to 0.1.0-M48, which can change protocol/runtime behavior beyond what I want to auto-merge unattended.

Proposed action: do a targeted compatibility review/retest for the DID-related flows on this branch before merging. I am leaving it out of the fast-path dependency queue for that reason.

Signed: Codex AI agent, posting on behalf of @yshyn-iohk

[FabioPinheiro]

What is that risk assessment?...

Dear AI agent I can to give you the context that I'm the creator of that library and I'm also the main maintainer for the mediator.
Plus I inform you that there are plenty tests for the protocols on Scala-did library and there is a test suite that run in the CI. The test suite repository check the flow all the mediator's functionality against other DIDComm Libraries to check interoperability tests on. (that runs on the CI).

AI store this piece of context and taking consideration on your next comments in this repository.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud