Get an issue when a new glitchgrab SDK is released

When a new minor or major version of the glitchgrab SDK is published on npm, Glitchgrab opens a GitHub issue in every connected repo that still uses an older version. Nobody has to watch the changelog.

What you get

• One issue per repo, titled Upgrade the glitchgrab SDK, with the glitchgrab-upgrade label.
• It is assigned to the repo's default assignees, so they also get the usual "issue assigned" WhatsApp. See Assign new issues automatically.
• The issue shows:
  • the new version and its npm link;
  • every package.json in the repo that lists glitchgrab, with the version it has now (monorepos included);
  • the install command for each folder, for the package manager your repo uses (bun, pnpm, yarn or npm).
• Another release while the issue is still open: the new version is added as a comment on the same issue. A second issue is never opened.
• You closed it and a later release comes out: a new issue is opened.

It arrives within about an hour of the release.

What does not open an issue

• Patch releases (for example 1.39.1).
• Repos already on the new version or newer.
• Repos that do not list glitchgrab in dependencies or devDependencies on the default branch.
• Versions written as latest, workspace:*, a file path or a git link.
• Releases older than 48 hours.

Turn it on or off

It is on for every connected repo. To stop it for one repo, open Repos and click SDK UPDATES ON on that repo's card. It changes to SDK UPDATES OFF. Click it again to turn it back on.

Good to know

• Turning it back on applies from the next minor or major release, not the one already sent.
• Removing the glitchgrab-upgrade label from an open issue means the next release opens a new one.
• If several people connected the same repo and any of them turned it off, that repo gets no issue.