From cecf0f1917fa16cb20c378bd1619a90d4db46e12 Mon Sep 17 00:00:00 2001
From: Maor Elfassy <maorel@jfrog.com>
Date: Sun, 22 Mar 2026 12:28:46 +0200
Subject: [PATCH] fix: add contents:write permission to release workflow

The release workflow needs explicit contents:write permission to force-push
the v4 major version tag. Without this permission, the v4 tag is not updated
when new releases are published, causing users calling @v4 to get outdated
versions.

This fixes the issue where v4.10.0 was released but the v4 tag was not updated,
leaving users on @v4 stuck with Node 20 instead of Node 24.

Relates to: JA-20235

Made-with: Cursor
---
 .github/workflows/release.yml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index f90601708..51d318d44 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -3,6 +3,9 @@ on:
   release:
     types: [published]
 
+permissions:
+  contents: write
+
 jobs:
   release:
     runs-on: ubuntu-latest