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

[WFCORE-6039] Upgrading JBoss MSC to 1.5.0.Beta3 #5196

Merged
merged 1 commit into from Nov 2, 2022

Conversation

ropalka
Copy link
Contributor

@ropalka ropalka commented Aug 31, 2022

@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label Aug 31, 2022
@ropalka ropalka changed the title [WFCORE-6039] Upgrading JBoss MSC to 1.5.0.Beta1 [WFCORE-6039] Upgrading JBoss MSC to 1.5.0.Beta2 Aug 31, 2022
@bstansberry
Copy link
Contributor

@ropalka I put the 20.x label (i.e. WF 28) on this as we are past the point of integrating Betas into WildFly 27. We need to be getting the existing beta components moved to final releases over the next 10 days.

@ropalka
Copy link
Contributor Author

ropalka commented Sep 2, 2022

Sure, no problem @bstansberry .

@github-actions
Copy link

There has been no activity on this PR for 45 days. It will be auto-closed after 90 days.

@github-actions github-actions bot added the Stale label Oct 18, 2022
@ropalka ropalka changed the title [WFCORE-6039] Upgrading JBoss MSC to 1.5.0.Beta2 [WFCORE-6039] Upgrading JBoss MSC to 1.5.0.Beta3 Oct 19, 2022
@yersan
Copy link
Collaborator

yersan commented Oct 31, 2022

/retest

@github-actions github-actions bot removed the Stale label Nov 1, 2022
@yersan yersan added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Nov 2, 2022
@yersan yersan merged commit 6cefc1c into wildfly:main Nov 2, 2022
@ropalka ropalka deleted the WFCORE-6039 branch November 2, 2022 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
3 participants