Releases: ProgrammeVitam/vitam
Releases · ProgrammeVitam/vitam
v7.0.2
Full Changelog: 7.0.1...7.0.2
v6.4
Full Changelog: 6.3...6.4
Changelog V6.3 -> V6.4
PIC
- Story #13906: CP nvm-wrapper & spotless execution in Jenkins
- Story #13929: Check if internal cache exists instead of downloading binaries from internet
To avoid being blocked by the providers when downloading their binaries too frequently.
Ansible
- Bug #14044: Fix avast-vpsupdate
Since newest version of avast, a systemd service is available for vps sync. - Bug #13842: Remove deprecated mongodb-org-tools package for restic usage.
Otherwise, former mongodb tools will stay present if offer component is not colocated with mongodb. - Story #11855: Clean code for ansible sources.
- Bug #13568: Install logrotate when enable rotate logs.
Ensure logrotate is installed when enabling log's rotation. - DS #13355: Fix python-jmespath install on different OS.
- Bug #13577: Fail on init_scheduler_jobs when using update_vitam_configuration tag.
When updating the configuration, the service is restarted by the handlers but the service checks are not done and lead to a failure when trying to call the api. - Bug #13567: Added missing MongoDB components in troubleshoot.
Application
- Bug #13581: Add configuration for disabling KeepAlive for Swift clients
- Bug #13758: Fix XML XXE security vulnerability
Secure xml handling
Remove saxon / Saxon-HE library xml library (was used for xslt)
Add ArchTest for enforcing security constraints - Bug #13603 : Override existing scheduler job configuration
- Bug #13602: Disable IdentityExpirationJob secondary site
- Bugs #13562 : Disable rectification mode of metadata consistency audit
- Bug #13442 : Fix lfc traceability operations failure after transfer requests
The lifecycle unit traceability would fail when a transfer is requested for a recently ingested or updated unit.
This is because the _v field was also incremented when setting the _opts field
Add migration playbook
Add tests for ensuring all internal metadata fields are either explicitly marked as secured or temporary.
Cleanup : Remove non existing _uds field from object group model - Bug #13435: Fix export with invalid ObjectGroup Xml Id reference
- Bug #13434 : Fix export when empty or missing FileInfo/FileName export
Fix DIP & transfer request exports when :
Filename is empty
FileInfo is missing - Story #11867: Fix random tests
- Story #13307 : Fix concurrent LFC traceability chaining
Bug #13307 - Ensure strict linear traceability chaining : Load last LFC traceability operation only once the operation is actually running to avoid some rare race conditions.
If "last LFC traceability operation" is loaded before workflow is started, it may cause obsolete data in some rare racing conditions :
* 2 threads load "last LFC traceability operation", and both check that not operation is currently running.
* First thread starts a 1st traceability operation, that completes successfully quickly.
* Second thread starts another traceability operation. But this one is scheduled for execution after the first one completes (e.g. process-engine was too busy / not enough worker threads are available...).
In that case, the second operation would use an obsolete "last LFC traceability operation" that is not the latest.
v8.0.0
v6.3
v7.1.1
Full Changelog: 7.1.0...7.1.1
v7.1.0
Full Changelog: 7.0.1...7.1.0
v7.0.1
Full Changelog: 7.0.0...7.0.1
v6.2
v7.0.0
Full Changelog: 6.1...7.0.0