I just finished upgrading them from 1.3.2 to 1.4-rolling-202306130317 and the bgp configuration failed to commit, complaining about a missing remote-as on the neighbor. On 1.3.2 the config worked without issue.
old config:
[edit protocols bgp]
set neighbor wg3 interface v6only peer-group 'peers'
set peer-group peers address-family ipv4-unicast prefix-list export 'internal'
set peer-group peers address-family ipv4-unicast prefix-list import 'internal'
set peer-group peers address-family ipv4-unicast soft-reconfiguration inbound
set peer-group peers address-family ipv6-unicast prefix-list export 'internal-6'
set peer-group peers address-family ipv6-unicast prefix-list import 'internal-default-6'
set peer-group peers address-family ipv6-unicast soft-reconfiguration inbound
set peer-group peers capability extended-nexthop
set peer-group peers remote-as 'external'
after modifying the config as seen here it works without isse:
[edit protocols bgp]
set neighbor wg3 interface v6only peer-group 'peers'
set neighbor wg3 interface v6only remote-as 'external'
set peer-group peers address-family ipv4-unicast prefix-list export 'internal'
set peer-group peers address-family ipv4-unicast prefix-list import 'internal'
set peer-group peers address-family ipv4-unicast soft-reconfiguration inbound
set peer-group peers address-family ipv6-unicast prefix-list export 'internal-6'
set peer-group peers address-family ipv6-unicast prefix-list import 'internal-default-6'
set peer-group peers address-family ipv6-unicast soft-reconfiguration inbound
set peer-group peers capability extended-nexthop
It’s not a big deal if going forward the remote-as must be configured directly on the neighbor, but a migration would be nice, to avoid losing the entire bgp config on an upgrade