From d0502e39bcc923adc09237ee64d710dc8561260f Mon Sep 17 00:00:00 2001 From: Mati OS Date: Fri, 11 Sep 2026 15:37:20 -0300 Subject: [PATCH 1/2] docs: require a version bump and pull request per issue PR 12 merged the plugin half of explorer#402 without touching the version. npm-publish runs on every push to main, but pnpm publish skips a version already on the registry without failing, so the run went green and npm still serves 1.3.1 without the fix. Document that a branch changing packages/plugin/ bumps the package version in a final vX.Y.Z commit, and that every resolved issue ends in a pull request against upstream main: in full in CLAUDE.md, and the version bump in CONTRIBUTING.md. --- CLAUDE.md | 29 +++++++++++++++++++++++++++++ CONTRIBUTING.md | 5 +++++ 2 files changed, 34 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index bdb1c23..462a566 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -48,3 +48,32 @@ Commits and PRs carry no AI attribution — no `Co-Authored-By: Claude` trailer, `🤖 Generated with [Claude Code]` footer, no "AI-generated" notes in code comments or PR bodies. The human running the session is the sole author; write commit messages in their voice, describing the change rather than what produced it. + +## Resolving an issue + +Issues are tracked in +[openscan-explorer/explorer](https://github.com/openscan-explorer/explorer/issues): +`issue-402-trim-build-info` resolves explorer#402. Every resolved issue ends with +the two steps below, without waiting to be asked. No hook enforces them. + +**Bump the plugin version** whenever the branch changes anything under +[packages/plugin/](packages/plugin/). Set `version` in +[packages/plugin/package.json](packages/plugin/package.json) one step past upstream +`main`: minor for `feat`, major for a breaking change, patch for anything else. +Commit it last and on its own, with the bare version as the subject (`v1.3.2`, +exempt from the format check). One bump per branch; if `main` reaches that version +first, rebase and bump again. Merging to `main` publishes to npm, and `pnpm publish` +skips an already-published version without failing, so an unbumped merge ships +nothing while CI stays green. + +**Open a pull request** for the issue: + +```bash +pnpm build && pnpm test && pnpm lint +git push -u origin +gh pr create --repo openscan-explorer/hardhat-plugin --base main --head MatiasOS: +``` + +Title it like a commit subject. Open the body with +`Fixes openscan-explorer/explorer#`, or `Part of` when work on the issue remains +outside this repo. Leave the merge to a maintainer, since merging publishes. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3bbfc98..3756352 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -76,6 +76,11 @@ pnpm build && pnpm test && pnpm lint pnpm test:hooks # only if you changed .githooks/ ``` +A change under [packages/plugin/](packages/plugin/) also bumps `version` in its +`package.json` (minor for `feat`, major for a breaking change, patch +otherwise) in a final commit whose subject is the bare version (`v1.3.2`). +Merging to `main` publishes to npm, and an unchanged version publishes nothing. + Push your branch to your fork and open the PR against `openscan-explorer/hardhat-plugin`, base `main`: From 21f11d8c23a2baa715e52bf2a943f8e9dc5b4e44 Mon Sep 17 00:00:00 2001 From: Mati OS Date: Fri, 11 Sep 2026 15:37:20 -0300 Subject: [PATCH 2/2] v1.3.2 --- packages/plugin/package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/plugin/package.json b/packages/plugin/package.json index f4d704a..98eb74f 100644 --- a/packages/plugin/package.json +++ b/packages/plugin/package.json @@ -1,6 +1,6 @@ { "name": "@openscan/hardhat-plugin", - "version": "1.3.1", + "version": "1.3.2", "description": "Hardhat 3 plugin to use openscan explorer", "license": "MIT", "type": "module",