chore(@graphiql/plugin-code-exporter): Fix Typo #2864
Conversation
🦋 Changeset detectedLatest commit: fe679ac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| "@graphiql/plugin-code-exporter": patch | ||
| --- | ||
|
|
||
| chore(@graphiql/plugin-code-exporter): Fix Typo |
There was a problem hiding this comment.
As it's just the README, we don't need a changeset for that (we don't need to publish a new version just because of a typo 😅 )
There was a problem hiding this comment.
But otherwise people reading the README on npm won’t get the update
There was a problem hiding this comment.
good point @LekoArts - especially because it's currently a standalone workspace, it won't get another release until there's another changeset to just this plugin. it seems excessive but I understand why from a release tooling automation standpoint
acao
dismissed
thomasheyenbrock’s stale review
I think it's fair to consider a code example typo to be necessary for a patch release for sure. Maybe small spelling issue elsewhere in the docs, but a broken link or broken example should necessitate a patch release for npm and other registries
|
thank you @LekoArts ! |
Small typo fix in the README