Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🛠 Repo: Automate releases #5159

Closed
5 tasks done
voxpelli opened this issue Jun 17, 2024 · 1 comment · Fixed by #5186
Closed
5 tasks done

🛠 Repo: Automate releases #5159

voxpelli opened this issue Jun 17, 2024 · 1 comment · Fixed by #5186
Assignees
Labels
area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue

Comments

@voxpelli
Copy link
Member

Tooling Suggestion Checklist

Overview

We should automate the releases of Mocha.

Why?

  • Lowers the threshold for releases
  • Minimizes human errors
  • Attestation of releases package

We could eg. do something similar to what I did in: neostandard/neostandard@c9d4425

Additional Info

The (granular) access token should be owned by a bot account. I wonder if eg. the OpenJSF account could do this?

@voxpelli voxpelli added area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue labels Jun 17, 2024
@JoshuaKGoldberg
Copy link
Member

+1 from me on this. It's definitely something we should do as a team (as opposed to an external contributor).

@voxpelli voxpelli self-assigned this Aug 1, 2024
voxpelli added a commit that referenced this issue Aug 5, 2024
@voxpelli voxpelli linked a pull request Aug 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue
Projects
Development

Successfully merging a pull request may close this issue.

2 participants