Version 0.112.1

• Change of strategy: when the dependency file is changed after the build list is created, the build list is now re-created from scratch.
• Bug fixes
  • CreateAPIfromCFG made shy tfns non-shy
  • UpdateTatin had a problem on Linux and Mac-OS once the bug in ]activate is fixed
  • InitPackageConfig does not perform a check on the names in a package config file anymore

Version 0.112.0

• Major flaw in ]CopyRegistry fixed: must copy deprecated packages as well for compatibility reasons
• Package updated (CommTools)

Version 0.111.0

• The user command ]LoadDependencies did not cooperate with Cider. Now it does: if no argument is specified, it looks for open Cider projects and acts accordingly. Same for the folder to load from.
• Bug fixes
  • Under rare circumstances editing a group homepage caused a server error 500.
  • The internal function ReturnDependencyFiles did not react appropriately in case a package was not found.

Version 0.110.0

• User command ]CopyRegistry and its API equivalent implemented
• Concurrent development of Client and Server is made much easier, and documented as well
• User command help pages polished
• Help pages reorganzied: they are now variables for much easier editing
• The ]Maintenance user command now excepts [MyUCMDs] as an argument
• Bug fixes
  • When the newly introduced optional parameter exclude pointed exclusively to non-existing files, then the attempt to produce a message crashed.
  • BuildPackage wrongly refused to run without .NET Framework on Windows - not required anymore
  • ]ListPackages crashed when [*] was specified as an argument depending on which Registries are defined
  • ]Tatin.Version -check crashed

Version 0.109.0

• New API function CreateAPIfromCFG implemented that creates an API automatically
• New (optional) package property exclude introduced
• For Linux & Mac-OS /home/<⎕AN> is no longer hard coded but established with 2 ⎕NQ'.' 'GetEnvironment' 'HOME'
• Documentation for the server and the "Load and Update Strategy" improved
• When a package is fully specified to InstallPackages (and therefore, implicitly, also to LoadPackages)
  (read: owner+name+full-version-number) but without a Registry, then when there is only one Registry defined
  in the user settings with a priority greater than 0 AND the package (and any dependencies) is available
  from the cache, no Internet is required anymore
• The Run function does not re-create the user command cache anymore
• Package alias names properly documented

Version 0.108.1

Fix for a bug that was introduced by version 0.108.0: ListVersions and siblings returned the list properly sorted but in reverse order.

Version 0.108.0

• Integrity check added to ]PublishPackage regarding the origin of dependencies
• ]PublishPackage now returns messages as a result rather than printing them to ⎕SE
• Bug fixes
  • On the production server, calling the usage data page caused an error 500
  • Reporting ignored Registries by CheckForLaterVersion was wrong
  • A package installed into a non-managed Registry was not found by InstallPackages
  • Run.aplf gets around problems caused by saving Tatin in the session file
  • DeletePackage did not deal with case problems
  • New version of ZipArchive that runs on Mac-OS High Sierra+
  • OnHouseKeeping did not execute ⎕OFF in Runtime when it should have
  • SortIndexForPackageIDs did not return the expected result when the path carried hyphens
  • Under rare circumstances a dependency ref injected into a package was pointing to the wrong package
  • Incompatibilities when running/developing on Linux and Mac OS addressed

Version 0.107.0

DeletePakcages could run into a problem in case a package was deleted from a Registry with two aliases and two different passwords.

Note that the syntax of the DeletePackages API function has changed .

Version 0.106.2

• After updating Tatin to 0.106.1 a newly started session did not offer any ]Tatin user commands
• ]UpdateTatin reported a wrong installation folder

Version 0.106.1

• User command help polished
• Flag renamed in ]PackageConfig: -quiet is now -force
• Bug fixes
  • Version 0.106.0 introduced a bug that made ]UpdateTatin crash with a VALUE ERROR
  • API function Version was buggy with * and -all

If you are currently on 0.106.0 (the version that introduced a bug into ]UpdateTatin), then read this:
Installing and Updating the Tatin Client: When updating goes wrong