Repository navigation
Conversation
Docs, CODEOWNERS, .github/, scripts/ and test/ changes no longer need a version bump or changelog entry. Matches the Glassnode repository rules.
| import { compareSemver, parseSemver } from './release-plan.mjs'; | ||
|
|
||
| // Changes to these paths never reach users of the npm package, so they need no version bump. | ||
| const NO_RELEASE_PATHS = [ |
There was a problem hiding this comment.
it could be "inverted" and changes only in src/ directory should generate Changelog (otherwise we keep growing this list with other stuff + package.json to reflect dependency update
Collaborator
Author
There was a problem hiding this comment.
Agreed, inverted in 2742410: RELEASE_PATHS lists what requires a bump, and anything else needs none. Besides src/ and package.json it includes tsconfig.json (changes the compiled dist/) and LICENSE/NOTICE (shipped in the npm tarball). README.md is in the tarball too but left out, so a docs fix does not force a release.
List the paths that change the npm package (src/, tsconfig.json, package.json, LICENSE, NOTICE) instead of the paths that don't, so new docs or tooling files need no list update.
…ncy type (GN-240) devDependencies never reach users, so a package.json change that only touches them is not a release. Dependabot opens separate runtime and development PRs: development ones pass as opened, runtime ones get a version bump before merging.
This was referenced Oct 13, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI required a version bump on every PR into
main, so a CODEOWNERS-only change (#33) could only pass by publishing an npm release with no code change. The Glassnode repository rules say docs-, CI- and tooling-only changes don't bump the version.What changed
scripts/check-changelog-heading.mjs: the version comparison applies only when a file changed sinceBASE_SHAmatchesRELEASE_PATHS:src/,tsconfig.json,package.json,LICENSE,NOTICE. These are whatnpm packships (asdist/) or what changes it. Inpackage.json, a change todevDependenciesalone doesn't count: those never reach users. Any other change (docs,CODEOWNERS,.github/,scripts/,test/, the lockfile,CHANGELOG.md) needs no bump. The heading check is unchanged..github/dependabot.yml: the weekly group is split intoruntime(dependency-type: production) anddevelopment. A development PR passes CI as opened; a runtime PR changes what users install, so it gets a version bump and CHANGELOG entry pushed onto it before merging (as on Bump the minor-and-patch group across 1 directory with 7 updates #34). This replaces the Dependabot exemption proposed in CI: exempt Dependabot PRs from the version bump; fix source-map-js alert #37.CONTRIBUTING.mdandCLAUDE.md: the bump rule applies to changes to the published package; the exempt paths are listed.src/,package.jsondependencies,tsconfig.jsonorNOTICEstill requires one.Verification
pnpm test: 119 passed (test/release-scripts.spec.ts: 61, including 11 new cases). This PR only touches exempt paths, so its own CI exercises the new rule.Downstream impact
main.README.mdchanges no longer trigger a release; the npm page shows the new README with the next package release.check-changelog-heading.mjsis not one of the scripts shared with glassnode-api, so nothing to sync there.