tree-company/linting-config
5
0
Fork 0
mirror of https://github.com/tree-company/linting-config.git synced 2026-04-20 18:39:34 +02:00
Code Issues Projects Releases Packages Wiki Activity
No description
185 commits 1 branch 8 tags 3.9 MiB
  • JavaScript 100%
Find a file
Exact
dependabot[bot] b4c9c6de1f
 Bump prettier from 3.8.2 to 3.8.3 (#255) 
Bumps [prettier](https://github.com/prettier/prettier) from 3.8.2 to 3.8.3.
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/3.8.2...3.8.3)

---
updated-dependencies:
- dependency-name: prettier
  dependency-version: 3.8.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-04-20 16:43:46 +02:00
.github Bump release-drafter/release-drafter from 6 to 7 (#250) 2026-04-17 16:30:11 +02:00
eslint-config Bump @eslint/js from 9.39.2 to 9.39.4 (#253) 2026-04-17 16:26:41 +02:00
stylelint-config Update the minimum version to stylelint v17 (#249) 2026-04-20 16:39:45 +02:00
.gitignore Setup a separate repo for linting configs 2023-03-01 15:17:15 +01:00
eslint.config.js Fix react config 2024-05-06 12:55:54 +02:00
LICENSE Setup a separate repo for linting configs 2023-03-01 15:17:15 +01:00
logo_tree.png Setup a separate repo for linting configs 2023-03-01 15:17:15 +01:00
package.json Bump prettier from 3.8.2 to 3.8.3 (#255) 2026-04-20 16:43:46 +02:00
README.md Setup a separate repo for linting configs 2023-03-01 15:17:15 +01:00
yarn.lock Bump prettier from 3.8.2 to 3.8.3 (#255) 2026-04-20 16:43:46 +02:00

README.md

@tree-company/linting-config

This repository contains the default linting configs for all Tree company projects. These configs are published as separate packages:

Except for patch versions, all packages are released at the same time, with the same version.

Releasing a new version

If you changed some of the default configs, you can easily publish a new version. We always publish a version of all packges - even if nothing changed.

To create a new release:

  • Edit the version in the all the package.json files
  • Create a new tag
  • Push your changes to github

Logo Tree company