- last update
over 1 year ago 17 pass -
bbrala →
committed 72b777b7 on 8.x-3.x authored by
dmitry.korkhau →
Issue #3262264 by dmitry.korkhau, bbrala, bradjones1, johnny5th:...
-
bbrala →
committed 72b777b7 on 8.x-3.x authored by
dmitry.korkhau →
- 🇳🇱Netherlands bbrala Netherlands
Been a while, and been used in prod so im gonna merge this. Thanks all.
- Status changed to Fixed
over 1 year ago 2:29pm 31 August 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
over 1 year ago 5:44am 20 October 2023 - 🇦🇺Australia dpi Perth, Australia
Informational only, feel free to disregard. Noting its in a tagged release, not dev. etc.
- 🇳🇱Netherlands bbrala Netherlands
I'm always a bit confused if I should change version to the release version or not. I could do that, but not sure what the convention is.
- 🇦🇺Australia dpi Perth, Australia
Github has a thing where on MR's it displays the first tagged release code can be found in the timeline/comment list.
In my projects, sometimes I'll post the tag of the first release that code for an issue can be found in.
The info is quite helpful when chasing down whether composer updates included a patch or whether it needs a reroll. Or other tweaks to constraints are necessary: such as stability, removing -dev/locked to commit, loosening constraints.
In the end, feel no obligation to change. Just trying to be helpful.