Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: tox-dev/filelock
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4.2.7
Choose a base ref
...
head repository: tox-dev/filelock
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4.2.8
Choose a head ref
  • 8 commits
  • 22 files changed
  • 5 contributors

Commits on Nov 2, 2026

  1. πŸ‘· ci(news): stop cancelling the news check (#901)

    Opening a pull request with labels, as `gh pr create --label` does,
    fires `labeled` a moment after `opened`. Both started the news check,
    and the concurrency group cancelled the first run, which the PR then
    listed as a failed `πŸ“ News fragment` check while the other run passed. πŸ‘·
    
    This moves the news check to [github-workflows
    6.3.0](tox-dev/github-workflows#40), whose
    `validate-news` passes at once for a label set within a minute of
    opening since the run for opening already reads the current labels, and
    stops cancelling runs in progress. The check keeps its name, so the
    ruleset needs no change.
    gaborbernat authored Nov 2, 2026
    Configuration menu
    Copy the full SHA
    4257ca7 View commit details
    Browse the repository at this point in the history
  2. πŸ”§ build(deps): use release-creator 4.4 (#902)

    [release-creator 4.4.0](https://pypi.org/project/release-creator/4.4.0/)
    accepts descriptive changelog fragment names without a `+` prefix.
    Update this project's news check and release tools to that version.
    
    The package-specific cutoff admits the new release during the seven-day
    cooldown. The lock changes only `release-creator` and dependencies it no
    longer requires.
    gaborbernat authored Nov 2, 2026
    Configuration menu
    Copy the full SHA
    e386afb View commit details
    Browse the repository at this point in the history

Commits on Nov 3, 2026

  1. πŸ‘· ci(scorecard): publish OpenSSF results (#903)

    Publish [OpenSSF Scorecard](https://scorecard.dev/) results for this
    repository and show its score in the README. The README also links its
    new Best Practices registration. Analysis runs through
    [tox-dev/github-workflows#42](tox-dev/github-workflows#42);
    this repository controls the triggers and token permissions.
    gaborbernat authored Nov 3, 2026
    Configuration menu
    Copy the full SHA
    825f3b5 View commit details
    Browse the repository at this point in the history
  2. πŸ”§ build(deps): refresh CI and docs tools (#904)

    Co-authored-by: BernΓ‘t GΓ‘bor <gaborjbernat@gmail.com>
    Signed-off-by: dependabot[bot] <support@github.com>
    dependabot[bot] and gaborbernat authored Nov 3, 2026
    Configuration menu
    Copy the full SHA
    bee5ab3 View commit details
    Browse the repository at this point in the history
  3. build(deps): refresh project lock (#906)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    Configuration menu
    Copy the full SHA
    6223054 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    2ac1e92 View commit details
    Browse the repository at this point in the history

Commits on Nov 4, 2026

  1. πŸ‘· ci: adopt shared check, CodeQL and release workflows (#907)

    filelock's checks and release maintenance now come from the
    [tox-dev/github-workflows](https://github.com/tox-dev/github-workflows)
    repository shared by the tox-dev projects, so a fix to the release
    notes, the GitHub Release or the CodeQL setup lands once for all of
    them. πŸ”§
    
    The tox environment checks (`dev`, `type`, `docs`, `pkg_meta`) run from
    the shared check workflow, on Ubuntu and Windows. The GitHub Release is
    created by the shared release workflow after the PyPI artifacts are
    verified. The required checks `🚦 Required checks pass` and `πŸ—οΈ Build
    distributions` keep their names, so branch protection does not change.
    
    The dependency hygiene part pins the shared workflows to
    [6.5.0](https://github.com/tox-dev/github-workflows/tree/6.5.0) and
    moves setup-uv to v10.3.3. πŸ“Œ
    
    ### Architecture
    
    The shared workflows own the generic parts: the tox environment checks,
    CodeQL, the release notes and the GitHub Release with its PyPI check.
    This repository keeps what is specific to filelock: the test matrix with
    its PyPy special case, the NFS, SMB, Termux and capability checks that
    exercise real file systems, the weekly GraalPy run, the benchmark
    matrix, and the PyPI upload with trusted publishing. The gate reads
    every job result through the shared required-checks action, and GraalPy
    may still be skipped.
    
    ### Behavior changes
    
    The PyPI upload no longer waits for the release notes to render, which
    run in parallel. A broken changelog section still blocks the GitHub
    Release.
    
    The CodeQL checks are now named `πŸ›‘οΈ Analyze / πŸ›‘οΈ Analyze actions` and
    `πŸ›‘οΈ Analyze / πŸ›‘οΈ Analyze python`. No ruleset requires the old names.
    
    The tox environment checks no longer set `UV_PYTHON_PREFERENCE`, because
    the shared check workflow does not expose that setting.
    
    The `release-creator` cutoff exception in `pyproject.toml` now records
    its expiry, 2026-11-09, which the file's existing comment already
    states.
    gaborbernat authored Nov 4, 2026
    Configuration menu
    Copy the full SHA
    19af0ad View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    90760d8 View commit details
    Browse the repository at this point in the history
Loading