[jwrosewell]

Releases what has collected on rc since the last release, #83, which merged into main on 13 November 2026 at 10:49 UTC. Its Publish run 43412143722 failed in one example test before it published anything, so npm still has 4.5.102 of every package, and this release takes #83's changes to npm too. Everything below "Before you upgrade" that #83 listed is listed here again, because no one has had it yet.

This is the first release in which each package has its own version (#37). A package is released when its own code changed since its last release, or when a package it depends on is released, and only the patch number moves. Since 4.5.102 every package has changed or depends on one that has, so all 16 are released, each at 4.5.103.

This release comes three days after #83 merged, sooner than the week common-ci's CONTRIBUTING.md asks between releases, by James Rosewell's decision of 13 November to release every 51Degrees repository on Monday 16 November. npm last had a release of these packages on 4 November, so the Publish workflow's weekly check, which counts from each package's last release, does not refuse it.

This release moves Node.js toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. The native modules take the C library release 51degrees-cxx 4.5.106, whose C code is that of 4.5.105.

Before you upgrade

1. On-premise Device Detection defaults change. performanceProfile now defaults to 'Balanced', where it was 'LowMemory', and updateMatchedUserAgent is now on. Set performanceProfile: 'LowMemory' and updateMatchedUserAgent: false to keep the old behavior (#42).
2. The JSON Builder needs a Sequence Element. It fails with "The JSON Builder needs a sequence number. Place a Sequence Element before the JSON Builder in the Pipeline." when there is none. PipelineBuilder now adds the Sequence Element first, so only a Pipeline built with addSequenceElement: false, or one that adds JSONBundlerElement by hand, is affected (#53, #74).
3. The JSON sent to the browser gains a sequence entry, which holds session-id and sequence. A request with a session id and no sequence now gets sequence 1, where it got 2 (#59).
4. The Cloud Request Engine sends more Evidence. It sends every Evidence value apart from the reserved names resource, license, licence and values, which it writes itself. Before, it sent only the Evidence that a Flow Element in the Pipeline accepted, so do not add Evidence that must not reach the cloud service (#72).
5. Usage Sharing shares no cookie but 51D_ ones. It shared every cookie. It now shares a cookie only when its name starts 51D_, whatever the settings, shareAll: true included, and never the Cookie header. With trackSession on, the session cookie named by cookie is read for the repeat check and is not sent unless its name starts 51D_. Every query string and form value is still shared by default. To share only those whose names start 51D_ or are in queryWhitelist, set the new option shareAllQueryStringParameters: false (#35, #45, #135).
6. A Flow Element of your own must name its Evidence. An element with no evidenceKeyFilter accepted every key and now accepts none, and flowData.evidence.get gives undefined for a key that no element accepts. Give the element evidenceKeyFilter: new BasicListEvidenceKeyFilter([...]) with the keys it reads (#45).
7. Data update log entries change. Each error entry starts Error during check for data update, so a log search or alert on the old text needs to change (#69).
8. Latitude and Longitude have 3 decimal places, as do the points of WKT values such as Areas, so 18.542741172521133 is now 18.543 (#62).
9. A client IP value is read only when all of it is one address. Values such as 1.2.3.4/24, 1.2.3.4, 5.6.7.8 and 01.2.3.4 were read and are now skipped. Pass one address in each value (#67).
10. An Engine built with no properties keeps the first Data File's Properties across every data update. A Property that only a later Data File holds has no value until the Engine is created again (#55).
11. Settings that were accepted now throw when the element is built. These are a JavaScript Builder protocol other than http or https, an objName such as window or document (#31, #60), and a Translation Engine behavior that names none of Original, EmptyString or FlowError (#49).
12. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused with the status INVALID_BASE64. FodId.toStandardBase64 returns null for such a text, so a TypeScript caller needs to handle null (#40, #56).
13. Where one name is under more than one Evidence prefix, the Cloud Request Engine sends it once. It sends the value of the highest prefix in the order query, header, cookie, server, fiftyone, location, and compares prefixes and names ignoring letter case, so header.User-Agent and query.user-agent are sent as one field (#75).
14. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. The Cloud Request Engine and the 51Did client read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. An engine whose endpoint came from the old name logs one warning to its Pipeline, and the first 51Did client that uses it raises one Node DeprecationWarning for the process. The baseURL and endpoint options still come first. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#77, #88).
15. Each package now has its own version. All 16 are 4.5.103 in this release, and from the next release on only the packages that changed, and those that depend on them, get a new number, so the numbers will differ between packages. Each package requires the others here with ^, so a caller that pins every fiftyone.* package to one number should pin each to its own (#37).
16. The shared packages keep their code in lib. fiftyone.devicedetection.shared and fiftyone.ipintelligence.shared moved the modules their index.js exports out of examples and tests. A require of an old path, such as fiftyone.devicedetection.shared/tests/keyUtils, still works, as each old file now re-exports the module in lib. The generated types are only under types/lib (#37).
17. The JSON sent to the browser marks delayexecution only on a Property with a value, as the JSON Builder specification asks, so a Property with no value no longer carries it (#66).
18. The client-side endpoints should answer a matching If-None-Match before processing. Call Helpers.writeClientSideNotModified(request, response, flowData, options) once the evidence is added and stop when it returns true, as every web example now does. Without it a revalidation is still answered correctly but processed first. A 304 sent while processing records errors now carries Cache-Control: private, max-age=<max-age>, the Vary header and the ETag of a good response, where it carried private, no-cache and no ETag (#120).
19. A Resource Key that includes no product a cloud engine reads is logged at warning level, once for each engine, where it was an error, and warnings the cloud service sends are now logged (#123).
20. FodId's raw flags byte _flags is deprecated. Read type, usage and usageIsIndirect, which name its bits. A later release removes it (#115, #128).
21. The TypeScript types are written again from the code. HardwareProfileCloudEngine from the Device Detection cloud package now has its real type, where a caller that skips checking type files got any, so that caller's use of it is now checked (#113).
22. The JSON sent to the browser writes each item of a list of Element Data, such as the cloud hardware lookup's profiles, as plain lower-case values, with null and a nullreason for a Property with no value, where it wrote each Property's _value, hasValue and noValueMessage. With no Sequence Element in the Pipeline, the script carries an empty session id and a sequence of 1, where it carried the evidence's (#118).
23. A weighted IP Intelligence value from the cloud engine also carries weight and rawWeight, as the on-premise engine's values do. rawweighting is still there and deprecated, so read rawWeight in new code (#124, #138).
24. A query.sequence added as a JavaScript number now counts as absent. The Sequence Element counts a given sequence only when it is a BigInt or text made only of digits, from 0 up to 2,147,483,646, so an application that adds query.sequence itself as a number now gets a sequence of 1. Add the text of the number, as a query string gives it, or a BigInt. A web integration that hands over the request sees no change (#134).
25. The match metric Properties' category is now "Device Metrics", where it was "Device metrics", and they are listed in the order of the specification's table. Code that compares the category or relies on their order needs to change (#137).
26. A built Pipeline cannot be changed. It keeps a frozen copy of the list of elements it was built from, and of each list of parallel elements in it, and freezes pipeline.flowElements. Code that changed a list given to addParallel or new Pipeline, flowElementsChain or pipeline.flowElements after the build needs to build a new Pipeline instead. A method that changes flowElementsChain now throws a TypeError, and so does a change to pipeline.flowElements in strict mode code (#142).
27. weight and rawWeight on each weighted item in the JSON sent to the browser are deprecated. Each item now also carries rawweighting and value, as the specification writes them, so read those. A later release removes weight and rawWeight (#139, #147).
28. A cloud answer whose errors array has entries now fails the request, whatever its HTTP status, with an error for each entry, and the error messages name the URL the request went to. A log search or alert on "No data in response from cloud service" or "Cloud service returned status code" needs to change, and a failed answer that is not JSON gives the status code message, not "Error parsing response" (#140).
29. Usage Sharing's warnings are emitted at 'warn', as every other element's are, and at 'warning' as well, which is deprecated. Listen with pipeline.on('warn', ...). A later release stops emitting 'warning' (#141, #149).
30. minify: true now minifies the client script. It never did, as the JavaScript Builder threw the minified script away. Minifying takes time on every request for the script, so measure it before keeping the setting (#150, #132).

What changes

Packages and versions

• Each package has its own version, tagged <package>/<version> in this repository with one GitHub release for each, and the Publish workflow releases only the packages that changed since their last tag, with every package that depends on one of them. A change only to documentation, tests, examples, or a manifest's description, keywords or links releases nothing (#37).
• fiftyone.pipeline.core packs only the template its JavaScript Builder reads, JavaScriptResource.mustache, and not the rest of the JavaScript templates repository, its tests, workflows, README and licence (#106).
• fiftyone.pipeline.did carries the OWID library as a submodule and packs only its v1.js and its licence, where it installed OWID from GitHub as a bundled dependency, so installing the package needs no access to GitHub (#107).
• The six main Device Detection and IP Intelligence packages describe themselves in the words people search npm for, and name the products they are an alternative to, being UAParser.js, DeviceAtlas and WURFL, and MaxMind and IPinfo (#15).
• Every package's TypeScript types are written again with npm run tsc, so they match the code, and each package's types compile for a TypeScript caller (#113).

Web integration and client-side caching

• Helpers.writeClientSideResponse writes the response of a client-side JavaScript or JSON endpoint with Cache-Control, Vary and an ETag. Node.js has no web integration package, so call it from your own endpoints, as the web examples do (#44).

• The ETag is a weak entity tag, W/"...", and If-None-Match is compared weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. A match gets 304 for GET and HEAD, and 412 for any other method. A response to a request whose processing failed has Cache-Control: private, no-cache and no ETag. The same Evidence gives the same ETag in every process (#44).

• Evidence.addFromRequest adds the web request as a read-only view under server.http-request (#45).

• Helpers.writeClientSideNotModified answers a request whose If-None-Match matches before the Pipeline processes it, with 304 for GET and HEAD and 412 for any other method, as the web integration specification asks. A 304 carries a good response's Cache-Control, Vary and ETag, during an outage too, and writeClientSideResponse gives a matching request the same answer (#120).

• A Set Header Property's identifier may hold digits and other characters, and the header name starts at the next upper-case letter, so SetHeaderBrowser2Accept-CH sets Accept-CH (#120).

• PipelineBuilder adds the Sequence Element, the JSON Builder, the JavaScript Builder and the Set Headers Element only where the Pipeline has none with that key, compared ignoring case, so one the caller added is the one used, and building twice adds none of them twice (#105).

JavaScript Builder

• The JavaScript Builder checks the callback URL before it writes it into the client script. The protocol must be http or https, and the host must be ASCII labels or an IPv6 address in brackets, with no user information, query, fragment or zone identifier, following RFC 3986. A URL from the request that fails is left out of the script and logged (#31, #51).

• The script always carries the page request's query parameters, whether or not the builder has a callback URL, as step 7 of the JavaScript Builder specification asks (#97).

• The script takes its session id and sequence from the Sequence Element's data, with sequence 1 and no session id where there is no Sequence Element, and the JSON writes each item of a list of Element Data by the same rules as the Element Data's own Properties (#118).

• The JSON sent to the browser writes each item of a weighted value with rawweighting and value, keeping weight and rawWeight beside them for this release (#139).

Evidence

• Evidence keys and Property names are compared ignoring letter case, so header.User-Agent and header.user-agent are one key, and flowData.device.get('IsMobile') works in any letter case (#71, #68).
• An Engine's cache key is its accepted Evidence sorted by key, with each key in lower case and each value as given, made once for each request before processing, so the same Evidence added in another order or with keys in other letters is served from the cache (#125).
• Element Data is found by its key in any letter case, so flowData.get('Device') and flowData.Device work as flowData.device does (#122).
• The Sequence Element counts a given query.sequence only when it is a BigInt or text made only of digits, from 0 up to 2,147,483,646. Any other value gives a sequence of 1 (#134).

Cloud

• The Cloud Request Engine can authenticate with a License Key, alone or with a Resource Key, through licenseKey. With a License Key alone the Properties wanted must be named with requestedProperties. Both keys now travel in the request body (#64).
• A License Key appears in log entries and error messages only as its last 4 characters, with the rest as *. The packages mask a key where one can enter a message, so the mask no longer runs on each detection, and Pipeline.log passes the message it is given to its listeners unchanged (#58, #85).
• A cloud response that holds a 51Did is never stored in or served from the cache that cacheSize sets (#57).
• The Cloud Request Engine fetches its accessible Properties and accepted Evidence keys before its first request, whatever else is in the Pipeline, so a Pipeline with a cache and no Cloud Engine serves a repeated request from the cache (#73).
• Each entry of a cloud response's warnings array, from discovery or processing, is logged as a warning with any License Key masked, and a product the Resource Key does not include is logged once for each engine at warning level (#123).
• The IP Intelligence cloud engine gives each weighted value as value, weight and rawWeight, as the on-premise engine does, keeping the service's rawweighting beside them for this release (#124).
• An empty answer, or one whose errors array has entries, fails the request with the specification's messages, which name the URL (#140).

Usage Sharing

• Usage Sharing accepts no Evidence, so a Pipeline that holds it no longer accepts every header, and a header no other Flow Element reads takes no part in a cache key, the ETag or the Vary header. The Flow Data still keeps what Usage Sharing shares. evidence.add keeps a value when a Flow Element accepts its key or when Usage Sharing would share it. An application that adds its own Evidence therefore has nothing to change, and the values it adds are shared under the same rules as the values of a request. evidence.addFromRequest also adds the whole request as server.http-request, which is Constants.evidenceHttpRequest in fiftyone.pipeline.core, a frozen object that holds each value of the request under the key it has as Evidence. Read it with evidence.get('server.http-request'). evidence.getAll() leaves it out, and it is never shared whole (#45).
• After 10 failed sends in 100 seconds, sending pauses, and the pause doubles up to 300 seconds while sends keep failing. A new trackSession option tells sessions apart (#36, #35).
• The record names the version of the Pipeline that wrote it, read from fiftyone.pipeline.core, where every release wrote 4.4.7, so the spread of a release can be measured. The session id and sequence are recorded as SessionId and Sequence whatever the letters of their keys (#109).
• The record marks a value with replaced characters escaped="true", where it was replaced="true", and cuts a value at 10,000 code points, where it was 512 characters (#54).
• A new shareAllQueryStringParameters option, true unless set to false, shares every query string and form value. Set to false, only the names that start 51D_ and those in queryWhitelist are shared. No cookie but 51D_ ones is shared, shareAll included (#135).

Data updates

• Data update log entries and errors use the text and levels of the specification's error table, which every language now shares. Every check reports a status, and an updateComplete listener that throws is logged (#69).

• With updateOnStart and a License Key or an update URL, an on-premise Engine downloads a missing Data File, where the build threw. DataFileUpdateService.updateFromMemory is new (#52).

• The file system watcher runs on its own fileSystemWatcher setting, whether automatic updates are on or not, and needs no License Key. This reverses a change on rc that made the watcher wait for automatic updates, and so for a License Key (#52), which was a mistake. That change never reached npm, so the watcher behaves as in 4.5.102 (#90).

• A data file has one polling timer. An update started by hand with updateDataFile replaces the waiting timer rather than adding another, so the file is checked once in each polling interval however many updates are started (#63).

Device Detection and IP Intelligence

• Node.js reads each on-premise Property by name, because a read by name measured faster than a read by position, at 711 ns against 2,797 ns for one read of IsMobile on Ubuntu ARM with Node.js 22 (run 42995016804, #68). The IP Intelligence engine was timed on its own as well, and a read by name took about a third of the time of a read by position on Ubuntu x64 and ARM (run 43487633019, #81).
• Both on-premise engines read their accepted Evidence keys again after each data refresh, as the specification asks, so the keys a new data file accepts are used from then on (#130).
• Each match metric Property of the on-premise Device Detection engine has the category "Device Metrics", the data files "Lite", "Premium", "Enterprise" and "TAC" and a default value, and they are listed in the order of the specification's table, after the data file's Properties (#137).

51Did

• A 51Did payload too short for its header whose flags byte names version 1, 2 or 3 is refused as an unsupported version naming that version, as one of normal length is (#115).

Translation

• TranslationEngine accepts the specification's option names, sourceElementDataKey and missingTranslationBehavior. sourceDataKey and behavior still work and are deprecated (#49).

C library

• The C library moves from 51degrees-cxx 4.5.103 to 4.5.106, whose C code is that of 4.5.105. The HighPerformance profile holds in memory only what the named Properties read, and for 51D_GetHighEntropyValues and 51D_StructuredUserAgent the query value is used before the cookie value (#67, #55, #92).

Configuration

• A list setting may be given as one comma separated string, as the pipeline configuration specification says a configuration file gives a list. The engines' restrictedProperties and usage sharing's queryWhitelist and headerBlacklist read it as its items, through the new listSetting of fiftyone.pipeline.core, and an array works as before (#129).

Examples and documentation

• Every on-premise example runs with no settings on the free Data Files, which it downloads the first time. A Property that only the Enterprise Data File holds is shown as needing that file, with a link to ask for a copy (#32).
• Every example, console and web, ends with a Find out more section giving the repositories and tagged 51degrees.com pages to follow up, including where it stops early for want of a key or a data file (#103).
• Each example's 51d.json names its engines by package, so the same file works in this repository and with the installed packages, where eleven named them by a path into the source (#110).
• The IP Intelligence mixed API example runs with no settings on the free Device Detection and IP Intelligence Lite files, where it searched the disk for paid files first. It names each Property only the Enterprise data files hold as needing them, with a link to ask for a copy (#111).
• The data update examples check for a License Key before they look for a data file, the IP Intelligence ones use the small ASN file, every automatic update example ends with status 0 when it succeeds, and both update data file examples read _51DEGREES_LICENSE_KEY first. The cloud metadata example says a resource key is needed when none is set, and the match metrics example prints a documentation link a person can follow (#101).
• fiftyone.pipeline.cloudrequestengine has the star sign Cloud Engine example the pipeline specification asks for, using the real Cloud Request Engine against a star sign service it starts on the same machine, so it needs no key or network. The simple star sign example takes a date of birth as its argument (#121).
• The IP Intelligence on-premise web example shares usage when its configuration names the usage sharing element, as its own 51d.json does and as the Device Detection one does, with a comment saying production should leave usage sharing on. The console examples still turn it off (#131).
• Every cloud example run with no Resource Key ends without an error and with status 0, names _51DEGREES_RESOURCE_KEY, gives a tagged link to where a key is created and ends with its Find out more section, and a test runs each of the 20 with no key (#133).
• Links to the configuration page, in the READMEs, code comments, example output and the messages that say where to create a Resource Key, point at https://51degrees.com/configure, where the page has moved from configure.51degrees.com (#87).
• The repository has one LICENSE file at its root, the EUPL 1.2 text, and every JavaScript source file carries the standard 51Degrees header. The fiftyone.geolocation package no longer carries a LICENSE file of its own (#79).

Building and testing

• The Selenium contract tests run for real on Linux. The CI removed .NET to free disk space, so dotnet was missing and the step reported a pass without running a test. The step now fails when dotnet is missing or when no test passed, and a pull request into rc is built on the configurations its changes need, with macOS and the performance tests left to builds of rc and the release (#27).
• The pipeline examples' tests run each example in its own process and check what it prints or serves, where they built a function and never called it, and the 51Did offline reader and usage sharing examples have tests of their own (#104).
• The umbrella getting started tests run each example in its own process and check its answers, and a new test reloads a Device Detection engine from the Lite data file onto the Enterprise data file and checks that it keeps its first Properties, as the C library does (#108).
• The web integration elements test runs as a unit test, so the Publish tests, which run the integration tests against the packed packages, no longer look for a test file the core package does not pack (#112).
• The native read timing test compares paired rounds and counts the case work, so it no longer fails at random on macOS (#96).
• The Publish workflow takes allow-early-release, for a release agreed to go out less than a week after the last, and common-ci-ref, to run common-ci's steps from a branch other than main (#99).
• The cloud 51Did tests run on pull requests into rc as well as main, so a change to the 51Did package is tested against the live cloud service before it reaches a release (#100).
• AGENTS.md says that a test failing on timing is fixed rather than run again, and points at common-ci's one list of environment variable names (#93, #89).
• Tests of the cloud Property metadata before and after discovery and of the Evidence a Cloud Aspect Engine accepts, and of a session cookie found only in the web request (#144, #145).

Environment variables

Each name below has a new name that starts _51DEGREES_, which every shell can set. The Cloud Request Engine and the 51Did client read the cloud endpoint, and the examples and tests read the rest. Every old name is still read in this release, but only when its new name is unset or empty, and its first use is reported as deprecated, through the Pipeline's logger or a DeprecationWarning in the packages, and in a printed message in the examples and tests. Each constant that held an old name holds it again and is marked @deprecated (#70, #77, #88).

Old name, deprecated	New name
FOD_CLOUD_API_URL	_51DEGREES_CLOUD_ENDPOINT
51DEGREES_DD_PATH	_51DEGREES_DD_PATH
51DEGREES_IPI_PATH	_51DEGREES_IPI_PATH
51DEGREES_RESOURCE_KEY, RESOURCE_KEY	_51DEGREES_RESOURCE_KEY
LICENSE_KEY	_51DEGREES_LICENSE_KEY
LicenseKey, LICENSEKEY (the update data file examples)	_51DEGREES_LICENSE_KEY
TEST_SUPER_RESOURCE_KEY, TEST_PLATFORM_RESOURCE_KEY, TEST_HARDWARE_RESOURCE_KEY, TEST_BROWSER_RESOURCE_KEY, TEST_NO_SETHEADER_RESOURCE_KEY	_51DEGREES_RESOURCE_KEY_SUPER, _51DEGREES_RESOURCE_KEY_PLATFORM, _51DEGREES_RESOURCE_KEY_HARDWARE, _51DEGREES_RESOURCE_KEY_BROWSER, _51DEGREES_RESOURCE_KEY_NO_SETHEADER

Fixed

• From the second request on, the JSON sent to the browser lost delayexecution and evidenceproperties for every element but one, because the JSON Builder kept each element's delayed Properties under one shared key (#66).
• An update started by hand with updateDataFile started another polling timer for the same data file each time, so the file was checked once for each of them in every polling interval (#63).
• With no callback URL, the client script's renderedParameters returned nothing, and the script then threw a TypeError on a page whose tab held a record of an earlier request and values saved from it (#97).
• A data update download cut short part way was logged as "No response from data update service", or on Windows as the access error, depending on timing. It is now always the access error, "Error accessing data update service", with its cause, and the part file is removed before the failure is reported (#94).
• The mixed web example named its IP Intelligence engine by a path into the source folder, so it failed against the published packages, as it did in the 13 November publish. It now names the package. The location examples printed ReferenceError: resourceKey is not defined, and now read the key as the other examples do (#95).
• The Cloud Request Engine asked the cloud service for its Evidence keys and accessible Properties before every request, so each request made three calls to the cloud service in place of one. Release 4.5.102 and earlier have the fault (#73).
• In 4.5.102 a Cloud Engine threw TypeError: Cannot convert undefined or null to object when the Resource Key did not include its product. One error is now logged for each Engine and the request carries on (#41).
• An updateComplete listener that threw ended the Node.js process (#65).
• The wait before a data update check used only the millisecond part of the Data File's expected update time, so polling did not wait for that time (#52).
• Usage Sharing put a comma between the <Device> elements of a message, logged a failed send as Usage data sent, and wrote <ClientIP>undefined</ClientIP> for a request with no client IP (#35, #36, #54).
• The on-premise web examples never showed their warning about an old data file, because each was given the current time as the file's published date and compared days with milliseconds. They now warn from the file's own published date (#102).
• The client-side evidence and on-premise flow element web examples ended their own server on the first page, because each page read a star sign or hemisphere that the element left out of its data until it was known. Both are now null until known (#104).
• The IP Intelligence compare, metrics, suspicious and mixed examples stopped with RangeError: Maximum call stack size exceeded while they searched for a Data File (#32).
• flowData.get('Device') and flowData.Device threw where flowData.device worked (#122).
• The Device Detection cloud package's types did not compile for a TypeScript caller (TS2307), because its index.js required its own files through .. (#113).
• A list setting given as one comma separated string stopped the build with a TypeError for restrictedProperties and headerBlacklist, and was split into single characters for queryWhitelist (#129).
• The simple and client-side star sign examples gave no star sign for 21 June (#121).
• With no Resource Key set, three cloud web examples stopped with an uncaught error and the 51Did creator context demo exited with status 1 and no link to where a key is created (#133).
• A list of parallel elements given to addParallel stayed the caller's list, so an element added to it after the build was processed by the built Pipeline, and one taken out was not (#142).
• The same Evidence added in another order, or with a key in other letters, missed an Engine's cache and was processed again, and the key stored was made after processing (#125).
• A failed cloud answer with an empty body read as "Error parsing response - [object Object]", and one whose JSON had no errors member threw a TypeError (#140).
• One JSON Builder added to a second Pipeline failed on any element the first Pipeline lacked, and used the first Pipeline's delayed execution for an element with the same data key. An element whose Properties were replaced after its first request, as a cloud engine's are when discovery succeeds late, kept the delayed execution of its old Properties (#143).
• Usage Sharing's warnings of a full queue, a pause and each failed send were emitted only as the event warning, which no example or document listens for (#141).
• Helpers.setResponseHeaders threw when processing stopped before the Set Headers element, which ended the process where it was called in a promise with no catch, as the getting started web examples do. It now sets no headers and logs a warning (#146).
• With minify: true the JavaScript Builder gave its script unminified, because it used the minified script only when uglify-js reported error as null, where uglify-js leaves it undefined. A failure to minify is now logged as a warning (#150).

Issues this closes

• Closes Authenticate a Cloud Request Engine on a license key alone, and name the properties wanted #7, done by #64, which reached main with Release candidate #83.
• Closes The rendered script does not parse when no endpoint is configured #8, fixed by #97.
• Closes Take OWID as a submodule, as the other languages do #78, done by #107.

Build

The release build, the timing against main, the Publish dry run and the Nightly Pipeline dry run on this head are running, and this section is filled in from them when they end.

Only the patch number moves.