Releases: aplteam/Tatin
Releases · aplteam/Tatin
Version 0.98.2
- Fix for #137
- Documentation updated regarding server certificates
Version 0.98.1
- Restriction removed that required a placeholder for user command packages
- Documentation corrected: Credentials.txt and setup.dyalog
- Test server certificates were missing
Version 0.98.0
- Passwords are now salted and hashed
- The file
Credentials.txt
is automatically converted to a new format which is saved
in a fileCredentials.csv
whileCredentials.txt
is deleted - A file
apl-dependencies.txt
may now carry comment lines, recognized by a leading⍝
- Bug fixes
GetDeletePolicy
did not react well in case of a 400 or 404- Error handling in
PublishPackageToRemoteRegistry_
improved ]Tatin.PublishPackage
did not ask for confirmation when it established the zip file itself
Version 0.97.1
- Bug fixes
- ]ReInstallDependencies showed namespace assignments under some circumstances
- Fix for #136
- Documentation polished regarding user command scripts.
Version 0.97.0
- BREAKING CHANGE: The
]FindDependencies
user command's-detailed
flag has been renamed toverbose
- BREAKING CHANGE: The API function
FindDependencies
has a changed syntax and returns a changed result - Level-1 help now repeats the help given by level 0 which in many cases is required in order to refer
to arguments by name because by default only the names of modifiers are provided by the framework ]TATIN.FindDependencies
now accepts not only a local folder but a Registry alias or a URL as well
as[*]
as argument; the API functionFindDependencies
has been enhanced accordingly- Packages
CommTools
andGitHubAPIv3
updated - Fixes
- User command help level 0 corrected: some (most) options carried square brackets despite the fact
that they are by definition always optional ]TATIN.FindDependencies
help confused the arguments which are
<folder|registry-alias|URL>- In case an invalid
TargetRequest
parameter was specified a Tatin client appeared to hang ]Installpackage
did not ask for confirmation in case no argument was provided and only one Cider
project was open and had only one dependency folder defined- In case the installation folder was derived from a Cider project's dependency settings it went
wrong in case a namespace was assigned - In case the user used an outdated version of Tatin for accessing a Tatin Server the message provided
was wrong in case the server did not run the version that was required but a later one. That can
lead to problems when the server runs a yet unpublished beta version. - Two directories in
TestData/
had an uppercase/lowercase problem: Uninstall[56] versus UnInstall[56]
- User command help level 0 corrected: some (most) options carried square brackets despite the fact
Version 0.96.2
UpdateClient
does not rely on .NET anymore on any platform- You might save a GitHub personal token if GitHub's limit policy poses a problem (client only)
- Bug fixes
- Handling of
MyUserSetting
was faulty - Default handling for
license
was faulty - Minor fix in
EstablishRegistry_
- Documentation regarding
UserSettings
fixed - Creating/updating tatin_os.list (server only) failed on Mac-OS if the Registry path contained /../
- Handling of
Several small improvements and bug fixes
- The server now checks all newly introduced config properties and returns a helpful message
in case one of them is not defined. - New version of Plodder with a new version of RumbaLean (proxy related)
- Bug fixes
- Server crashed on packages that did not provide
maintainer
orminimumAplVersion
- Help page for
]CheckForLaterVersion
was not correct
- Server crashed on packages that did not provide
Several improvements
Proper email address introduced for tatin.dev: [email protected]
- Help pages for
]PackageConfig
polished - In case of no Internet connection a hint is provided now in the error message
- Bug fixes
- Proxies
- When a new package config file was created no license information was requested
- In a new package config file
ml
became an array rather than a single value
Major change on BuildPackage
- BREAKING CHANGE:
BuildPackage
now requires a namespace with parameters as right argument, and it does
not accept an optional left argument anymore.
Ift needsdistributionFolder
and therefore at least Cider 0.26.0 ]BuildPackage
now checks Cider projects in case the target folder is not specified. It defaults to
distributionFolder
now.]PublishPackage
now works without any parameter at all by using CidersdistributionFolder
if available- New version of both
Plodder
andRumbaLean
supporting proxies as well as elevating http to https in the process - Bug fixes
- In case a user command was re-installed
InstallPackages
produced a FILENAME ERROR on the user command script
- In case a user command was re-installed
0.94.0
- BREAKING CHANGE: this version of Tatin requires Cider 0.25.0 or better
This is because the Cider config propertytatinFolder
is nowdependencies.tatin
&dependencies_dev.tatin
- Bug fixes:
LoadPackages
did not work as expected when called from a sub-namespace of#
- Passing a Cider alias to
]InstallPackages
crashed - this was recently introduced ]UnInstallPackage
was ill-named: should have been]UnInstallPackages
Potentially (though unlikely) this is also a BREAKING CHANGE]UnInstallPackages
did not always ask for confirmation when the folder was established by Tatin]UnInstallPackages
should have accepted a Cider alias but did notListPackages
produced incomplete results or LENGTH errors when[*]
was used together with two
or more flags (-date
,-project_url
,-noaggr
)