[PR #10] [MERGED] chore(release): sync develop with main for v3.0.0 #17

Closed
opened 2026-03-04 01:39:17 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/yigitkonur/cli-continues/pull/10
Author: @yigitkonur
Created: 2/21/2026
Status: Merged
Merged: 2/23/2026
Merged by: @yigitkonur

Base: developHead: pr/sync-main-v3-release


📝 Commits (2)

  • 5f1b220 feat!: land v3 refactor on main + registry-driven cross-tool flag forwarding (#9)
  • d0babe7 chore: release v3.0.0 [skip publish]

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 package.json (+1 -1)

📄 Description

Summary

This PR syncs develop with the latest main release state so develop reflects the finalized v3.0.0 release metadata.

Why

  • develop currently carries the v3 refactor tree but still reports a beta package version.
  • main has already moved to stable 3.0.0.
  • Keeping develop aligned avoids version drift in downstream CI/publish and local install flows.

Included commits from main

  • d0babe7 chore: release v3.0.0 [skip publish]
  • 5f1b220 feat!: land v3 refactor on main + registry-driven cross-tool flag forwarding (#9)

Effective file delta vs develop

  • package.json
    • version: 3.0.0-beta.0 -> 3.0.0

Validation

Ran on this branch:

  • pnpm test (passed)
  • pnpm run build (passed)

Risk

Low:

  • No behavioral/runtime source diff versus current develop tree.
  • Release metadata/version alignment only.

Rollback

If needed, rollback is a single revert of this PR commit range, restoring prior package.json version.


Open with Devin

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/yigitkonur/cli-continues/pull/10 **Author:** [@yigitkonur](https://github.com/yigitkonur) **Created:** 2/21/2026 **Status:** ✅ Merged **Merged:** 2/23/2026 **Merged by:** [@yigitkonur](https://github.com/yigitkonur) **Base:** `develop` ← **Head:** `pr/sync-main-v3-release` --- ### 📝 Commits (2) - [`5f1b220`](https://github.com/yigitkonur/cli-continues/commit/5f1b2206983e27cba4c1414d01f663413e09898d) feat!: land v3 refactor on main + registry-driven cross-tool flag forwarding (#9) - [`d0babe7`](https://github.com/yigitkonur/cli-continues/commit/d0babe7a35fa4aba20fb56a58141bca3c4dcad05) chore: release v3.0.0 [skip publish] ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) </details> ### 📄 Description ## Summary This PR syncs `develop` with the latest `main` release state so `develop` reflects the finalized `v3.0.0` release metadata. ## Why - `develop` currently carries the v3 refactor tree but still reports a beta package version. - `main` has already moved to stable `3.0.0`. - Keeping `develop` aligned avoids version drift in downstream CI/publish and local install flows. ## Included commits from `main` - `d0babe7` chore: release v3.0.0 [skip publish] - `5f1b220` feat!: land v3 refactor on main + registry-driven cross-tool flag forwarding (#9) ## Effective file delta vs `develop` - `package.json` - `version`: `3.0.0-beta.0` -> `3.0.0` ## Validation Ran on this branch: - `pnpm test` (passed) - `pnpm run build` (passed) ## Risk Low: - No behavioral/runtime source diff versus current `develop` tree. - Release metadata/version alignment only. ## Rollback If needed, rollback is a single revert of this PR commit range, restoring prior `package.json` version. <!-- devin-review-badge-begin --> --- <a href="https://app.devin.ai/review/yigitkonur/cli-continues/pull/10" target="_blank"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1"> <img src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1" alt="Open with Devin"> </picture> </a> <!-- devin-review-badge-end --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-04 01:39:17 +03:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cli-continues#17
No description provided.