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.

Sign up for GitHub

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

Jump to bottom

Desk research on release automation #5584

Closed
1 task done
Tracked by #5580
domoscargin opened this issue Jan 7, 2025 · 0 comments
Closed
1 task done
Tracked by #5580

Desk research on release automation #5584

domoscargin opened this issue Jan 7, 2025 · 0 comments
Assignees
@owenatgov
Labels
research

Comments

@domoscargin
Copy link
Contributor

domoscargin commented Jan 7, 2025 •
edited
Loading

What

Understand how other packages handle release automation.

A couple of repositories in our space have some automation for their release:

  • govuk-prototype-kit, for which we have a breakdown of what the scripts do. There's a few interesting things around pulling PR content from the CHANGELOG (on top of publishing the package itself).
  • stylelint-config-gds, which pushes to npm when the package version changes through this GitHub action

But we might also look further afield and see how popular packages handle their releases

TIMEBOX: Probably not worth giving this more than a day

Done when

  • We have documented anything that might be helpful
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@owenatgov owenatgov

Labels
research
Projects
GOV.UK Design System cycle board
Status: Done 🏁
Milestone
No milestone
Development

No branches or pull requests
2 participants
@domoscargin @owenatgov