Skip to content

Replace canary releases with pkg.pr.new previews#4259

Open
trevor-scheer wants to merge 4 commits into
graphql:mainfrom
trevor-scheer:trevor/replace-canary-with-pkg-pr-new
Open

Replace canary releases with pkg.pr.new previews#4259
trevor-scheer wants to merge 4 commits into
graphql:mainfrom
trevor-scheer:trevor/replace-canary-with-pkg-pr-new

Conversation

@trevor-scheer
Copy link
Copy Markdown
Contributor

Summary

Replace the changeset-gated npm canary release with pkg.pr.new per-commit previews.

Why

  • Canary required a linked changeset for a publishable (non-private) package, so PRs whose only changesets target the VSCode extensions got a misleading "no linked changesets" comment.
  • Canary uses kamilkisiela/release-canary@master (no tags, no releases) and needs NPM_TOKEN. pkg.pr.new requires neither and posts its own PR comment with install instructions.

Changes

  • Swap the canary job in pr.yml for a pkg-pr-new job that runs npx pkg-pr-new publish './packages/*' after the existing gating checks.
  • Delete scripts/canary-release.mts and the release:canary root script.
  • Drop the root deps that only canary-release.mts imported.

Test plan

The new job runs on this PR.

Drops the `kamilkisiela/release-canary` job and the `release:canary` script in favor of `pkg.pr.new` per-commit previews. Removes `@changesets/{apply-release-plan,assemble-release-plan,config,read}`, `@manypkg/get-packages`, and `@types/semver` since the canary script was their only consumer.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 14, 2026

⚠️ No Changeset found

Latest commit: 2f8aa76

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

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 14, 2026

Open in StackBlitz

cm6-graphql

npm i https://pkg.pr.new/graphql/graphiql/cm6-graphql@4259

codemirror-graphql

npm i https://pkg.pr.new/graphql/graphiql/codemirror-graphql@4259

graphiql

npm i https://pkg.pr.new/graphql/graphiql@4259

@graphiql/plugin-code-exporter

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/plugin-code-exporter@4259

@graphiql/plugin-doc-explorer

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/plugin-doc-explorer@4259

@graphiql/plugin-explorer

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/plugin-explorer@4259

@graphiql/plugin-history

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/plugin-history@4259

@graphiql/react

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/react@4259

@graphiql/toolkit

npm i https://pkg.pr.new/graphql/graphiql/@graphiql/toolkit@4259

graphql-language-service

npm i https://pkg.pr.new/graphql/graphiql/graphql-language-service@4259

graphql-language-service-cli

npm i https://pkg.pr.new/graphql/graphiql/graphql-language-service-cli@4259

graphql-language-service-server

npm i https://pkg.pr.new/graphql/graphiql/graphql-language-service-server@4259

monaco-graphql

npm i https://pkg.pr.new/graphql/graphiql/monaco-graphql@4259

commit: 2f8aa76

@trevor-scheer trevor-scheer requested a review from dimaMachina May 14, 2026 06:26
"name": "cm6-graphql",
"version": "0.2.1",
"description": "GraphQL language support for CodeMirror 6",
"repository": {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The pkg.pr.new logs called this out as missing, so adding in this PR.

@trevor-scheer trevor-scheer marked this pull request as ready for review May 14, 2026 13:34
…-with-pkg-pr-new

# Conflicts:
#	.github/workflows/pr.yml
#	package.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant