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
This can create subtle bugs in installing the CLI, since the install.sh script looks for target binaries in our latest release, and if a blank release is getting published, they won't exist. There could be a case where we have drafted full release notes, and can't publish them (without realizing) and what we're instead left with is a blank release.
The notes initially come out blank. If the release manager already had a draft in progress, it can no longer be published since there can only be 1 release for any given tag.
The desired process:
release notes are drafted from a tag
release actions build and distribute binaries
we publish the notes with the binaries when all checks have passed and we're ready to go live
The text was updated successfully, but these errors were encountered:
greyscaled
added
chore
DX, infra etc that's not build or CI related
build
Build or release related
ci
Related to CI/CD
and removed
chore
DX, infra etc that's not build or CI related
labels
Jan 10, 2024
greyscaled
changed the title
Remove automation for release being published
Remove blank gh release notes being published
Jan 11, 2024
Release notes are automatically published (public). The author is
github-actions
. We prefer drafting them from a tag and releasing them manually.Reference: (notice the author) - https://github.com/GlareDB/glaredb/releases/tag/v0.8.0
This can create subtle bugs in installing the CLI, since the
install.sh
script looks for target binaries in our latest release, and if a blank release is getting published, they won't exist. There could be a case where we have drafted full release notes, and can't publish them (without realizing) and what we're instead left with is a blank release.The notes initially come out blank. If the release manager already had a draft in progress, it can no longer be published since there can only be 1 release for any given tag.
The desired process:
The text was updated successfully, but these errors were encountered: