[issues/282] Draft v2.0.0 dev.to release announcement#600
Merged
Conversation
## Summary Adds a publish-ready draft of the v2.0.0 dev.to release post and propagates an "Update" banner across the three prior dev.to articles pointing readers to the new release. The draft is structured around a bind-first thesis: every R-\* keybinding now routes through a bound destination, with clipboard preservation as the headline secondary win. ## Changes - `media/devto-post-vscode-extension-v2.0.0.md` (new): full v2.0.0 release post, ~170 lines. Title is "RangeLink 2.0.0: Bind first. Every R-\* follows". Section order: thesis → clipboard preservation → R-D/R-M unification → BYOA (with config example) → Gemini built-in → right-click menus → upgrade toast. Includes R-keybinding table, Upgrading checklist, Quick Start, and a closing "Why six months?" essay framing the integration-test harness work. - `media/devto-post-vscode-extension-v0.2.1.md`, `v0.3.0.md`, `v1.0.0.md`: added a uniform `> **Update (2026-MM-DD):** RangeLink 2.0.0 has shipped. [Read the v2.0.0 release post.](TBD-DEV-TO-URL)` banner near the top of each. The v1.0.0 banner replaced a pre-existing variant. ## Key Discoveries - **Screenshot placeholders use HTML comments** so a forgotten placeholder doesn't ship as a broken image or visible meta-text. - **Outstanding publish-day items (all known, none branch-blocking):** `cover_image:` blank, 4 screenshot placeholders, `TBD-DEV-TO-URL` × 3 banners, `2026-MM-DD` × 3 banners, CHANGELOG `#200` anchor needs the `[Unreleased]` → `[2.0.0]` rename at release time, `published: false` flipped on publish. ## Test Plan - [x] Prettier check passes after format pass - [x] No code changes (media files only); no test suite to run ## Related - Part of #282
Contributor
|
Warning Review limit reached
Your plan includes 1 review of capacity. Refill in 11 minutes and 51 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughFour Dev.to blog post markdown files are updated to support the RangeLink v2.0.0 release announcement. Legacy posts (v0.2.1, v0.3.0, v1.0.0) gain YAML frontmatter metadata and update callouts linking to v2.0.0. A new v2.0.0 announcement post documents routing changes, new keybindings, clipboard behavior, custom AI assistant integration, and provides an upgrade path from v1.0.0. ChangesDev.to v2.0.0 Release Announcement
🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Owner
Author
|
@coderabbitai review - I was rate-limited in #600 (comment) |
Contributor
|
(∩｀-´)⊃━☆ﾟ.*･｡ﾟ ✅ Actions performedReview triggered.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
media/devto-post-vscode-extension-v2.0.0.md (1)
106-106: ⚡ Quick winUse repo-relative anchor links for internal cross-references.
Line 106 and Line 168 should use relative markdown links (not GitHub blob URLs) to keep links portable and consistent in-repo.
Suggested edit
-_The same table also lives in the [extension README](https://github.com/couimet/rangeLink/blob/main/packages/rangelink-vscode-extension/README.md#command-palette) for quick reference inside your editor._ +_The same table also lives in the [extension README](./packages/rangelink-vscode-extension/README.md#command-palette) for quick reference inside your editor._ ... -- [CHANGELOG](https://github.com/couimet/rangeLink/blob/main/packages/rangelink-vscode-extension/CHANGELOG.md#200) +- [CHANGELOG](./packages/rangelink-vscode-extension/CHANGELOG.md#200)As per coding guidelines, "Use relative links with anchors for cross-references:
[text](./FILE.md#section-anchor)- anchor format is lowercase with hyphens for spaces and special chars removed".Also applies to: 168-168
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@media/devto-post-vscode-extension-v2.0.0.md` at line 106, Replace the absolute GitHub blob links to the extension README with repo-relative markdown links: change the URL in the sentence referencing "extension README" so it uses a relative path to the README file (e.g. ./packages/rangelink-vscode-extension/README.md#command-palette) and ensure the anchor uses the lowercase-hyphen format "command-palette"; do the same for the other occurrence that currently points to a GitHub blob URL so both cross-references are portable and repo-relative.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@media/devto-post-vscode-extension-v0.2.1.md`:
- Line 10: Replace the publish placeholders in the update banner string "Update
(2026-MM-DD): RangeLink 2.0.0 has shipped. [Read the v2.0.0 release
post.](TBD-DEV-TO-URL)" with the actual release date and the final Dev.to post
URL so the callout reads e.g. "Update (YYYY-MM-DD): RangeLink 2.0.0 has shipped.
[Read the v2.0.0 release post.](https://dev.to/your-post-url)"; ensure the date
uses ISO format and the link is a fully qualified URL and not a placeholder.
In `@media/devto-post-vscode-extension-v2.0.0.md`:
- Line 168: The markdown link labeled [CHANGELOG] currently points to a brittle
anchor "`#200`"; update the link so it won't break on publish by removing the
anchor or replacing it with a stable permalink (for example link to the
CHANGELOG root URL or to the specific release permalink such as the repository's
releases/tag/v2.0.0); locate the [CHANGELOG] link (the URL that ends with
"CHANGELOG.md#200") and change it to either "CHANGELOG.md" (no anchor) or the
stable releases/tag/v2.0.0 permalink.
---
Nitpick comments:
In `@media/devto-post-vscode-extension-v2.0.0.md`:
- Line 106: Replace the absolute GitHub blob links to the extension README with
repo-relative markdown links: change the URL in the sentence referencing
"extension README" so it uses a relative path to the README file (e.g.
./packages/rangelink-vscode-extension/README.md#command-palette) and ensure the
anchor uses the lowercase-hyphen format "command-palette"; do the same for the
other occurrence that currently points to a GitHub blob URL so both
cross-references are portable and repo-relative.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 66d3a76e-034f-4a56-9af7-17a67fa6ea4f
📒 Files selected for processing (4)
media/devto-post-vscode-extension-v0.2.1.mdmedia/devto-post-vscode-extension-v0.3.0.mdmedia/devto-post-vscode-extension-v1.0.0.mdmedia/devto-post-vscode-extension-v2.0.0.md
|
|
||
| # I Built a VS Code Extension to Stop the Copy-Paste Madness | ||
|
|
||
| > **Update (2026-MM-DD):** RangeLink 2.0.0 has shipped. [Read the v2.0.0 release post.](TBD-DEV-TO-URL) |
Contributor
There was a problem hiding this comment.
Replace publish placeholders in the update banner before merge.
Line 10 still contains 2026-MM-DD and TBD-DEV-TO-URL, which will ship as a broken/stale callout if not finalized.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@media/devto-post-vscode-extension-v0.2.1.md` at line 10, Replace the publish
placeholders in the update banner string "Update (2026-MM-DD): RangeLink 2.0.0
has shipped. [Read the v2.0.0 release post.](TBD-DEV-TO-URL)" with the actual
release date and the final Dev.to post URL so the callout reads e.g. "Update
(YYYY-MM-DD): RangeLink 2.0.0 has shipped. [Read the v2.0.0 release
post.](https://dev.to/your-post-url)"; ensure the date uses ISO format and the
link is a fully qualified URL and not a placeholder.
| - [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=couimet.rangelink-vscode-extension) | ||
| - [Open VSX Registry](https://open-vsx.org/extension/couimet/rangelink-vscode-extension) | ||
| - [Project Home](https://ouimet.info/projects/rangelink-extension.html) | ||
| - [CHANGELOG](https://github.com/couimet/rangeLink/blob/main/packages/rangelink-vscode-extension/CHANGELOG.md#200) |
Contributor
There was a problem hiding this comment.
Stabilize the CHANGELOG anchor before publish.
Line 168 uses #200, which is brittle and already called out in PR objectives as pending release-anchor cleanup; this can become a broken link on publish.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@media/devto-post-vscode-extension-v2.0.0.md` at line 168, The markdown link
labeled [CHANGELOG] currently points to a brittle anchor "`#200`"; update the link
so it won't break on publish by removing the anchor or replacing it with a
stable permalink (for example link to the CHANGELOG root URL or to the specific
release permalink such as the repository's releases/tag/v2.0.0); locate the
[CHANGELOG] link (the URL that ends with "CHANGELOG.md#200") and change it to
either "CHANGELOG.md" (no anchor) or the stable releases/tag/v2.0.0 permalink.
CodeRabbit nitpick from PR #600 review: switched the README and CHANGELOG links from /blob/ to /tree/ for cleaner permalinks. Also dropped /README.md from the README link since GitHub auto-renders it on directory pages. Ref: #600 (review)
✅ CI / Integration Tests (with extensions) — run summary
|
✅ CI / Test & Validate — run summary
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a publish-ready draft of the v2.0.0 dev.to release post and propagates an "Update" banner across the three prior dev.to articles pointing readers to the new release. The draft is structured around a bind-first thesis: every R-* keybinding now routes through a bound destination, with clipboard preservation as the headline secondary win.
Changes
media/devto-post-vscode-extension-v2.0.0.md(new): full v2.0.0 release post, ~170 lines. Title is "RangeLink 2.0.0: Bind first. Every R-* follows". Section order: thesis → clipboard preservation → R-D/R-M unification → BYOA (with config example) → Gemini built-in → right-click menus → upgrade toast. Includes R-keybinding table, Upgrading checklist, Quick Start, and a closing "Why six months?" essay framing the integration-test harness work.media/devto-post-vscode-extension-v0.2.1.md,v0.3.0.md,v1.0.0.md: added a uniform> **Update (2026-MM-DD):** RangeLink 2.0.0 has shipped. [Read the v2.0.0 release post.](TBD-DEV-TO-URL)banner near the top of each. The v1.0.0 banner replaced a pre-existing variant.Key Discoveries
cover_image:blank, 4 screenshot placeholders,TBD-DEV-TO-URL× 3 banners,2026-MM-DD× 3 banners, CHANGELOG#200anchor needs the[Unreleased]→[2.0.0]rename at release time,published: falseflipped on publish.Test Plan
Related
2.0.0release #282Summary by CodeRabbit