Skip to content

feat[build]: Rearchitect release workflow #1835

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
Open
tmccombs wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat[build]: Rearchitect release workflow #1835

tmccombs wants to merge 1 commit into from
+67 −38

Conversation

@tmccombs
Copy link
Collaborator

@tmccombs tmccombs commented Nov 10, 2025

This makes the following changes:

  • Creates a new "release" workflow that re-uses the CIDCD workflow for build steps. This allows us to avoid having to check if it is a release in several steps.
  • Remove dependency on third party action for release, and uses the gh command directly.
  • Automatically generates release notes from the changelog.
tmccombs
tmccombs commented Nov 10, 2025
View reviewed changes
.github/workflows/release.yml
awk '/^# / { if (p) { exit }; p=1; next } p' CHANGELOG.md > notes.md
- name: Publish Release
run: |
gh release create --notes-file notes.md \
Copy link
Collaborator Author

@tmccombs tmccombs Nov 10, 2025

Choose a reason for hiding this comment

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

Would it be worth releasing as a draft, and having the releaser manually publish the release after making sure it looks good?
@tmccombs
feat[build]: Rearchitect release workflow
1b36431 
This makes the following changes:

- Creates a new "release" workflow that re-uses the CIDCD workflow for
  build steps. This allows us to avoid having to check if it is a
  release in several steps.
- Remove dependency on third party action for release, and uses the `gh`
  command directly.
- Automatically generates release notes from the changelog.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant

@tmccombs