You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in the 16.0 branch of the OCA/crm repository, the pylint-odoo version specified in the pre-commit configuration is 8.0.19, while the latest release is currently 9.2.0.
I’m curious about the update strategy for these pre-commit checks. Will the version of pylint-odoo be updated eventually in the 16.0 branch, or is 8.0.19 intentionally fixed for this branch?
Thanks.
The text was updated successfully, but these errors were encountered:
yibudak
changed the title
Question: How OCA Distribute Pre-commit Rules?
Question: How OCA Distribute pre-commit Rules?
Dec 26, 2024
yibudak
changed the title
Question: How OCA Distribute pre-commit Rules?
Question: How Does OCA Distribute and Update Pre-Commit Rules?
Dec 26, 2024
Versions are normally pinned for existing branches, and reviewed when a new version arises, pulling that new linter versions only for this new branch. The reason is to keep maximum compatibility with existing merged code (as the new linter version may bring some new checks that can turn the branch red). If any critical aspect requires the version bumping, then it can be discussed and incorporated.
Hello,
I noticed that in the 16.0 branch of the OCA/crm repository, the pylint-odoo version specified in the pre-commit configuration is 8.0.19, while the latest release is currently 9.2.0.
I’m curious about the update strategy for these pre-commit checks. Will the version of pylint-odoo be updated eventually in the 16.0 branch, or is 8.0.19 intentionally fixed for this branch?
Thanks.
The text was updated successfully, but these errors were encountered: