chore: example CI modification to publish napi flight sql client packages #31
Conversation
This file contains 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
dav1do
force-pushed
the
chore/publish-napi
branch
from
88d40a7 to
26a5b2c
Compare
this currently runs based on commit message which will not cause anything to run, however, until we set up a real NPM_TOKEN and decide how we want to release, this won't be able to publish
dav1do
force-pushed
the
chore/publish-napi
branch
from
26a5b2c to
1be0d89
Compare
nathanielc
approved these changes
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Example modification to CI workflow that could be used to publish the napi packages. We could obviously publish from the root to include all packages in the future. Currently there is a secret called
NPM_TOKENbut the value is simply TODO so it will not be able to publish.