Skip to content

chore: Prepare release 3.4.3#1572

Merged
fsbraun merged 3 commits intomasterfrom
chore/release-3.4.3
Jan 17, 2026
Merged

chore: Prepare release 3.4.3#1572
fsbraun merged 3 commits intomasterfrom
chore/release-3.4.3

Conversation

@fsbraun
Copy link
Member

@fsbraun fsbraun commented Jan 17, 2026

Description

Prepare the 3.4.3 release by bumping the package version and adding coverage for management commands.

Related resources

  • #...
  • #...

Checklist

  • I have opened this pull request against master
  • I have added or modified the tests when changing logic
  • I have followed the conventional commits guidelines to add meaningful information into the changelog
  • I have read the contribution guidelines and I have joined #workgroup-pr-review on
    Slack to find a “pr review buddy” who is going to review my pull request.

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jan 17, 2026

Reviewer's Guide

Prepares the 3.4.3 release by bumping the package version and adding comprehensive tests for the generate_thumbnails and import_files management commands, covering normal flows, edge cases, and filesystem interactions.

Sequence diagram for generate_thumbnails management command execution

sequenceDiagram
    actor Developer
    participant DjangoManage as manage_py
    participant GenerateThumbnailsCommand as generate_thumbnails
    participant FileModel as File
    participant ThumbnailBackend as ThumbnailBackend
    participant Storage as Storage

    Developer->>DjangoManage: run generate_thumbnails
    DjangoManage->>GenerateThumbnailsCommand: handle()
    GenerateThumbnailsCommand->>FileModel: query files needing thumbnails
    FileModel-->>GenerateThumbnailsCommand: list of files
    loop for each File
        GenerateThumbnailsCommand->>ThumbnailBackend: generate(file)
        ThumbnailBackend->>Storage: read original file
        Storage-->>ThumbnailBackend: original file content
        ThumbnailBackend->>Storage: write generated thumbnail(s)
        Storage-->>ThumbnailBackend: thumbnail locations
        ThumbnailBackend-->>GenerateThumbnailsCommand: result for file
    end
    GenerateThumbnailsCommand-->>DjangoManage: summary of processed files
    DjangoManage-->>Developer: print summary and exit code
Loading

Sequence diagram for import_files management command execution

sequenceDiagram
    actor Developer
    participant DjangoManage as manage_py
    participant ImportFilesCommand as import_files
    participant OSFilesystem as Filesystem
    participant FileModel as File
    participant Storage as Storage

    Developer->>DjangoManage: run import_files /path/to/files
    DjangoManage->>ImportFilesCommand: handle(path)
    ImportFilesCommand->>Filesystem: scan directory tree
    Filesystem-->>ImportFilesCommand: list of file paths
    loop for each path
        ImportFilesCommand->>Filesystem: open file
        Filesystem-->>ImportFilesCommand: file handle
        ImportFilesCommand->>Storage: save content
        Storage-->>ImportFilesCommand: stored file location
        ImportFilesCommand->>FileModel: create file record
        FileModel-->>ImportFilesCommand: saved instance
    end
    ImportFilesCommand-->>DjangoManage: summary of imported files
    DjangoManage-->>Developer: print summary and exit code
Loading

File-Level Changes

Change Details Files
Bump library version to 3.4.3 for the new release.
  • Update the version constant to 3.4.3 in the package initializer to reflect the new release version.
filer/__init__.py
Update release notes for version 3.4.3.
  • Adjust the changelog to document changes included in the 3.4.3 release (exact entries not visible in the diff snippet).
CHANGELOG.rst
Add extensive tests for management commands generate_thumbnails and import_files.
  • Introduce GenerateThumbnailsTestCase to verify basic execution, missing file handling, memory management pattern, and output format of the generate_thumbnails management command.
  • Introduce ImportFilesTestCase to exercise import_files command over realistic directory hierarchies, base folder handling, duplicate prevention behavior, folder hierarchy and file<->folder relations, verbosity modes, image-vs-file classification, empty and deeply nested directories, public flag handling, and path normalization.
  • Introduce ImportFilesEdgeCasesTestCase to cover filenames with special characters, mixed file extensions including images, and to assert resulting object statistics (counts of Folder, File, Image).
tests/test_management_commands.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@codecov
Copy link

codecov bot commented Jan 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.98%. Comparing base (63ab81c) to head (af00a87).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1572   +/-   ##
=======================================
  Coverage   76.98%   76.98%           
=======================================
  Files          78       78           
  Lines        3671     3671           
  Branches      498      498           
=======================================
  Hits         2826     2826           
  Misses        675      675           
  Partials      170      170           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Several tests call File.objects.all().delete() and Folder.objects.all().delete() in tearDown; consider targeting only the objects created by the test (e.g., tracking IDs) to avoid accidentally wiping out shared/fixture data if the test setup evolves.
  • The management command tests assert on human-readable output strings (e.g., 'Processing image', progress format); if the commands’ messaging changes frequently, you might want to narrow assertions to more stable identifiers (like counts, IDs, or key phrases) to make the tests less brittle.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Several tests call `File.objects.all().delete()` and `Folder.objects.all().delete()` in `tearDown`; consider targeting only the objects created by the test (e.g., tracking IDs) to avoid accidentally wiping out shared/fixture data if the test setup evolves.
- The management command tests assert on human-readable output strings (e.g., `'Processing image'`, progress format); if the commands’ messaging changes frequently, you might want to narrow assertions to more stable identifiers (like counts, IDs, or key phrases) to make the tests less brittle.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@fsbraun fsbraun merged commit 05f613f into master Jan 17, 2026
89 checks passed
@fsbraun fsbraun deleted the chore/release-3.4.3 branch January 17, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant