Skip to content
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.

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

feat: publishing to github packages from develop #274

Merged
merged 7 commits into from
Jun 26, 2020

Conversation

rflechtner
Copy link
Contributor

@rflechtner rflechtner commented Jun 25, 2020

fixes KILTProtocol/ticket#599

Builds and publishes the sdk as a npm package to the GitHub Packages repo.
These releases are versioned with the current commit id and tagged dev.

Possible issues:

  • there is a (almost empty) .npmrc in this repo that may interfere with the publishing process
    • removed it after talking to Dudley, who added it
  • the package.json mentions a target for publishing (publishConfig) that could potentially interfere
    • does not seem to interfere

How to test:

By adding this branch to the triggers I have successfully triggered a release. You can find the published package in https://github.com/KILTprotocol/sdk-js/packages/286306.

Checklist:

  • I have verified that the code works
  • I have verified that the code is easy to understand
    • If not, I have left a well-balanced amount of inline comments
  • I have left the code in a better state
  • I have documented the changes (where applicable)

@rflechtner rflechtner added ✨ new feature feature: new feature 🚨 tests chore: tests labels Jun 25, 2020
@rflechtner rflechtner force-pushed the publish-github-package branch from 12e2176 to beb2b62 Compare June 25, 2020 10:29
This reverts commit a34ed45.
@rflechtner rflechtner marked this pull request as ready for review June 25, 2020 10:40
@rflechtner rflechtner force-pushed the publish-github-package branch from f80a01d to a4aa5c5 Compare June 26, 2020 11:29
@rflechtner rflechtner requested a review from tjwelde June 26, 2020 11:30
@rflechtner rflechtner force-pushed the publish-github-package branch from a4aa5c5 to 8034705 Compare June 26, 2020 11:48
@rflechtner rflechtner force-pushed the publish-github-package branch from 8034705 to 8d8fcdd Compare June 26, 2020 11:55
.npmrc Outdated
@@ -1 +0,0 @@
tag-version-prefix=""
Copy link
Contributor

Choose a reason for hiding this comment

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

The tag version prefix was necessary for doing the public release to npm registry. Is it obsolete?

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 don't actually know - it looked like Dudley introduced this with his last PR and he said it was irrelevant, so I removed it. If we still need it, I can put it back in

Copy link
Contributor Author

Choose a reason for hiding this comment

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

image

Copy link
Contributor

@tjwelde tjwelde left a comment

Choose a reason for hiding this comment

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

LGTM

@rflechtner rflechtner merged commit 5b84729 into develop Jun 26, 2020
@rflechtner rflechtner deleted the publish-github-package branch June 26, 2020 13:23
@wischli wischli added this to the v0.19.0 milestone Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ new feature feature: new feature 🚨 tests chore: tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants