35.0.0
Long Term Support (LTS)
This release marks the start of the 35 Long Term Support (LTS) release line. This release line will be supported with security and critical patches until at least July 2026.
Upgrade Instructions
This major release requires a database schema upgrade. Please consult the documentation about upgrading your database schema.
The following changes are necessary and are covered by the alembic upgrade head
command:
-
Dropping and re-creation of the
SUBSCRIPTIONS_HISTORY_PK
primary key in thesubscriptions_history
table (Alembic revisionb5493606bbf5
) -
Creating
deleted_did_meta
table (Alembic revisionb0070f3695c8
)
General
Features
- Core & Internals: Document and cleanup discrepancies between surl and lfn2pfn algorithms #5129
- Metadata: MongoDB metadata implementation does not allow using authentication #6605
- Metadata: Alter schema in preparation for metadata deletion trigger #6958
Enhancements
- Database: Migrating core/replica.py to SQLAlchemy 2.0 #6586
- REST & API: Metrics API endpoint: allow option to return RSEs identified by RSE attribute #6564
- REST & API: Rename internal
API
layer togateway
#6644 - Release management: Remove upper bound version constraints for rucio-clients #6663
- Release management: Refactor Python dependencies into multiple files depending on app #6750
- Release management: Rucio 35 dependency upgrade #6890
- Transfers: Updates to overwrite configuration on tape #6581
- Transfers: Transfers: add overwrite_when_only_on_disk FTS logic #6903
Bugs
- Database: Inconsistencies in Model Registration and Unregistration Functions in
models.py
#6677 - Possible redundant util function #6598
- REST & API: Capital
I
inId
in REST API for Subscriptions #6316 - Release management: Mismatch between package names in
setuputil
and requirements files #6969 - Replicas: Regression in core/replica.py SQL migration #6983
- Subscriptions: SUBSCRIPTIONS_HISTORY integrity error #6292
- Testing: Race conditions in
test_lifetime.py
#6911