» Sentinel Runtime Release Notes
These are the release notes for the Sentinel runtime.
Sentinel integrations and embedded runtimes may not always have the latest version installed, depending on the product's individual release cycle. For more information, contact the support team for your specific integration.
» 0.10.4 (August 15, 2019)
runtime/encoding: Fixed an issue with conversion of null values that could lead to crashes in imports.
» 0.10.3 (July 15, 2019)
command/config: Parsing a configuration file where malformed data is encountered after apparently properly-formed data will now report an error. An example would be a situation where misplaced braces would cause a JSON object to only parse part of the configuration file.
» 0.10.2 (June 25, 2019)
lang/parser: Corrected an issue where parsing certain compound binary expressions where the negation predicate (
not) was in use would cause the negation to have no effect. Example:
foo else "bar" not in "baz"would have been parsed and evaluated as
foo else "bar" in "baz", effectively producing the opposite result.
» 0.10.1 (May 9, 2019)
sentinel testnow displays policies without tests as an unknown result with [no test files], instead of the somewhat erroneous behavior of displaying it as a PASS. A full test run with a mixture of passing tests and no tests still results in an overall successful result.
» 0.10.0 (April 18, 2019)
- Mixed-number arithmetic operations are now allowed. Addition (
+), subtraction (
-), multiplication (
*), division (
/), and remainder operations (
%) are no longer restricted to number values of the same type, and can mix integer and floating point. The result of these operations is always a floating-point number.
- Remainder (modulo,
%) operations are now allowed on floating-point numbers.
lang/parser: Fixed a bug that affected the user of
inin a compound expression.
runtime/eval: Fixed error messages on evaluation errors with
into indicate that strings are an allowed type along with lists and maps.
» 0.9.2 (March 15, 2019)
This is a dependency update related to the changes mentioned in 0.9.1. No other changes have been made.
» 0.9.1 (March 14, 2019)
This is a patch release that is required to integrate with the latest versions of the Sentinel SDK. No other changes have been made.
» 0.9.0 (January 28, 2019)
imports/strings: Added a
joinfunction to the
stringsimport. This can be used to join a list into a string with a specific separator. Multi-dimensional lists and all Sentinel primitives are supported.
» 0.8.1 (January 17, 2019)
lang/eval: Fixed a bug that prevents the effective use of
» 0.8.0 (January 14, 2019)
- Mocks can now be represented by Sentinel code. This allows for the mocking of functions and other complex data structures that cannot be represented in JSON. For more information on using this feature via mocks, click here.
- Import validation has now been moved to the semantic checking phase. This
should result in better reporting of validation errors. In addition, import
validation will now enforce the use of an
asidentifier when an import path is not a valid identifier on its own (example:
» 0.7.0 (December 12, 2018)
- There have been changes to the runtime in how scope is handled over multiple policy executions. Scope is now correctly unique per single policy execution, and values set or builtins that are overridden in one policy will no longer affect those values within another.
» 0.6.0 (November 30, 2018)
imports/runtime: This new import allows for one to check various aspects of the Sentinel runtime as it may be embedded in the simulator or a specific implementation. For now, it allows the version to be checked.
» 0.5.1 (November 28, 2018)
imports/time: Added the
zone_stringattributes to assist with validation of a timespace's zone.
command/fmt: Added a new -check flag. This option does not commit changes, but instead checks to see what files need formatting and outputs them on stdout.
command/test: Ensure that passing test results are correctly output one per line. Tests are also now run in a deterministic fashion based on lexicographical (alphabetical) order.
weekday_namewill now show up correctly in a returned timespace result.
» 0.5.0 (November 5, 2018)
spec: Selectors can now contain any reserved word (example:
rule) or keyword operator (example:
not). This only works for the selector part of the expression (after the first period) - the first primary expression (before the first period) still needs to be an identifier that does not conflict with reserved words.
- The simulator should now display import function call names correctly in import errors.
» 0.4.0 (October 1, 2018)
builtin: Added the
boolbuilt-in type conversion function. Booleans will also now accepted as conversion into other values as well, with the full list of behaviors available in the spec.
» 0.3.2 (September 27, 2018)
sentinel applynow prints out messages output by the
print()function when a trace is output on policy failure, or when a trace is forced with
imports/time: Added the
weekday_namekeys to the timespace, which return full-English names for the month and day of the week.
sentinel fmt -Will no longer print out the filter status message on the output stream when
-write=falseIs not explicitly stated. This brings the behavior of the command in line with the help text.
runtime: Index operations on the right-hand-side that have negative indexes that go out of range (example:
length(list) * -1 - 1) now correctly return
undefined. left-hand-side index assignments with a out-of-range negative index still return runtime errors.
» 0.3.1 (August 3, 2018)
runtime: Basic index assignment has been implemented as per the spec.
runtime: Index expressions for lists with negative indexes will no longer panic if the list index is less than
length(list) * -1.
» 0.3.0 (July 20, 2018)
- New standard import:
types. This can be used to dynamicaly detect the type of some value.
» 0.2.0 (April 11, 2018)
- New standard import:
json. Marshal and unmarshal JSON documents and access their contents as native Sentinel values.
continue. These are now both specified and implemented.
breakallows loop exiting and
continueallows immediate execution of the next iteration.
print()map values are now ordered alphabetically by keys.
- command/test: If no
testblock exists, test behaves like it is asserting
- runtime: default maximum stack depth to 500
print()map values now appear like more typical maps.
- runtime: division by zero is an error, not a crash
- runtime: plugins that send map values with
nullvalues now decode properly into native Sentinel values.
» 0.1.0 (September 19, 2017)