Skip to content

[CLD-127]: ci: setup go releaser#3

Merged
graham-chainlink merged 1 commit intomainfrom
ggoh/cld-127/setup-changesets
Apr 14, 2025
Merged

[CLD-127]: ci: setup go releaser#3
graham-chainlink merged 1 commit intomainfrom
ggoh/cld-127/setup-changesets

Conversation

@graham-chainlink
Copy link
Collaborator

  • Add push tag workflow
  • setup goreleaser config
  • npm commands to running changeset release

JIRA: https://smartcontract-it.atlassian.net/browse/CLD-127

@graham-chainlink graham-chainlink requested a review from a team as a code owner April 14, 2025 04:12
@changeset-bot
Copy link

changeset-bot bot commented Apr 14, 2025

⚠️ No Changeset found

Latest commit: 9cb2ef7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Comment on lines 9 to 32
ci-lint:
name: Lint
runs-on: ubuntu-latest
permissions:
id-token: write
contents: read
actions: read
steps:
- name: Linting Go
uses: smartcontractkit/.github/actions/ci-lint-go@eeb76b5870e3c17856d5a60fd064a053c023b5f5 # ci-lint-go@1.0.0
with:
golangci-lint-version: v2.0.2
# Override the lint args because the detault ones are not compatible with golangci-lint v2
golangci-lint-args: --output.checkstyle.path=golangci-lint-report.xml

ci-test:
runs-on: ubuntu-latest
permissions:
id-token: write
contents: read
actions: read
steps:
- name: ci-test
uses: smartcontractkit/.github/actions/ci-test-go@eeb76b5870e3c17856d5a60fd064a053c023b5f5 # ci-test-go@1.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we actually need this to run on release?

Since it's not a needs on the publish, they are just running and are not a blocker for a release

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh nice pick up, i copied this from MCMS, but i think you are right, the changesets raise a PR before pushing a tag, that PR will have all the required ci checks so we dont have to duplicate here again.

Removing it.

@graham-chainlink graham-chainlink force-pushed the ggoh/cld-127/setup-changesets branch from ee665d5 to 5865871 Compare April 14, 2025 07:36
- Add push tag workflow
- setup goreleaser config
- npm commands to running changeset release
@graham-chainlink graham-chainlink force-pushed the ggoh/cld-127/setup-changesets branch from 5865871 to 9cb2ef7 Compare April 14, 2025 07:43
@graham-chainlink graham-chainlink added this pull request to the merge queue Apr 14, 2025
Merged via the queue into main with commit 0c79d41 Apr 14, 2025
5 checks passed
@graham-chainlink graham-chainlink deleted the ggoh/cld-127/setup-changesets branch April 14, 2025 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants