@kungfu-tech/buildchain 2.4.11-alpha.0 → 2.4.11-alpha.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -58,12 +58,20 @@ permissions:
|
|
|
58
58
|
issues: write
|
|
59
59
|
|
|
60
60
|
steps:
|
|
61
|
+
- uses: actions/create-github-app-token@v2
|
|
62
|
+
id: buildchain-issue-token
|
|
63
|
+
with:
|
|
64
|
+
app-id: ${{ secrets.BUILDCHAIN_ISSUE_APP_ID }}
|
|
65
|
+
private-key: ${{ secrets.BUILDCHAIN_ISSUE_APP_PRIVATE_KEY }}
|
|
66
|
+
owner: kungfu-systems
|
|
67
|
+
repositories: buildchain
|
|
68
|
+
|
|
61
69
|
- uses: kungfu-systems/buildchain/actions/report-buildchain-issue@v2
|
|
62
70
|
if: failure()
|
|
63
71
|
with:
|
|
64
|
-
token: ${{ github.token }}
|
|
72
|
+
token: ${{ steps.buildchain-issue-token.outputs.token || secrets.BUILDCHAIN_ISSUE_TOKEN || secrets.BUILDCHAIN_PROMOTION_TOKEN || github.token }}
|
|
65
73
|
report-kind: workflow-friction
|
|
66
|
-
target-repository:
|
|
74
|
+
target-repository: kungfu-systems/buildchain
|
|
67
75
|
repository: ${{ github.repository }}
|
|
68
76
|
workflow: ${{ github.workflow }}
|
|
69
77
|
run-id: ${{ github.run_id }}
|
|
@@ -390,6 +390,9 @@ set is missing or ambiguous.
|
|
|
390
390
|
jobs:
|
|
391
391
|
promote:
|
|
392
392
|
uses: kungfu-systems/buildchain/.github/workflows/release-candidate-promote.yml@v2
|
|
393
|
+
secrets:
|
|
394
|
+
buildchain-issue-app-id: ${{ secrets.BUILDCHAIN_ISSUE_APP_ID }}
|
|
395
|
+
buildchain-issue-app-private-key: ${{ secrets.BUILDCHAIN_ISSUE_APP_PRIVATE_KEY }}
|
|
393
396
|
with:
|
|
394
397
|
channel: alpha
|
|
395
398
|
target-ref: alpha/v22/v22.22
|
|
@@ -410,6 +413,16 @@ jobs:
|
|
|
410
413
|
release-passport-product-name: Libnode
|
|
411
414
|
```
|
|
412
415
|
|
|
416
|
+
`buildchain-issue-app-id` and `buildchain-issue-app-private-key` are optional
|
|
417
|
+
but recommended for cross-repository consumers. They should identify a GitHub
|
|
418
|
+
App installation with `issues: write` on `kungfu-systems/buildchain`; the
|
|
419
|
+
wrapper mints the installation token before calling
|
|
420
|
+
`actions/report-buildchain-issue`. Consumers can also pass a pre-minted
|
|
421
|
+
`buildchain-issue-token`. If both are omitted, the wrapper falls back to
|
|
422
|
+
`BUILDCHAIN_ISSUE_TOKEN`, `BUILDCHAIN_PROMOTION_TOKEN`, and then the consumer
|
|
423
|
+
workflow's `github.token`; the last fallback can only report issues when it has
|
|
424
|
+
write access to the target Buildchain repository.
|
|
425
|
+
|
|
413
426
|
`publish-required-artifacts-json` can still be passed explicitly for custom
|
|
414
427
|
publish targets. For the default `publish-artifact-kind: npm` path, consumers do
|
|
415
428
|
not download artifacts or run repository scripts to build publish evidence. The
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kungfu-tech/buildchain",
|
|
3
|
-
"version": "2.4.11-alpha.
|
|
3
|
+
"version": "2.4.11-alpha.2",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Buildchain Release Passport, release governance, CLI toolkit, and site facts.",
|
|
6
6
|
"repository": "https://github.com/kungfu-systems/buildchain",
|