[jwrosewell]

Problem

James Rosewell's rule for the 11 November 2026 release is "The point of the release is consistency." When no Sequence Element has produced a sequence number, the JSON Builder fails with an error, and each language that has the error gave it its own wording. Node said "There is no sequence number. A Sequence Element needs to be placed before the JSON Builder Element in the Pipeline." (pipeline/fiftyone.pipeline.core/jsonbundler.js lines 73 and 74 on rc).

What the specification says

specifications#139, merged into rc as d72eb074, gives the exact text. json-builder.md at d72eb074, lines 120 to 142:

If no Sequence Element has produced a sequence number when the Element runs, the Element MUST fail with an error and MUST NOT set its JSON value. The error MUST carry the message below, which is the text every implementation gives, so that the message reads the same in every language and makes life easier for 51Degrees support.

The JSON Builder needs a sequence number. Place a Sequence Element before the JSON Builder in the Pipeline.

PHP names this Element the JSON Bundler, so PHP gives the same message with JSON Bundler in place of JSON Builder, reading "The JSON Bundler needs a sequence number. Place a Sequence Element before the JSON Bundler in the Pipeline." Nothing else differs. Where an implementation wraps the error in another, such as a Pipeline Configuration Exception that carries the first error as its cause, the error the caller reads carries the message.

The message is the whole text of the error. An implementation MUST NOT add anything to it, such as a link to documentation. A prefix that a language's error type writes in front of every error of that type when the error is shown, such as the type's name, is not part of the message.

What changed

Two commits, the test first (f654ea0) and then the message (a7bb064). Nothing else changes.

• pipeline/fiftyone.pipeline.core/jsonbundler.js lines 73 and 74, getSequence reads the sequence from the Sequence Element's data, or from query.sequence when there is no such data, and throws an Error with the text when the value it reads is not a whole number. Nothing wraps it, so the error recorded for jsonbundler carries the text as it is.

• fails with an error and sets no JSON in pipeline/fiftyone.pipeline.core/tests/jsonBuilderSequence.test.js lines 54 to 64 now asserts the recorded error's message with toBe against the exact text, where it matched /Sequence Element/ before, which the old wording also passed.

Tests and builds

• Red, the test commit f654ea0 with the message change left out, on a temporary branch, https://github.com/51Degrees/51degrees-node/actions/runs/43020709820. expect(received).toBe(expected) fails in that one test (1 failed, 8 passed), expecting the text.
• Full build on the head a7bb064, https://github.com/51Degrees/51degrees-node/actions/runs/43022749173, GREEN. Every Setting 'PullRequestSha' line in its job logs (7 of them) reads a7bb064. macOS was left out of this draft's full build under the 9 November decision. The rc head is built with macOS before it merges into main.

What remains

specifications#139, which states the text, has merged into rc as d72eb074. The same text goes into the other languages in 51degrees-dotnet#135, 51degrees-java#104, 51degrees-python#101, 51degrees-php#69, 51degrees-go#100 and 51degrees-rust#383. Nothing else is outstanding here.