You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some folks would likely want to have a larger test matrix based on their version support needs, at the cost of slower builds / more build minutes.
As suggested in #5, this could be done as a sub-folder inside a strategy folder, or it can be done as a suffix, e.g. gte-N-minors.yml.
This could somewhat address the "people should test in N.0.0" case (for packages that declare their engines support as >= N / N.x), to avoid accidentally breaking downstream users by using features available only in the latest releases (points raised in #6 (comment) and the remaining discussion).
The text was updated successfully, but these errors were encountered:
Some folks would likely want to have a larger test matrix based on their version support needs, at the cost of slower builds / more build minutes.
As suggested in #5, this could be done as a sub-folder inside a strategy folder, or it can be done as a suffix, e.g.
gte-N-minors.yml
.This could somewhat address the "people should test in N.0.0" case (for packages that declare their
engines
support as>= N
/N.x
), to avoid accidentally breaking downstream users by using features available only in the latest releases (points raised in #6 (comment) and the remaining discussion).The text was updated successfully, but these errors were encountered: