mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-11 19:34:01 +01:00
Krzysztof kuhy Rudnicki
1c98d39ddb
Some checks are pending
crdt_sync_flutter tests / test (push) Waiting to run
design_system tests / test (push) Waiting to run
file length / file-length (push) Waiting to run
github_device_auth tests / test (push) Waiting to run
md-naming / markdown naming convention (push) Waiting to run
palette drift / palette (push) Waiting to run
shared gate tests / gate unit tests (push) Waiting to run
sync_settings_ui tests / test (push) Waiting to run
Exact-pins every registry dependency (crypto 3.0.7, google_sign_in 7.2.0, http 1.6.0, shared_preferences 2.5.5, url_launcher 6.3.2, uuid 4.6.0) and takes flutter_secure_storage 10.3.1 -> 11.0.0, a major. The major is safe here for a specific reason, not by assumption. 11.0.0 removes the algorithms deprecated in v10 and makes data written by them unreadable -- but this package has been on ^10.x throughout, and v10 migrated that data automatically. It also removes `encryptedSharedPreferences` and `sharedPreferencesName` from `AndroidOptions`; keystore.dart constructs a bare `FlutterSecureStorage()` and passes no AndroidOptions at all, so neither is reachable from here. The remaining break is minSdk 24 / compileSdk 37, which consuming apps inherit from `flutter.minSdkVersion` (Flutter 3.35 already raised its own floor to 24) and which fails a Gradle build loudly if wrong. Analyze clean, 88 tests green, coverage held at 202/202 (100%). Also installs the dependency-freshness gate in pre-commit -- the first repo to carry it. Pre-commit only, not CI: the other ten manifests here are not upgraded yet, and `--all` in CI would be permanently red until they are. The `files:` regex means a source-only commit makes zero network requests. Proven in both directions through the hook itself, not just the CLI: crdt_sync_flutter/pubspec.yaml passes, github_device_auth/pubspec.yaml fails and names http ^1.2.0 and url_launcher ^6.3.0, and a .dart path is skipped by the filter. Version 0.2.1 -> 0.3.0; consumers move their git pins after the tag. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK
60 lines
2.9 KiB
YAML
60 lines
2.9 KiB
YAML
# Repo-wide gate for the shared 250-line file cap (refactor_claude_todo.md).
|
|
#
|
|
# A file that cannot be read in one piece forces re-reads and partial edits,
|
|
# which is the largest avoidable cost in an LLM-assisted workflow. A refactor
|
|
# without a gate silently regrows, so this is the part that makes it stick.
|
|
#
|
|
# Checks only the files in the commit, so an unrelated commit never breaks on
|
|
# a violation it did not introduce, and it FAILS (exit 1) rather than warning.
|
|
# No baseline and no allowlist -- those are suppressions.
|
|
#
|
|
# The subprojects (gatelock/, crdt-sync/, web_ui/, design_system/,
|
|
# sync_settings_ui/) each keep their own .pre-commit-config.yaml for their own
|
|
# linters, and carry this same hook so committing with one of those configs is
|
|
# gated too. This root config is what `pre-commit install` wires up, and it is
|
|
# the only one that covers the subprojects without a config of their own
|
|
# (aur-publish/, guard-lib/, crdt_sync_dart/, file_length/, ...).
|
|
#
|
|
# The path is repo-relative on purpose. pre-commit always runs hooks from the
|
|
# git root, so this resolves the same locally and on a CI runner -- an absolute
|
|
# /home/... path exits 127 in Actions, which is how this was first written.
|
|
repos:
|
|
- repo: local
|
|
hooks:
|
|
- id: file-length-cap
|
|
name: file length <= 250 lines
|
|
entry: bash scripts/check_file_length.sh
|
|
language: system
|
|
pass_filenames: true
|
|
|
|
# Four markdown namespaces (README / CLAUDE* / DOCS* / TODO*), plus the
|
|
# rule that a TODO carries "REMOVE ME AFTER FINISH" and nothing else may.
|
|
# Shared gate in ~/utils owns the namespaces and the exemption list, so
|
|
# one repo's idea of a valid name cannot drift from every other repo's.
|
|
- id: md-naming
|
|
name: markdown naming convention
|
|
entry: scripts/check_md_naming.sh
|
|
language: system
|
|
files: \.(md|markdown)$
|
|
|
|
# Every dependency on its ecosystem's newest STABLE release, exact-pinned
|
|
# so the question is mechanically answerable at all.
|
|
#
|
|
# `files:` is what keeps this cheap: a commit touching only source makes
|
|
# ZERO network requests, and manifest commits mostly hit a 6h disk cache.
|
|
#
|
|
# Runs WITHOUT --strict on purpose. Offline it degrades to the cached
|
|
# answer and passes with a loud banner; `--no-verify` is banned here, so
|
|
# a hook that hard-failed on a flaky connection would leave no way to
|
|
# commit at all. CI, always online, is the strict authority.
|
|
- id: dependency-freshness
|
|
name: dependencies on newest stable
|
|
entry: bash scripts/check_dependency_freshness.sh
|
|
language: system
|
|
pass_filenames: true
|
|
files: >-
|
|
(pubspec\.(yaml|lock)|pyproject\.toml|requirements.*\.txt|uv\.lock
|
|
|package\.json|package-lock\.json|pnpm-lock\.yaml
|
|
|Cargo\.(toml|lock)|go\.(mod|sum)
|
|
|\.fvmrc|\.nvmrc|\.python-version)$
|