ci: configure pre-release workflow via pkg.pr.new

[serhalp]

Summary

In preparation for enabling/requiring Trusted Publishing and revoking folks' ability to publish manually, this configures pkg.pr.new to craete pre-releases automatically on all PRs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f042867c-4662-4baa-85db-59f438300a07

📥 Commits

Reviewing files that changed from the base of the PR and between 1df94d5 and 83b39e6.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• netlify/blueprints (manual)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

---

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Pull requests and pushes to main now automatically publish installable prerelease packages.
  • Workflow runs provide the generated package version and installation details for testing.
  • Prereleases are available through a streamlined automated publishing process without manual release preparation.

• Documentation

  • Updated prerelease instructions to explain automated publishing and how to access generated packages from workflow runs.
  • Removed outdated instructions for manually creating and publishing prerelease branches.

Walkthrough

The prerelease workflow now runs for pushes to main and selected pull request events. It uses read-only contents access, pinned actions, ubuntu-slim, and non-persistent checkout credentials. The workflow removes release tagging, versioning, Git push, and authenticated npm publishing. It adds pkg-pr-new and uses pkg-pr-new publish. Contribution instructions now describe the automated prerelease process.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes configuring the pre-release workflow with pkg.pr.new.
Description check	✅ Passed	The description explains that pkg.pr.new will create prereleases automatically for pull requests, which matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch serhalp/ci/pkg-pr-new

---

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/netlify-cli@8392

commit: 83b39e6

[github-actions]

📊 Benchmark results

Comparing with 40ff986

• Dependency count: 1,165 (no change)
• Package size: 455 MB (no change)
• Number of ts-expect-error directives: 346 (no change)

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 208-209: Update the documentation text describing automatically
published installable prereleases to use the linter-approved spelling
“pre-releases,” while leaving the surrounding pkg.pr.new workflow instructions
unchanged.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ee51ab12-528c-47d8-88a9-3329ee2289af

📥 Commits

Reviewing files that changed from the base of the PR and between 05db4ef and dc5cc2d.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• .github/workflows/pre-release.yml
• CONTRIBUTING.md
• package.json

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• netlify/blueprints (manual)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dc5cc2d3e0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 83b39e66bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Install yq before using the slim runner

On GitHub's ubuntu-slim image, yq is not included in the runner's minimal installed toolset, but the workflow invokes it in “Read primary Node version” before installing anything. Consequently, every pull-request and main run exits with yq: command not found before Node setup and never publishes a prerelease; either retain ubuntu-latest or explicitly install/replace yq.

Useful? React with 👍 / 👎.

[serhalp]

welp, it clearly does not in fact fail in that way, so...