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

tooling: release automation #118

Open
LukeWinikates opened this issue Oct 27, 2022 · 3 comments
Open

tooling: release automation #118

LukeWinikates opened this issue Oct 27, 2022 · 3 comments
Labels

Comments

@LukeWinikates
Copy link
Contributor

Releasing a new SDK version has an 18-step process. It seems as though this could be simplified a bit using make recipes, or a possibly using a tool like goreleaser.

@LukeWinikates LukeWinikates changed the title tooling request: automate release steps using goreleaser or a Makefile target tooling: release automation Aug 31, 2023
@LukeWinikates
Copy link
Contributor Author

  • update RELEASING.md to reflect new steps we're introducing for the OSS license process
  • where possible, create make targets for the steps in RELEASING.md
  • see if we can make the tagging steps a bit less cumbersome
  • look into whether drafting the release using the github UI is the best approach - the auto-generated release notes have been a great starting point for previous release notes
  • look into whether letting the github UI create the tag for us is the best approach

@LukeWinikates
Copy link
Contributor Author

  • maybe we can make tool that suggests the next release version string for us

@LukeWinikates
Copy link
Contributor Author

  • maybe we can do something automated with OSM tooling to create a PR to update the open_source_licenses.txt file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant