`@astrojs/upgrade` announces integration updates that are already up to date

[jurajkapsz]

Astro Info

Astro                    v5.0.0-beta.8
Node                     v20.11.1
System                   Linux (x64)
Package Manager          pnpm
Output                   static
Adapter                  @astrojs/node
Integrations             @astrojs/mdx
                         build/images
                         build/cleanup
                         @astrojs/sitemap

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

No response

Describe the Bug

Running pnpm dlx @astrojs/upgrade beta:

, but the to be updated packages are already up to date, from package.json:

  "dependencies": {
    "@astrojs/check": "^0.9.4",
    "@astrojs/mdx": "4.0.0-beta.3",
    "@astrojs/node": "9.0.0-beta.3",
    "@astrojs/sitemap": "^3.2.1",

Happens repeatedly.

Maybe it's because of the ^ package version denotion.

What's the expected result?

Already up to date packages should be marked as such/not processed.

Link to Minimal Reproducible Example

Not sure if there can be a stackblitz repro for this one.

Participation

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