There's a good discussion at
https://github.com/wildfly-extras/wildfly-graphql-feature-pack/issues/202
-- I just wanted to call attention to it as I know others are interested in
either GraphQL in particular or the general topic of the lifecycle of
feature packs.
N.B. I'm not wanting to fork the discussion; I'm just calling attention to
it.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
We've supported OIDC request parameters since WildFly 32 and additional OIDC scope values since WildFly 33. Now, we'd like to promote this feature to community stability for WildFly 37. We need someone from the security team to act as the SME, while Brian will provide the outside perspective. If anyone is interested in helping out, I'd greatly appreciate it.
The feature issue: https://github.com/wildfly/wildfly-proposals/issues/720
The analysis: https://github.com/wildfly/wildfly-proposals/pull/722
The main work here is analyze and approve the PR: https://github.com/wildfly/wildfly/pull/18471.
Thanks
Pedro Silva
Hi,
The final date for PRs to WildFly 36.0.1.Final is this coming Tuesday 6th
of May.
The branches any fixes or component upgrades you would like to apply are:
* https://github.com/wildfly/wildfly-core/tree/28.x
* https://github.com/wildfly/wildfly/tree/36.x
Please make sure your pull requests also contain a link to any upstream PR
to main in the corresponding repo or add a quick comment explaining why a
PR to main is not required.
Thanks,
Kabir