Coverage remained the same at 99.45% when pulling db48957 on paescuj:pnpm into ed3c18f on open-cli-tools:main.

LGTM I think, is there anything still pending here? 😄

Only the open conversation... I'm going to rebase and merge it afterwards 🚀

🤔 it seems pnpm is a pickier than npm when running publish:

$ pnpm publish
 ERR_PNPM_GIT_NOT_UNCLEAN  Unclean working tree. Commit or stash changes first.

If you want to disable Git checks on publish, set the "git-checks" setting to "false", or run again with "--no-git-checks".

$ git status
On branch main
Your branch is up to date with 'origin/main'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	tst-npm/

nothing added to commit but untracked files present (use "git add" to track)

(though I might be on a possibly old release of pnpm, and this might have been a bug)

🤔 it seems pnpm is a pickier than npm when running publish:

$ pnpm publish
 ERR_PNPM_GIT_NOT_UNCLEAN  Unclean working tree. Commit or stash changes first.

If you want to disable Git checks on publish, set the "git-checks" setting to "false", or run again with "--no-git-checks".

$ git status
On branch main
Your branch is up to date with 'origin/main'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	tst-npm/

nothing added to commit but untracked files present (use "git add" to track)

(though I might be on a possibly old release of pnpm, and this might have been a bug)

Hmm you mean because it's not really "unclean" since it's only an untracked file? In that case it might indeed be a bit pickier and also this might have been addressed in a newer pnpm release...