Skip to content

feat: Manifest v3 support, add communciation with JabRef via HTTP #1

feat: Manifest v3 support, add communciation with JabRef via HTTP

feat: Manifest v3 support, add communciation with JabRef via HTTP #1

Triggered via pull request March 16, 2026 10:05
Status Failure
Total duration 27s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
test
Process completed with exit code 1.
tests/translator-import.test.mjs > Zotero translator > exports expected entry points for Bibliontology RDF.js: translators/zotero/Bibliontology RDF.js#L365
ReferenceError: Type is not defined ❯ translators/zotero/Bibliontology RDF.js:365:6 ❯ tests/translator-import.test.mjs:47:7
tests/translator-import.test.mjs > Zotero translator > imports Bibliontology RDF.js: tests/translator-import.test.mjs#L47
AssertionError: promise rejected "ReferenceError: Type is not defined" instead of resolving ❯ tests/translator-import.test.mjs:47:38 Caused by: Caused by: ReferenceError: Type is not defined ❯ translators/zotero/Bibliontology RDF.js:365:6 ❯ tests/translator-import.test.mjs:47:7
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/