Skip to content

Add changesets based publishing#145

Merged
JoviDeCroock merged 2 commits into
mainfrom
changesets-based-publishing
May 15, 2026
Merged

Add changesets based publishing#145
JoviDeCroock merged 2 commits into
mainfrom
changesets-based-publishing

Conversation

@JoviDeCroock
Copy link
Copy Markdown
Member

Summary

  • add Changesets-based release PR creation and npm publishing
  • split publishing into a separate OIDC-enabled job
  • use .github/scripts/has-unpublished-packages.mjs to skip publishing when the current package version is already on npm

Testing

  • GITHUB_OUTPUT=/tmp/publish-check-output node .github/scripts/has-unpublished-packages.mjs

@@ -0,0 +1,88 @@
import { appendFileSync } from "node:fs";
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I have no problem with merging this as-is, and I'm guessing it's copy/pasted across numerous projects, but it's a tad overengineered for single-package repos like this one.

There's only one package.json that's relevant here, don't need to go hunting for it or abstract out a system to find it 🤷

Much easier to read than the bash though, I'm a slave to syntax highlighting

@JoviDeCroock JoviDeCroock force-pushed the changesets-based-publishing branch from 49515a5 to 66741e3 Compare May 13, 2026 18:54
@JoviDeCroock JoviDeCroock merged commit f23c9f1 into main May 15, 2026
1 check passed
@JoviDeCroock JoviDeCroock deleted the changesets-based-publishing branch May 15, 2026 15:46
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.

2 participants