Merged
Conversation
Member
Author
|
Marking as a draft until the required token can be provisioned. |
juliaschiller150
force-pushed
the
fix-release-please
branch
from
4666e30 to
ab3f0a8
Compare
juliaschiller150
force-pushed
the
fix-release-please
branch
from
ab3f0a8 to
61c3014
Compare
Member
Author
|
I think we're good; going to try with |
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.
Trying some extra configuration changes to get release-please to cut a release and publish to npm even when only chores are involved. That's because this repo is chore heavy, and we want to be able to regularly release even with no feat or fix commits.