Mark new releases as pre-release and suppress auto-latest promotion#23754
Mark new releases as pre-release and suppress auto-latest promotion#23754
Conversation
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/ae85a74a-aacb-47c9-a406-fb7d895863c7 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the automated release workflow to prevent newly created releases from being promoted to “Latest” by default, requiring maintainers to explicitly promote a release when appropriate.
Changes:
- Add
--prereleaseto automatedgh release createcalls so releases are created as pre-releases by default. - Add
--latest=falseto suppress automatic “latest release” promotion. - Recompile the generated workflow lockfile to reflect the template change.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/release.md | Updates the gh release create invocation to create pre-releases and avoid latest promotion. |
| .github/workflows/release.lock.yml | Regenerates the locked workflow, carrying the updated gh release create flags through to the runnable workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Create release with binaries (SBOM files will be added later) | ||
| gh release create "$RELEASE_TAG" \ | ||
| dist/* \ | ||
| --title "$RELEASE_TAG" \ | ||
| --generate-notes | ||
| --generate-notes \ | ||
| --prerelease \ | ||
| --latest=false |
There was a problem hiding this comment.
The workflow relies on the GitHub-hosted runner’s preinstalled gh CLI, but gh release create --latest=false requires a gh version that supports the --latest flag for releases. To avoid the release job breaking if the runner image lags/changes, pin/install a known compatible gh version (or add an explicit version check/fallback) before invoking gh release create.
| # Create release with binaries (SBOM files will be added later) | ||
| gh release create "$RELEASE_TAG" \ | ||
| dist/* \ | ||
| --title "$RELEASE_TAG" \ | ||
| --generate-notes | ||
| --generate-notes \ | ||
| --prerelease \ | ||
| --latest=false |
There was a problem hiding this comment.
gh release create --latest=false depends on a gh CLI version that includes the --latest option; since the workflow doesn’t pin/install gh, this can fail if the runner image’s gh version changes. Consider pinning/installing a specific gh version (or validating gh --version) before creating the release.
New releases were automatically marked as the latest release, requiring manual intervention to revert. Releases should be pre-release by default; a maintainer explicitly promotes one to latest.
Changes
release.md: Added--prereleaseand--latest=falsetogh release create, so every automated release is created as a pre-release without becoming the latest.release.lock.yml: Recompiled to reflect the above change.