Skip to content

chore(deps): bump cycjimmy/semantic-release-action from 4 to 6 #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump cycjimmy/semantic-release-action from 4 to 6 #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/rspec_and_release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ jobs:
zip -r datadog_backup.zip ./*
- name: Semantic Release
id: semantic
uses: cycjimmy/semantic-release-action@v4
uses: cycjimmy/semantic-release-action@v6

@cursor cursor Bot Feb 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pinned semantic_version: 17 incompatible with action v6

High Severity

The action is bumped to v6, which internally expects semantic-release v25 and runs on Node 24, but semantic_version: 17 still pins a very old semantic-release version. Action v6's result-handling code (windUpJob.task.js, updated in v5.0.1/v5.0.2 and again in v6) likely expects v25's output structure. Running semantic-release v17 (CommonJS-based, different result format) under action v6 could cause the release step to fail or produce incorrect outputs. The extra_plugins (@semantic-release/changelog@5, @semantic-release/git@9, semantic-release-rubygem@1) are also pinned to versions designed for v17 and may not be compatible with v25 if the pin is simply removed.

Additional Locations (1)

Fix in Cursor Fix in Web

env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GEM_HOST_API_KEY: ${{ secrets.RUBYGEMS_API_TOKEN }}
Expand Down