Repository navigation
GN-177: Prepare the move to glassnode/glassnode-terminal - #25
Merged
Merged
Conversation
Same as glassnode-api's move to glassnode/glassnode-api-ts-client: - package.json: repository/bugs/homepage -> glassnode/glassnode-terminal, Glassnode AG under contributors, publishConfig.provenance (no forced tag), version 0.2.1. - LICENSE appendix names Jordi Planadecursach and Glassnode AG (otherwise the official Apache-2.0 text); NOTICE likewise. README: badges, org links, Contributing section, MIT history. - CONTRIBUTING.md, CHANGELOG.md (0.1.0-0.2.1), .nvmrc. - Release flow ported from glassnode-api: publish.yml releases package.json's version on merges to main (verify via ci.yml, read-only release check, approval in the `npm` environment, Trusted Publishing with provenance, tag, GitHub Release from CHANGELOG). Only runs in glassnode/glassnode-terminal. scripts/release-state.sh, release-plan.mjs, check-changelog-heading.mjs and their tests come from glassnode-api unchanged (test made ESM-safe). - ci.yml: workflow_call, release/** PRs, CHANGELOG heading check, actions pinned by SHA. CLAUDE.md: versioning, CI and publishing sections. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PzJHgXssByMwBXH1PGbXCL
planadecu
added a commit
that referenced
this pull request
Oct 5, 2026
* GN-177: Prepare the move to glassnode/glassnode-terminal Same as glassnode-api's move to glassnode/glassnode-api-ts-client: - package.json: repository/bugs/homepage -> glassnode/glassnode-terminal, Glassnode AG under contributors, publishConfig.provenance (no forced tag), version 0.2.1. - LICENSE appendix names Jordi Planadecursach and Glassnode AG (otherwise the official Apache-2.0 text); NOTICE likewise. README: badges, org links, Contributing section, MIT history. - CONTRIBUTING.md, CHANGELOG.md (0.1.0-0.2.1), .nvmrc. - Release flow ported from glassnode-api: publish.yml releases package.json's version on merges to main (verify via ci.yml, read-only release check, approval in the `npm` environment, Trusted Publishing with provenance, tag, GitHub Release from CHANGELOG). Only runs in glassnode/glassnode-terminal. scripts/release-state.sh, release-plan.mjs, check-changelog-heading.mjs and their tests come from glassnode-api unchanged (test made ESM-safe). - ci.yml: workflow_call, release/** PRs, CHANGELOG heading check, actions pinned by SHA. CLAUDE.md: versioning, CI and publishing sections. * GN-177: Enforce PR version bumps and release notes ---------
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.
What changed
This prepares the repository for its move to github.com/glassnode/glassnode-terminal, following the same steps as
glassnode-api's move toglassnode/glassnode-api-ts-client(its commitse740aab,0913123and4c35dad). Tracked in GN-177.Repo identity and licensing
package.json:repository,bugsandhomepagepoint toglassnode/glassnode-terminal, and Glassnode AG is listed undercontributors.package.json:publishConfiggainsprovenance: trueand drops the forcedtag: latest, so the dist-tag guard decides the tag.LICENSE: the official Apache-2.0 text. The appendix copyright line now reads Jordi Planadecursach and Glassnode AG.NOTICEnames both, plus the original author.CONTRIBUTING.md(PR flow, checks, versioning, releases, security, licensing of contributions),CHANGELOG.md(0.1.0 to 0.2.2) and.nvmrc(Node 24).Release flow, ported from glassnode-api
publish.ymlno longer publishes on tag pushes. On a merge tomain, it:ci.yml(verify)package.json's version is already on npm (release)npmenvironment, publishes with Trusted Publishing and provenance, pushesv<version>and creates the GitHub Release from theCHANGELOG.mdsection (publish)It never pushes to
main. A newer version can't move npm'slatestbackwards, and versions that were skipped get flagged.The publish job only runs in
glassnode/glassnode-terminal. That blocks forks, and blocks this repo before the transfer, where no protectednpmenvironment exists.scripts/release-state.sh,release-plan.mjsandcheck-changelog-heading.mjs, and their tests (test/release-scripts.spec.ts) started from glassnode-api. The heading check additionally enforces a version greater than the exact PR base commit and nonempty release notes for PRs intomain; release-branch PRs are exempt. Tests cover unchanged, lower and metadata-only versions, empty notes, and the release-branch exception.ci.ymlis now callable bypublish.yml, also runs on PRs intorelease/**, checks theCHANGELOG.mdheading, and pins every action by SHA (the same SHAs as glassnode-api).CLAUDE.md gains Versioning, CI and Publishing sections.
Migration status
Repository transferred to
glassnode/glassnode-terminal. Main and release-branch rulesets are active, requiringtest (22)andtest (24). Thenpmenvironment requires approval byplanadecu(no admin bypass), and allows themainbranch only. Private vulnerability reporting is enabled; Dependabot alerts and GitGuardian are active. Local origin now points to the org repository.Trusted Publisher is configured for
glassnode/glassnode-terminal,publish.yml, environmentnpm, with publishing permission; the old connection is removed. PR merged as955d98fdc9ab1c454fd931b40354fc9372db9824. Release workflow 37307283892 passed all jobs, published 0.2.2 with signed provenance, and created v0.2.2. npm accepted the package and is processing it before registry availability.Original transfer checklist
This PR bumps to 0.2.2, the first release from the org repo.
Transfer checklist (GN-177)
glassnode, keeping the nameglassnode-terminal. History, issues, PRs (including this one) and stars move, and GitHub redirects the old URLs.test (22)andtest (24).release/**.npmenvironment: Settings → Environments →npm. Add the maintainer as a required reviewer, and set the deployment branches tomainonly.glassnode-terminal→ Settings → Trusted Publisher → GitHub Actions. Set repositoryglassnode/glassnode-terminal, workflowpublish.yml, environmentnpm. Remove the oldplanadecu/glassnode-terminalentry.v0.2.2tag and its GitHub Release.git remote set-url origin https://github.com/glassnode/glassnode-terminal.git.Verification
tscpasses and 94 tests pass, including the 45 release-script tests from glassnode-api.actionlintfinds no problems in both workflows.check-changelog-heading.mjsaccepts## 0.2.2for bothmainandrelease/**.scripts/release-state.shagainst the live npm registry givesaction=publish,dist_tag=latestand currentlatest0.2.0.npm pack --dry-runcontainsLICENSE,NOTICE,README.mdanddist/.LICENSEdiffers from apache.org's text only in the two copyright lines.Impact
For users: no behaviour change. The package name stays
glassnode-terminal, and its metadata links point to the org repo. For contributors: every PR now bumps the version and adds aCHANGELOG.mdentry, and CI enforces the version increase and nonempty release notes for PRs intomain.