- Issue created by @phenaproxima
- ๐บ๐ธUnited States phenaproxima Massachusetts
I know this is post-MVP, but adding to the sprint to keep people busy.
- ๐ฎ๐ณIndia omkar.podey
omkar.podey โ made their first commit to this issueโs fork.
- Assigned to omkar.podey
- @omkarpodey opened merge request.
- Issue was unassigned.
- Status changed to Needs review
about 2 years ago 4:15am 28 March 2023 - ๐บ๐ธUnited States phenaproxima Massachusetts
I have to research this more closely, but I'm not entirely certain the test coverage here is correct.
I might be misreading it, but it looks like it's testing how we handle packages that are at dev stability, but that's not what this issue is about. This is about updating packages that are dev requirements -- i.e., they're listed in composer.json's
require-dev
section, regardless of stability.Am I completely off-base here?
- Status changed to RTBC
about 2 years ago 2:30pm 28 March 2023 - ๐บ๐ธUnited States phenaproxima Massachusetts
I think my suspicion was correct.
The good news is that it was really easy to adjust the test - everything was already pretty much perfect.
-
phenaproxima โ
committed bd0ef69e on 3.0.x authored by
omkar.podey โ
Issue #3347267 by omkar.podey, phenaproxima:...
-
phenaproxima โ
committed bd0ef69e on 3.0.x authored by
omkar.podey โ
- Status changed to Fixed
about 2 years ago 3:03pm 28 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.