[SutuSebastian]

The composite setup action runs its own setup-node (Node 22, npm 10.x), which put npm 10 back on PATH after our Node 24 step. npm 10 cannot do OIDC, so the first trusted publish went out anonymous and the registry 404d every PUT. Moving our step last guarantees npm 11 at publish time. Retries the unpublished 0.1.1s on merge.

Summary by CodeRabbit

• Chores
  • Updated the release process’s tool setup sequence. This change does not alter app features or behavior visible to users.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 557f294

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 54 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 88036ddc-cc78-4106-943a-eb2c9a15aa19

Commits

Reviewing files that changed from the base of the PR and between d399039 and 557f294.

Files selected for processing: 1

• apps/docs/blume.config.ts

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: acccfa4c-1aba-4cac-8645-63eeff71c7e2

Commits

Reviewing files that changed from the base of the PR and between d2eaa7a and d399039.

Files selected for processing: 1

• .github/workflows/release.yml

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

Walkthrough

The release workflow now sets up Bun before configuring Node 24 and npm for trusted publishing. Updated comments describe the npm version and PATH behavior, and state that switching Node has no ABI consequences in this repository.

Changes: Release workflow

Layer / File(s)	Summary
Bun and publishing setup order .github/workflows/release.yml	The workflow runs Setup Bun and install before Setup Node + npm for trusted publishing. Updated comments explain why Node 24’s npm 11 is configured last and state that switching Node has no ABI consequences in this repository.

Priority: Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix

Merge Risk: Minimal · up to d3990

The publishing workflow order is correct and no unresolved merge risk was identified.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main workflow change: configuring Node 24 after the Bun installation.
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

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