Publish step hanging with partial success - possible globbing issue
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 42/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 停滞
- 技術スタック
- github, javascript
- 領域
- release
調査の方向性
lib/publish.js の34行目と56行目付近で参照されている箇所から始め、次に .releaserc.yml の2つの asset 設定を比較します。'**' glob と dist/*.tgz を使って publish ステップを再現し、デバッグ出力を使って glob ステップを切り分けます。設定された glob によって publish がハングしなくなり、意図した asset で release が完了すれば完了です。
索引モデルが issue の本文から書いたものです。
説明
My issue seems very similar to this closed issue - https://github.com/semantic-release/github/issues/193 - but since that is closed and a couple of years old I figured it might not be relevant.
Even with debug logging turned on, the logs go silent after this log message - https://github.com/semantic-release/github/blob/master/lib/publish.js#L34 . The draft release is created correctly, we just never seem to make it as far as https://github.com/semantic-release/github/blob/master/lib/publish.js#L56 as we never get any additional debug logging. So it seems perhaps there is an issue with the glob step.
The complete log entries from release that are relevant to github plugin are shown below.
[3:29:08 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
' export RELEASE_VERSION="$RELEASE_VERSION"\n' +
...
2021-05-26T15:29:08.805Z semantic-release:plugins options for @semantic-release/github/verifyConditions: {
assets: [ { path: '**', label: 'distribution files' } ],
failComment: false,
successComment: false
}
...
2021-05-26T15:29:08.805Z semantic-release:plugins options for @semantic-release/github/verifyConditions: {
assets: [ { path: '**', label: 'distribution files' } ],
failComment: false,
successComment: false
}
...
[3:29:08 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
...
[3:29:08 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
2021-05-26T15:29:08.811Z semantic-release:plugins options for @semantic-release/github/success: {
assets: [ { path: '**', label: 'distribution files' } ],
failComment: false,
successComment: false
}
...
2021-05-26T15:29:08.812Z semantic-release:plugins options for @semantic-release/github/fail: {
assets: [ { path: '**', label: 'distribution files' } ],
failComment: false,
successComment: false
}
...
[3:29:08 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
...
[3:29:08 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
...
[3:29:13 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/github"
[3:29:13 PM] [semantic-release] [@semantic-release/github] › ℹ Verify GitHub authentication (https://api.github.com)
[3:29:13 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/github"
...
[3:29:20 PM] [semantic-release] › ℹ Start step "publish" of plugin "@semantic-release/github"
2021-05-26T15:29:20.072Z semantic-release:github release object: {
owner: 'onelive-dev',
repo: 'OLX',
tag_name: 'v1.5.0-cicd.3',
target_commitish: 'cicd',
name: 'v1.5.0-cicd.3',
body: '# [1.5.0-cicd.3](https://github.com/onelive-dev/OLX/compare/v1.5.0-cicd.2...v1.5.0-cicd.3) (2021-05-26)\n' +
'\n' +
'\n' +
'### Bug Fixes\n' +
'\n' +
'* **cicd:** enable semantic-release debug + force release ([d262911](https://github.com/onelive-dev/OLX/commit/d26291168b6b82d16d56eed242c12ef60871e8ce))\n' +
'\n' +
'\n' +
'\n',
prerelease: true
}
Our .releaserc.yml file is as follows
branches:
- master
# @todo enable automated release for all branches once some outstanding branches with non-compliant names are closed
# - name: '**'
# prerelease: true
- name: cicd
prerelease: true
plugins:
- '@semantic-release/commit-analyzer'
- '@semantic-release/release-notes-generator'
- '@semantic-release/changelog'
- - '@semantic-release/exec'
# This hook is run only if a release is to be made
# We create source-able file so future workflow steps can easily get to release metadata
- prepareCmd: |
RELEASE_VERSION="${nextRelease.version}"
echo "Version to be released: $RELEASE_VERSION"
cat > version.sh <<-EOF
#!/bin/bash
export RELEASE_VERSION="$RELEASE_VERSION"
export RELEASE_CHANNEL="${nextRelease.channel}"
export RELEASE_HEAD="${nextRelease.gitHead}"
export RELEASE_NOTES="${nextRelease.notes}"
export RELEASE_TAG="${nextRelease.gitTag}"
export RELEASE_TYPE="${nextRelease.type}"
EOF
- - '@semantic-release/npm'
- npmPublish: false
- - '@semantic-release/git'
- assets:
- CHANGELOG.md
- package.json
- package-lock.json
- - '@semantic-release/github'
- assets:
- path: '**'
label: distribution files
failComment: false
successComment: false
Note I am able to make releases by making npm plugin generate a tarball and explicitly using that tarball in assets config. So a config like this works.
branches:
- master
# @todo enable automated release for all branches once some outstanding branches with non-compliant names are closed
# - name: '**'
# prerelease: true
- name: cicd
prerelease: true
plugins:
- '@semantic-release/commit-analyzer'
- '@semantic-release/release-notes-generator'
- '@semantic-release/changelog'
- - '@semantic-release/exec'
# This hook is run only if a release is to be made
# We create source-able file so future workflow steps can easily get to release metadata
- prepareCmd: |
RELEASE_VERSION="${nextRelease.version}"
echo "Version to be released: $RELEASE_VERSION"
cat > version.sh <<-EOF
#!/bin/bash
export RELEASE_VERSION="$RELEASE_VERSION"
export RELEASE_CHANNEL="${nextRelease.channel}"
export RELEASE_HEAD="${nextRelease.gitHead}"
export RELEASE_NOTES="${nextRelease.notes}"
export RELEASE_TAG="${nextRelease.gitTag}"
export RELEASE_TYPE="${nextRelease.type}"
EOF
- - '@semantic-release/npm'
- npmPublish: false
tarballDir: dist
- - '@semantic-release/git'
- assets:
- CHANGELOG.md
- package.json
- package-lock.json
- - '@semantic-release/github'
- assets:
- path: dist/*.tgz
label: distribution files
- 主要言語
- JavaScript
- スター
- 535
- フォーク
- 150
- 平均マージ
- 5日 16時間
- マージ済み PR(30日)
- 11
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
semantic-release/github のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
semantic-release/github#1297 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 38/100
semantic-release/github#1242 · コメント 1 件 · リアクション 4 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
semantic-release/github#1103 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 68/100
semantic-release/github#1092 · コメント 6 件 ·
メンテナーはふだん 1 日以内に返信
-
immutable releasesオープン
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
semantic-release/github#1082 · コメント 5 件 · リアクション 2 件 ·
メンテナーはふだん 1 日以内に返信
semantic-release/github の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
keyxmakerx/Chronicle#967 ·
メンテナーはふだん 1 日以内に返信
-
good first issue hacktoberfest
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
RogueAlg0/taken#386 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
external-issue to-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
LearningCircuit/local-deep-research#7067 ·
メンテナーはふだん 1 日以内に返信