SUSHI 2.5.0 includes the following enhancements and bug fixes:
- New
--require-latestflag to indicate SUSHI should fail if it is not the latest version (details below) (#1083) - Failure to determine latest SUSHI version is now logged as a warning (rather than error) (#1084)
- Fix handling of extensions in
CodeSystemandValueSetdefinitions (#1069) - Fix resolution of
baseDefinitions that use a versioned canonical URL (#1067) - Only consider
master/mainbranches when searching forcurrentdependency version (#1017) - Fix download of
currentdependencies that usemainbranch (#1075) - Warn when authors access an existing slice by index rather than slice name (#1030)
New --require-latest flag to indicate SUSHI should fail if it is not the latest version
As of SUSHI 2.4.0, SUSHI informs users when there is a newer version of SUSHI available. Starting with this release (2.5.0), authors may optionally use the --require-latest flag to force SUSHI to exit with an error if it detects that a newer version is available or if it can't determine what the latest version is. This may be especially helpful in publication workflows where it is important that the latest version of SUSHI be used.
Full Documentation
For additional documentation, refer to FSH School's SUSHI documentation and/or the FSH Specification.
Install or Update
To install or update to this release, run the following command:
$ npm install -g fsh-sushiTo revert to a previous release, run a command like the following:
$ npm install -g fsh-sushi@2.4.1To check or confirm what version of SUSHI you have installed, you can run the following command:
$ sushi -v