You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: allow building from prepare-release without adding git hash suffix
Gradually trying to work out a reasonable release workflow. Something
like:
- Update version number etc on branch "prepare-release"
- Trigger release workflow: This generates a source archive and a draft
GitHub release object. The GitHub release has a propsed tag that
comes from the version in libjsonnet.h.
- Trigger Python publish workflow: This generates Python packages,
then waits for approval before publishing to PyPI.
- Fill in release notes in GitHub. Do any last minute checks.
Consider actually downloading the release artifacts and checking
them locally.
- Approve the Python publish workflow.
- Publish the GitHub release (which will create the version tag)
- Fast-forward master to the new version.
It's a little ugly, but the benefits here are:
- All the final build artifacts are generated before any publishing
so they can be checked (manually or otherwise).
- Release notes can be edited in GitHub.
- The tag is created at publish time.
0 commit comments