Skip to content

ci: automate releases#53

Open
matejchalk wants to merge 2 commits into
mainfrom
automate-releases
Open

ci: automate releases#53
matejchalk wants to merge 2 commits into
mainfrom
automate-releases

Conversation

@matejchalk
Copy link
Copy Markdown
Contributor

@matejchalk matejchalk commented May 11, 2026

Will hopefully close #48. Needs to be tested after merging. 🤞

I've replicated the releases setup from code-pushup/cli.

  • Copy/pasted release.yml and publish.yml with only minor changes.
    • Used the latest actions/* versions. For create-github-app-token, this required switching from the deprecated app-id to a client-id.
    • Omitted NX_CLOUD_ACCESS_TOKEN, since this repo doesn't use Nx Cloud for now.
    • Minimized release.yml permissions as per CodeQL warning.
  • Connected GitHub Actions as a trusted publisher for both packages on npmjs.com, disabled tokens.
    image
  • In GitHub repo settings:
    • Added repository variable and secret for the Code PushUp bot GitHub App.
      image
      image
    • Created a ruleset to allow the Code PushUp bot to push to main.
      image
    • Created a release environment.
      image

Comment thread .github/workflows/release.yml Fixed
@matejchalk matejchalk self-assigned this May 11, 2026
@matejchalk matejchalk added 🦾 CI/CD continuous integration and deployment 🧹 maintenance This doesn't seem right 🧩 eslint-config 🧩 create-eslint-config labels May 11, 2026
@matejchalk matejchalk requested review from hanna-skryl and vmasek May 11, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🦾 CI/CD continuous integration and deployment 🧩 create-eslint-config 🧩 eslint-config 🧹 maintenance This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI/CD releases for eslint-config packages

2 participants