Yes that is exactly what I observed. It was a mix of new defaults in line with best practices that come with FRR 7.5 vs the 7.3 you would have been running on pfSense 2.4.5 as well as some bugs that are now in redmine.
If you see your BGP session as "Established" but your prefixes are not being announced checklist here:
In your environment, are the prefixes to be announced in your local RIB or are they not ? If not, you need to set a flag
no bgp network import-check
This is sort of exposed in the GUI but currently broken because if you uncheck it in the GUI the new FRR 7.5 default means it is inherently enabled anyway. Thus you need to work with RAW CONFIG for now.
Do you have any sort of filtering for your announcements ? A route map or prefix list ? Or do you just go Services -> FRR BGP and drop the prefixes in there. If so, you will need to enable a policy to satisfy the new default of bgp ebgp-requires-policy
You could, but probably should not disabled this check with
no bgp ebgp-requires-policy
This is exposed in the GUI and seems to work but it is not regarded best practice. Better you create a prefix list with the stuff you want to announce and then attach it to your neighbor(s).
Edit: Since this effects 2.5.0-release and we are no longer using a dev snapshot: There is more detail in this thread I have in the FRR sub-forum