[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cycjimmy/semantic-release-action	action	major	v6 → v8.1.4

Warnings (1)

Please correct - or verify that you can safely ignore - these warnings before you merge this PR.

• cycjimmy/semantic-release-action: Could not determine new digest for update (github-tags package cycjimmy/semantic-release-action)

---

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

cycjimmy/semantic-release-action

v8.1.4

Compare Source

Bug Fixes

• hint on ENOPKG instead of warning about a missing package.json (0773dda), closes #​333

v8.1.3

Compare Source

Bug Fixes

• locate npm-cli.js from PATH on Windows runners (b810ddb), closes #​332

v8.1.2

Compare Source

Bug Fixes

• deps: update @​semantic-release/github to 12.0.10 (2479d22), closes semantic-release/github#1224

v8.1.1

Compare Source

Bug Fixes

• split extends configurations on whitespace (6938171)

v8.1.0

Compare Source

Features

• output last_release_* from Git tags when no release is published (ef475bf)

v8.0.2

Compare Source

Bug Fixes

• resolve extra plugins with working_directory and relative extends (340bd34), closes #​254

v8.0.1

Compare Source

Bug Fixes

• bypass package manager shims for internal npm calls (45d3d9c), closes #​258

v8.0.0

Compare Source

Features

• require semantic-release v20 or above (1d650fa)

BREAKING CHANGES

• semantic-release v16~v19 are no longer supported. The minimum
  supported version is now v20. If semantic_version is pinned below 20, the action
  fails with an error; update it to v20 or above, or remove it to use the latest
  version.

v7.1.2

Compare Source

Bug Fixes

• install: improve npm install logging for error visibility (3f9efbb)

v7.1.1

Compare Source

Bug Fixes

• ci: improve error handling for push permission failures (895d556), closes #​312

v7.1.0

Compare Source

Features

• core: add option to skip npm plugin for non-Node.js projects (d1038bc), closes #​313

v7.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 25be22be-a504-48d3-92aa-5fcbb2ee955c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: ffb2b0c
• Latest commit, not reviewed: c588ec8

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review.

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 7f90dc7a-19d8-4c0e-8a82-459ab15ec18f

📥 Commits

Reviewing files that changed from the base of the PR and between 33085a9 and ffb2b0c.

📒 Files selected for processing: 1

• .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the release publishing workflow to use a newer version of its release automation tooling. This is an internal release-management change and does not alter app features or behavior for end users.

The release workflow updates cycjimmy/semantic-release-action from v6 to v8.1.2.

Changes: Release workflow

Layer / File(s)	Summary
Update semantic-release action .github/workflows/release.yml	The release workflow now uses cycjimmy/semantic-release-action v8.1.2 instead of v6.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: Minimal · previous review ffb2b

The release action upgrade preserves the workflow’s configured release setup and downstream outputs; no change-specific issue blocks merging.

Architecture risk: Low · up to ffb2b

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/release.yml: The semantic-release step now uses action v8.1.2 instead of v6.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the dependency action and the major version update from v6 to v8.
Description check		The description directly explains the Renovate update, release notes, compatibility requirement, digest warning, and manual merge configuration.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the release run,
The action’s update is now done.
Version eight point one point two,
Hops into the workflow view.
Fresh steps await the next release.}

_{Comment @coderabbitai help to get the list of available commands.}