From adc33787ac22c91ebd5696484b8b7367e790eb9d Mon Sep 17 00:00:00 2001 From: Mark Dumay <61946753+markdumay@users.noreply.github.com> Date: Fri, 10 Jul 2026 07:38:39 +0200 Subject: [PATCH] docs: fold pnpm into the ecosystem caveat Extend the existing reusable-CI/org-secrets note so it also states that modules from this template use pnpm internally, and point npm-preferring authors to swap the pnpm commands when working outside the organization. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8d2948f..77a9150 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,7 @@ Hinode is a clean blog theme for [Hugo][hugo], an open-source static site genera This module uses [semantic-release][semantic-release] to automate the release of new versions. The package uses `husky` and `commitlint` to ensure commit messages adhere to the [Conventional Commits][conventionalcommits] specification. > [!NOTE] -> The bundled workflows call gethinode's shared reusable CI (`gethinode/.github`) and expect the gethinode organization context — including organization secrets such as `SEMANTIC_RELEASE_GIT`, used by the release and module-update workflows. Modules created from this template are intended for the gethinode ecosystem. If you maintain a module **outside** the gethinode organization, replace the reusable-workflow callers under `.github/workflows/` with self-contained equivalents and supply your own release credentials. +> The bundled workflows call gethinode's shared reusable CI (`gethinode/.github`) and expect the gethinode organization context — including organization secrets such as `SEMANTIC_RELEASE_GIT`, used by the release and module-update workflows. Modules created from this template are intended for the gethinode ecosystem and use **pnpm** internally (via the `packageManager` field and `pnpm-workspace.yaml`). If you maintain a module **outside** the gethinode organization, replace the reusable-workflow callers under `.github/workflows/` with self-contained equivalents and supply your own release credentials — and, if you prefer **npm**, swap the `pnpm` commands in `package.json` and the workflows for their npm equivalents.