Skip to content

docs: fold pnpm into the ecosystem caveat #866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markdumay merged 1 commit into from
Jul 10, 2026
Merged

docs: fold pnpm into the ecosystem caveat #866

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<!-- ## Configuration

Expand Down