refactor: remove platform npm packages, download from GitHub Releases#173
Merged
Merged
Conversation
…eleases Replace the 3 platform-specific npm packages (archgate-darwin-arm64, archgate-linux-x64, archgate-win32-x64) with on-demand binary download from GitHub Releases. The npm shim now downloads the binary on first run and caches it to ~/.archgate/bin/. This simplifies the release pipeline (no more platform npm publishes), removes optionalDependencies from package.json, and eliminates 3 packages to maintain. Changes: - bin/archgate.cjs: download from GitHub Releases instead of npm registry - scripts/postinstall.cjs: check ~/.archgate/bin/ instead of node_modules - package.json: remove optionalDependencies - .simple-release.js: remove optionalDependencies version sync - release-binaries.yml: remove npm publish steps, keep GH Release upload - ARCH-013: remove optional-deps-version-sync rule - Delete packages/ directory - Update docs and CLAUDE.md
Deploying archgate-cli with
|
| Latest commit: |
231c212
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8b2f6192.archgate-cli.pages.dev |
| Branch Preview URL: | https://refactor-remove-platform-npm.archgate-cli.pages.dev |
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
1 participant
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.
Summary
archgate-darwin-arm64,archgate-linux-x64,archgate-win32-x64) and theiroptionalDependenciesentry~/.archgate/bin/optionalDependenciesversion sync in.simple-release.js, no moreoptional-deps-version-syncADR ruleWhat changed
bin/archgate.cjsgithub.com/archgate/cli/releasesinstead ofregistry.npmjs.org; cache to~/.archgate/bin/scripts/postinstall.cjs~/.archgate/bin/instead ofnode_modules/archgate-*/package.jsonoptionalDependenciesblock.simple-release.jsrelease-binaries.ymlid-token: writepermissionARCH-013optional-deps-version-syncrule (21 checks remain)packages/Why
npm install is not the preferred installation path. The platform packages added complexity (3 extra npm publishes per release, version sync logic, OIDC setup) for a path we don't want to optimize for. The standalone installers (
install.sh,install.ps1) andarchgate upgradealready download from GitHub Releases.Test plan
bun run validatepasses (lint, typecheck, format, 599 tests, 21/21 ADR checks, build)npm install archgateon a clean machine triggers postinstall downloadarchgateinvocation with empty~/.archgate/bin/downloads binaryrelease-binaries.ymlstill uploads assets to GitHub Releases correctly