chore(publish): simplify the experimental build comment - #205
Merged
Conversation
Drop the install command block - the version is right there and the command was only ever `npm install <name>@<version>`. List every package that was actually published instead. It named only the plugin, while the run publishes the two providers at the same version too, so anyone testing a provider change had no way to know what to install. The names are read back out of the tarballs rather than hardcoded, so the comment cannot drift when a package is added or renamed. Also link the run that produced the build. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #204, from reviewing the comment it posted on #201.
Drops the install command block. It was only ever
npm install <name>@<version>, and the version is in the table directly above.Lists every package that was published. The comment named only the plugin,
but the run publishes both providers at the same version — so anyone testing a
provider change had nothing telling them what to install. The names are read
back out of the tarballs in the publish step rather than hardcoded, so the
comment cannot drift if a package is added or renamed.
Links the run.
Result:
Touches
publish.yml, so it needs a maintainer to merge.🤖 Generated with Claude Code