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

Version 0.106.0

• The user command script is now a redirect-only script. The real thing is an ordinary namespace: Tatin.UC

  This is part of the Tatin project: saved in APLSource/UC/

• When a Cider project "Tatin" is opened, the user is asked whether she wants to execute the code in #.Tatin rather than ⎕SE._Tatin, making work on the user commands significantly easier.

• Bug fixes

  • Usage Data crashed at the turn of the year and thereafter.

Version 0.105.0

• ]DeletePackage renamed to ]DeletePackages
  • ]DeletePackages now accepts an incomplete package ID and works out group name and list of packages fitting the input before attempting to delete it/them
  • ⎕SE.Tatin.DeletePackages now accepts these inputs (examples):
    • aplteam-foo
    • aplteam-foo-1
    • foo
  • UpdateClient handles 302 (redirect) now no matter what
  • ]ListRegistries has now a flag -raw
  • New version of MarkAPL integrated with a bug fix in the dark print theme
  • Bug fixes
    • UpdateClient appeared to hang once the new release notes were shown in the default browser (#186)
    • Instructions for installing and updating Tatin corrected and polished
    • Initializing process of Tatin is now more robust

Version 0.104.1

• No instance of the UserSettings class is any longer distributed with the Client workspace
• Sending ZIPped data is no longer Base64-encoded but declared as binary data with the HTTP header "Content-Type"

Version 0.104.0

• The results of both ]ListRegistries and its API counterpart have changed
• TatinVars.HOME is much more flexible now , addressing Dyalog stand-alone applications
• Bug fixes
  • UpdateClient had a problem with Run.aplf
  • UserSettings.ReplaceRegistry did not correctly identify an id
  • DefineRegistry did not allow changing the id
  • DefineRegistry's constructor did not handle a port number as in 'https://localhost:9090'
  • Client.ListRegistries did not return the id - delivers now a changed and complete result

Version 0.103.2

• New version of FilesAndDirs integrated
• ]UserSettings now accepts a flag -home that prints the folder hosting the user settings file
• UserSettings documentation improved.
• Bug fixes
  • It was possible to publish without an API key though not with an invalid one
  • The function SplitLogFile caused a WS FULL at the turn of the year due to a bad implementation
  • GetProgramFilesFolder did return a wrong folder on Linux and Mac-OS
  • ]UpdateTatin did not put the release notes into a Ride browser when it should
  • ]InstallPackage when acting on a non-existing ZIP file did not provide a useful error message

Version 0.103.1

• BuildPackage can now update TatinVars.CONFIG. For that the newly introduced parameter tatinVars (see CreateBuildParms) must point to the package's TatinVars
• Documentation now uses the new version of "MarkAPL", including the new "Dark" theme.
• The Tatin client does not rely on the .NET Framework on Windows anymore, .NET (formerly known as .NET Core) will do.
• UpdateTatin now checks all HTTP status codes and reports any problems early and in detail
• Bug fixes
  • CheckBuildList got the timestamps wrong when checking the dependency file and the build list
  • Test cases left much too many temp files and temp dirs behind
  • ]PackageConfig -edit crashed when the config did not have a minimumAplVersion

Version 0.103.0

• You must specify now an email address for your group before you can publish a package if that's enforced via the INI file
• Bug fixes
  • BuildPackages checks whether the .NET Framework is available and throws an error if not
  • ListVersions works on local un-managed Registries
  • UpdateTatin did not define its explicit result in case of success, causing a VALUE ERROR
  • Documentation for how to add a new API key was flawed.
  • GetRegistryIndex did not return anything useful in case of a local but unmanaged Registry

Version 0.102.3

• Bug fixes
  • If the files property pointed to a file in a sub-folder it was not handled correctly
  • WritePackageConfigFile could throw an error when it should not

Version 0.102.2

Documentation corrected regarding the installation.