Until now, forge detection only knew the SaaS hostnames — a self-hosted GitLab or Gitea on git.company.com came back as "no forge", so you had to set forge = "gitlab" yourself to get automatic release creation.
Now, when FerrFlow doesn't recognise the remote's hostname, it probes the host's API over HTTPS to figure out what it is:
The probe is unauthenticated, short (a ~2s timeout), best-effort, and cached — so a run checks a given host at most once, and a hostname FerrFlow already knows never touches the network. You only need to set forge explicitly now if your host isn't reachable over HTTPS or you'd rather skip the probe.