Publishing & Release Guide
Step-by-step procedures for building, releasing, and publishing RepoAtlas packages.
3 min read•Updated July 22, 2026
RepoAtlas packages are distributed across npm (core engine packages) and the Visual Studio Code Marketplace (VS Code extension).
npm Package Publishing
Automated (GitHub Actions — Recommended)
Add your NPM_TOKEN to GitHub Repository Secrets. When code merges to main with a Changeset version bump, GitHub Actions automatically publishes all packages.
Published packages:
| Package | Registry |
|---|---|
@repoatlasdev/core | npm |
@repoatlasdev/renderers | npm |
@repoatlasdev/exporters | npm |
@repoatlasdev/icons | npm |
@repoatlasdev/config | npm |
@repoatlasdev/detector | npm |
@repoatlasdev/utils | npm |
@repoatlasdev/cli | npm |
Manual Publishing
bash
pnpm build
pnpm publish -r --access public --no-git-checksVS Code Extension Publishing
The VS Code Extension is published manually via the Marketplace web portal.
Build & Package
bash
pnpm --filter repo-atlas-vscode build
cd apps/vscode
npx -y @vscode/vsce package --no-dependencies --out repo-atlas-<version>.vsixUpload to Marketplace
- Go to the Marketplace Manager
- Click ⋮ next to the extension → Update
- Select your
.vsixfile and upload
Version Bumping with Changesets
bash
1# Create a changeset
2pnpm changeset
3
4# Apply version bumps
5pnpm changeset version
6
7# Commit and push
8git add . && git commit -m "chore: version packages" && git push