Question: How do Pre-Releases Work?

[Evynglais]

Hi,

I'd like to use go-semantic-release to handle publishing pre-release tags, but wouldn't want it to interfere with the CHANGELOG/GitLab release generation.

Our flow is:

Dev Branch -> Test -> Approve MR -> Merge into Stage

Stage Branch -> Generate Pre-Release Version -> Test and Deploy Images with Version -> Merge into Main

Main Branch -> Release -> Tag Images with Version (and "latest") -> Deploy to Production

On Stage, that "Generate Pre-Release Version" - I'd like to use go-semantic-release for that, to generate a tag of some kind that identifies it as a follow-on, i.e., if the latest is 1.0.1, we'd want it to be 1.0.2-SNAPSHOT.

Current .semrelrc:

{
    "plugins": {
        "commit-analyzer": {
            "name": "default"
        },
        "ci-condition": {
            "name": "gitlab",
            "options": {
                "defaultBranch": "main"
            }
        },
        "changelog-generator": {
            "name": "default",
            "options": {
                "emojis": "true"
            }
        },
        "provider": {
            "name": "gitlab",
            "options": {
                "gitlab_projectid": "123456"
            }
        }
    }
}

Thanks,
Evynglai