github-archiver 1.0.8 → 1.0.9

package/CHANGELOG.md

@@ -1,32 +1,41 @@
 ## [1.0.8](https://github.com/mynameistito/github-archiver/compare/v1.0.7...v1.0.8) (2026-01-11)
 
-## [1.0.7](https://github.com/mynameistito/github-archiver/compare/v1.0.6...v1.0.7) (2026-01-11)
+## 1.0.9
+
+### Patch Changes
+
+- [`230c310`](https://github.com/mynameistito/github-archiver/commit/230c3106625c6b4170aff58dc8a79ed78f7a6938) Thanks [@mynameistito](https://github.com/mynameistito)! - Migrate from semantic-release to @changesets/cli for better release control
 
+  - Replace semantic-release with @changesets/cli for explicit version management
+  - Add GitHub-linked changelog generation with PR/commit references
+  - Update to two-step release process (Version Packages PR + manual merge)
+  - Integrate with bun for improved package management
+  - Update Node requirement to 22+ (aligns with actual dependencies)
+  - Update CI/CD workflows to use bun exclusively
+
+## [1.0.7](https://github.com/mynameistito/github-archiver/compare/v1.0.6...v1.0.7) (2026-01-11)
 
 ### Bug Fixes
 
-* update version number in source code to match package.json ([f9ef48c](https://github.com/mynameistito/github-archiver/commit/f9ef48c344cf46e2ebb37141a9db211bddf57d47))
+- update version number in source code to match package.json ([f9ef48c](https://github.com/mynameistito/github-archiver/commit/f9ef48c344cf46e2ebb37141a9db211bddf57d47))
 
 ## [1.0.6](https://github.com/mynameistito/github-archiver/compare/v1.0.5...v1.0.6) (2026-01-11)
 
-
 ### Bug Fixes
 
-* ensure ESM output in bundled dist file ([48a242a](https://github.com/mynameistito/github-archiver/commit/48a242ad0b15c16e78c66aafab69ba84b64590b9))
+- ensure ESM output in bundled dist file ([48a242a](https://github.com/mynameistito/github-archiver/commit/48a242ad0b15c16e78c66aafab69ba84b64590b9))
 
 ## [1.0.5](https://github.com/mynameistito/github-archiver/compare/v1.0.4...v1.0.5) (2026-01-11)
 
-
 ### Bug Fixes
 
-* build output as ESM to match package.json type ([e0aadd7](https://github.com/mynameistito/github-archiver/commit/e0aadd740c559333375e57b0f34e7e2d6a04240c))
+- build output as ESM to match package.json type ([e0aadd7](https://github.com/mynameistito/github-archiver/commit/e0aadd740c559333375e57b0f34e7e2d6a04240c))
 
 ## [1.0.4](https://github.com/mynameistito/github-archiver/compare/v1.0.3...v1.0.4) (2026-01-11)
 
-
 ### Bug Fixes
 
-* add repository URL to package.json for npm provenance ([02ddb1c](https://github.com/mynameistito/github-archiver/commit/02ddb1c9f4b6a7b7ca91497b2633011accf94356))
+- add repository URL to package.json for npm provenance ([02ddb1c](https://github.com/mynameistito/github-archiver/commit/02ddb1c9f4b6a7b7ca91497b2633011accf94356))
 
 ## [1.0.3](https://github.com/mynameistito/github-archiver/compare/v1.0.2...v1.0.3) (2026-01-11)
 
@@ -34,17 +43,15 @@
 
 ## [1.0.1](https://github.com/mynameistito/github-archiver/compare/v1.0.0...v1.0.1) (2026-01-11)
 
-
 ### Bug Fixes
 
-* correct relative import path in CLI wrapper ([cc64796](https://github.com/mynameistito/github-archiver/commit/cc64796d2d0a06175faf053d63e9c1e8ffe0d371))
+- correct relative import path in CLI wrapper ([cc64796](https://github.com/mynameistito/github-archiver/commit/cc64796d2d0a06175faf053d63e9c1e8ffe0d371))
 
 # 1.0.0 (2026-01-11)
 
-
 ### Bug Fixes
 
-* separate CLI wrapper to resolve ESM shebang conflict ([fc9918a](https://github.com/mynameistito/github-archiver/commit/fc9918a46953634b1ad15a0f64175937acb4f29b))
+- separate CLI wrapper to resolve ESM shebang conflict ([fc9918a](https://github.com/mynameistito/github-archiver/commit/fc9918a46953634b1ad15a0f64175937acb4f29b))
 
 # Changelog
 
@@ -56,6 +63,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [1.0.0] - 2025-01-11
 
 ### Added
+
 - Initial release of GitHub Archiver CLI
 - Mass archive GitHub repositories with parallel processing
 - Three input methods: editor, file, and stdin
@@ -77,6 +85,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Biome formatting and linting enforcement
 
 ### Commands
+
 - `auth login` - Authenticate with GitHub
 - `auth logout` - Remove stored token
 - `auth status` - Check authentication status
@@ -84,6 +93,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `archive` - Archive repositories with multiple options
 
 ### Features
+
 - Parallel processing with p-queue
 - Retry logic with exponential backoff (1s → 2s → 4s)
 - Repository validation (exists, permissions, already archived)
@@ -93,6 +103,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Support for configuration files and comments in input
 
 ### Documentation
+
 - Comprehensive README with quick start guide
 - Installation instructions
 - Command reference with examples
@@ -101,6 +112,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Architecture overview
 
 ### Testing
+
 - 34 unit tests covering:
   - URL parsing (20+ tests)
   - Output formatting (15+ tests)
@@ -108,6 +120,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Vitest configuration for fast testing
 
 ### Code Quality
+
 - TypeScript strict mode enabled
 - 0 compilation errors
 - 0 implicit any types
@@ -119,6 +132,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## Unreleased
 
 ### Planned Features
+
 - [ ] Batch progress reporting with live updates
 - [ ] Support for organization-wide archiving
 - [ ] Integration tests for archive command
@@ -130,6 +144,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - [ ] Undo/rollback capability (unarchive)
 
 ### Under Consideration
+
 - Docker image distribution
 - NPX support for one-time use
 - Scheduled archiving via cron

package/docs/RELEASE.md

@@ -1,123 +1,177 @@
 # Release Process
 
-This document details the automated release process for GitHub Archiver CLI using semantic-release.
+This project uses **Changesets** for version management and publishing.
 
-## How Releases Work
+## Overview
 
-### 1. Commit Format
+The release process is **two-step and automated**:
 
-Use [Conventional Commits](https://www.conventionalcommits.org/):
+1. **Developer creates changesets** - Explicit intent for what's being released
+2. **GitHub Actions automates the rest** - Creates version PR, then publishes
 
-- `feat:` - New features → **minor** version bump (1.0.0 → 1.1.0)
-- `fix:` - Bug fixes → **patch** version bump (1.0.0 → 1.0.1)
-- `BREAKING CHANGE:` - Breaking changes → **major** version bump (1.0.0 → 2.0.0)
-- `chore:`, `docs:`, `test:` - No version bump
+## For Contributors
 
-### 2. Automatic Trigger
+### Creating a Changeset
 
-Push to `main` branch triggers the release workflow:
+When you've made changes that should be included in a release:
 
-1. Semantic release analyzes commits and determines version bump
-2. Package version is updated, published to npm
-3. GitHub release is created with changelog
-4. Git tag is created automatically
+1. **Create a changeset file:**
+   ```bash
+   bun run changeset:add
+   ```
 
-### 3. Trusted Publishing
+2. **Answer the prompts:**
+   - Which packages are affected? → Select `github-archiver`
+   - What's the type of change? → Choose:
+     - `patch` - bug fixes (1.0.0 → 1.0.1)
+     - `minor` - new features (1.0.0 → 1.1.0)
+     - `major` - breaking changes (1.0.0 → 2.0.0)
+   - Write a description of your change
 
-Uses OpenID Connect (OIDC) for secure, tokenless authentication:
+3. **Commit the generated changeset file:**
+   ```bash
+   git add .changeset/*.md
+   git commit -m "docs: add changeset for feature X"
+   ```
 
-- No npm tokens required - eliminates security risks
-- Short-lived, cryptographically-signed tokens for each publish
-- Works with personal GitHub accounts
+4. **Push your branch and open a PR as usual**
 
-### 4. Node Version Requirements
+### Automated Release
 
-- Package runs on Node 18+ (see `package.json` engines)
-- Release workflow uses Node 22+ (semantic-release requirement)
-- CI tests on Node 18 and 22 for maximum compatibility
+Once your PR is merged to `main`:
 
-### 5. Example Workflow
+1. GitHub Actions detects the changeset files
+2. Creates a "Version Packages" PR with:
+   - Updated `package.json` version
+   - Updated `CHANGELOG.md` with your descriptions
+   - GitHub links to commits and PRs
+3. Merge the "Version Packages" PR
+4. GitHub Actions automatically:
+   - Publishes to npm
+   - Creates a GitHub release
+   - Tags the commit with the version
 
-```bash
-git checkout main
-git pull
-# Make your commits with conventional format
-git commit -m "feat: add support for custom config file"
-git push
-# Release happens automatically!
+### Changeset File Format
+
+Example: `.changeset/excited-newts-talk.md`
+
+```markdown
+---
+"github-archiver": minor
+---
+
+Add support for custom GitHub token configuration in config file
 ```
 
-## Trusted Publishing Setup
+**Note:** Changeset filenames are auto-generated with whimsical names (e.g., `silly-cats-dance.md`). Edit the description after generation if needed.
 
-This project uses npm's **Trusted Publishing** feature for secure, tokenless package publishing.
+## For Maintainers
 
-### Setup (one-time)
+### Understanding Releases
 
-1. Go to https://www.npmjs.com/package/github-archiver/settings
-2. Under **Trusted Publisher**, click **GitHub Actions**
-3. Fill in:
-   - **Organization or user**: `mynameistito`
-   - **Repository**: `github-archiver`
-   - **Workflow filename**: `release.yml`
-4. Click **Set up connection**
-5. (Recommended) Enable **"Require two-factor authentication and disallow tokens"**
+**What triggers a release?**
+- Any changeset file committed to main
+- Automatic via GitHub Actions (no manual intervention needed)
 
-That's it! No tokens to manage, rotate, or worry about.
+**What happens?**
+1. Action detects changeset files
+2. Runs validation (tests, lint, typecheck, build)
+3. Creates "Version Packages" PR with:
+   - Version bumps in `package.json`
+   - Updated `CHANGELOG.md` with GitHub links
+   - Changeset files consumed
+4. After PR merge: Automatically publishes to npm
 
-## Commit Message Examples
+### Merging the "Version Packages" PR
 
-```bash
-# Feature (minor version bump)
-git commit -m "feat: add support for custom config file"
+When GitHub Actions creates a "Version Packages" PR:
+- Review the version bump (patch/minor/major)
+- Review the changelog entries with GitHub links
+- Merge to trigger automatic publish
+
+### Release Changelog
 
-# Bug fix (patch version bump)
-git commit -m "fix: handle empty repository list gracefully"
+The changelog is auto-generated with GitHub links:
 
-# Breaking change (major version bump)
-git commit -m "feat!: change CLI command structure
+```markdown
+## 1.1.0
 
-BREAKING CHANGE: The 'auth' subcommand is now required"
+### Minor Changes
 
-# No release
-git commit -m "chore: update dependencies"
-git commit -m "docs: clarify installation steps"
-git commit -m "test: add unit tests for parser"
+- [abc123d](https://github.com/mynameistito/github-archiver/commit/abc123d) ([#42](https://github.com/mynameistito/github-archiver/pull/42)): Add custom token config support
 ```
 
-## Manual Releases
+### Manual Publishing (if needed)
 
-If you need to publish without merging to main:
+If automation fails, you can publish manually on the commit with updated versions:
 
 ```bash
-npm run release -- --no-ci
+bun run changeset:publish
 ```
 
-## Release Workflow Details
+### Troubleshooting
+
+**Action not creating PR?**
+- Check that changesets exist in `.changeset/` directory
+- Verify `GITHUB_TOKEN` and `NPM_TOKEN` secrets are configured
+- Review workflow logs in GitHub Actions
+
+**Publish failed?**
+- Verify `NPM_TOKEN` has publish permissions
+- Check npm registry status
+- Review the error in GitHub Actions logs
+
+**Version bump incorrect?**
+- Verify correct changeset type was selected (patch/minor/major)
+- Check that description was provided
+- Ensure changeset file syntax is valid (YAML front matter)
 
-The `.github/workflows/release.yml` file handles:
+## Versioning Strategy
 
-- Running tests on Node 18 and 22
-- Building the project
-- Publishing to npm using Trusted Publishing
-- Creating GitHub releases with changelog
-- Managing version tags automatically
+This project uses **Semantic Versioning**:
 
-## Troubleshooting
+- **patch**: Bug fixes, minor improvements (1.0.0 → 1.0.1)
+- **minor**: New features, backward compatible (1.0.0 → 1.1.0)
+- **major**: Breaking changes, incompatible updates (1.0.0 → 2.0.0)
 
-### Release Not Triggered
+Choose the appropriate type when creating your changeset.
 
-- Ensure commits follow conventional commit format
-- Check that workflow file is named `release.yml`
-- Verify GitHub Actions permissions are enabled
+## GitHub Releases
 
-### Publish Failed
+After publishing, a GitHub Release is automatically created with:
+- Release notes generated from CHANGELOG.md
+- Direct link to the npm package
+- Git tag for the release (v1.1.0, etc.)
 
-- Check npm Trusted Publisher configuration
-- Ensure package name in package.json matches npm registry
-- Verify semantic-release version range is valid
+## Environment & CI/CD
+
+**Required Secrets:**
+- `GITHUB_TOKEN` - Auto-provided by GitHub Actions
+- `NPM_TOKEN` - Set in repository settings with publish permissions
+
+**Node Version:** 22.x (tested on 24.x and 25.x in CI)  
+**Package Manager:** Bun
+
+**Publishing Method:** OIDC trusted publishing with npm
+
+## Trusted Publishing Setup
+
+This project uses npm's **Trusted Publishing** feature for secure, tokenless package publishing.
+
+### Setup (one-time)
+
+1. Go to https://www.npmjs.com/package/github-archiver/settings
+2. Under **Trusted Publisher**, click **GitHub Actions**
+3. Fill in:
+   - **Organization or user**: `mynameistito`
+   - **Repository**: `github-archiver`
+   - **Workflow filename**: `release.yml`
+4. Click **Set up connection**
+5. (Recommended) Enable **"Require two-factor authentication and disallow tokens"**
+
+That's it! No tokens to manage, rotate, or worry about.
 
-### Version Bump Incorrect
+## See Also
 
-- Review commit history for proper prefixes
-- Check that `BREAKING CHANGE:` is in commit body (footer)
-- Ensure no duplicate release tags exist
+- [Contributing Guidelines](../CONTRIBUTING.md#release-process)
+- [Changesets Documentation](https://github.com/changesets/changesets)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "github-archiver",
-  "version": "1.0.8",
+  "version": "1.0.9",
   "description": "Archive GitHub repositories via CLI",
   "type": "module",
   "main": "dist/index.js",
@@ -8,7 +8,8 @@
     "github-archiver": "bin/github-archiver.js"
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=22.0.0",
+    "bun": ">=1.0.0"
   },
   "scripts": {
     "build": "tsx scripts/build.ts",
@@ -20,7 +21,11 @@
     "tsc": "tsc --noEmit",
     "test": "vitest",
     "test:coverage": "vitest --coverage",
-    "release": "semantic-release",
+    "changeset": "changeset",
+    "changeset:add": "changeset add",
+    "changeset:version": "changeset version",
+    "changeset:publish": "changeset publish",
+    "release": "changeset publish",
     "prepublishOnly": "npm run build && npm run typecheck && npm run lint"
   },
   "dependencies": {
@@ -31,11 +36,11 @@
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.11",
-    "@semantic-release/changelog": "^6.0.3",
-    "@semantic-release/git": "^10.0.1",
+    "@changesets/changelog-github": "^0.5.2",
+    "@changesets/cli": "^2.29.8",
+    "@changesets/get-github-info": "^0.7.0",
     "@types/node": "^25.0.6",
     "esbuild": "^0.27.2",
-    "semantic-release": "^25.0.2",
     "tsx": "^4.21.0",
     "typescript": "^5.9.3",
     "ultracite": "^7.0.11",
@@ -52,6 +57,10 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/mynameistito/github-archiver"
+    "url": "git+https://github.com/mynameistito/github-archiver.git"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
   }
 }