Skip to content

docs: document offset-version fix and release publishing#4213

Merged
shumkov merged 1 commit into
v4.1-devfrom
docs/release-skill-publish-step
Jul 23, 2026
Merged

docs: document offset-version fix and release publishing#4213
shumkov merged 1 commit into
v4.1-devfrom
docs/release-skill-publish-step

Conversation

@shumkov

@shumkov shumkov commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

What was done

Extends the project-level release skill (added in #4210) with the two steps learned while cutting 4.1.0-beta.1:

  • Offset-version fixyarn release sets every npm package to the same version, but yarn.config.cjs requires dash-spv (+1), dash (+3), and wallet-lib (+7) to lead the root major. Documents running yarn constraints --fix on the release PR to clear the JS dependency versions check.
  • Publishing the GitHub release — after merge, publishing a GitHub release (with the version tag) fires release.yml (on: release: published) to build/attach dashmate + Docker assets. Includes the gh release create recipe and non-technical release-notes guidance.
  • Notes that E2E/Swift reds are frequently environmental (devnet bring-up, self-hosted-runner Keychain perms) and non-blocking (0 required checks).

Docs-only; no code changes.

🤖 Generated with Claude Code

…ublishing

Add the post-`yarn release` steps learned cutting 4.1.0-beta.1:
- the yarn.config.cjs offset-major fix (dash-spv +1, dash +3, wallet-lib
  +7) that the JS dependency versions check requires;
- publishing the GitHub release after merge, which tags and triggers
  release.yml to build/attach dashmate + Docker assets;
- note that E2E/Swift reds are often environmental and non-blocking (0
  required checks).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@shumkov
shumkov requested a review from QuantumExplorer as a code owner July 23, 2026 12:54
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@shumkov, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ed8ec39-d866-47ae-a536-64d599defce3

📥 Commits

Reviewing files that changed from the base of the PR and between b485096 and e95e42c.

📒 Files selected for processing (1)
  • .claude/skills/release/SKILL.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/release-skill-publish-step

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added this to the v4.1.0 milestone Jul 23, 2026
@thepastaclaw

thepastaclaw commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

🕓 Ready for review — 25 ahead in queue (commit e95e42c)
Queue position: 26/26 · 3 reviews active
ETA: start ~16:27 UTC · complete ~16:47 UTC (median 20m across 30 recent reviews; 3 slots)
Queued 11m ago · Last checked: 2026-07-23 13:30 UTC

@shumkov shumkov changed the title docs(release-skill): document offset-version fix and release publishing docs: document offset-version fix and release publishing Jul 23, 2026
@shumkov
shumkov merged commit 079e6de into v4.1-dev Jul 23, 2026
17 of 20 checks passed
@shumkov
shumkov deleted the docs/release-skill-publish-step branch July 23, 2026 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants