refactor: switch all E2E tests to 2025/1 DSP version #5427
Merged
Conversation
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
ndr-brt
force-pushed
the
5424-switch-tests-2025-1
branch
2 times, most recently
from
68046cd to
1378f4b
Compare
|
This pull request is stale because it has been open for 14 days with no activity. |
ndr-brt
force-pushed
the
5424-switch-tests-2025-1
branch
from
1378f4b to
8878c5e
Compare
wolf4ood
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What this PR changes/adds
Switch all the E2E tests to DSP 2025/1
Why it does that
Briefly state why the change was necessary.
Further notes
json-ld-libmodule, this way they can be loaded also in theParticipantclass to setup a proper client jsonld service, instead to get the one from the connectorProtocolrecord instead of the two separated string variablesWho will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes #5424
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.