[recrwplay]

Bumps @neo4j-antora/tabbed-nav from 0.4.1 to 0.4.2.

What

Each version in docsetVersions (on a component's latest tabs.json entry) now carries selectorText, and docsets.json passes it through to each version:

{ "version": "2026.11", "latest": true, "selectorText": "(Current) (LTS)", "url": "/cypher-manual/2026.11/", "pdf": "..." }

selectorText is the text the page's version selector shows after the version. The selector-labels extension sets it on each component version: (Current) for the latest version, (LTS) for a version marked lts: true in antora.yml, or both. The docsets modal in docs-ui (docs-restructure) uses it so it shows the same markers as the page, including LTS, which it could not show before.

• It is '' when a version has no marker, and absent for a docset that has not been built since this change, so a consumer can tell the two apart. The modal falls back to (Current) for the latest version when the field is absent.
• It relies on selector-labels having run before tabbed-nav. The docs build adds tabbed-nav last, so it should have.

Testing

• The docsets.js merge was checked on sample data: a rebuilt docset keeps selectorText (including ''), and an older one has no such field.
• Not tested: a full Antora build with selector-labels and tabbed-nav together, so the ordering above is not confirmed against a real build.

Rollout

• The aggregator in docs-publish already installs the latest tabbed-nav (neo4j/docs-publish#37), so it needs no change.
• A docset only gains the field when it is next built with this version.

Follow-up

Document selectorText, along with docsets.json and its attributes, in the docs-playbook tabbed-nav page, from main.

[neo4j-docops-agent]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.