ci: auto-create changeset for dependabot PRs

[Copilot]

• Create .github/workflows/dependabot-changeset.yml workflow that:
  • Triggers on opened and reopened pull_request events from dependabot[bot]
  • Checks whether .changeset/dependabot-pr-<number>.md already exists (the specific file it creates)
  • If it doesn't exist, creates it with "nostream": patch bump and PR title as description
  • Commits and pushes the changeset to the PR branch

[changeset-bot]

⚠️ No Changeset found

Latest commit: 83ee5c9

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

[coveralls]

Coverage is 63.498% — copilot/add-dependabot-changeset-workflow into dependabot/npm_and_yarn/uuid-14.0.0. No base build found for dependabot/npm_and_yarn/uuid-14.0.0.

[Copilot]

Pull request overview

Adds a GitHub Actions workflow intended to automatically create a Changesets entry on Dependabot PRs so they pass the repo’s “Changeset Required” CI check.

Changes:

• Introduces .github/workflows/dependabot-changeset.yml to generate a patch changeset for nostream using the PR title.
• Commits and pushes the generated .changeset/dependabot-pr-<number>.md back onto the Dependabot PR branch.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The "Check for existing changeset" step is checking whether any .changeset/*.md file exists in the repo, which will be true on branches created from main (this repo already contains many changesets). As a result, exists will almost always be true and the workflow will never create a changeset for Dependabot PRs.

Instead, detect whether the PR introduces a changeset relative to the base branch (e.g. reuse the same logic as CI: pnpm exec changeset status --since origin/${{ github.base_ref }}), or at least check for the presence of the specific file you intend to create (.changeset/dependabot-pr-<number>.md).

[cameri]

@copilot The "Check for existing changeset" step is checking whether any .changeset/*.md file exists in the repo, which will be true on branches created from main (this repo already contains many changesets). As a result, exists will almost always be true and the workflow will never create a changeset for Dependabot PRs.

Instead, detect whether the PR introduces a changeset relative to the base branch (e.g. reuse the same logic as CI: pnpm exec changeset status --since origin/${{ github.base_ref }}), or at least check for the presence of the specific file you intend to create (.changeset/dependabot-pr-.md).

[Copilot]

@copilot The "Check for existing changeset" step is checking whether any .changeset/*.md file exists in the repo, which will be true on branches created from main (this repo already contains many chan...

Fixed in 83ee5c9 — the check now tests specifically for .changeset/dependabot-pr-<number>.md (the exact file the workflow creates) rather than scanning for any changeset file.