From a4763f1be5ca628516786990faab04699b8019e2 Mon Sep 17 00:00:00 2001
From: Andrey Avtomonov <andreybavt@gmail.com>
Date: Wed, 20 May 2026 16:55:25 +0200
Subject: [PATCH] test(release): pin GITHUB_REF_NAME in main-rc releaseTag
 assertion

The bare releaseTag('rc') call defaulted to process.env.GITHUB_REF_NAME,
which on PR CI is the merge ref (e.g. 186/merge) and yields
'branch-186-merge' instead of 'next'. Pass an explicit { GITHUB_REF_NAME:
'main' } so the test exercises the main-rc path regardless of CI env.
---
 scripts/semantic-release-config.test.mjs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/semantic-release-config.test.mjs b/scripts/semantic-release-config.test.mjs
index 59ff57f8..56c9e88f 100644
--- a/scripts/semantic-release-config.test.mjs
+++ b/scripts/semantic-release-config.test.mjs
@@ -25,7 +25,7 @@ function pluginNames(config) {
 describe('semantic-release config', () => {
   it('configures rc releases as a prerelease on main', () => {
     assert.equal(releaseKind({ KTX_RELEASE_KIND: 'rc' }), 'rc');
-    assert.equal(releaseTag('rc'), 'next');
+    assert.equal(releaseTag('rc', { GITHUB_REF_NAME: 'main' }), 'next');
     assert.deepEqual(releaseBranches({ KTX_RELEASE_KIND: 'rc', GITHUB_REF_NAME: 'main' }), [
       { name: 'main', prerelease: 'rc', channel: 'next' },
     ]);