Next-20250926

This is a bugfix and feature release:

• Fix old issue with only showing Server Admin app for actual admins (#40)
• Expanded sftp access to also cover read-only and write-only sharelinks (#284)
• Various obsolete python2 leftover cleanups (#301)
• Update quicktips with entries about Apps and site Status page (#304)
• Add common local disk file systems to migstat and prevent output on success (#305)
• Retire obsolete inline image preview support (#306)
• Fix theoretical PAM/NSS string handling overflow issues (#307, #308, #309, #310, #311, #312, #313)
• Polish DeIC storage helpers (#216, #314)
• Silence migimportdoi and migindexdoi in cronjobs unless actually in use ( #315)
• Integrate QR code on sharelink invite page to ease direct visual sharing (#316, #317)
• Limit GDP log noise from configured known security scanners (#319)
• Port old paramiko scan noise silencer to modern platforms and versions (#320)
• New janitor service to do recurring background cleanup and automate trivial operator tasks (#322)
• Remove recursive directory loops from obsolete legacy symlinks (#323)
• Increased unit test coverage (#324, #326, #327)
• More migration of scripts and code to mig/lib/, bin/ and sbin/ (#329)
• Fix failures from utf-8 interpretation of path strings in chkXroot logging (#331)
• Fix a corner-case in make_hash helper (#333)
• Remove all cleverness from unit test filesystem cleanup for consistency (#334)
• Reduce noise from harmless issues in monitoring of sftp/webdavs/ftps logs (#278, #337)
• Filtering of peers email and email during external user sign up (#321, #325 , #339)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: since v1.25.0 we only release the Next branch which is suitable for all modern deployments using python3. We leave the legacy-python2 branch around but it will neither receive further support nor releases.

Next-20250724

This is a bugfix and feature release:

• Fix another issue with show vgrid/workgroup private file rendering (PR #275, issue #258 )
• HTTP header hardening as recommended by W3C and security scans (PR #276, #277)
• Selenium helper updates to support screenshooter with Firefox from snap (PR #280)
• Prevent concurrent migverifyarchives cronjobs and resulting interference (PR #282)
• HSTS tweaks for hardening of BASE_FQDN and PUBLIC_ALIAS_FQDN vhosts (PR #283)
• Address pylint warnings/errors (PR #285, #286, #287)
• Fix python3 issue in usagestats.py helper (PR #288, #289)
• Add simple migstats weekly cronjob using usagestats.py (PR #290)
• Fix python3 issue when using subprocess output (PR #291 - #298)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: since v1.25.0 we only release the Next branch which is suitable for all modern deployments using python3. We leave the legacy-python2 branch around but it will neither receive further support nor releases.

Next-20250702-rc1

This is a bugfix and feature pre-release:

• fix another issue with show vgrid/workgroup private file rendering (PR #275, issue #258 )
• HTTP header hardening as recommended by W3C and security scans (PR #276, #277)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: since v1.25.0 we only release the Next branch which is suitable for all modern deployments using python3. We leave the legacy-python2 branch around but it will neither receive further support nor releases.

Next-20250625

This is a bugfix and feature release:

• fix Server Admin page crash on py3 with existing sitestats (PR #256, issue #257)
• fix show vgrid/workgroup private file rendering (PR #270, issue #269)
• preparation for the eventual merge of PR116 with Archives update (PR #271)
• fix regression from PR233 to allow hyphen in sftpsubsys usernames (PR #272, issue #263)
• add profile Xgi helper (PR #273)
• switch verifyarchives to use our serializer helpers for py3 support (PR #274)
• add state check to verifyarchives helper and use to verify FINAL Archives (PR #268)
• drop svn repo, old py2 and legacy alias branches and complete the move to python3

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: with this release we at least temporarily dropped the old Stable-YYYYMMDD release series specifically pointing to the master branch, which was strictly in lock-step with the now retired SourceForge repo. The same applies for the matching Main-YYYYMMDD releases pointing to the corresponding main python2 branch. We also dropped the old edge and experimental alias branches replaced by main and next.
Thus, we now only release the Next branch which is suitable for all modern deployments using python3. We leave the legacy-python2 branch around but it will neither receive further support nor releases.

Next-20250606

This is a bugfix and feature release:

• Point OIDC logout back to proper login page (PR #245)
• Support include_sections in config e.g. for separate SITE and CLOUD section files (PR #244, #249)
• Fix Jupyter sftp port discovery (PR #247)
• Upgrade to Jupyter 4.x support and expose full proxy TLS support (PR #254)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Next for all modern deployments using python3 and Main for any remaining legacy python2 deployments until phased out.

Main-20250606

This is a bugfix and feature release:

• Point OIDC logout back to proper login page (PR #245)
• Support include_sections in config e.g. for separate SITE and CLOUD section files (PR #244, #249)
• Fix Jupyter sftp port discovery (PR #247)
• Upgrade to Jupyter 4.x support and expose full proxy TLS support (PR #254)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Next for all modern deployments using python3 and Main for any remaining legacy python2 deployments until phased out.

Next-20250514

This is a bugfix and feature release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197 + #198)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors (Issue #224 / PR #225)
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Fix session clean up on logout, including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Allow SFTP(subsys) access to GDP projects with space in name (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235
• Fix broken dict key check in datatransfer page (Issue #228 / PR #229)
• Fix 'Move to trash' issue on GDP sites (Issue #169 / PR #240)
• Include support for old style vgrid layout in lustre quota helper
• Rework web download in Files on GDP sites to show progress and errors (Issue #238 / PR #239)
• Update expire warning emails to new Renew button on Account page (Issue #241 / PR #242)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Next for all modern deployments using python3 and Main for any remaining legacy python2 deployments until phased out.

Main-20250514

This is a bugfix and feature release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197 + #198)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors (Issue #224 / PR #225)
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Fix session clean up on logout, including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Allow SFTP(subsys) access to GDP projects with space in name (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235
• Fix broken dict key check in datatransfer page (Issue #228 / PR #229)
• Fix 'Move to trash' issue on GDP sites (Issue #169 / PR #240)
• Include support for old style vgrid layout in lustre quota helper
• Rework web download in Files on GDP sites to show progress and errors (Issue #238 / PR #239)
• Update expire warning emails to new Renew button on Account page (Issue #241 / PR #242)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Next for all modern deployments using python3 and Main for any remaining legacy python2 deployments until phased out.

Stable-20250514

This is a bugfix and feature release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197 + #198)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors (Issue #224 / PR #225)
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Fix session clean up on logout, including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Allow SFTP(subsys) access to GDP projects with space in name (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235
• Fix broken dict key check in datatransfer page (Issue #228 / PR #229)
• Fix 'Move to trash' issue on GDP sites (Issue #169 / PR #240)
• Include support for old style vgrid layout in lustre quota helper
• Rework web download in Files on GDP sites to show progress and errors (Issue #238 / PR #239)
• Update expire warning emails to new Renew button on Account page (Issue #241 / PR #242)

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Next for all modern deployments using python3 and Main for any remaining legacy python2 deployments until phased out.

Next-20250430-rc3

This is a bugfix and feature pre-release in preparation for next actual release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors in issue #224
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Proper session clean up during logout including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Fix GDP projects with space in name not accessible through SFTP (subsys) (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.