Closed daveashworth closed 6 years ago
This would be an issue across all the versions of auto-publishers. Ex: https://github.com/sindresorhus/np/issues/99.
@daveashworth LOL, I just found the same article!
git ls-remote
is something I've seen Capistrano do to check repo permissions, but I think we'd want something to ensure we have git tag
& push support.I could've sworn that NPM_TOKEN
from ~/.npmrc
(when put into CI) is how we addressed this.
@ericclemmons saw that too! Man, unless the NPM_TOKEN originally used for this repo is no longer valid, I also thought that was how the publish permissions were verified. π
Using npm
as the provider in travis.yml
would publish to npm for us, but would skip out on the rest of our gsv
script, right?
You're right. I just thought the token adding was easier. Although they still have to do it for GitHub...
On Mon, Dec 5, 2016, 3:49 PM Dave Ashworth notifications@github.com wrote:
@ericclemmons https://github.com/ericclemmons saw that too! Man, unless the NPM_TOKEN originally used for this repo is no longer valid, I also thought that was how the publish permissions were verified. π
Using npm as the provider would publish to npm for us, but would skip out on the rest of our gsv script, right?
β You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ericclemmons/github-semantic-version/issues/18#issuecomment-264988305, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA7TtbvpgIMjIWYwj0isQWAL9guWxPJks5rFIbxgaJpZM4LEuee .
--
- Eric Clemmons
@ericclemmons I'm looking to add some new features to this project, but Travis currently failing. Could you double check the tokens in Travis are still valid?
Just settled into Seattle & updated the token. π€
Ok, GH_TOKEN
was also wrong. Updated that & retrying the build...
It should work with the next release, but this error has occurred:
Error: No commits found in v7.6.0..HEAD
any resolution to this?
for me i resolved by adding this to my circleci/config.yml
- run: echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
Deploy log from Travis CI:
Before we push to Github or publish to npm, maybe we need to run pre-checks for permissions on both. One succeeding but not the other causes issues.