Skip to content

Update dependency filesender/filesender to v3.8#42

Open
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/filesender-filesender-3.x
Open

Update dependency filesender/filesender to v3.8#42
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/filesender-filesender-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 24, 2026

This PR contains the following updates:

Package Update Change
filesender/filesender minor 3.63.8

Release Notes

filesender/filesender (filesender/filesender)

v3.8

Compare Source

Release Version 3.8

Release date: 7 April 2026

Installation

Documentation is available at https://docs.filesender.org/filesender/v3.0/install/

Major changes since 3.7

The database update script DOES NOT need to be run.
The templates directory HAS changed.

Short summary:

This release makes the main code path that is used to write data to disk in the server code more efficient in terms of CPU and memory use #​2640

All changes:

Efficiency: use stream_copy_to_stream to allow lower CPU/RAM use #​2640

[Docs] Fix log_facilities process values: use lowercase #​2643

[Docs] Fix log_facilities process values: use lowercase strings #​2644

Add the hour +59m59s of same day to getMaxExpire() #​2645

build(deps): bump aws/aws-sdk-php from 3.368.0 to 3.371.4 in /optional-dependencies/s3 #​2647

Fix Guest::getMaxExpire() to consider user timezone offset #​2648

floor exp in www/js/transfer.js #​2649

2026/apr/d3 upload gal email user always has a preference #​2650

lack of support for i18n #​2651

auditlog when recipients are added #​2653

Fix expiry message shown when guest invite has no expiration #​2654

new terms for i18n #​2655

i18n: ui3: auto import from poedtor on 2026-04-07-1775525596 #​2656

bump in build version number #​2657

build(deps-dev): bump activesupport from 7.1.3.2 to 7.2.3.1 in /docs #​2639

Configuration changes

performance_allow_direct_copy_from_put_to_disk which is true by default to allow efficiency improvements writing to native filesystems and s3 backend.

If performance_allow_direct_copy_from_put_to_disk is true and storage_filesystem_hash_check is true then the new internal configuration option client_calculate_sha256 will be set to have the client calculate the sha256 of the chunk so the server can do a hash_check after writing.

Support and Feedback

Please lodge new github issues for things that might improve the next release!
See Support and Mailinglists or create a Feature requests using Github issues.

v3.7

Compare Source

Release Version 3.7

Release date: 24 March 2026

Installation

Documentation is available at https://docs.filesender.org/filesender/v3.0/install/

Major changes since 3.6

The database update script DOES need to be run.
The templates directory HAS changed.

Short summary:

Some updates for data validation. File names are now normalized to NFD.

All changes:

Modifications for 2.67 release plus

Disable send button if guest not input recipient #​2599

don't allow guests to choose the transfer forward to another server #​2603

db pg stats update quoting update #​2607

Update known-installs.md #​2611

add defaults into configdefaults so they are in the same place #​2612

urlencode flattened data (suggestion from https://github.com/filesend… #​2613

FIX: OIDC missing idp attribute and ensureLocalIdPMetadata method #​2616

feat: add last_chunk_time to accurately clean up abandoned uploads without interrupting long transfers #​2617

Php8x deprecation fixes #​2623

Feature/better expiring files time #​2624

Filesender rest client add useragent to curl #​2625

oidc add docs for idp_attribute #​2626

Allow Admins to download files directly from admin view #​2627

Fix: invitation detail pagination loses guest_id and ignores offset #​2628

Fix: hide archive download button while transfer is still uploading #​2633

bump in build version number #​2637

Configuration changes

Support and Feedback

Please lodge new github issues for things that might improve the next release!
See Support and Mailinglists or create a Feature requests using Github issues.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/filesender-filesender-3.x branch from f49613a to 1d8f3e5 Compare April 7, 2026 05:51
@renovate renovate Bot changed the title chore(deps): update dependency filesender/filesender to v3.7 chore(deps): update dependency filesender/filesender to v3.8 Apr 7, 2026
@renovate renovate Bot changed the title chore(deps): update dependency filesender/filesender to v3.8 Update dependency filesender/filesender to v3.8 Apr 10, 2026
@renovate renovate Bot changed the title Update dependency filesender/filesender to v3.8 chore(deps): update dependency filesender/filesender to v3.8 Apr 15, 2026
@renovate renovate Bot changed the title chore(deps): update dependency filesender/filesender to v3.8 Update dependency filesender/filesender to v3.8 Apr 24, 2026
@renovate renovate Bot changed the title Update dependency filesender/filesender to v3.8 chore(deps): update dependency filesender/filesender to v3.8 Apr 29, 2026
@renovate renovate Bot changed the title chore(deps): update dependency filesender/filesender to v3.8 Update dependency filesender/filesender to v3.8 Apr 30, 2026
@renovate renovate Bot changed the title Update dependency filesender/filesender to v3.8 chore(deps): update dependency filesender/filesender to v3.8 Apr 30, 2026
@renovate renovate Bot changed the title chore(deps): update dependency filesender/filesender to v3.8 Update dependency filesender/filesender to v3.8 May 1, 2026
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.

0 participants