github-archiver 1.0.7 → 1.0.9

package/CHANGELOG.md

@@ -1,30 +1,41 @@
-## [1.0.7](https://github.com/mynameistito/github-archiver/compare/v1.0.6...v1.0.7) (2026-01-11)
+## [1.0.8](https://github.com/mynameistito/github-archiver/compare/v1.0.7...v1.0.8) (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)
 
@@ -32,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
 
@@ -54,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
@@ -75,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
@@ -82,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)
@@ -91,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
@@ -99,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)
@@ -106,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
@@ -117,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
@@ -128,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/README.md

@@ -4,23 +4,21 @@
 [![npm](https://img.shields.io/npm/v/github-archiver)](https://www.npmjs.com/package/github-archiver)
 [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
 
-A powerful command-line tool for mass archiving GitHub repositories with parallel processing, comprehensive error handling, and user-friendly feedback.
+A powerful CLI for mass archiving GitHub repositories with parallel processing and comprehensive error handling.
 
 ## Features
 
-✨ **Mass Archive Repositories** - Archive multiple GitHub repositories in parallel
-🔐 **Secure Authentication** - Token stored locally in `~/.github-archiver/config.json`
-⚡ **Parallel Processing** - Archive multiple repos simultaneously (configurable 1-50 concurrency)
-📋 **Multiple Input Methods** - Load repos from editor, file, or stdin
-🔍 **Validation** - Dry-run mode to validate without archiving
-📊 **Progress Tracking** - Real-time progress bars and ETA
-🛡️ **Error Recovery** - Comprehensive error handling with helpful guidance
-📝 **Detailed Logging** - Structured logging to files and console
+- ✨ **Mass Archive** - Archive multiple repositories in parallel
+- 🔐 **Secure Auth** - Token stored locally at `~/.github-archiver/config.json`
+- ⚡ **Parallel Processing** - Configurable concurrency (1-50)
+- 📋 **Flexible Input** - Load repos from editor, file, or stdin
+- 🔍 **Validation** - Dry-run mode to validate without archiving
+- 📊 **Progress Tracking** - Real-time progress bars and ETA
+- 🛡️ **Error Recovery** - Comprehensive error handling with helpful guidance
+- 📝 **Detailed Logging** - Structured logging to files and console
 
 ## Installation
 
-### npm
-
 ```bash
 npm install -g github-archiver
 ```
@@ -30,8 +28,7 @@ npm install -g github-archiver
 ```bash
 git clone https://github.com/mynameistito/github-archiver.git
 cd github-archiver
-npm install
-npm run build
+npm install && npm run build
 npm install -g .
 ```
 
@@ -44,18 +41,12 @@ npm run dev -- <command>
 
 ## Quick Start
 
-### 1. Authenticate with GitHub
-
 ```bash
+# Authenticate
 github-archiver auth login
-# Paste your GitHub Personal Access Token when prompted
-```
 
-### 2. Archive Repositories
-
-```bash
+# Archive (opens editor to input repos)
 github-archiver archive
-# Opens your default text editor to enter repository URLs
 ```
 
 ## Commands
@@ -64,101 +55,61 @@ github-archiver archive
 
 Manage GitHub authentication.
 
-#### `auth login`
-Authenticate with GitHub using a Personal Access Token.
-
-```bash
-github-archiver auth login
-```
-
-#### `auth logout`
-Remove stored GitHub token.
-
-```bash
-github-archiver auth logout
-```
-
-#### `auth status`
-Check current authentication status.
-
-```bash
-github-archiver auth status
-```
+| Command | Description |
+|---------|-------------|
+| `auth login` | Authenticate with Personal Access Token |
+| `auth logout` | Remove stored token |
+| `auth status` | Check authentication status |
 
 ### `archive`
 
-Archive multiple GitHub repositories.
+Archive multiple repositories.
 
 ```bash
 github-archiver archive [options]
 ```
 
-#### Options
-
 | Option | Default | Description |
 |--------|---------|-------------|
 | `--file <path>` | - | Read repository URLs from file |
-| `--stdin` | - | Read repository URLs from stdin |
+| `--stdin` | - | Read from stdin |
 | `--dry-run` | false | Validate without archiving |
-| `--concurrency <n>` | 3 | Number of parallel operations (1-50) |
+| `--concurrency <n>` | 3 | Parallel operations (1-50) |
 | `--timeout <n>` | 300 | API timeout in seconds (10-3600) |
 | `--verbose` | false | Enable verbose logging |
 | `--force` | false | Skip confirmation prompts |
 
-#### Examples
+**Examples:**
 
-**Interactive (opens editor):**
 ```bash
+# Interactive (opens editor)
 github-archiver archive
-```
 
-**From file:**
-```bash
+# From file
 github-archiver archive --file repos.txt
-```
 
-**From stdin:**
-```bash
+# From stdin
 cat repos.txt | github-archiver archive --stdin
-```
 
-**Dry-run (validate only):**
-```bash
+# Dry-run
 github-archiver archive --file repos.txt --dry-run
-```
 
-**Fast processing (higher concurrency):**
-```bash
+# High concurrency
 github-archiver archive --file repos.txt --concurrency 10
-```
 
-**Force without confirmation:**
-```bash
+# Force without confirmation
 github-archiver archive --file repos.txt --force
 ```
 
 ## Input Format
 
-Repository URLs can be specified in three formats:
+Supported formats:
 
-### HTTPS Format
-```
-https://github.com/owner/repo
-https://github.com/owner/repo.git
-```
-
-### SSH Format
-```
-git@github.com:owner/repo.git
-git@github.com:owner/repo
-```
-
-### Shorthand Format
-```
-owner/repo
-```
+- HTTPS: `https://github.com/owner/repo` or `https://github.com/owner/repo.git`
+- SSH: `git@github.com:owner/repo.git` or `git@github.com:owner/repo`
+- Shorthand: `owner/repo`
 
-### File Example
+**File Example:**
 
 ```
 # Repositories to archive
@@ -166,22 +117,16 @@ https://github.com/facebook/react
 torvalds/linux
 owner/private-repo
 
-# Comments are ignored
+# Comments ignored
 https://github.com/nodejs/node
 ```
 
 ## GitHub Token Requirements
 
-You need a GitHub Personal Access Token with the following:
-
 - **Scope**: `repo` (Full control of private repositories)
-- **Minimum Permissions**: Push access to repositories you want to archive
-
-### How to Generate a Token
+- **Minimum Permissions**: Push access to target repositories
 
-1. Go to https://github.com/settings/tokens/new
-2. Create a new token with `repo` scope
-3. Copy the token and run `github-archiver auth login`
+**Generate token:** https://github.com/settings/tokens/new → Create with `repo` scope → Run `github-archiver auth login`
 
 ## Output Example
 
@@ -219,225 +164,108 @@ Starting to archive repositories... (concurrency: 3)
 
 ## Troubleshooting
 
-### Authentication Issues
+### Authentication
 
-**Error: No GitHub token found**
-- Run: `github-archiver auth login`
-- Ensure you have a valid Personal Access Token with `repo` scope
+**No token found**: Run `github-archiver auth login`
 
-**Error: Invalid or expired token**
-- Generate a new token at https://github.com/settings/tokens
-- Run: `github-archiver auth logout` then `github-archiver auth login`
+**Invalid/expired token**: Generate new token at https://github.com/settings/tokens → `auth logout` → `auth login`
 
-### Permission Issues
+### Permissions
 
-**Error: Permission denied for owner/repo**
-- Verify you are the repository owner or have push access
-- Check that your token has the `repo` scope
-- The repository must not be archived yet
+**Permission denied**: Verify repo ownership/push access, check `repo` scope, ensure repo isn't already archived
 
 ### Rate Limiting
 
-**Error: GitHub API rate limit exceeded**
-- Wait a few minutes (rate limit resets hourly)
-- Use lower concurrency: `--concurrency 1`
-- Increase timeout: `--timeout 600`
+**Rate limit exceeded**: Wait (resets hourly), lower `--concurrency 1`, increase `--timeout 600`
 
-### Network Issues
+### Network
 
-**Error: Network error or timeout**
-- Check your internet connection
-- GitHub API may be temporarily unavailable
-- Try again in a moment
-- Increase timeout: `--timeout 600`
+**Network error/timeout**: Check connection, GitHub API may be unavailable, retry with `--timeout 600`
 
 ### Repository Not Found
 
-**Error: Repository not found**
-- Verify the repository URL is correct
-- The repository may have been deleted
-- Check your GitHub access to the repository
+**Repository not found**: Verify URL, check if deleted, confirm GitHub access
 
 ## Configuration
 
-Configuration is stored at:
-- **Linux/macOS**: `~/.github-archiver/config.json`
-- **Windows**: `%USERPROFILE%\.github-archiver\config.json`
+**Config**: `~/.github-archiver/config.json` (Linux/macOS) or `%USERPROFILE%\.github-archiver\config.json` (Windows)
 
-Logs are stored at:
-- **Linux/macOS**: `~/.github-archiver/logs/`
-- **Windows**: `%USERPROFILE%\.github-archiver\logs\`
+**Logs**: `~/.github-archiver/logs/` (Linux/macOS) or `%USERPROFILE%\.github-archiver\logs\` (Windows)
 
 ## Architecture
 
 ```
 src/
-├── commands/        # CLI commands (auth, archive)
-├── services/        # GitHub API, archiving, auth management
-├── utils/           # Utilities (parsing, formatting, logging)
-├── types/           # TypeScript type definitions
-└── constants/       # Configuration constants and messages
+├── commands/      # CLI commands (auth, archive)
+├── services/      # GitHub API, archiving, auth management
+├── utils/         # Parsing, formatting, logging
+├── types/         # TypeScript definitions
+└── constants/     # Configuration constants
 
 tests/
-└── unit/            # Unit tests for utilities
+└── unit/          # Unit tests
 ```
 
-### Core Services
+**Core Services:**
 
-- **GitHubService**: Handles GitHub API interactions with retry logic
-- **Archiver**: Manages parallel repository archiving with p-queue
-- **AuthManager**: Manages secure token storage
-- **InputHandler**: Handles input from editor, file, or stdin
-- **ProgressDisplay**: Manages progress bar and summary output
+- **GitHubService**: GitHub API interactions with retry logic
+- **Archiver**: Parallel archiving with p-queue
+- **AuthManager**: Secure token storage
+- **InputHandler**: Input from editor, file, or stdin
+- **ProgressDisplay**: Progress bar and summary output
 
 ## Development
 
-### Setup
-
 ```bash
 npm install
-npm run typecheck
-npm run test
-npm run build
+npm run typecheck    # Check TypeScript
+npm run test         # Run unit tests
+npm run build        # Build production bundle
+npm run lint         # Check code style
+npm run format       # Auto-format code
 ```
 
-### Commands
-
-| Command | Description |
-|---------|-------------|
-| `npm run dev -- <cmd>` | Run CLI in development mode |
-| `npm run typecheck` | Check TypeScript compilation |
-| `npm run test` | Run unit tests |
-| `npm run build` | Build production bundle |
-| `npm run lint` | Check code style |
-| `npm run format` | Auto-format code |
-
 ### Code Standards
 
-This project uses **Ultracite**, a zero-config preset that enforces:
-
-- Strict TypeScript with no implicit `any`
-- Accessibility, performance, and security best practices
-- Consistent formatting via Biome
+This project uses **Ultracite** (Biome) for:
+- Strict TypeScript (no implicit `any`)
+- Accessibility, performance, security best practices
+- Consistent formatting
 - Comprehensive error handling
 
-See `AGENTS.md` for detailed standards.
-
-### Testing
-
-```bash
-npm run test              # Run all tests
-npm run test:coverage     # Run with coverage report
-```
+See `AGENTS.md` for details.
 
 ## Release Process
 
-This project uses **semantic-release** for automated versioning and publishing to npm.
-
-### How Releases Work
-
-1. **Commit Format**: Use [Conventional Commits](https://www.conventionalcommits.org/):
-   - `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
-
-2. **Automatic Trigger**:
-   - Push to `main` branch triggers the release workflow
-   - Semantic release analyzes commits and determines version bump
-   - Package version is updated, published to npm
-   - GitHub release is created with changelog
-   - Git tag is created automatically
-
-3. **Trusted Publishing**:
-   - Uses OpenID Connect (OIDC) for secure, tokenless authentication
-   - No npm tokens required - eliminates security risks
-   - Short-lived, cryptographically-signed tokens for each publish
-   - Works with personal GitHub accounts
-
-4. **Node Version Requirements**:
-   - 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
-
-5. **Example Workflow**:
-   ```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!
-   ```
-
-### 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.</think></tool_call>
-
-### Commit Message Examples
+This project uses **semantic-release** for automated versioning and publishing.
 
-```bash
-# Feature (minor version bump)
-git commit -m "feat: add support for custom config file"
-
-# Bug fix (patch version bump)
-git commit -m "fix: handle empty repository list gracefully"
+**Commit format** (Conventional Commits):
+- `feat:` → minor bump
+- `fix:` → patch bump
+- `BREAKING CHANGE:` → major bump
+- `chore:`, `docs:`, `test:` → no bump
 
-# Breaking change (major version bump)
-git commit -m "feat!: change CLI command structure
-
-BREAKING CHANGE: The 'auth' subcommand is now required"
-
-# No release
-git commit -m "chore: update dependencies"
-git commit -m "docs: clarify installation steps"
-git commit -m "test: add unit tests for parser"
-```
-
-### Manual Releases
-
-If you need to publish without merging to main:
-```bash
-npm run release -- --no-ci
-```
+Pushing to `main` triggers automatic release. See [docs/RELEASE.md](docs/RELEASE.md) for detailed setup and workflow.
 
 ## Contributing
 
-Contributions are welcome! Please:
-
-1. Follow the code standards (run `npm run format`)
+1. Follow code standards (`npm run format`)
 2. Add tests for new features
 3. Ensure `npm run typecheck` and `npm run test` pass
-4. Create a pull request with a clear description
+4. Create pull request with clear description
 
 ## License
 
-MIT - See LICENSE file for details
+MIT - See LICENSE file for details.
 
 ## Support
 
-Having issues? Check the [Troubleshooting](#troubleshooting) section or open an issue on GitHub.
+Check the [Troubleshooting](#troubleshooting) section or open an issue on GitHub.
 
 ## Acknowledgments
 
-- Built with TypeScript, Commander.js, Octokit, and Winston
-- Uses Biome for code formatting and linting
-- Inspired by the need for efficient GitHub repository management
-
-## Version
+Built with TypeScript, Commander.js, Octokit, Winston, and Biome.
 
-Current version: 1.0.0
+---
 
-For the latest updates and release notes, visit: https://github.com/mynameistito/github-archiver/releases
+Current version: 1.0.0 | [Releases](https://github.com/mynameistito/github-archiver/releases)

package/docs/RELEASE.md

@@ -0,0 +1,177 @@
+# Release Process
+
+This project uses **Changesets** for version management and publishing.
+
+## Overview
+
+The release process is **two-step and automated**:
+
+1. **Developer creates changesets** - Explicit intent for what's being released
+2. **GitHub Actions automates the rest** - Creates version PR, then publishes
+
+## For Contributors
+
+### Creating a Changeset
+
+When you've made changes that should be included in a release:
+
+1. **Create a changeset file:**
+   ```bash
+   bun run changeset:add
+   ```
+
+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
+
+3. **Commit the generated changeset file:**
+   ```bash
+   git add .changeset/*.md
+   git commit -m "docs: add changeset for feature X"
+   ```
+
+4. **Push your branch and open a PR as usual**
+
+### Automated Release
+
+Once your PR is merged to `main`:
+
+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
+
+### Changeset File Format
+
+Example: `.changeset/excited-newts-talk.md`
+
+```markdown
+---
+"github-archiver": minor
+---
+
+Add support for custom GitHub token configuration in config file
+```
+
+**Note:** Changeset filenames are auto-generated with whimsical names (e.g., `silly-cats-dance.md`). Edit the description after generation if needed.
+
+## For Maintainers
+
+### Understanding Releases
+
+**What triggers a release?**
+- Any changeset file committed to main
+- Automatic via GitHub Actions (no manual intervention needed)
+
+**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
+
+### Merging the "Version Packages" PR
+
+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
+
+The changelog is auto-generated with GitHub links:
+
+```markdown
+## 1.1.0
+
+### Minor Changes
+
+- [abc123d](https://github.com/mynameistito/github-archiver/commit/abc123d) ([#42](https://github.com/mynameistito/github-archiver/pull/42)): Add custom token config support
+```
+
+### Manual Publishing (if needed)
+
+If automation fails, you can publish manually on the commit with updated versions:
+
+```bash
+bun run changeset:publish
+```
+
+### 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)
+
+## Versioning Strategy
+
+This project uses **Semantic Versioning**:
+
+- **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)
+
+Choose the appropriate type when creating your changeset.
+
+## GitHub Releases
+
+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.)
+
+## 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.
+
+## See Also
+
+- [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.7",
+  "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/"
   }
 }