Version 2.8.5

• Calling saveTransform() with one argument now returns the serialised transform
  object, as intended, rather than producing an error.
• Comparisons between floating-point and enumeration types are now avoided when
  using the C++20 or later standard for compilation, since this now leads to a
  warning. (Reported by BDR.)
• The "Upgrading to RNiftyReg 2.x" section of the README has been removed, since
  the 2.x line of releases is now over 10 years old(!).

Version 2.8.4

• The logic for reading FSL-FLIRT transforms from file previously overlooked a
  quirk whereby FLIRT flips images whose xforms have positive determinant (see,
  for example, https://neurostars.org/t/understanding-fsl-flirt-transformation-matrices/26406).
  This could result in a spurious flip when these transforms were applied, if the
  originally registered images were in, say, LAS and RAS orientations. This
  detail is now handled when FLIRT transforms are imported. (Reported by Martin
  Wilson.)
• Affine initialisation matrices for linear registration would previously be
  replaced by a default internally. This has been corrected.
• Default affine initialisation matrices now take the pixel/voxel dimensions into
  account when image sform and qform codes are both zero.
• The package's dependency on the ore package has been removed, with base R
  regular expression functions being used instead.

Version 2.8.3

• A NiftyReg class method referencing a nonexistent data member has been removed.
  (Picked up by LLVM pre-19, reported by BDR.)

Version 2.8.2

• Objects of class "niftyregRDS" gain a simple asAffine() method for convenience.
• The code should now ensure that an affine result from loadTransform() has the
  "affine" class.
• An incorrect internal assignment has been corrected.