tree-company/linting-config
3
0
Fork 0
mirror of https://github.com/tree-company/linting-config.git synced 2025-10-24 05:49:12 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
166 commits 7 branches 8 tags 1.6 MiB
Find a file
Exact
dependabot[bot] fb061d829a
 Bump eslint from 9.33.0 to 9.34.0 (#211) 
Bumps [eslint](https://github.com/eslint/eslint) from 9.33.0 to 9.34.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
- [Commits](https://github.com/eslint/eslint/compare/v9.33.0...v9.34.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-version: 9.34.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-08-29 16:53:32 +02:00
.github Bump actions/checkout from 4 to 5 (#210) 2025-08-29 16:53:23 +02:00
eslint-config Bump eslint-plugin-prettier from 5.5.3 to 5.5.4 (#208) 2025-08-14 09:25:46 +02:00
stylelint-config Bump stylelint-config-standard from 38.0.0 to 39.0.0 (#206) 2025-08-04 08:21:25 +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 eslint from 9.33.0 to 9.34.0 (#211) 2025-08-29 16:53:32 +02:00
README.md Setup a separate repo for linting configs 2023-03-01 15:17:15 +01:00
yarn.lock Bump eslint from 9.33.0 to 9.34.0 (#211) 2025-08-29 16:53:32 +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