Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Schema Inaccuracy] Boolean default value for string-type `make_latest` parameter in `repos/update-release`

Open
  • Is something wrong?
#5,858 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
json, openapi
Domain
api

Research direction

Inspect descriptions/api.github.com/api.github.com.json at the PATCH schema for /repos/{owner}/{repo}/releases/{release_id}; use the provided jq command to confirm the make_latest definition. Compare it with the POST create-release schema, then verify that the update-release schema uses the same string default and rerun both jq checks.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

The repos/update-release operation has a boolean default value for a string-type field. The make_latest parameter is defined as type: "string" with enum ["true", "false", "legacy"], but has default: true (boolean) instead of default: "true" (string).

This is inconsistent with the repos/create-release operation which correctly uses the string default "true".

Expected

{
  "make_latest": {
    "type": "string",
    "enum": ["true", "false", "legacy"],
    "default": "true"
  }
}

Reproduction Steps

jq '.paths["/repos/{owner}/{repo}/releases/{release_id}"].patch.requestBody.content["application/json"].schema.properties.make_latest' descriptions/api.github.com/api.github.com.json

Shows "default": true (boolean) instead of "default": "true" (string).

Compare with the correct version:

jq '.paths["/repos/{owner}/{repo}/releases"].post.requestBody.content["application/json"].schema.properties.make_latest' descriptions/api.github.com/api.github.com.json

Shows "default": "true" (string).

Dominant language
No language data
Stars
1.6k
Forks
345
Avg merge
6h
Merged PRs (30d)
82

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.