Skip to content

Commit

Permalink
Problem: goreleaser is using wrong Env for GitHub token (fixes crypto…
Browse files Browse the repository at this point in the history
…-org-chain#251)

Solution: updated to use github token + commented out brews, as it may need to be updated manually
before permissioning is figured out
  • Loading branch information
tomtau committed Nov 6, 2020
1 parent b45fdbb commit beaec41
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 10 deletions.
4 changes: 3 additions & 1 deletion .github/workflows/goreleaser.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,9 @@ jobs:
- name: release dry run
run: make release-dry-run
- name: setup release environment
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |-
echo 'GITHUB_TOKEN=${{secrets.GORELEASER_ACCESS_TOKEN}}' > .release-env
echo 'GITHUB_TOKEN=${{secrets.GITHUB_TOKEN}}' > .release-env
- name: release publish
run: make release
18 changes: 9 additions & 9 deletions .goreleaser.yml
Original file line number Diff line number Diff line change
Expand Up @@ -74,12 +74,12 @@ changelog:
snapshot:
name_template: "{{ .Tag }}-next"

brews:
- name: "chain-maind"
description: "chain-main daemon"
homepage: "https://github.com/crypto-com/chain-main"
github:
owner: "crypto-com"
name: "homebrew-chain-maind"
install: |
bin.install "chain-maind"
# brews:
# - name: "chain-maind"
# description: "chain-main daemon"
# homepage: "https://github.com/crypto-com/chain-main"
# github:
# owner: "crypto-com"
# name: "homebrew-chain-maind"
# install: |
# bin.install "chain-maind"

0 comments on commit beaec41

Please sign in to comment.