Skip to content

Conversation

@JoelSpeed
Copy link
Contributor

This adds configuration for goreleaser to automatically publish new releases when we publish git tags.

We have had requests for published binaries from at least one community so I think this makes sense.

Hoping to publish v0.1.0 soon 👀

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 31, 2025
Comment on lines +40 to +44
footer: >-

---

Released by [GoReleaser](https://github.com/goreleaser/goreleaser).
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a valid configuration? It looks like this is supposed to only be available in the Pro version 🫠

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It came by default, so I assume it's allowed?

filters:
exclude:
- "^docs:"
- "^test:"
Copy link
Contributor

Choose a reason for hiding this comment

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

Out of scope for this PR, but this makes me think we should probably start enforcing a commit formatting convention so we can more reliably remove things we think aren't applicable to include in the changelogs.

Probably also just good hygiene anyways 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I'll check what others are doing in this regard, I think CAPI/controller-runtime both have a fairly reasonable pattern

version: "~> v2"
args: release --clean
env:
GITHUB_TOKEN: ${{ secrets.GH_PAT }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I hope you aren't using a personal access token to your github account like this signals.

AFAIK, the general convention is to use ${{ secrets.GITHUB_TOKEN }} and then toggle on the read/write permissions in the repository "Actions" settings so that the token is limited to the surface area of the repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants