Skip to content

Add config to control whether GitHub releases are marked as latest - #8

Open
tnaroska wants to merge 1 commit into
PackagrIO:masterfrom
tnaroska:feature/github-release-make-latest-config
Open

tnaroska wants to merge 1 commit into
PackagrIO:masterfrom
tnaroska:feature/github-release-make-latest-config

Conversation

@tnaroska

Copy link
Copy Markdown

Summary

  • GitHub release creation always defaulted make_latest implicitly (GitHub API default is true), with no way to override it.
  • Adds PACKAGR_SCM_GITHUB_RELEASE_MAKE_LATEST config (default "true", preserving current behavior), settable via env var like the existing PACKAGR_SCM_GITHUB_* options (e.g. PACKAGR_SCM_GITHUB_ACCESS_TOKEN).
  • Accepts GitHub's own "true", "false", or "legacy" values and is passed through as MakeLatest on the github.RepositoryRelease payload.

Test plan

  • go build ./...
  • go test ./scm/... passes
  • Consumers (e.g. publishr) bump their go-common dependency to a release containing this change once merged

🤖 Generated with Claude Code

Github releases are always created with make_latest defaulting to "true".
Add PACKAGR_SCM_GITHUB_RELEASE_MAKE_LATEST (default "true", preserving
current behavior) so callers can override it via env var, matching the
existing PACKAGR_SCM_GITHUB_* configuration pattern. Accepts GitHub's own
"true"/"false"/"legacy" values.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tnaroska
tnaroska marked this pull request as ready for review August 24, 2026 19:09
@tnaroska

Copy link
Copy Markdown
Author

Hi @AnalogJ , could you take a look at this? Fairly simple change to allow github releases without marking them "latest".
CI is failing though it seems unrelated to the change. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant