chore(melos): updated dependencies to latest stable versions

invertase / melos

🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.

https://melos.invertase.dev/~melos-latest

Apache License 2.0

1.11k stars 198 forks source link

chore(melos): updated dependencies to latest stable versions #618

Closed OutdatedGuy closed 8 months ago

OutdatedGuy commented 8 months ago

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
[x] 🗑️ chore -- Chore

docs-page[bot] commented 8 months ago

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

melos.invertase.dev/~618

Documentation is deployed and generated using docs.page.

CLAassistant commented 8 months ago

All committers have signed the CLA.

OutdatedGuy commented 8 months ago

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 commented 8 months ago

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.