mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-10 20:07:16 +01:00
Krzysztof kuhy Rudnicki
d67c770cc9
Python side: gatelock v0.7.1 -> v0.7.2 and crdt-sync v0.9.0 -> v0.9.1 (both re-cut so consumers stop resolving pre-upgrade constraints), plus every `>=` floor turned into an exact pin -- five majors among them (mypy 1 -> 2.3.1, pylint 3 -> 4.0.7, pytest 8 -> 9.1.1, pytest-cov 4 -> 7.1.0, ruff 0.8 -> 0.16.5) and mcp pinned at 2.1.1. `scripts/ci_mirror.sh` builds a clean venv from requirements.txt and runs the whole CI set: 1146 tests, 100% branch coverage, no lint or type finding. workout_app: sync_settings_ui v0.1.0 -> v0.4.1 and ten exact pins, with the flutter_secure_storage 11 chain (compileSdk 37 / AGP 9.3.2 / Gradle 9.7.1). 411 tests green, analyzer clean, release APK builds. CI's Flutter pin was 3.44.6 while `.fvmrc` says 3.47.2 -- the drift that made kuhylog red on a commit that is clean locally. Both workflows now say 3.47.2, and the gate reads that pin from now on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK
58 lines
2.1 KiB
YAML
58 lines
2.1 KiB
YAML
name: dependency freshness
|
|
|
|
# Every dependency on its ecosystem's newest STABLE release, enforced on push
|
|
# as well as at commit time. The local pre-commit hook only sees the manifests
|
|
# in a commit and can be skipped entirely by a fresh clone that never ran
|
|
# `pre-commit install`; this runs `--all` over the whole repo.
|
|
#
|
|
# `--strict` is CI-only. Offline the gate degrades to its cached answer and
|
|
# passes, because `--no-verify` is banned locally and a hook that hard-failed
|
|
# on a flaky connection would leave no way to commit. A runner is always
|
|
# online, so here an undeterminable answer is a real failure.
|
|
#
|
|
# Expect this to go red for reasons this repo's commit did not cause: an
|
|
# upstream release overnight is enough. That is the chosen behaviour -- the
|
|
# alternative is a gate that only notices staleness when someone remembers to
|
|
# look.
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
dependency-freshness:
|
|
name: dependencies on newest stable
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
# The gate lives in the shared utils repo so every repo resolves the
|
|
# same "latest stable" the same way. Checking it out beats vendoring a
|
|
# copy, which is exactly how a gate and its survey start disagreeing.
|
|
- name: Check out the shared gate
|
|
uses: actions/checkout@v4
|
|
with:
|
|
repository: kuhyx/utils
|
|
path: .utils
|
|
|
|
- name: Set up Python
|
|
uses: actions/setup-python@v5
|
|
with:
|
|
python-version: "3.13"
|
|
|
|
- name: Install the gate's two runtime dependencies
|
|
run: python -m pip install --upgrade pyyaml packaging
|
|
|
|
- name: Cache registry lookups
|
|
uses: actions/cache@v4
|
|
with:
|
|
path: ~/.cache/dep-freshness
|
|
key: dep-freshness-${{ hashFiles('**/pubspec.yaml', '**/pyproject.toml',
|
|
'**/requirements*.txt', '**/package.json', '**/Cargo.toml', '**/go.mod') }}
|
|
restore-keys: dep-freshness-
|
|
|
|
- name: Every dependency is on newest stable
|
|
run: bash .utils/scripts/check_dependency_freshness.sh --all --strict
|