create-release

Task

You will analyze the codebase and plan how to release or publish a new version of this package or module, and then execute that plan. To do so, you will follow all of the steps bellow.

Steps

Analyze Codebase

1. Run git commands to understand which branch is checked out, whether the main branch is named main or master, if the working directory is clean or has uncommitted changes, how far ahead or behind we are from main, and what the local git config/custom git options are:

   # EXACT COMMAND: Run this exact command to check branch, status and recent commits
   run_terminal_cmd(
     command: "git branch --show-current && git status && git log --oneline -n 5 | cat",
     is_background: false,
     explanation: "Checking current branch, status, and recent commits"
   )
   

   # EXACT COMMAND: Run this exact command to check git configuration
   run_terminal_cmd(
     command: "git config --list | grep -E '^(user|core|remote|branch)' | cat",
     is_background: false,
     explanation: "Checking git configuration"
   )
   

2. If GitHub info is accessible (via CLI or other tools), check whether there is an open pull request for this branch and how local commits diverge from the remote repository:

   # EXACT COMMAND: Run this exact command to check commits relative to upstream
   run_terminal_cmd(
     command: "git fetch && git rev-list --count --left-right @{upstream}...HEAD | cat",
     is_background: false,
     explanation: "Checking commits ahead/behind remote"
   )
   

3. Look in .github/workflows to see which release steps occur locally vs remotely (e.g., GitHub Actions):

   # EXACT COMMAND: Run this exact command to list workflow files
   list_dir(
     relative_workspace_path: ".github/workflows",
     explanation: "Checking for CI/CD workflow configurations"
   )
   

4. Grep for package files to identify package name, version, publish registries, and any release tools:

   # EXACT COMMAND: Run this exact command to find version information in JSON files
   grep_search(
     query: "version",
     include_pattern: "*.json",
     explanation: "Finding version information in package files"
   )
   

   # EXACT COMMAND: Run this exact command to extract package metadata
   run_terminal_cmd(
     command: "find . -name 'package.json' -o -name 'deno.json' -o -name 'jsr.json' | xargs cat | grep -E '\"(name|version|publish|registry)\"' | cat",
     is_background: false,
     explanation: "Extracting package information"
   )