Skip to content

Releases: Skyscanner/eslint-config-skyscanner

22.5.1

14 Aug 09:48
a2495ee
Compare
Choose a tag to compare

What’s Changed

Fixed

22.5.0

19 Jul 09:41
154e583
Compare
Choose a tag to compare

What’s Changed

Dependency updates

22.4.0

07 Jul 09:22
00a4b15
Compare
Choose a tag to compare

What’s Changed

Added

Functionality of the no-enum has not changed, it has simply been changed from an unmaintained third party package to a definition within @skyscanner/eslint-plugin-rules:

If someone was previously suppressing using comments like

// eslint-disable-next-line typescript-enum/no-enum

they will now need to use

// eslint-disable-next-line @skyscanner/rules/no-enum

22.3.1

19 Jun 09:41
6bd85ae
Compare
Choose a tag to compare

What’s Changed

Dependency updates

22.2.1

05 Jun 12:37
2201bba
Compare
Choose a tag to compare

What’s Changed

Fixed

22.2.0

03 Jun 13:47
86f34e8
Compare
Choose a tag to compare

What's Changed

  • ST-6572 : Enable ESLint to resolve TypeScript and Node imports by @mariamuzas in #841

New Contributors

Full Changelog: 22.1.0...22.2.0

22.1.0

23 May 14:21
6779a38
Compare
Choose a tag to compare

What’s Changed

Dependency updates

22.0.0

24 Apr 15:02
6e64acd
Compare
Choose a tag to compare

What’s Changed

Breaking

21.1.0

15 Apr 08:00
bab0637
Compare
Choose a tag to compare

What’s Changed

21.0.0

12 Apr 10:15
71bd1b7
Compare
Choose a tag to compare

What’s Changed

Breaking

https://github.com/prettier/eslint-config-prettier/releases/tag/v10.0.0

This is not expected to be a breaking change for Skyscanner repositories. The changes included should not impact consumers using Skyscanner's standard linting setup, however for other consumers or those who have customised their setup there are changes as listed below.

As noted in the PR that generated the major version of eslint-config-prettier:

v10 should be compatible mostly, but it adds @stylistic/* support, I released it as major because not everyone is using @stylistic/*, there could be a tiny chance to break.

Additionally, we migrated the releasing tool to changesets and leave package.json and files structure untouched, so the file structure is different now.

Updated