Skip to content

Publish to NPM setup #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Feb 17, 2021
Merged

Publish to NPM setup #2

merged 2 commits into from
Feb 17, 2021

Conversation

schulmacher
Copy link
Contributor

No description provided.

@schulmacher schulmacher requested a review from a team February 17, 2021 10:06
tot-ra
tot-ra reviewed Feb 17, 2021
View reviewed changes
Jenkinsfile
@@ -0,0 +1,3 @@
DEFAULT_NODE_VERSION = '14'
NODE_VERSIONS = ['8', '14']
Copy link
Owner

Choose a reason for hiding this comment

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

10? 12?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought it will take longer, 10-12 should be covered with 14 :D

tot-ra
tot-ra previously approved these changes Feb 17, 2021
View reviewed changes
@schulmacher schulmacher added the npm-ready-for-publish Will trigger publishing the package label Feb 17, 2021
@pipedrive-bot pipedrive-bot merged commit dc2e6d8 into master Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tot-ra tot-ra tot-ra left review comments

Assignees
No one assigned
Labels
npm-ready-for-publish Will trigger publishing the package npm-version-patch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@schulmacher @tot-ra @pipedrive-bot