Hi, We have now released WildFly Core 16.0.0.Final for the upcoming release of WildFly 24 and will start development of WildFly Core 17. We’ll take the opportunity to be early in the development cycle to change the default branch for wildfly/wildfly-core project from “master" to “main". GitHub has some instructions that should help with the move: https://github.com/github/renaming. It should work transparently at the project level and each contributor will just need to update their local environment. We also need to update all the CI scripts we are using to test WildFly Core. Once the switch is done, I’ll send another mail to inform each contributor with the steps to update their local environment. Best regards, Jeff -- Jeff Mesnil Principal Software Engineer Red Hat http://jmesnil.net/ _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Hi, The renaming of “master" to “main” branch for wildfly-core is over. If you go to https://github.com/wildfly/wildfly-core, you should have a notification to update your local environment. This includes running the following commands: —8<— git branch -m master main git fetch origin git branch -u origin/main main git remote set-head origin -a —8<— If you have opened PR against wildfly/wildfly-core, you have nothing to do, the change is automatic. The CI has been updated and I verified the PR jobs runs fine (from https://ci.wildfly.org/project/WildFlyCore_PullRequest?mode=builds). I tried to do a thorough change in all the WildFly Core jobs on https://ci.wildfly.org/project/WildFlyCore?mode=builds and most of the jobs are fine too. Best regards, Jeff -- Jeff Mesnil Principal Software Engineer Red Hat http://jmesnil.net/