Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions packages/rangelink-vscode-extension/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,14 @@ All notable changes to the RangeLink VS Code extension will be documented in thi
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added

### Changed

### Fixed

## [2.0.0]

### Added
Expand Down
4 changes: 4 additions & 0 deletions packages/rangelink-vscode-extension/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@
> **"Claude Code today. Cursor AI tomorrow. Different shortcuts, different muscle memory."**<br />
> **RangeLink ends it.** One keybinding. Any AI, any tool. Character-level precision. `recipes/baking/chickenpie.ts#L3C14-L314C16`

> [!IMPORTANT]
> This documentation is for the `main` branch and may include unreleased features marked with <sup>Unreleased</sup>.
> Install the latest published version from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=couimet.rangelink-vscode-extension) or [Open VSX Registry](https://open-vsx.org/extension/couimet/rangelink-vscode-extension) (Cursor) for currently available features.

## Why RangeLink?

Every AI coding assistant has its own way to share code — different shortcuts, different formats, different muscle memory. If you use multiple AI tools, you're constantly context-switching.
Expand Down
14 changes: 14 additions & 0 deletions packages/rangelink-vscode-extension/scripts/start-release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ set -euo pipefail
# package.json. Idempotent — safe to re-run.
#
# Steps:
# 0. If on main, create a post-release-v<VERSION> branch (otherwise apply in-place)
# 1. Prepend [Unreleased] header with empty sections to CHANGELOG
# 2. Re-add [!IMPORTANT] banner to README
#
Expand Down Expand Up @@ -38,6 +39,19 @@ if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
exit 1
fi

# --- Branch management ---

CURRENT_BRANCH=$(git -C "$PACKAGE_DIR" rev-parse --abbrev-ref HEAD)
MAIN_BRANCH=$(git -C "$PACKAGE_DIR" symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo 'main')

if [[ "$CURRENT_BRANCH" == "$MAIN_BRANCH" ]]; then
NEW_BRANCH="post-release-v${VERSION}"
echo -e "On ${MAIN_BRANCH} — creating branch ${GREEN}${NEW_BRANCH}${NC}"
git -C "$PACKAGE_DIR" checkout -b "$NEW_BRANCH"
else
echo -e "${YELLOW}On branch ${CURRENT_BRANCH} — applying changes in-place.${NC}"
fi

# --- Prerequisites ---

QA_YAML="$QA_DIR/qa-test-cases.yaml"
Expand Down