Skip to content

Commit 3219f6d

Browse files
committed
readme
1 parent 100a3fc commit 3219f6d

File tree

1 file changed

+12
-6
lines changed

1 file changed

+12
-6
lines changed

README.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -78,14 +78,20 @@ This ensures upgrades stay on your radar without overwhelming you. No more "oops
7878

7979
We know we're behind the latest versions of our dependencies, but where to start? Which versions should be force to update first? We can get lot of conflicts if we try to bump wrong end of knot.
8080

81-
Instead, let composer handle it. How? We open-up package versions to the next version:
81+
Instead, let Composer handle it. How? We open-up package versions to the next version:
82+
83+
```bash
84+
vendor/bin/jack open-versions
85+
```
86+
87+
This command opens up 5 versions to their next nearest step, e.g.:
8288

8389
```diff
8490
{
8591
"require": {
8692
"php": "^7.4",
87-
- "symfony/console": "^5.0"
88-
+ "symfony/console": "^5.0|^6.0"
93+
- "symfony/console": "5.1.*"
94+
+ "symfony/console": "5.2.*|5.2.*"
8995
},
9096
"require-dev": {
9197
- "phpunit/phpunit": "^9.0"
@@ -95,14 +101,14 @@ Instead, let composer handle it. How? We open-up package versions to the next ve
95101
}
96102
```
97103

98-
This "opens up" 5 versions without forcing updates. If no blockers exist, Composer will upgrade to the next version.
99-
100-
Then we run composer and let it do the work:
104+
Then we run Composer to do the work:
101105

102106
```bash
103107
composer update
104108
```
105109

110+
If no blockers exist, Composer will update packages to their next version.
111+
106112
<br>
107113

108114
To change the number of packages, use `--limit` option:

0 commit comments

Comments
 (0)