🦋 Changeset detected

Latest commit: 9242dcd

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Rebased onto latest main (was 146 commits behind, now 0 behind / 1 ahead — status: ahead instead of diverged, so mergeable_state should unblock once CI re-runs green). All 25 @astrojs/upgrade tests pass locally including the new does not downgrade packages when a requested tag points to an older version regression test.

The fix is still relevant: main's verify.ts still uses the bare semverCoerce(packageInfo.currentVersion)\! without the parseCurrentVersion helper, so the downgrade bug from #17024 persists. cc @ocavue since you own packages/upgrade/
Happy to adjust the approach or the test if you'd prefer a different shape.

@farrosfr It appears the fix for this issue has already been merged and published in #17216

Hi @kydecker Thanks for checking in.

While #17216 handles stable-version fallbacks, it misses when the current version is a newer prerelease (e.g. 7.0.0-beta.3) and the requested beta tag is older (e.g. 7.0.0-beta.2). On main, this falls back to latest (e.g. ^6.4.5), which still results in a downgrade.

This PR has been rebased and updated with a minimal fix and a unit test to prevent this prerelease-to-prerelease downgrade. Let me know what you think!