(minor) pnpm create astro --ref next ⇒ Houston: v4.16.14 instead of v5.0.0-beta.10

[ppo]

Astro Info

(not relevant)

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

When executing pnpm create astro --ref next, the Houston animation mentions the wrong Astro version. It displays v4.16.14, while it actually installs 5.0.0-beta.10.

Houston:
Welcome to astro v4.16.14, Pascal!

What's the expected result?

Houston:
Welcome to astro v5.0.0-beta.10, Pascal!

Link to Minimal Reproducible Example

https://example.com/NOT-RELEVANT

Participation

• I am willing to submit a pull request for this issue.

[bluwy]

I think this is working as expected, however it should be pnpm create astro@beta --ref next that prints the beta version, so it's installing the beta version of create-astro. But that doesn't seem to work so I'll mark this as a bug then.

We likely have to update here:

astro/packages/create-astro/src/actions/context.ts

Line 96 in b140a3f

version: getVersion(packageManager, 'astro', process.env.ASTRO_VERSION),

astro/packages/create-astro/src/messages.ts

Lines 63 to 72 in b140a3f

	export const getVersion = (packageManager: string, packageName: string, fallback = '') =>
	new Promise<string>(async (resolve) => {
	let registry = await getRegistry(packageManager);
	const { version } = await fetch(`${registry}/${packageName}/latest`, {
	redirect: 'follow',
	})
	.then((res) => res.json())
	.catch(() => ({ version: fallback }));
	return resolve(version);
	});

So we're fetching the /beta tag instead of /latest during pnpm create astro@beta.