Weird } in gitlab output

[glensc]

Seems to be present after each package name.

Here's copy of full HTML:

• danger.html

[glensc]

@orta can you make a new release, this time actually containing the fix?

See #45 (comment)

Preferably with some automation for transparency to the end users:

• Automate npm publishing with GitHub Actions #51

[glensc]

The current workaround, use any version before:

• feat($monorepo): coalesce duplicate dep updates w/ multiple package.json #44

That appears to be 1.3.3

[glensc]

@orta ping. seems easy fix just make new release from the default branch

[orta]

Yep, deployed as 1.5.0

[glensc]

Looks like 1.5.0 update is breaking change. No longer can run jest

    Details:

    /Users/glen/Library/Caches/glen/node_modules/danger-plugin-dangered/node_modules/danger-plugin-yarn/node_modules/node-fetch/src/index.js:9
    import http from 'node:http';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

[glensc]

Apparently broken with 9e16443 commit

Unclear what's the commit purpose,
Why no Pull Request? Why no explanation what is the problem to be solved?

Perhaps this repo should be moved to a danger organization, so the community can deal with the maintenance?

[orta]

Broke by 714f03b and the commit message says what it does - typescript did not build on master when I cloned it

[orta]

Fixed in 1.5.1, and no, I'm not really into moving to the danger org - that's not really for plugins

[glensc]

Confirming fixed with 1.5.1. Thanks!