src: mark config file as stable - #66431
marco-ippolito wants to merge 2 commits into
Conversation
|
Review requested:
|
9c195cc to
fa46cf3
Compare
fa46cf3 to
e546cdb
Compare
|
I would love for this to get to stable (I one of my recent favourites in node), but I think we still have an important unresolved issue (that I admittedly haven't raised properly): The schema(s) cite a specific node version, but that is not checked against the actual version of node running. So looking at the code, all looks well; and then it runs and 💥 This really reared its head with the recent breaking change of |
Signed-off-by: Marco Ippolito <marcoippolito54@gmail.com>
e546cdb to
c260c9c
Compare
that's because it's an experimental feature, it made no sense to make the breaking change a semver major. it's trivial to add a check to match the version |
For sure yes not a major; I would expect it on the current line (just not backported to a stable line).
Yeah, I'm suggesting we do that before marking this stable 🙂 |
|
Mind that this feature you are asking already partially xists: If you specify a |
Ish. It wouldn't have addressed the above problem though because it's only major (and the break was in a minor); but maybe that's a non-issue once it becomes stable? 🤔 |
Signed-off-by: Marco Ippolito <marcoippolito54@gmail.com>
yes because it is stable across majors, at worse node has a more features thatn the config file but not breaking changes |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #66431 +/- ##
==========================================
- Coverage 90.39% 90.38% -0.01%
==========================================
Files 792 792
Lines 275580 275717 +137
Branches 52840 52861 +21
==========================================
+ Hits 249104 249206 +102
- Misses 16897 16899 +2
- Partials 9579 9612 +33
🚀 New features to boost your workflow:
|
No description provided.