Update reference regex to not break on beta versions

[davepagurek]

Most appropriate sections of the p5.js website?

Reference

What is your operating system?

Mac OS

Web browser and version

Firefox

Actual Behavior

In the reference builder, we add a v to the start of the latest release if it seems to all be numeric:

p5.js-website/src/scripts/parsers/reference.ts

Lines 26 to 28 in df16dae

	if (/^\d+\.\d+\.\d+$/.exec(latestRelease)) {
	latestRelease = 'v' + latestRelease;
	}

This regex breaks for beta releases, e.g. 2.0.0-beta.5. We're about to release 2.0 so we won't have beta releases for a while, but we may want this working for the future when we do beta 3.0 releases.

Expected Behavior

The regex should match strings like 2.0.0-beta.5 too.

Steps to reproduce

Manually edit this

p5.js-website/src/globals/p5-version.ts

Line 1 in df16dae

export const p5Version = "v2.0.0-beta.8" as const;

to not start with a v

Would you like to work on the issue?

Feel free to take this on for me!

[webermayank]

hey @davepagurek , i would like to take this on and update regex to not break.
The regex should accept beta versions too — e.g., 2.0.0-beta.5 right?
if there are any other things that you would like me to keep in mind, please state that, i will address those.

[ksen0]

@webermayank thanks for volunteering, and yes, both "1.2.3" and "1.2.3-beta.4" should be covered (so that 'v' is correctly prepended). Please make 2 PRs for both main and 2.0. Thank you!

[webermayank]

Hey @ksen0 , i just have a quick question
In the description of this issue, in Steps to reproduce - @davepagurek mentioned

Manually edit this

p5.js-website/src/globals/p5-version.ts

Line 1 in df16dae

export const p5Version = "v2.0.0-beta.8" as const;

to not start with a v

But i just recently saw that in this commit, this thing has already been implemented in p5-version.ts or am i wrong about this whole information ?

so should i leave this part and just focus in regex in p5.js-website/blob/main/src/scripts/parsers/reference.ts ?

[ksen0]

@webermayank thanks for working on this and for your patience! First, the builds were breaking for an unrelated reason which should not be resolved (this one #831)

But i just recently saw that in this commit, this thing has already been implemented in p5-version.ts or am i wrong about this whole information ?

Good question, this is more about preventing future problems with beta deployments, while the memory of what goes wrong here is still fresh.