Skip to content

fix(ci): use PAT_TOKEN for tag push in release workflow#193

Merged
jdsika merged 2 commits intomainfrom
fix/release-tag-push-permission
May 4, 2026
Merged

fix(ci): use PAT_TOKEN for tag push in release workflow#193
jdsika merged 2 commits intomainfrom
fix/release-tag-push-permission

Conversation

@jdsika
Copy link
Copy Markdown
Collaborator

@jdsika jdsika commented May 4, 2026

Problem

The release workflow fails with a 403 when triggered via workflow_dispatch. The "Create and push tag" step uses the default GITHUB_TOKEN from actions/checkout, which lacks push permission to create and push tags.

Failed run: https://github.com/lichtblick-suite/asam-osi-converter/actions/runs/25326002385

remote: Permission to lichtblick-suite/asam-osi-converter.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/lichtblick-suite/asam-osi-converter.git/': The requested URL returned error: 403

Fix

Authenticate the git remote with PAT_TOKEN before pushing the tag — the same pattern already used later in the workflow for the changelog commit (line 76).

Changes

  • Added git remote set-url origin with PAT_TOKEN to the "Create and push tag" step

Testing

This is a CI-only change. Verification requires re-running the workflow_dispatch release trigger after merge.

The 'Create and push tag' step used the default GITHUB_TOKEN from
actions/checkout, which lacks push permission. This caused a 403 error
when the workflow_dispatch trigger attempted to create and push a tag.

Use the PAT_TOKEN secret (already used for the changelog commit) to
authenticate the tag push.

Signed-off-by: Carlo van Driesten <carlo.van-driesten@bmw.de>
@jdsika jdsika self-assigned this May 4, 2026
@jdsika jdsika added bug Something isn't working labels May 4, 2026
@jdsika jdsika merged commit a93f974 into main May 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant