🚀 Feature Request: Consider using prerelease tags based on the soon-to-be-verson

[GregBrimble]

Describe the solution

Right now, we cut prereleases as 0.0.0-${gitHash}. When making API requests, we send the User Agent as wrangler/${version}. This means the API is basically unable to see what rough version this particular Wrangler client is.

Instead, npm supports prerelease tags based off of the upcoming verison (e.g. 4.0.0-alpha.0 is a release candidate for 4.0.0). We could change how we generate our prerelease version tags and adopt something similar to this so we can better gate the behavior of our APIs in the future.

[RamIdeas]

I have thought this too. +1 to including the base version. Would work and be 'easier' to use the "runId" in the format: 3.24.0-beta.${runId} or 4.0.0-alpha.${runId}.

Can we also store our prereleases on npm rather than github? With tags for the HEAD of a PR: wrangler@pr-1234 -> 3.24.0-beta.${runId}