chore(melos): updated dependencies to latest stable versions

[OutdatedGuy]

Description

Updated packages file and pub_updater to latest stable versions i.e. v7.0.0 and v0.4.0 respectively.

Also updated dependency versions in the melos.yaml file to properly bootstrap melos while using melos bootstrap.

Type of Change

• ✨ feat -- New feature (non-breaking change which adds functionality)
• 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
• ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 refactor -- Code refactor
• ✅ ci -- Build configuration change
• 📝 docs -- Documentation
• 🗑️ chore -- Chore

[docs-page]

To view this pull requests documentation preview, visit the following URL:

melos.invertase.dev/~618

Documentation is deployed and generated using docs.page.

[CLAassistant]

All committers have signed the CLA.

[spydon]

This does not pass the dependency constraints.

[spydon]

I don't think this change gives us anything, it will be more work maintaining those dependency ranges. It's better to wait with bumping these dependencies until we bump Dart.

[OutdatedGuy]

Yo @spydon, this is the same tactic we used while updating the http package in this commit.

Also because of these constraints, I'm unable to add melos as I'm using packages with the latest versions of pub_updater and file.

Additionally, we can later remove the range after the current melos is updated.

[spydon]

Yo @spydon, this is the same tactic we used while updating the http package in this commit.

Also because of these constraints, I'm unable to add melos as I'm using packages with the latest versions of pub_updater and file.

Additionally, we can later remove the range after the current melos is updated.

The dependencies of Melos should not affect your usage of it? If you have a package/app in the root I recommend that you move it into a sub-directory, for example packages/ for packages or apps/ for apps, because you shouldn't share the Melos workspace pubspec with it.