Another releaseAs prerelease and preid chat

[rcompton78]

I have just read a few other discussions and issues around prerelease and preid. I am having issues with an alpha/beta release and was wondering if I was doing something wrong.

I have noticed this behavior with version --releaseAs prerelease --preid alpha. Later I explain that not specifying a preid seems to work.

• If pkg has no previous [email protected] tags, then the system wants to start with @0.0.1-alpha.X. Would we not want to start with the highest current tag, add the appropriate bump and with the alpha tag?
• If I manually added the alpha tag to a previous commit, say pkg-0.1.2-alpha.0 - then tag the last commit for pkg with pkg-0.1.3, the system would try to set as pkg-0.2.3-alpha-1. It filters out anything that doesn't have the alpha tag and tries to bump that.

Looking in the try-bump.js that uses get-last-version.js I see

    const versions = tags
        .map((tag) => tag.substring(tagPrefix.length))
        .filter((v) => {
        if (includePrerelease) {
            const { prerelease } = semver.parse(v);
            return preid ? prerelease[0] === preid : true; 
        }
        return semver.prerelease(v) === null;
    });

The line "return preid ? prerelease[0] === preid : true;" made me think that if I don't use preid, the system would work as I think it should be. I tested and sure enough.

Am I missing something or is this a possible bug?