Git Product home page Git Product logo

semantic-release-gh-pages-plugin's Introduction

@qiwi/semantic-release-gh-pages-plugin

CI Test Coverage Maintainability npm (tag)

gh-pages publishing plugin for semantic-release

Step Description
verifyConditions Verify the presence of the GH_TOKEN set via environment variables.
publish Pushes commit to the documentation branch

Install

# yarn
yarn add @qiwi/semantic-release-gh-pages-plugin --dev
# npm
npm i @qiwi/semantic-release-gh-pages-plugin -D

Usage

Describe plugin configuration in package.json / .releaserc.js

{
  "release": {
    "branch": "master",
    "verifyConditions": [
      "@semantic-release/changelog",
      "@semantic-release/npm",
      "@semantic-release/git",
      "@qiwi/semantic-release-gh-pages-plugin"
    ],
    "publish": [
      "@semantic-release/npm",
      "@semantic-release/github",
      [
        "@qiwi/semantic-release-gh-pages-plugin",
        {
          "msg": "updated",
          "branch": "docs"
        }
      ]
    ]
  }
}

or even shorter if default settings are used:

{
  "release": {
    "branch": "master",
    "plugins": [
      "@semantic-release/release-notes-generator",
      "@semantic-release/changelog",
      "@semantic-release/git",
      "@semantic-release/github",
      "@semantic-release/npm",
      "@qiwi/semantic-release-gh-pages-plugin"
    ]
  }
}

Configuration

Environment variables

Variable Description
GH_TOKEN or GITHUB_TOKEN Required. The token used to authenticate with GitHub.

Options

Option Description Default
msg Commit message template docs updated <%= nextRelease.gitTag %>
src Documentation directory docs

NOTE don't forget to run docs builder (yarn docs, yarn typedoc, etc) as a part of your build step or any other way
dst Destination directory . (root)
branch Docs branch to push gh-pages
branches Optional list of src-to-target branches association. If defined it suppresses branch option. For example, [['master', 'gh-pages'], ['beta', beta-docs]] undefined
repositoryUrl Repository url inherited from .git
enterprise Disables host assertion for GitHub Enterprise domains false
pullTagsBranch Target branch for tags fetching hook. If '' empty string, skips this action globalConfig.branch || master
dotfiles gh-pages dotfiles option false
add gh-pages add option false

License

MIT

semantic-release-gh-pages-plugin's People

Contributors

alebianco avatar antongolub avatar dependabot[bot] avatar greenkeeper[bot] avatar heshammeneisi avatar oljekechoro avatar qiwibot avatar renovate-bot avatar renovate[bot] avatar shanejonas avatar sumwatshade avatar yyynnn avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

semantic-release-gh-pages-plugin's Issues

An in-range update of yargs is breaking the build 🚨

The devDependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 14 commits.

  • a6e67f1 chore(release): 13.2.4
  • fc13476 chore: update standard-verison dependency
  • bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
  • a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
  • b4f8018 build: add .versionrc that hides test/build
  • 0c39183 chore(release): 13.2.3
  • 08e0746 chore: update deps (#1340)
  • 843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
  • 84cac07 docs: restore removed changelog of v13.2.0 (#1337)
  • b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
  • c294d1b test: accept differently formatted output (#1327)
  • ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
  • 0295132 fix: address issues with dutch translation (#1316)
  • 9f2468e doc: clarify parserConfiguration object structure (#1309)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Cannot find module 'defaults'

Steps to reproduce

  1. Using the following example config .releaserc:
{
  "tagFormat": "${version}",
  "branch": "master",
  "verifyConditions": [
    "@semantic-release/changelog",
    "@semantic-release/git",
    "@qiwi/semantic-release-gh-pages-plugin"
  ],
  "publish": [
    "@semantic-release/github",
    {
      "path": "@qiwi/semantic-release-gh-pages-plugin",
      "msg": "deploy: new gh-pages release",
      "src": "build",
      "branch": "gh-pages"
    }
  ]
}
  1. run npx semantic-release
  2. See error below

Additional information

An error occurred while running semantic-release: { Error: Cannot find module 'defaults'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (<>/node_modules/@qiwi/semantic-release-gh-pages-plugin/lib/es5/index.js:10:22)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }
{ Error: Cannot find module 'defaults'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (<>node_modules/@qiwi/semantic-release-gh-pages-plugin/lib/es5/index.js:10:22)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }%

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Invalid username or password: Command failed with exit code 1: git pull --tags --force https://[secure]@github.com/org/package-foo.git

I am getting the following error message.

The GitHub action step is like this (included GITHUB_TOKEN):

      - name: Semantic Release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
          SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
        run: npm run semantic-release

Error:

2020-03-28T16:56:02.2949375Z > @org/[email protected] semantic-release /home/runner/work/package-foo/package-foo
2020-03-28T16:56:02.2951615Z > semantic-release
2020-03-28T16:56:02.2952044Z 
2020-03-28T16:56:02.5652247Z [4:56:02 PM] [semantic-release] › ℹ  Running semantic-release version 17.0.4
2020-03-28T16:56:02.7732114Z [4:56:02 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:02.7869179Z [4:56:02 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer" in shareable config "@org/semantic-release-config"
2020-03-28T16:56:02.7873798Z [4:56:02 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:04.1790636Z [4:56:04 PM] [semantic-release] › ✔  Run automated release from branch master on repository https://x-access-token:[secure]@github.com/org/package-foo
2020-03-28T16:56:04.4949960Z [4:56:04 PM] [semantic-release] › ✔  Allowed to push to the Git repository
2020-03-28T16:56:04.4954865Z [4:56:04 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:04.5145253Z [4:56:04 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  verify gh-pages config
2020-03-28T16:56:04.5149162Z [4:56:04 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:04.5218546Z [4:56:04 PM] [semantic-release] › ℹ  Found git tag v1.8.0 associated with version 1.8.0 on branch master
2020-03-28T16:56:04.5323660Z [4:56:04 PM] [semantic-release] › ℹ  Found 8 commits since last release
2020-03-28T16:56:04.5326398Z [4:56:04 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
2020-03-28T16:56:04.5405042Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: ci: removes debug
2020-03-28T16:56:04.5412875Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5414120Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: ci: enables debug for semantic-release-gh-pages-plugin
2020-03-28T16:56:04.5415375Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5416539Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: docs: triggers a release
2020-03-28T16:56:04.5425867Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5434728Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: ci: adds docs generating step
2020-03-28T16:56:04.5460054Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5461370Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat: adds typedoc and GitHub pages (#305)
2020-03-28T16:56:04.5462427Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is minor
2020-03-28T16:56:04.5463273Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: test: fixes missing param
2020-03-28T16:56:04.5464110Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5464894Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Update CNAME
2020-03-28T16:56:04.5465633Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5466369Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Create CNAME
2020-03-28T16:56:04.5467151Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
2020-03-28T16:56:04.5467986Z [4:56:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 8 commits complete: minor release
2020-03-28T16:56:04.5468753Z [4:56:04 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
2020-03-28T16:56:04.5507963Z [4:56:04 PM] [semantic-release] › ℹ  The next release version is 1.9.0
2020-03-28T16:56:10.7167862Z [4:56:10 PM] [semantic-release] › ✔  Created tag v1.9.0
2020-03-28T16:56:10.7172458Z [4:56:10 PM] [semantic-release] › ℹ  Start step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:10.7220160Z [4:56:10 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  Publishing docs via gh-pages
2020-03-28T16:56:10.9265845Z [4:56:10 PM] [semantic-release] › ✖  Failed step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2020-03-28T16:56:10.9289607Z [4:56:10 PM] [semantic-release] › ✖  An error occurred while running semantic-release: Error: Command failed with exit code 1: git pull --tags --force https://[secure]@github.com/org/package-foo.git
2020-03-28T16:56:10.9290354Z remote: Invalid username or password.
2020-03-28T16:56:10.9291317Z fatal: Authentication failed for 'https://github.com/org/package-foo.git/'
2020-03-28T16:56:10.9292177Z     at makeError (/home/runner/work/package-foo/package-foo/node_modules/@qiwi/semantic-release-gh-pages-plugin/node_modules/execa/lib/error.js:58:11)
2020-03-28T16:56:10.9304463Z     at handlePromise (/home/runner/work/package-foo/package-foo/node_modules/@qiwi/semantic-release-gh-pages-plugin/node_modules/execa/index.js:114:26)
2020-03-28T16:56:10.9304986Z     at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-03-28T16:56:10.9305833Z     at async validator (/home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
2020-03-28T16:56:10.9306998Z     at async /home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
2020-03-28T16:56:10.9307858Z     at async /home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/lib/plugins/pipeline.js:31:3
2020-03-28T16:56:10.9308766Z     at async Object.pluginsConf.<computed> [as publish] (/home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/lib/plugins/index.js:80:11)
2020-03-28T16:56:10.9317031Z     at async run (/home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/index.js:197:20)
2020-03-28T16:56:10.9319981Z     at async module.exports (/home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/index.js:259:22)
2020-03-28T16:56:10.9320956Z     at async module.exports (/home/runner/work/package-foo/package-foo/node_modules/@org/semantic-release-config/node_modules/semantic-release/cli.js:55:5) {
2020-03-28T16:56:10.9321729Z   shortMessage: 'Command failed with exit code 1: git pull --tags --force https://[secure]@github.com/org/package-foo.git',
2020-03-28T16:56:10.9322425Z   command: 'git pull --tags --force https://[secure]@github.com/org/package-foo.git',
2020-03-28T16:56:10.9322772Z   exitCode: 1,
2020-03-28T16:56:10.9323067Z   signal: undefined,
2020-03-28T16:56:10.9323377Z   signalDescription: undefined,
2020-03-28T16:56:10.9323808Z   stdout: '',
2020-03-28T16:56:10.9324338Z   stderr: 'remote: Invalid username or password.\n' +
2020-03-28T16:56:10.9325006Z     "fatal: Authentication failed for 'https://github.com/org/package-foo.git/'",
2020-03-28T16:56:10.9325369Z   failed: true,
2020-03-28T16:56:10.9325669Z   timedOut: false,
2020-03-28T16:56:10.9325965Z   isCanceled: false,
2020-03-28T16:56:10.9326242Z   killed: false,
2020-03-28T16:56:10.9326734Z   pluginName: '@qiwi/semantic-release-gh-pages-plugin'
2020-03-28T16:56:10.9327106Z }
2020-03-28T16:56:10.9327937Z Error: Command failed with exit code 1: git pull --tags --force https://[secure]@github.com/org/package-foo.git
2020-03-28T16:56:10.9328367Z remote: Invalid username or password.
2020-03-28T16:56:10.9329051Z fatal: Authentication failed for 'https://github.com/org/package-foo.git/'
2020-03-28T16:56:10.9329888Z     at makeError (/home/runner/work/package-foo/package-foo/node_modules/�[4m@qiwi�[24m/semantic-release-gh-pages-plugin/node_modules/�[4mexeca�[24m/lib/error.js:58:11)
2020-03-28T16:56:10.9330849Z     at handlePromise (/home/runner/work/package-foo/package-foo/node_modules/�[4m@qiwi�[24m/semantic-release-gh-pages-plugin/node_modules/�[4mexeca�[24m/index.js:114:26)
2020-03-28T16:56:10.9331556Z �[90m    at processTicksAndRejections (internal/process/task_queues.js:97:5)�[39m
2020-03-28T16:56:10.9332614Z     at async validator (/home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/lib/plugins/normalize.js:34:24)
2020-03-28T16:56:10.9333690Z     at async /home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/lib/plugins/pipeline.js:37:34
2020-03-28T16:56:10.9334589Z     at async /home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/lib/plugins/pipeline.js:31:3
2020-03-28T16:56:10.9335595Z     at async Object.pluginsConf.<computed> [as publish] (/home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/lib/plugins/index.js:80:11)
2020-03-28T16:56:10.9336567Z     at async run (/home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/index.js:197:20)
2020-03-28T16:56:10.9337759Z     at async module.exports (/home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/index.js:259:22)
2020-03-28T16:56:10.9340804Z     at async module.exports (/home/runner/work/package-foo/package-foo/node_modules/�[4m@org�[24m/semantic-release-config/node_modules/�[4msemantic-release�[24m/cli.js:55:5) {
2020-03-28T16:56:10.9341662Z   shortMessage: �[32m'Command failed with exit code 1: git pull --tags --force https://[secure]@github.com/org/package-foo.git'�[39m,
2020-03-28T16:56:10.9342222Z   command: �[32m'git pull --tags --force https://[secure]@github.com/org/package-foo.git'�[39m,
2020-03-28T16:56:10.9342552Z   exitCode: �[33m1�[39m,
2020-03-28T16:56:10.9342876Z   signal: �[90mundefined�[39m,
2020-03-28T16:56:10.9343192Z   signalDescription: �[90mundefined�[39m,
2020-03-28T16:56:10.9343504Z   stdout: �[32m''�[39m,
2020-03-28T16:56:10.9343862Z   stderr: �[32m'remote: Invalid username or password.\n'�[39m +
2020-03-28T16:56:10.9344357Z     �[32m"fatal: Authentication failed for 'https://github.com/org/package-foo.git/'"�[39m,
2020-03-28T16:56:10.9344711Z   failed: �[33mtrue�[39m,
2020-03-28T16:56:10.9345013Z   timedOut: �[33mfalse�[39m,
2020-03-28T16:56:10.9345331Z   isCanceled: �[33mfalse�[39m,
2020-03-28T16:56:10.9347397Z   killed: �[33mfalse�[39m,
2020-03-28T16:56:10.9347903Z   pluginName: �[32m'@qiwi/semantic-release-gh-pages-plugin'�[39m
2020-03-28T16:56:10.9504391Z }npm ERR! code ELIFECYCLE
2020-03-28T16:56:10.9504672Z npm ERR! errno 1
2020-03-28T16:56:10.9507930Z npm ERR! @org/[email protected] semantic-release: `semantic-release`
2020-03-28T16:56:10.9508203Z npm ERR! Exit status 1
2020-03-28T16:56:10.9510511Z npm ERR! 
2020-03-28T16:56:10.9511395Z npm ERR! Failed at the @org/[email protected] semantic-release script.
2020-03-28T16:56:10.9511791Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-03-28T16:56:10.9673896Z 
2020-03-28T16:56:10.9676343Z npm ERR! A complete log of this run can be found in:
2020-03-28T16:56:10.9678391Z npm ERR!     /home/runner/.npm/_logs/2020-03-28T16_56_10_951Z-debug.log
2020-03-28T16:56:10.9780648Z ##[error]Process completed with exit code 1.
2020-03-28T16:56:10.9828334Z Cleaning up orphan processes

Any ideas?

Thanks!

Updates were rejected because the tag already exists in the remote

First release on https://github.com/iki/expenses-app-react-ts-gql worked ok. Then I deleted and recreated repo, tried again and encountered the issue repeatedly since then.

It seems that https://github.com/qiwi/semantic-release-gh-pages-plugin tries to create a release tag that is already created by https://github.com/semantic-release/git.

Didn't help repeatedly:

  • hard resetting local/remote master before the release commit + removing local/remote release tags + removing local/remote gh_pages branch
  • same as above + deleting GitHub repo and creating again

Worked ok repeatedly with any of these changes in .releaserc.yml`:

  • removed @qiwi/semantic-release-gh-pages-plugin
  • or removing @semantic-release/git
  • or replacing @semantic-release/git with @semantic-release/github

Failing configuration:

plugins:
  - '@semantic-release/commit-analyzer'
  - '@semantic-release/release-notes-generator'
  - '@semantic-release/changelog'
  - '@semantic-release/git'
  -
    - '@qiwi/semantic-release-gh-pages-plugin'
    -
      src: build
      msg: 'deploy(gh-pages): {{=it.nextRelease.gitTag}}'

release:
  branch: master

Using current versions:

  "devDependencies": {
    "@qiwi/semantic-release-gh-pages-plugin": "^1.10.4",
    "@semantic-release/changelog": "^3.0.4",
    "@semantic-release/git": "^7.0.16",
    "semantic-release": "^15.13.19"
  },

Failing debug log:

yarn run v1.12.3
$ yarn run-env semantic-release --no-ci --debug
=== yarn run-env semantic-release --no-ci --debug
$ sh -c "dotenv -e .env -e .env.local -e .env.${NODE_ENV:=development} -e .env.${NODE_ENV:=development}.local -- $@" -- semantic-release --no-ci --debug
[7:12:49 PM] [semantic-release] » i  Running semantic-release version 15.13.19
  semantic-release:config load config from: C:\Users\iki\..src\expenses-app-react-ts-gql\.releaserc.yml +0ms
  semantic-release:config options values: {
  semantic-release:config   branch: 'master',
  semantic-release:config   repositoryUrl: 'git+https://github.com/iki/expenses-app-react-ts-gql',
  semantic-release:config   tagFormat: 'v${version}',
  semantic-release:config   plugins: [
  semantic-release:config     '@semantic-release/commit-analyzer',
  semantic-release:config     '@semantic-release/release-notes-generator',
  semantic-release:config     '@semantic-release/changelog',
  semantic-release:config     '@semantic-release/git',
  semantic-release:config     [ '@qiwi/semantic-release-gh-pages-plugin', [Object] ]
  semantic-release:config   ],
  semantic-release:config   release: { branch: 'master' },
  semantic-release:config   _: [],
  semantic-release:config   ci: false,
  semantic-release:config   debug: true,
  semantic-release:config   '$0': 'node_modules\\semantic-release\\bin\\semantic-release.js',
  semantic-release:config   noCi: true
  semantic-release:config } +5ms
  semantic-release:plugins options for @semantic-release/changelog/verifyConditions: {} +0ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "verifyConditions" from "@semantic-release/changelog"
  semantic-release:plugins options for @semantic-release/git/verifyConditions: {} +6ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "verifyConditions" from "@semantic-release/git"
  semantic-release:plugins options for @qiwi/semantic-release-gh-pages-plugin/verifyConditions: { src: 'build', msg: 'deploy(gh-pages): {{=it.nextRelease.gitTag}}' } +3ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "verifyConditions" from "@qiwi/semantic-release-gh-pages-plugin"
  semantic-release:plugins options for @semantic-release/commit-analyzer/analyzeCommits: {} +8ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
  semantic-release:plugins options for @semantic-release/release-notes-generator/generateNotes: {} +4ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
  semantic-release:plugins options for @semantic-release/changelog/prepare: {} +3ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "prepare" from "@semantic-release/changelog"
  semantic-release:plugins options for @semantic-release/git/prepare: {} +4ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "prepare" from "@semantic-release/git"
  semantic-release:plugins options for @qiwi/semantic-release-gh-pages-plugin/publish: { src: 'build', msg: 'deploy(gh-pages): {{=it.nextRelease.gitTag}}' } +5ms
[7:12:50 PM] [semantic-release] » √  Loaded plugin "publish" from "@qiwi/semantic-release-gh-pages-plugin"
[7:12:50 PM] [semantic-release] » √  Run automated release from branch master
[7:12:56 PM] [semantic-release] » √  Allowed to push to the Git repository
[7:12:56 PM] [semantic-release] » i  Start step "verifyConditions" of plugin "@semantic-release/changelog"
[7:12:56 PM] [semantic-release] » √  Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[7:12:56 PM] [semantic-release] » i  Start step "verifyConditions" of plugin "@semantic-release/git"
[7:12:56 PM] [semantic-release] » √  Completed step "verifyConditions" of plugin "@semantic-release/git"
[7:12:56 PM] [semantic-release] » i  Start step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[7:12:56 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] » i  verify gh-pages config
[7:12:56 PM] [semantic-release] » √  Completed step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
  semantic-release:get-last-release found tags: [] +0ms
[7:12:57 PM] [semantic-release] » i  No git tag version found
[7:12:57 PM] [semantic-release] » i  No previous release found, retrieving all commits
[7:12:57 PM] [semantic-release] » i  Found 5 commits since last release
  semantic-release:get-commits Parsed commits: [ { commit: { long: '72da2c219c9ec70e23240d95765585c4d6134994', short: '72da2c2' }, tree: { long: 'fe68f0f44826d68636b13bcfb22732a88453a5c6', short: 'fe68f0f' }, author: { name: 'Jan Killian', email: '...', date: 2019-07-31T16:23:29.000Z }, committer: { name: 'Jan Killian', email: '...', date: 2019-07-31T17:11:38.000Z }, subject: 'chore(build): add yarn release command to create and deploy new release', body: '', hash: '72da2c219c9ec70e23240d95765585c4d6134994', message: 'chore(build): add yarn release command to create and deploy new release', gitTags: '(HEAD -> master, origin/master, origin/HEAD)', committerDate: 2019-07-31T17:11:38.000Z }, { commit: { long: 'd52574f33d7ef6000e43cd7d069fce6169f12e3c', short: 'd52574f' }, tree: { long: 'f56bc814d9fe1766b7b6dce8f8e94edfc575e5ce', short: 'f56bc81' }, author: { name: 'Jan Killian', email: '...', date: 2019-07-31T16:13:43.000Z }, committer: { name: 'Jan Killian', email: '...', date: 2019-07-31T16:13:43.000Z }, subject: 'docs(readme): add environment settings docs', body: '', hash: 'd52574f33d7ef6000e43cd7d069fce6169f12e3c', message: 'docs(readme): add environment settings docs', gitTags: '', committerDate: 2019-07-31T16:13:43.000Z }, { commit: { long: '3cf0230fe66bf86082d54b9b8c5f76942b521f10', short: '3cf0230' }, tree: { long: '312aabe58afb01b2d7789aa305a0034c14f3fc36', short: '312aabe' }, author: { name: 'Jan Killian', email: '...', date: 2019-07-31T14:44:50.000Z }, committer: { name: 'Jan Killian', email: '...', date: 2019-07-31T14:44:50.000Z }, subject: 'chore(project): set project package properties', body: '', hash: '3cf0230fe66bf86082d54b9b8c5f76942b521f10', message: 'chore(project): set project package properties', gitTags: '', committerDate: 2019-07-31T14:44:50.000Z }, { commit: { long: 'd379edb72411b9b70753dc28228e9248481eab4f', short: 'd379edb' }, tree: { long: '2a22022c91647403a3e462a9aaeef0a02fab68f8', short: '2a22022' }, author: { name: 'Jan Killian', email: '...', date: 2019-07-31T14:07:17.000Z }, committer: { name: 'Jan Killian', email: '...', date: 2019-07-31T14:08:24.000Z }, subject: 'fix(security): fix CVE-2019-10744 in lodash<4.17.13 and lodash.template<4.5.0', body: '', hash: 'd379edb72411b9b70753dc28228e9248481eab4f', message: 'fix(security): fix CVE-2019-10744 in lodash<4.17.13 and lodash.template<4.5.0', gitTags: '', committerDate: 2019-07-31T14:08:24.000Z }, { commit: { long: '8d4abde0cebecac9405817e11b4575417b8b90b0', short: '8d4abde' }, tree: { long: 'b566799d6da231e2c1ad24b18fdbe27e959cd0b6', short: 'b566799' }, author: { name: 'Jan Killian', email: '...', date: 2019-07-28T19:37:35.000Z }, committer: { name: 'Jan Killian', email: '...', date: 2019-07-31T14:03:32.000Z }, subject: 'feat(core): create React app with TypeScript support', body: '', hash: '8d4abde0cebecac9405817e11b4575417b8b90b0', message: 'feat(core): create React app with TypeScript support', gitTags: '(0)', committerDate: 2019-07-31T14:03:32.000Z } ] +0ms
[7:12:57 PM] [semantic-release] » i  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: chore(build): add yarn release command to create and deploy new release
  semantic-release:commit-analyzer Analyzing with default rules +0ms
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The commit should not trigger a release
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: docs(readme): add environment settings docs
  semantic-release:commit-analyzer Analyzing with default rules +11ms
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The commit should not trigger a release
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: chore(project): set project package properties
  semantic-release:commit-analyzer Analyzing with default rules +6ms
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The commit should not trigger a release
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: fix(security): fix CVE-2019-10744 in lodash<4.17.13 and lodash.template<4.5.0
  semantic-release:commit-analyzer Analyzing with default rules +9ms
  semantic-release:commit-analyzer The rule { type: 'fix', release: 'patch' } match commit with release type 'patch' +0ms [7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The release type for the commit is patch
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analyzing commit: feat(core): create React app with TypeScript support
  semantic-release:commit-analyzer Analyzing with default rules +11ms
  semantic-release:commit-analyzer The rule { type: 'feat', release: 'minor' } match commit with release type 'minor' +14ms
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  The release type for the commit is minor
[7:12:57 PM] [semantic-release] [@semantic-release/commit-analyzer] » i  Analysis of 5 commits complete: minor release
[7:12:57 PM] [semantic-release] » √  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[7:12:57 PM] [semantic-release] » i  There is no previous release, the next release version is 1.0.0
[7:12:57 PM] [semantic-release] » i  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
  semantic-release:release-notes-generator version: '1.0.0' +0ms
  semantic-release:release-notes-generator host: undefined +2ms
  semantic-release:release-notes-generator owner: 'iki' +2ms
  semantic-release:release-notes-generator repository: 'expenses-app-react-ts-gql' +1ms
  semantic-release:release-notes-generator previousTag: undefined +2ms
  semantic-release:release-notes-generator currentTag: 'v1.0.0' +1ms
  semantic-release:release-notes-generator host: 'https://github.com' +3ms
  semantic-release:release-notes-generator host: 'https://github.com' +2ms
  semantic-release:release-notes-generator linkReferences: undefined +2ms
  semantic-release:release-notes-generator issue: 'issues' +3ms
  semantic-release:release-notes-generator commit: 'commit' +5ms
[7:12:58 PM] [semantic-release] » √  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator" [7:12:58 PM] [semantic-release] » i  Start step "prepare" of plugin "@semantic-release/changelog"
[7:12:58 PM] [semantic-release] [@semantic-release/changelog] » i  Create C:\Users\iki\..src\expenses-app-react-ts-gql\CHANGELOG.md
[7:12:58 PM] [semantic-release] » √  Completed step "prepare" of plugin "@semantic-release/changelog"
[7:12:58 PM] [semantic-release] » i  Start step "prepare" of plugin "@semantic-release/git"
  semantic-release:git globed assets: [ 'CHANGELOG.md', 'package.json' ] +0ms
[7:12:58 PM] [semantic-release] [@semantic-release/git] » i  Found 1 file(s) to commit
  semantic-release:git add file to git index {
  stdout: '',
  stderr: '',
  code: 0,
  failed: false,
  killed: false,
  signal: null,
  cmd: 'git add --force --ignore-errors CHANGELOG.md',
  timedOut: false
} +0ms
  semantic-release:git commited files: [ 'CHANGELOG.md' ] +124ms
[7:13:04 PM] [semantic-release] [@semantic-release/git] » i  Prepared Git release: v1.0.0
[7:13:04 PM] [semantic-release] » √  Completed step "prepare" of plugin "@semantic-release/git"
[7:13:04 PM] [semantic-release] » i  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
  semantic-release:release-notes-generator version: '1.0.0' +7s
  semantic-release:release-notes-generator host: undefined +4ms
  semantic-release:release-notes-generator owner: 'iki' +2ms
  semantic-release:release-notes-generator repository: 'expenses-app-react-ts-gql' +1ms
  semantic-release:release-notes-generator previousTag: undefined +2ms
  semantic-release:release-notes-generator currentTag: 'v1.0.0' +2ms
  semantic-release:release-notes-generator host: 'https://github.com' +2ms
  semantic-release:release-notes-generator host: 'https://github.com' +2ms
  semantic-release:release-notes-generator linkReferences: undefined +3ms
  semantic-release:release-notes-generator issue: 'issues' +2ms
  semantic-release:release-notes-generator commit: 'commit' +3ms
[7:13:04 PM] [semantic-release] » √  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator" [7:13:11 PM] [semantic-release] » √  Created tag v1.0.0
[7:13:11 PM] [semantic-release] » i  Start step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[7:13:11 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] » i  Publishing docs via gh-pages
[7:13:22 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] » ×  Publish docs failure ProcessError: To https://github.com/iki/expenses-app-react-ts-gql.git
 * [new branch]      gh-pages -> gh-pages
 * [new tag]         v1.0.1 -> v1.0.1
 ! [rejected]        v1.0.0 -> v1.0.0 (already exists)
error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'
hint: Updates were rejected because the tag already exists in the remote.

    at ChildProcess.<anonymous> (C:\Users\iki\..src\expenses-app-react-ts-gql\node_modules\gh-pages\lib\git.js:42:16)
    at ChildProcess.emit (events.js:203:13)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 1,
  message: 'To https://github.com/iki/expenses-app-react-ts-gql.git\n' +
    ' * [new branch]      gh-pages -> gh-pages\n' +
    ' * [new tag]         v1.0.1 -> v1.0.1\n' +
    ' ! [rejected]        v1.0.0 -> v1.0.0 (already exists)\n' +
    "error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'\n" +
    'hint: Updates were rejected because the tag already exists in the remote.\n',
  name: 'ProcessError'
}
[7:13:22 PM] [semantic-release] » ×  Failed step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[7:13:22 PM] [semantic-release] » ×  An error occurred while running semantic-release: ProcessError: To https://github.com/iki/expenses-app-react-ts-gql.git
 * [new branch]      gh-pages -> gh-pages
 * [new tag]         v1.0.1 -> v1.0.1
 ! [rejected]        v1.0.0 -> v1.0.0 (already exists)
error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'
hint: Updates were rejected because the tag already exists in the remote.

    at ChildProcess.<anonymous> (C:\Users\iki\..src\expenses-app-react-ts-gql\node_modules\gh-pages\lib\git.js:42:16)
    at ChildProcess.emit (events.js:203:13)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 1,
  message: 'To https://github.com/iki/expenses-app-react-ts-gql.git\n' +
    ' * [new branch]      gh-pages -> gh-pages\n' +
    ' * [new tag]         v1.0.1 -> v1.0.1\n' +
    ' ! [rejected]        v1.0.0 -> v1.0.0 (already exists)\n' +
    "error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'\n" +
    'hint: Updates were rejected because the tag already exists in the remote.\n',
  name: 'ProcessError',
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}
ProcessError: To https://github.com/iki/expenses-app-react-ts-gql.git
 * [new branch]      gh-pages -> gh-pages
 * [new tag]         v1.0.1 -> v1.0.1
 ! [rejected]        v1.0.0 -> v1.0.0 (already exists)
error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'
hint: Updates were rejected because the tag already exists in the remote.

    at ChildProcess.<anonymous> (C:\Users\iki\..src\expenses-app-react-ts-gql\node_modules\gh-pages\lib\git.js:42:16)
    at ChildProcess.emit (events.js:203:13)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 1,
  message: 'To https://github.com/iki/expenses-app-react-ts-gql.git\n' +
    ' * [new branch]      gh-pages -> gh-pages\n' +
    ' * [new tag]         v1.0.1 -> v1.0.1\n' +
    ' ! [rejected]        v1.0.0 -> v1.0.0 (already exists)\n' +
    "error: failed to push some refs to 'https://[secure]@github.com/iki/expenses-app-react-ts-gql.git'\n" +
    'hint: Updates were rejected because the tag already exists in the remote.\n',
  name: 'ProcessError',
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

EDIT: Removed my email from parsed commits :)

Replace sync-request with then-request

[test:unit    ] Jest has detected the following 1 open handle potentially keeping Jest from exiting:
[test:unit    ] 
[test:unit    ]   ●  PROCESSWRAP
[test:unit    ] 
[test:unit    ]       at start (../../node_modules/sync-rpc/lib/index.js:30:13)
[test:unit    ]       at sendMessage (../../node_modules/sync-rpc/lib/index.js:127:17)
[test:unit    ]       at createClient (../../node_modules/sync-rpc/lib/index.js:157:27)
[test:unit    ]       at Object.<anonymous> (../../node_modules/sync-request/lib/index.js:22:14)

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

github-actions
.github/workflows/ci.yaml
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • actions/setup-node v4
  • paambaati/codeclimate-action v5.0.0
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • actions/setup-node v4
  • ubuntu 22.04
.github/workflows/codeql-analysis.yml
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • github/codeql-action v3
  • github/codeql-action v3
  • github/codeql-action v3
npm
package.json
  • @qiwi/substrate-types ^2.1.0
  • aggregate-error ^3.1.0
  • debug ^4.3.4
  • execa ^5.1.1
  • gh-pages ^6.1.1
  • git-url-parse ^14.0.0
  • lodash ^4.17.21
  • queuefy ^1.2.1
  • read-pkg ^5.2.0
  • then-request ^6.0.2
  • tslib ^2.6.2
  • @types/debug ^4.1.12
  • @types/git-url-parse ^9.0.3
  • @types/semantic-release ^20.0.6
  • @types/gh-pages ^6.1.0
  • @types/lodash ^4.14.202
  • @qiwi/libdefkit 6.1.3
  • @qiwi/npm-run-all ^4.1.7
  • @types/jest ^29.5.11
  • jest ^29.7.0
  • cpy-cli ^5.0.0
  • mkdirp ^3.0.1
  • rimraf ^5.0.5
  • ts-jest ^29.1.2
  • eslint ^8.56.0
  • eslint-config-prettier ^9.1.0
  • eslint-config-qiwi ^2.1.3
  • typedoc ^0.25.7
  • typescript 5.3.3

  • Check this box to trigger a request for Renovate to run again on this repository

An in-range update of @types/semantic-release is breaking the build 🚨

The devDependency @types/semantic-release was updated from 15.13.0 to 15.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Allow publishing of user's github page

The verifyConditions step fails while checking the repository url when publishing the github page repository of a user or organisation.

[3:22:50 PM] [semantic-release] › ✖  Failed step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[3:22:50 PM] [semantic-release] › ✖  An error occurred while running semantic-release: { Error: package.json repository.url does not match github.com pattern
    at AggregateError.errors.map.error (/Users/alebianco/Desktop/alebianco.github.io/node_modules/aggregate-error/index.js:23:11)
    at Array.map (<anonymous>)
    at new AggregateError (/Users/alebianco/Desktop/alebianco.github.io/node_modules/aggregate-error/index.js:13:24)
    at Object.<anonymous> (/Users/alebianco/Desktop/alebianco.github.io/node_modules/@qiwi/semantic-release-gh-pages-plugin/lib/es5/index.js:20:19)
    at step (/Users/alebianco/Desktop/alebianco.github.io/node_modules/tslib/tslib.js:133:27)
    at Object.next (/Users/alebianco/Desktop/alebianco.github.io/node_modules/tslib/tslib.js:114:57)
    at /Users/alebianco/Desktop/alebianco.github.io/node_modules/tslib/tslib.js:107:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/Users/alebianco/Desktop/alebianco.github.io/node_modules/tslib/tslib.js:103:16)
    at exports.verifyConditions (/Users/alebianco/Desktop/alebianco.github.io/node_modules/@qiwi/semantic-release-gh-pages-plugin/lib/es5/index.js:10:78) pluginName: '@qiwi/semantic-release-gh-pages-plugin' }

Doen't work properly with CircleCI (?)

git pull invokes unhandled ssh prompt.

Build log:

[7:52:58 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  Publishing docs via gh-pages
The authenticity of host 'github.com (192.30.253.112)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)? Too long with no output (exceeded 10m0s)

Relates:

An in-range update of @types/lodash is breaking the build 🚨

The devDependency @types/lodash was updated from 4.14.140 to 4.14.141.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v15.13.21

15.13.21 (2019-08-12)

Bug Fixes

  • package: update hosted-git-info to version 3.0.0 (391af98)
Commits

The new version differs by 3 commits.

  • 391af98 fix(package): update hosted-git-info to version 3.0.0
  • d45d8b6 docs: fix typo
  • 519df0d chore: remove commitizen from our dependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Update gh-pages local branch before the next push

This case is typical for monorepos.
https://travis-ci.com/qiwi/substrate/builds/148375328

[1:19:15 PM] [@qiwi/substrate-std] [@qiwi/semantic-release-gh-pages-plugin] › ✖  Publish docs failure ProcessError: To https://github.com/qiwi/substrate.git
 ! [rejected]        gh-pages -> gh-pages (fetch first)
error: failed to push some refs to 'https://[secure]@github.com/qiwi/substrate.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
    at ChildProcess.<anonymous> (/home/travis/build/qiwi/substrate/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (events.js:223:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 1,
  message: 'To https://github.com/qiwi/substrate.git\n'

Assert `docs` directory existence on `verifyConditions` step

[12:02:03 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  Publishing docs via gh-pages
[12:02:03 PM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ✖  Publish docs failure { Error: ENOENT: no such file or directory, stat 'docs'
    at Object.statSync (fs.js:855:3)
    at Object.statSync (/home/travis/build/qiwi/semantic-release-gh-pages-plugin/node_modules/graceful-fs/polyfills.js:302:16)
    at Object.publish (/home/travis/build/qiwi/semantic-release-gh-pages-plugin/node_modules/gh-pages/lib/index.js:71:13)

pullTags causes issues when currently checked out on a different branch other than master

Problem

I'm using this plugin with my main GitHub page. The main GitHub page requires that the distribution is on master and thus I have to store the codebase on a different branch.

Now while I can choose the target branch, I cannot choose the source branch. Especially when using this in GitHub actions where the current branch is already checked out, the pullTags promise then fails with the following error:

  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: 'From https://github.com/HeshamMeneisi/heshammeneisi.github.io\n' +
    ' * branch            HEAD       -> FETCH_HEAD\n' +
    'fatal: refusing to merge unrelated histories',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}
(node:2838) UnhandledPromiseRejectionWarning: TypeError: (s || "").replace is not a function
    at escapeData (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/command.js:66:10)
    at Command.toString (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/command.js:60:35)
    at issueCommand (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/command.js:23:30)
    at Object.issue (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/command.js:27:5)
    at error (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/core.js:127:15)
    at setFailed (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/@actions/core/lib/core.js:101:5)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:2838) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2838) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero

This makes sense as the master branch containing the distribution and the current branch (codebase - FETCH_HEAD) are completely unrelated.

Proposed Solution

currentBranch option that defaults to master.

So instead of executing git pull --tags {{repo}} we would execute git pull --tags {{repo}} {{currentBranch}}

pullBranch option that defaults to true (to avoid redundant actions when already checked out in GitHub actions without breaking current behaviour)

`publish` step should return an object as a result

The `publish` plugins must return an `Object`.\n\nThe `publish` function of the `@qiwi/semantic-release-gh-pages-plugin` returned `OK` instead.\n\nWe recommend to report the issue to the `@qiwi/semantic-release-gh-pages-plugin` authors, providing the following informations:\n- The **semantic-release** version: `15.13.3`\n- The **semantic-release** logs from your CI job\n- The value returned by the plugin: `OK`\n- A link to the **semantic-release** plugin developer guide: [https://github.com/semantic-release/semantic-release/blob/master/docs/developer-guide/plugin.md](https://github.com/semantic-release/semantic-release/blob/master/docs/developer-guide/plugin.md)

Authentication failure when using GitHub App token

Issue type

  • bug report
  • idea
  • question
  • other

Expected behavior

Not sure if this is a bug or feature request, but the plugin currently doesn't work with a GitHub App token.

Actual behavior

See GitHub actions logs: https://github.com/zeshuaro/appainter/actions/runs/7516650742/job/20462200224

Error
[3:49:11 AM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ✘  Publish docs failure ProcessError: remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/zeshuaro/appainter.git/'

    at ChildProcess.<anonymous> (/home/runner/work/appainter/appainter/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 128
}
[3:49:11 AM] [semantic-release] › ✘  Failed step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[3:49:11 AM] [semantic-release] › ✘  An error occurred while running semantic-release: ProcessError: remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/zeshuaro/appainter.git/'

    at ChildProcess.<anonymous> (/home/runner/work/appainter/appainter/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 128,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}
ProcessError: remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/zeshuaro/appainter.git/'

    at ChildProcess.<anonymous> (/home/runner/work/appainter/appainter/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 128,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}
  • I've read the docs. This case is not mentioned
  • Similar issue does not exist

Steps to reproduce

  1. Create a GitHub App and install onto a repository
  2. Use the github-app-token action to create a GitHub App token
  3. Set the app token as the GITHUB_TOKEN environment variable
  4. Run semantic release

GitHub Actions config: https://github.com/zeshuaro/appainter/actions/runs/7516650742/workflow#L277-L319
Semantic release config: https://github.com/zeshuaro/appainter/blob/main/publish.release.config.js

Specifications

  • version: 5.2.12
  • platform:
    • Operating System: Ubuntu 22.04.3 LTS
    • Environment details
      • node: v20.11.0
      • npm: 10.2.4
      • yarn: 1.22.21
  • ci: GitHub Actions

Problem setting up src-to-dst branch pairing

Issue type

  • bug report
  • idea
  • question
  • other

Expected behavior

I'm setting up the semantic-release workflow for my npm library.

I want to use the following destination branches for my gh-pages:

"branches": [
  ["main", "gh-pages"],
  ["alpha", "gh-pages-alpha"],
  ["beta", "gh-pages-beta"]
]

Actual behavior

The semantic-release-gh-pages-plugin resolves the wrong docsBranch (gh-pages),
although the ciBranch is correctly determined as alpha.

GitHub Action Log

[9:17:47 AM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2023-10-18T09:17:47.203Z semantic-release:gh-pages getRepoUrl:
2023-10-18T09:17:47.203Z semantic-release:gh-pages urlFromEnv= undefined
2023-10-18T09:17:47.203Z semantic-release:gh-pages urlFromStepOpts= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:17:47.203Z semantic-release:gh-pages urlFromOpts= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:17:47.203Z semantic-release:gh-pages urlFromPackage= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:17:47.204Z semantic-release:gh-pages resolveConfig args:
2023-10-18T09:17:47.204Z semantic-release:gh-pages pluginConfig= {"branches":[["main","gh-pages"],["alpha","gh-pages-alpha"],["beta","gh-pages-beta"]],"repositoryUrl":"https://github.some-enterprise.com/some-org/some-repo.git","tagFormat":"v${version}","_":[],"debug":true,"$0":"node_modules/.bin/semantic-release","enterprise":true}
2023-10-18T09:17:47.205Z semantic-release:gh-pages path= @qiwi/semantic-release-gh-pages-plugin
2023-10-18T09:17:47.205Z semantic-release:gh-pages step= publish
2023-10-18T09:17:47.205Z semantic-release:gh-pages ciBranch= alpha
2023-10-18T09:17:47.205Z semantic-release:gh-pages docsBranch= gh-pages
2023-10-18T09:17:47.205Z semantic-release:gh-pages pullTagsBranch= alpha
[9:17:47 AM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  verify gh-pages config
[9:17:47 AM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@qiwi/semantic-release-gh-pages-plugin"
...
[9:18:17 AM] [semantic-release] › ℹ  Start step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
2023-10-18T09:18:17.003Z semantic-release:gh-pages getRepoUrl:
2023-10-18T09:18:17.003Z semantic-release:gh-pages urlFromEnv= undefined
2023-10-18T09:18:17.004Z semantic-release:gh-pages urlFromStepOpts= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:18:17.004Z semantic-release:gh-pages urlFromOpts= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:18:17.004Z semantic-release:gh-pages urlFromPackage= https://github.some-enterprise.com/some-org/some-repo.git
2023-10-18T09:18:17.005Z semantic-release:gh-pages resolveConfig args:
2023-10-18T09:18:17.005Z semantic-release:gh-pages pluginConfig= {"branches":[["main","gh-pages"],["alpha","gh-pages-alpha"],["beta","gh-pages-beta"]],"repositoryUrl":"https://github.some-enterprise.com/some-org/some-repo.git","tagFormat":"v${version}","_":[],"debug":true,"$0":"node_modules/.bin/semantic-release","enterprise":true}
2023-10-18T09:18:17.006Z semantic-release:gh-pages path= @qiwi/semantic-release-gh-pages-plugin
2023-10-18T09:18:17.006Z semantic-release:gh-pages step= publish
2023-10-18T09:18:17.006Z semantic-release:gh-pages ciBranch= alpha
2023-10-18T09:18:17.006Z semantic-release:gh-pages docsBranch= gh-pages
2023-10-18T09:18:17.007Z semantic-release:gh-pages pullTagsBranch= alpha
[9:18:17 AM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  Publishing docs via gh-pages
[9:18:30 AM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ℹ  Docs published successfully, branch=gh-pages, src=docs, dst=.
[9:18:30 AM] [semantic-release] › ✔  Completed step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
  • I've read the docs. This case is not mentioned
  • Similar issue does not exist
  • I've searched the code. Could not figure out the reason.
  • I've forked and cloned the repo. Added a unit test, but was not able to reproduce the issue.

Steps to reproduce

.github/workflows/release.yml

name: Release

on:
  push:
    branches:
      - main
      - alpha
      - beta
  workflow_dispatch:

jobs:
  release:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        with:
          token: ${{ secrets.GH_TOKEN }}
          fetch-depth: 0

      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 16

      - name: Install dependencies
        run: npm ci

      - name: Run Semantic Release
        run: npm run semantic-release
        env:
          GH_TOKEN: ${{ secrets.GH_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package.json

{
  ...
  "scripts": {
    "semantic-release": "semantic-release",
  },
  "devDependencies": {
    "@qiwi/semantic-release-gh-pages-plugin": "^5.2.8",
    "@semantic-release/changelog": "^6.0.3",
    "@semantic-release/git": "^10.0.1",
    "semantic-release": "^19.0.5",
  },
  "release": {
    "branches": [
      "main",
      { "name": "alpha", "prerelease": true },
      { "name": "beta", "prerelease": true }
    ],
    "plugins": [
      [ "@semantic-release/commit-analyzer" ],
      [ "@semantic-release/release-notes-generator", {
          "preset": "conventionalcommits"
      }],
      [ "@semantic-release/changelog" ],
      [ "@semantic-release/npm" ],
      [ "@semantic-release/github", {
          "assets": [ "*.tgz" ]
      }],
      [ "@qiwi/semantic-release-gh-pages-plugin", {
          "branches": [
            ["main", "gh-pages"],
            ["alpha", "gh-pages-alpha"],
            ["beta", "gh-pages-beta"]
          ],
          "enterprise": true
      }],
      [ "@semantic-release/git", {
          "assets": [
            "package.json",
            "package-lock.json",
            "CHANGELOG.md"
          ]
      }]
    ]
  }
}

Specifications

CI Platform

  • Github Enterprise Server 3.8
  • Custom Linux Action Runner (Linux)
  • GITHUB_TOKEN Permissions
    • Actions: write
    • Checks: write
    • Contents: write
    • Deployments: write
    • Discussions: write
    • Issues: write
    • Metadata: read
    • Packages: write
    • Pages: write
    • PullRequests: write
    • RepositoryProjects: write
    • SecurityEvents: write
    • Statuses: write
  • git version 2.25.1
  • node: v16.20.2
  • npm: 8.1

"enterprise": "true" option seems to be ignored

Hello,

I'm trying to use this plugin to publish to a GitHub Enterprise repo.

I have my repo URL configured in the repository field in package.json, and my release config looks like this (also located in package.json):

"release": {
    "branch": "master",
    "verifyConditions": [
      "@semantic-release/github",
      "@qiwi/semantic-release-gh-pages-plugin"
    ],
    "publish": [
      {
        "path": "@semantic-release/exec",
        "cmd": "nuget pack dist/package -Version ${nextRelease.version}"
      },
      {
        "path": "@semantic-release/github",
        "assets": "*.nupkg"
      },
      {
        "path": "@qiwi/semantic-release-gh-pages-plugin",
        "enterprise": "true",
        "src": "dist/web"
      }
    ]
  },

As you can see, I've set enterprise: true in the options.

But when semantic release runs, I get the following error:

An error occurred while running semantic-release: { Error: package.json repository.url does not match github.com pattern
    at AggregateError.errors.map.error ([REDACTED]\node_modules\@qiwi\semantic-release-gh-pages-plugin\node_modules\aggregate-error\index.js:23:11)
    at Array.map (<anonymous>)
    at new AggregateError ([REDACTED]\node_modules\@qiwi\semantic-release-gh-pages-plugin\node_modules\aggregate-error\index.js:13:24)
    at [REDACTED]\node_modules\@qiwi\semantic-release-gh-pages-plugin\target\es5\index.js:23:19
    at step ([REDACTED]\node_modules\tslib\tslib.js:136:27)
    at Object.next ([REDACTED]\node_modules\tslib\tslib.js:117:57)
    at[REDACTED]\node_modules\tslib\tslib.js:110:75
    at new Promise (<anonymous>)
    at Object.__awaiter ([REDACTED]\node_modules\tslib\tslib.js:106:16)
    at Object.exports.verifyConditions [REDACTED]\node_modules\@qiwi\semantic-release-gh-pages-plugin\target\es5\index.js:13:78) pluginName: '@qiwi/semantic-release-gh-pages-plugin' }

I'm using semantic release version 15.13.24.

Any ideas what might be wrong?

remote: Invalid username or password when git pull --tags --force

This is a private repository. The log is following:

Error: Command failed with exit code 1 (EPERM): git pull --tags --force
    at makeError (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/@qiwi/semantic-release-gh-pages-plugin/node_modules/execa/lib/error.js:58:11)
    at handlePromise (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/@qiwi/semantic-release-gh-pages-plugin/node_modules/execa/index.js:112:26)
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
    at async validator (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
    at async /home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
    at async /home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/lib/plugins/pipeline.js:31:3
    at async Object.pluginsConf.<computed> [as publish] (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/lib/plugins/index.js:80:11)
    at async run (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/index.js:115:22)
    at async module.exports (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/index.js:168:22)
    at async module.exports (/home/runner/work/reacnetgenerator/reacnetgenerator/node_modules/semantic-release/cli.js:55:5) {
  command: 'git pull --tags --force',
  exitCode: 1,
  exitCodeName: 'EPERM',
  stdout: '',
  stderr: 'remote: Invalid username or password.\n' +
    "fatal: Authentication failed for 'https://github.com/***/reacnetgenerator/'",
  all: 'remote: Invalid username or password.\n' +
    "fatal: Authentication failed for 'https://github.com/***/reacnetgenerator/'",
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false,
  signal: undefined,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
##[error]Process completed with exit code 1.

Authentication failure in GitHub Page publish stage

# package.json
"release": {
  "branches": [
    "main"
  ],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    [
      "@qiwi/semantic-release-gh-pages-plugin",
      {
        "msg": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}",
        "src": "docs",
        "dst": ".",
        "branch": "docs",
        "pullTagsBranch": "",
        "dotfiles": true
      }
    ],  
    [
      "@semantic-release/github",
      {
        "assets": [
          {
            "path": "docs/**/*",
            "label": "docs bundle"
          }
        ]
      }
    ]
  ]
}

GitHub Actions error log: (unrelated parts are omitted)

[8:46:09 AM] [semantic-release] [@qiwi/semantic-release-gh-pages-plugin] › ✖  Publish docs failure ProcessError: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: Authentication failed for 'https://github.com/boxsnake/js-tutorial.git/'

    at ChildProcess.<anonymous> (/home/runner/work/js-tutorial/js-tutorial/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5) {
  code: 128
}
[8:46:09 AM] [semantic-release] › ✖  Failed step "publish" of plugin "@qiwi/semantic-release-gh-pages-plugin"
[8:46:09 AM] [semantic-release] › ✖  An error occurred while running semantic-release: ProcessError: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: Authentication failed for 'https://github.com/boxsnake/js-tutorial.git/'

    at ChildProcess.<anonymous> (/home/runner/work/js-tutorial/js-tutorial/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5) {
  code: 128,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}
ProcessError: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: Authentication failed for 'https://github.com/boxsnake/js-tutorial.git/'

    at ChildProcess.<anonymous> (/home/runner/work/js-tutorial/js-tutorial/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5) {
  code: 128,
  pluginName: '@qiwi/semantic-release-gh-pages-plugin'
}error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.