ci(repo): update base branch references for release/core-2 - #7409

Merged
nikosdouvlis merged 1 commit into
mainfrom
nikos/core2-base-branch-fix
Dec 9, 2025
Merged

ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom
nikos/core2-base-branch-fix

Conversation

@nikosdouvlis

@nikosdouvlisnikosdouvlis commented Dec 9, 2025•
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Chores
    • Updated internal build configuration and CI workflow settings.

✏️ Tip: You can customize this high-level summary in your review settings.

@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot

changeset-botBot commented Dec 9, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7d56e0e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel

vercelBot commented Dec 9, 2025•
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am

@coderabbitai

coderabbitaiBot commented Dec 9, 2025•
edited
Loading

Copy link
Copy Markdown
Contributor

Walkthrough

Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.

Changes

Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)

Poem

🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.

📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Changesets for version management and changelogs

Use Changesets for version management and releases

Files:

  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)

13-13: Clarify the intent and scope of the baseBranch configuration change.

The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:

  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)

1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.

The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:

  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted

Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.

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

@nikosdouvlis
nikosdouvlis merged commit 5aefbdf into mainDec 9, 2025
41 of 43 checks passed
@nikosdouvlis
nikosdouvlis deleted the nikos/core2-base-branch-fix branch December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

2 more reviewers
@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

actionscore-3

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
ci(repo): update base branch references for release/core-2 - #7409
Merged
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Dec 9, 2025
Merged
ci(repo): update base branch references for release/core-2#7409
nikosdouvlis merged 1 commit into
mainfrom 
nikos/core2-base-branch-fix
Conversation
@nikosdouvlis
@nikosdouvlisnikosdouvlis
commented
Dec 9, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
  • Set changesets baseBranch to origin/release/core-2
  • Update CI changeset status check to use release/core-2
Description
Checklist
  • pnpm test runs as expected.
  • pnpm build runs as expected.
  •  (If applicable) JSDoc comments have been added or updated for any package exports
  •  (If applicable) Documentation has been updated
Type of change
  •  🐛 Bug fix
  •  🌟 New feature
  •  🔨 Breaking change
  •  📖 Refactoring / dependency upgrade / documentation
  •  other:
Summary by CodeRabbit
  • Chores
    • Updated internal build configuration and CI workflow settings.
✏️ Tip: You can customize this high-level summary in your review settings.
@nikosdouvlis
ci(repo): update base branch references for release/core-2
7d56e0e
- Set changesets baseBranch to origin/release/core-2
- Update CI changeset status check to use release/core-2
@changeset-bot
changeset-botBot
commented
Dec 9, 2025

Copy link


Copy Markdown

⚠️ No Changeset found
Latest commit: 7d56e0e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@vercel
vercelBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentPreviewCommentsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewCommentDec 9, 2025 11:05am
@coderabbitai
coderabbitaiBot
commented
Dec 9, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Walkthrough
Configuration updates redirect CI/CD workflow and Changeset tooling base branch references from origin/main to origin/release/core-2, affecting branch-based version control and release tracking operations.
Changes
Cohort / File(s)Summary
Base branch configuration updates
.changeset/config.json, .github/workflows/ci.yml		Updated base branch reference from origin/main to origin/release/core-2 in Changeset configuration and GitHub Actions CI workflow pre-checks, affecting release branch tracking and version management.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~5 minutes
  • Configuration-only changes with single-line edits per file
  • No logic, control flow, or functionality modifications
  • Straightforward parameter substitution (base branch name swap)
Poem
🐰 A branch once rooted in main's domain,
Now hops to core-2 with newfound reign!
Changesets and workflows align their track,
On release rails, there's no turning back. ✨
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and specifically describes the main change: updating base branch references from origin/main to origin/release/core-2 in configuration files.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Post copyable unit tests in a comment
  •  Commit unit tests in branch nikos/core2-base-branch-fix
📜 Recent review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
  • Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📥 Commits
Reviewing files that changed from the base of the PR and between 11da6f5 and 7d56e0e.
📒 Files selected for processing (2)
  • .changeset/config.json (1 hunks)
  • .github/workflows/ci.yml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/config.json
📄 CodeRabbit inference engine (.cursor/rules/development.mdc)
Use Changesets for version management and changelogs
Use Changesets for version management and releases
Files:
  • .changeset/config.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (26)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 16, RQ)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.changeset/config.json (1)
13-13: Clarify the intent and scope of the baseBranch configuration change.
The global baseBranch change to origin/release/core-2 is a foundational configuration that affects how all changeset operations detect package changes and calculate versions across the repository. Before merging, please provide:
  1. Confirmation that origin/release/core-2 exists and is stable in all CI environments
  2. Explicit statement of whether this change applies to all branches or only release-specific workflows
  3. Rationale for the change and impact on the multi-branch release strategy (particularly on main-targeted PRs)
.github/workflows/ci.yml (1)
1-10: Add PR context explaining why release/core-2 is the new Changesets baseline and confirm branch stability.
The .changeset/config.json change to set baseBranch: "release/core-2" is valid configuration, but your PR description should clarify:
  • Why this branch replaces the previous baseline
  • Whether this is temporary or permanent
  • Confirmation that release/core-2 is stable and will not be deleted
Additionally, verify that no other CI workflows or automation tools depend on origin/main as a comparison baseline before merging.
Comment @coderabbitai help to get the list of available commands and usage tips.
@nikosdouvlis
nikosdouvlis
merged commit 5aefbdf
into
mainDec 9, 2025

41 of 43 checks passed

@nikosdouvlis
nikosdouvlis
deleted the

nikos/core2-base-branch-fix

branch
December 9, 2025 11:07
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


2 more reviewers

@octoperoctoperoctoper approved these changes
@anagstefanagstefanagstef approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

actionscore-3

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@nikosdouvlis@octoper@anagstef@clerk-cookie