refactor!: Pass release params by value and rename `EditRelease` to `UpdateRelease` by JamBalaya56562 · Pull Request #4329 · google/go-github

JamBalaya56562 · 2026-06-24T17:56:16Z

BREAKING CHANGE: CreateRelease & UpdateRelease now take RepositoryRelease by value; EditRelease is renamed to UpdateRelease.

Towards #3644.

Passes the request body of RepositoriesService.CreateRelease and RepositoriesService.UpdateRelease by value instead of by pointer, and renames EditRelease to UpdateRelease for naming consistency.

This continues the value-parameter conversion from the merged #3654, #3794 and #4320, and follows the Edit -> Update rename done for GistsService in #4320.

Changes

CreateRelease(ctx, owner, repo string, release *RepositoryRelease) -> release RepositoryRelease
EditRelease(ctx, owner, repo string, id int64, release *RepositoryRelease) -> UpdateRelease(..., release RepositoryRelease)
Removed the runtime release == nil checks, which the value signature now makes unnecessary.
No deprecated wrappers are added (clean break), consistent with the review consensus on refactor!: Refactor GistsService to use value parameters #3680/refactor!: Pass GistsService required params by value #4320.

Breaking changes

CreateRelease / UpdateRelease now take RepositoryRelease by value.
EditRelease is renamed to UpdateRelease.

The remaining body-pointer methods in repos_releases.go (EditReleaseAsset, GenerateReleaseNotes) are intentionally left for a follow-up, since they also involve allow-list and type-name changes.

Generated files are unchanged (no struct fields changed).

codecov · 2026-06-24T18:07:57Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.48%. Comparing base (642da7d) to head (419cb63).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4329      +/-   ##
==========================================
- Coverage   97.48%   97.48%   -0.01%     
==========================================
  Files         193      193              
  Lines       19400    19377      -23     
==========================================
- Hits        18912    18889      -23     
  Misses        270      270              
  Partials      218      218

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

gmlewis

Thank you, @JamBalaya56562!
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.

cc: @stevehipwell - @alexandear - @Not-Dhananjay-Mishra

alexandear

As we are making breaking changes, I propose creating separate structs for creating and updating a repository release. These structs have slightly different fields.

alexandear · 2026-06-24T21:13:55Z

-		return nil, nil, errors.New("release must be provided")
-	}
-
+func (s *RepositoriesService) CreateRelease(ctx context.Context, owner, repo string, release RepositoryRelease) (*RepositoryRelease, *Response, error) {


Suggested change

func (s *RepositoriesService) CreateRelease(ctx context.Context, owner, repo string, release RepositoryRelease) (*RepositoryRelease, *Response, error) {

func (s *RepositoriesService) CreateRelease(ctx context.Context, owner, repo string, body CreateReleaseRequest) (*RepositoryRelease, *Response, error) {

Done in 69f00c3 — added a dedicated CreateReleaseRequest and CreateRelease now takes it by value. Thanks!

alexandear · 2026-06-24T21:14:16Z

-		return nil, nil, errors.New("release must be provided")
-	}
-
+func (s *RepositoriesService) UpdateRelease(ctx context.Context, owner, repo string, id int64, release RepositoryRelease) (*RepositoryRelease, *Response, error) {


Suggested change

func (s *RepositoriesService) UpdateRelease(ctx context.Context, owner, repo string, id int64, release RepositoryRelease) (*RepositoryRelease, *Response, error) {

func (s *RepositoriesService) UpdateRelease(ctx context.Context, owner, repo string, id int64, body UpdateReleaseRequest) (*RepositoryRelease, *Response, error) {

Done — UpdateRelease now takes UpdateReleaseRequest by value. It omits GenerateReleaseNotes, since the update endpoint does not accept it.

alexandear · 2026-06-24T21:17:19Z

We can remove this after introducing CreateReleaseRequest and UpdateReleaseRequest

Removed — the internal repositoryReleaseRequest is gone now that CreateReleaseRequest/UpdateReleaseRequest carry the request fields directly and are serialized as-is.

…Release Introduce dedicated CreateReleaseRequest and UpdateReleaseRequest types for the bodies of RepositoriesService.CreateRelease and RepositoriesService.UpdateRelease, replacing the *RepositoryRelease parameter that also carried response-only fields. The new types are passed by value and serialized directly, dropping the internal repositoryReleaseRequest remap. EditRelease is renamed to UpdateRelease for naming consistency. This follows the value-parameter pattern established by the merged google#3654, google#3794 and google#4320, the Edit -> Update rename from google#4320, and the dedicated *Request body convention already used across the package (e.g. CreateHostedRunnerRequest). The runtime nil checks are removed since a value parameter makes them unnecessary. No deprecated wrappers are added (clean break). Updates google#3644.

alexandear · 2026-06-25T05:36:39Z

+		want := &CreateReleaseRequest{
 			Name:                   Ptr("v1.0"),
 			DiscussionCategoryName: Ptr("General"),
 			GenerateReleaseNotes:   Ptr(true),
 		}
 		testJSONBody(t, r, want)


Suggested change

testJSONBody(t, r, input)

alexandear · 2026-06-25T05:37:05Z

+		want := &UpdateReleaseRequest{
 			Name:                   Ptr("n"),
 			DiscussionCategoryName: Ptr("General"),
 		}
 		testJSONBody(t, r, want)


Suggested change

testJSONBody(t, r, input)

alexandear · 2026-06-25T05:38:57Z

 	DiscussionCategoryName *string `json:"discussion_category_name,omitempty"`

-	// The following fields are not used in EditRelease:
+	// The following fields are not used in UpdateRelease:


This comment is no longer needed:

Suggested change

// The following fields are not used in UpdateRelease:

alexandear · 2026-06-25T05:39:06Z

 	GenerateReleaseNotes *bool `json:"generate_release_notes,omitempty"`

-	// The following fields are not used in CreateRelease or EditRelease:
+	// The following fields are not used in CreateRelease or UpdateRelease:


This comment is no longer needed:

Suggested change

// The following fields are not used in CreateRelease or UpdateRelease:

alexandear · 2026-06-25T05:39:50Z

-	Prerelease             *bool   `json:"prerelease,omitempty"`
+// CreateReleaseRequest represents a request to create a release in a repository.
+type CreateReleaseRequest struct {
+	TagName         *string `json:"tag_name,omitempty"`


Suggested change

TagName *string `json:"tag_name,omitempty"`

TagName string `json:"tag_name"`

alexandear · 2026-06-25T05:43:05Z

 	client, mux, _ := setup(t)

-	input := &RepositoryRelease{
+	input := CreateReleaseRequest{


Please fill required TagName.

JamBalaya56562 added a commit to JamBalaya56562/go-github that referenced this pull request Jun 24, 2026

docs: Add google#4329 (release value-param refactor for google#3644)

6fb6ff1

gmlewis added NeedsReview PR is awaiting a review before merging. Breaking API Change PR will require a bump to the major version num in next release. Look here to see the change(s). labels Jun 24, 2026

gmlewis changed the title ~~refactor!: Pass release params by value and rename EditRelease to UpdateRelease~~ refactor!: Pass release params by value and rename EditRelease to UpdateRelease Jun 24, 2026

gmlewis approved these changes Jun 24, 2026

View reviewed changes

alexandear suggested changes Jun 24, 2026

View reviewed changes

alexandear reviewed Jun 24, 2026

View reviewed changes

JamBalaya56562 force-pushed the refactor/3644-release-value-params branch from 3d68e64 to 69f00c3 Compare June 25, 2026 02:03

JamBalaya56562 force-pushed the refactor/3644-release-value-params branch from 69f00c3 to 419cb63 Compare June 25, 2026 02:06

JamBalaya56562 requested a review from alexandear June 25, 2026 02:07

alexandear reviewed Jun 25, 2026

View reviewed changes

	func (s RepositoriesService) CreateRelease(ctx context.Context, owner, repo string, release RepositoryRelease) (RepositoryRelease, *Response, error) {
	func (s RepositoriesService) CreateRelease(ctx context.Context, owner, repo string, body CreateReleaseRequest) (RepositoryRelease, *Response, error) {

	func (s RepositoriesService) UpdateRelease(ctx context.Context, owner, repo string, id int64, release RepositoryRelease) (RepositoryRelease, *Response, error) {
	func (s RepositoriesService) UpdateRelease(ctx context.Context, owner, repo string, id int64, body UpdateReleaseRequest) (RepositoryRelease, *Response, error) {

	TagName *string `json:"tag_name,omitempty"`
	TagName string `json:"tag_name"`

Uh oh!

Conversation

JamBalaya56562 commented Jun 24, 2026 • edited by gmlewis Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Breaking changes

Uh oh!

codecov Bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

gmlewis left a comment

Choose a reason for hiding this comment

Uh oh!

alexandear left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

JamBalaya56562 commented Jun 24, 2026 •

edited by gmlewis

Loading

codecov Bot commented Jun 24, 2026 •

edited

Loading