Release Notes

Tatin release notes contain information regarding actions that need to be executed before a new version can be used, or outstandingly important pieces of information.

This document does not come with a complete list of fixes, added features etc. Consult Tatin on GitHub for that.

• The way build numbers are processed has changed: prior to 0.117.0 when a complete version number — including a build number — was passed on to ]BuildPackage the build number was not bumped. Now it is bumped.

• Tatin now requires at least 18.2: 18.0 is not supported any longer.

• Fixes a gaping security hole (Server only, group home page)

• No action required

• No action required

• No action required

In case you are on Windows and you are using OneDrive then you might need to pay attention.

Older versions of Tatin did not cooperate with OneDrive; this can potentially cause problems. A new document, “Tatin and OneDrive,” discusses this issue. If you use OneDrive, read it!

Otherwise no action is required, but be aware of changes made to ]ListVersions: if no argument is provided it checks on open Cider projects now. In other words, it became more powerful.

• No action required

• No action required

• No action required

• The ]CopyRegistry user command, introduced in 0.110.0, got a changed syntax:
  • The -full flag was removed
  • Default behaviour is now what was so far achievable with -full except that deprecated packages are now copied as well

    This is a necessity for compatability, because some package might well depend on an earlier version of a now deprecated package.

  • With -dry one might omit both arguments, meaning that the URL defaults to [tatin] while no path is required
  • The list of copied packages is now returned as a matrix

• No action required

• A maintenance file “2024-07-07-Inject-Exclude.aplf” was introduced.

It allows to add the new “exclude” property (introduced with version 0.109.0) to be introduced into all saved packages as an empty text vector.

You don't have to run this maintenance function on all your packages (Tatin deals with both a defined “exclude” as well as an absent “exclude”) but it is better for future use when this is part of all packages.

• No action required

• No action required

• You must update your client to 0.108.0 for correct results — prior versions are incompatible with 0.108.0!

• The syntax of the API function DeletePackages has changed.

• Action is required with version 18.2 and/or 18.0

  With this version the Tatin user commands won't be available in the session until you either execute ]UReset yourself, or you add the following code to your setup.dyalog in MyUCMDs/:

  :If ~IfAtLeastVersion 19
      {}⎕SE.SALTUtils.ResetUCMDcache -1
  :EndIf

• No action required when running Tatin.

• No action required when running Tatin.

  However, when developing (contributing to) Tatin there is a significant change: read “Special case: working on user commands” in the “Tatin for Contributors” document for details.

Potentially breaking changes:

• The function DeletePackage was renamed: DeletePackages
• The user command ]DeletePackage was renamed: ]DeletePackages

• The client requires a server on 0.104.1 as well

• The result of both ]ListRegistries and the corresponding API function return a different (extended) result now.

  This implies that older versions of Tatin than 0.104.0 are incompatible with this new version, therefore you are forced to update.

  Apart from the update no action is required.

• No action required.

• No action required.

• No action required but note that the result of the API function LoadPackages has changed.

• No action required

• No action required

• Most importantly, a bug fix in ]Tatin.CiderUpdate

• Most importantly, a revised install procedure

• Very important bug fix in UnInstallPackages

Two massive changes:

• This version is only compatible with Cider 0.36.0 or later
• The installation folder is not MyUCMDs/ anymore. However, ]Tatin.UpdateTatin of your old version cannot know about this, therefore you have to take action once in order to get Tatin into the right folder.

  See the “InstallingAndUpdatingTheTatinClient.html” document for details.

• Note that in the future ]Tatin.UpdateTatin will use the new installation folder

No breaking changes, no user actions required.

No breaking changes, no user actions required.

No breaking changes, no user actions required.

No breaking changes, no user actions required.

No breaking changes, no user actions required.

This release addresses a bug in the server; the client has not been changed.

Update only required if you run a server.

No breaking changes, no user actions required.

• No breaking changes for the Tatin client, therefore there are no user actions required
• If you run a Tatin server you don't need to take action but you should be aware of a major change

Before version 0.98.0 credentials got stored in a file Credentials.txt. The format was:

<group>=<api-key>

The API-keys were stored as clear text. We don't want that anymore.

With version 0.98.0 credentials will be stored in a file Credentials.csv. The format is different:

<group>,<api-key-hash>,<Salt>

The server will convert Credentials.txt automatically into Credentials.csv. Afterwards there is a new file Credentials.csv while the old file Credentials.txt will be deleted.

Note that you might create at a later stage a new file Credentials.txt with entries like

<group-name>=<api-key>

or

<group-name>,<api-key>

That allows you to add new groups, or overwrite existing ones, for example when somebody lost the API-key.

The server will perform the following actions:

• Take the data and convert it
• Delete rows from Credentials.csv that are also contained in Credentials.txt (same group name)
• Add the data to Credentials.csv
• Delete Credentials.txt

No breaking changes, no user actions required.

This version comes with several breaking changes:

• The ]FindDependencies user command's -detailed property has been renamed to verbose
• The API function FindDependencies has a changed syntax and returns a changed result.

No breaking changes, no user actions required.

No breaking changes, no user actions required.

No breaking changes, no user actions required.