Releases: dell/patches
Releases · dell/patches
v2.0.7
- Fixed a bug where common names with spaces were not properly handled
Full Changelog: v2.0.6...v2.0.7
v2.0.6
- Fixed a bug where certificate imports would not work if the common name did not have the FQDN.
- Updated patches.sh to display help correctly
Full Changelog: v2.0.5...v2.0.6
v2.0.5
- Fixed a bug where SELinux would block access to repository files
Full Changelog: v2.0.4...v2.0.5
v2.0.4
- Updated README with new language regarding the STIGs
- Updated Material because recent updates broke backwards compatibility
- Changed version to release
Full Changelog: v2.0.3-beta...v2.04
v2.0.3-beta
- Fixed a minor bug that would cause the installation to choke depending on the directory
- Made a note that STIGs have to be disabled
v2.0.2-beta
- Fixed a bug where the catalog page did not list correctly
- Fixed a bug where the code for enabling Patches on reboot did not work
Full Changelog: v2.0.1-beta...v2.0.2-beta
v2.0.1-beta
- Fixed a bug where Patches would not reload after restart
- Removed dependence on systemd and shifted to using cron
Full Changelog: v2.0.0-beta...v2.0.1-beta
v2.0.0-beta
- Complete overhaul of the Patches frontend and large parts of the backend logic
- Upgraded Material from v4 to v5
- Upgraded React from 17 to 18
- Overhauled all React components from old, class-based, notation, to functional components
- Removed several dead packages / components that were left in the code base but not in use
- Replaced multiple deprecated packages that broke on the upgrade from 17 to 18
- Added comments to undocumented code
- Overhauled naming so that it is more intuitive
- Removed all NFS functionality. It wasn't needed and added significant complexity to the code base
- Created a new logger utility
- Added fixes to account for generational differences in the DRM schema
- Overhauled the debugging document to account for the frontend
- Overhauled backend logic flow. The XML / parsing workflow originally bounced between several different files and was very confusing to follow. This has all been streamlined.
- Overhauled React routing logic
- Upgraded React router to v6
- Completely overhauled the way CSV download works - previously it was a large custom function. We now import and use fast-csv for the functionality
- Fixes #16
- Fixes #12
- Fixed a bug where you could add the same user as both an admin and a user causing the user to take precedence so the admin page would not display. The username now must be unique in the user_roles table. Also updated the corresponding code in patches.sh
- Added more useful feedback to the user based on their certificate
Full Changelog: v1.3.3-beta...v2.0.0-beta
v1.3.3-beta
- The August and July versions of the DRM repositories have different schemas - this accounts for that delta
- Fixes #14
Full Changelog: v1.3.2-beta...v1.3.3-beta
v1.3.2-beta
- Fixes #2
- See: https://unix.stackexchange.com/questions/753840/podman1-port-1veth0-entered-disabled-blocking-state-podman-does-not-gracefu
- The problem was thrashing which occurred between the container's restart policy and systemd
- Patches start/stop would not always behave reliably. I have overhauled how the Patches service works. It now leverages
podman generate systemd
to produce individual patches services for all containers. Those services are then subsequently controlled individually instead of using thepodman
command. This leads to significantly more reliable behavior. - Added a restart command
Full Changelog: v1.3.1-beta...v1.3.2-beta