Skip to content

Stable-20250514

Compare
Choose a tag to compare
@jonasbardino jonasbardino released this 14 May 11:13
· 15 commits to master since this release

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.