Maintenance branch vs prerelease branch in semantic-release for backporting a fix
Our project uses semantic-release with Conventional Commits, and we need to ship a bug fix to users still on the 1.x line while main has already moved to 2.x. The documented options are a maintenance branch (e.g., 1.x ) that publishes real patch versions, or a prerelease branch (e.g., beta ) that publishes dist-tagged prereleases consumers must opt into. Dur