Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[22.x][WFCORE-6547] Upgrading JBoss Marshalling to 2.1.3.SP1 #5712

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

ropalka
Copy link
Contributor

@ropalka ropalka commented Oct 11, 2023

@yersan yersan added the 22.x label Oct 11, 2023
@yersan yersan changed the title [WFCORE-6547] Upgrading JBoss Marshalling to 2.1.3.SP1 [22.x][WFCORE-6547] Upgrading JBoss Marshalling to 2.1.3.SP1 Oct 11, 2023
@yersan
Copy link
Collaborator

yersan commented Oct 11, 2023

Waiting for WildFly to open the 30.x branch

@yersan yersan added the hold Do not merge this PR label Oct 11, 2023
@yersan
Copy link
Collaborator

yersan commented Oct 11, 2023

/retest

@yersan
Copy link
Collaborator

yersan commented Oct 12, 2023

Somehow, some test results are not shown in the UI. To review, check the aggregator for this PR and the results of its dependencies

@luck3y
Copy link
Contributor

luck3y commented Oct 12, 2023

/retest

2 similar comments
@luck3y
Copy link
Contributor

luck3y commented Oct 12, 2023

/retest

@luck3y
Copy link
Contributor

luck3y commented Oct 12, 2023

/retest

@yersan yersan added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Oct 16, 2023
@yersan yersan merged commit 4479860 into wildfly:22.x Oct 16, 2023
@yersan
Copy link
Collaborator

yersan commented Oct 16, 2023

Thanks for backporting it, @ropalka

@ropalka ropalka deleted the WFCORE-6547_22x branch October 18, 2023 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hold Do not merge this PR ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants