Closed
Description
Me and @divlo shipped 17.0.0-0
today, #203, following the merge of #193.
17.0.0-0
is a prerelease.
One can install it using eslint-config-standard@next
Being a pre-release, 17.0.0-0
comes with no guarantees in regards to support / breaking changes etc. It exists to facilitate early feedback, from the wider community as well from our selves.
Next steps before we will ship a stable release of 17.0.0
are:
- Merge new
standard-engine
intostandard
: feat: update standard-engine to v15 standard#1754 - Ship a new major of
eslint-config-standard-jsx
- Update
standard
to17.0.0-0
of this module + the new major ofeslint-config-standard-jsx
- Ship a
17.0.0-0
ofstandard
to start getting some feedback on ecosystem compatibility - When we're confident that the ecosystem is ready for a stable
17.0.0
, roll one for this module...- Ship a
17.x
compliant update tovscode-standard
(Add support for Standard 17 vscode-standard#375) - All of the external tests in
standard
passes (Tracking issuetest-external
standard#1777) -
standard-engine
generated types (Generate and publish types standard-engine#279) + CI succeeds
- Ship a
- ...and then a stable
11.0.0
ofeslint-config-standard-jsx
-
...and then a stableNot used, skipped12.0.0
ofeslint-config-standard-react
- ...and then a stable
15.0.0
ofstandard-engine
- ...and then a stable
17.0.0
ofstandard
... - ...and then new version of the long tail of
standard
-siblings, likesemistandard
... - ...then close this issue and the
17.0.0
milestone
In the meanwhile, please report any breakage you discover 🙏
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done