{"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTypeScript reuses SourceFile objects between old and new programs, so untagging the old program also untags shared files in the new program. Re-apply shim tags on the new program to prevent getSemanticDiagnostics() crashes with TS 5.5+.\n\n(cherry picked from commit ae0ec7315c6fbc45ce40581a08a8243a008a91ec)", "completion": "fix(compiler-cli): re-tag SourceFiles after TsCreateProgramDriver.updateFiles()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTypeScript reuses SourceFile objects between old and new programs, so untagging the old program also untags shared files in the new program. Re-apply shim tags on the new program to prevent getSemanticDiagnostics() crashes with TS 5.5+.", "completion": "fix(compiler-cli): re-tag SourceFiles after TsCreateProgramDriver.updateFiles()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe -text option of the rsa app was not exercised by any test. Add a\nsubtest that prints both a private and a public key in text form and,\nafter stripping the colon-separated hex formatting, verifies the printed\nmodulus and private exponent match the committed testrsa.pem keypair\nrather than merely checking that the labels are present.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Paul Dale \n(Merged from https://github.com/openssl/openssl/pull/31950)", "completion": "apps: test rsa -text option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe -encopt option of the pkey app was not exercised by any test; the\nexisting ML-DSA codec tests only used genpkey -encopt and pkey with\n-provparam. Re-encode the seed-priv key into each supported PKCS#8\noutput format via 'pkey -encopt output_formats:
' and check the\nresult matches the reference for that form. A control compares against\nthe default (no -encopt) encoding so the match is attributed to -encopt\nrather than the default behaviour.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Daniel Kubec \nReviewed-by: Tim Hudson \nMergeDate: Fri Jul 17 08:51:40 2026\n(Merged from https://github.com/openssl/openssl/pull/31951)", "completion": "apps: test pkey -encopt option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: axios\nChanges:\nUpdated sponsorship link and added information about JBO Thailand.", "completion": "docs: update sponsors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe tests addded in commit d8a7e8e uncovered an odd error case.\n\nhttps://github.com/openssl/openssl/actions/runs/29303845665/job/86993085732\n\nIs failing when attempting to read in a der file converting from a\ncorresponding PEM file containing DSA parameters.\n\nInterestingly The problem was only occuring when:\n1) The input was a DER file\nand\n2) Blake2 was not configured\n\nDoing some tracing of the decoder operation showed that this is occuring\nbecause the OSSL_STORE lookup used to find the proper decoder uses a\n\"first successful decode wins\" approach, after which the loading code\nchecks to see if the decoded type matches the expected key type.\n\nWhen decoding PEM, this isn't a problem, as the PEM armoring gives the\ndecoder a hint as to why type of data the input file is.\n\nBut with DER, there is no such hint, and we're at the mercy of whichever\ndecoder happens to decode the data correctly first. Normally it works\njust fine, but when features are disabled or enabled, the order in which\nthe decoders are attempted may change, affecting the outcome. In this\nparticular case, disabling blake2 caused the DHX decoder to be attempted\nfirst, which decodes the input der file without issue. That in turn\ncaused the subsequent EVP_PKEY_is_a check to fail (as we were expecting\na DSA key), and so the test fails.\n\nFortunately, the code that the dsaparam applet uses to do this decode\nprovides a keytype hint, which we can use to guide the decode process.\nkeep the old store lookup method around in case anyone doesn't pass a\nuri that is a file path or provide a keytype, but if we do both those\nthings, we can use OSSL_DECODER_CTX_new_for_pkey to specifically tell\nthe decoder that we want to decode the input data as the expected type\n(in this case a DSA key).\n\nFixes #31944\n\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Tim Hudson \nMergeDate: Thu Jul 16 15:28:32 2026\n(Merged from https://github.com/openssl/openssl", "completion": "Fix dsaparams decoding from DER files"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe -text option was not exercised for the ec or ecparam apps. Add a\nsubtest to 15-test_ec.t that prints a private and a public EC key and,\nafter stripping the colon-separated hex formatting, verifies the printed\nprivate and public values match the committed testec-p256.pem keypair as\nwell as the curve identification. Add a subtest to 15-test_ecparam.t\nthat prints named and explicit parameters, checking the named form emits\nthe expected curve OID and NIST name while the explicit form emits the\nfield parameters and no OID.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Daniel Kubec \nReviewed-by: Tim Hudson \nMergeDate: Fri Jul 17 08:47:12 2026\n(Merged from https://github.com/openssl/openssl/pull/31952)", "completion": "apps: test ec and ecparam -text options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso:\n- curlx: pass this flag to the actual conversion calls, for consistency\n and robustness. (It's not stricly necessary because the initial call\n to determine size, with this flag passed, fails already on bad input.)\n- schannel: unfold `MultiByteToWideChar()` line (formatting).\n\nRef: https://learn.microsoft.com/windows/win32/api/stringapiset/nf-stringapiset-multibytetowidechar\n\nFollow-up to 6694a42aa0e820a6fe1e59d85ff8597b6d768d8d #19798\n\nCloses #22326", "completion": "idn: restore `MultiByteToWideChar()` `MB_ERR_INVALID_CHARS` flag"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe -peerform option of the pkeyutl app was not exercised by any test.\nExtend the -derive peer key subtest to convert the peer public key to\nDER and derive against it with -peerform DER, checking the shared secret\nmatches the one derived from the PEM peer key, and that reading the DER\npeer key as PEM fails.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:10:00 2026\n(Merged from https://github.com/openssl/openssl/pull/31953)", "completion": "apps: test pkeyutl -peerform option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMirrors file_modsqrt() in test/bntest.c. Both square roots are\naccepted for positive cases (ret and p - ret), since a square root has\ntwo roots.\n\nThe operand a is reduced into [0, p) with BN_nnmod() at the boundary\nbefore being handed to OSSL_FN_mod_sqrt(): BN_mod_sqrt() does that\nreduction internally, but OSSL_FN_mod_sqrt() is unsigned and sees only\nthe magnitude, so feeding a raw negative a (e.g. a = -5, p = 7, which\nreduces to 2) would present the wrong residue.\n\nRelated-to: doc/designs/fixed-size-large-numbers.md\nIssue: https://github.com/openssl/project/issues/2026\nAssisted-by: Pi:z-ai/glm-5.2\nSigned-off-by: Richard Levitte \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Igor Ustinov \nReviewed-by: Matt Caswell \nMergeDate: Fri Jul 31 09:39:06 2026\n(Merged from https://github.com/openssl/openssl/pull/31963)", "completion": "OSSL_FN: Add ModSqrt stanza test in fntest"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWithout it, compilers can figure out the possible values and optimize\nbased on it.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:46 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)\n\n(cherry picked from commit f8c26111bab30399d0c9262269089639ff8e4746)", "completion": "Add value_barrier in MOD_EXP_CTIME_COPY_FROM_PREBUF"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWithout it, compilers can figure out the possible values and optimize\nbased on it.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:46 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)", "completion": "Add value_barrier in MOD_EXP_CTIME_COPY_FROM_PREBUF"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReading an unencrypted PKCS#8 (PrivateKeyInfo) in PEM form with -nocrypt\nwas not exercised by any test; the existing round-trip test only read the\nDER form via -inform DER, hitting d2i_PKCS8_PRIV_KEY_INFO_bio(). The PEM\nbranch in apps/pkcs8.c (the informat == FORMAT_PEM || FORMAT_UNDEF case\ncalling PEM_read_bio_PKCS8_PRIV_KEY_INFO()) was left uncovered.\n\nAdd a subtest that writes an unencrypted PKCS#8 PEM and reads it back\nwith -nocrypt from PEM, exercising PEM_read_bio_PKCS8_PRIV_KEY_INFO(),\nand checks the recovered key matches the original.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nReviewed-by: Matt Caswell \nMergeDate: Mon Jul 27 09:10:45 2026\n(Merged from https://github.com/openssl/openssl/pull/31955)", "completion": "apps: test pkcs8 -nocrypt reading a PKCS#8 PEM"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWithout it, compilers can figure out the possible values and optimize\nbased on it.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:47 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)\n\n(cherry picked from commit 1d7a8dd73ff9e0fc197611433b9b60b4b5f5465c)", "completion": "Add value_barrier in BN_consttime_swap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWithout it, compilers can figure out the possible values and optimize\nbased on it.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:47 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)", "completion": "Add value_barrier in BN_consttime_swap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe -clcerts and -cacerts certificate filtering and the -name friendly\nname option of the pkcs12 app were not exercised by any test. Add a\nsubtest that exports a PKCS#12 holding a client cert (with a localKeyID),\na CA cert and a friendly name, then checks the friendly name is present,\nthat -clcerts outputs only the client certificate and -cacerts only the\nCA certificate.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:09:09 2026\n(Merged from https://github.com/openssl/openssl/pull/31956)", "completion": "apps: test pkcs12 -clcerts/-cacerts and -name options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe cookie consent popup showed only text and two buttons. Add the\nAngie greeting pose to it so the first thing a new visitor sees carries\nthe same mascot treatment already used across the docs (the 404 page,\nempty search results, the preview error state).\n\nThe message and mascot sit in a flex header row; the two action buttons\nnow share the row equally so they fill the card instead of leaving a\ntrailing gap. Layout only, the consent behaviour is unchanged.\n\n(cherry picked from commit 6a3487f7b7b6d859cd91337fa859fbbd84d9495a)", "completion": "feat(docs-infra): greet visitors with Angie in the cookie popup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe cookie consent popup showed only text and two buttons. Add the\nAngie greeting pose to it so the first thing a new visitor sees carries\nthe same mascot treatment already used across the docs (the 404 page,\nempty search results, the preview error state).\n\nThe message and mascot sit in a flex header row; the two action buttons\nnow share the row equally so they fill the card instead of leaving a\ntrailing gap. Layout only, the consent behaviour is unchanged.", "completion": "feat(docs-infra): greet visitors with Angie in the cookie popup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nVerify in test 2093\n\nFixes #22316\nReported-by: xmoezzz on github\nCloses #22328", "completion": "tool_cb_prg: avoid integer overflows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nget_json_table_plan() parenthesized the child of a parent/child\n(OUTER/INNER) plan only when that child was a sibling (UNION/CROSS)\njoin, not when it was itself a parent/child join. A plan such as\nPLAN (p0 OUTER (p1 INNER p11)) was therefore deparsed as\nPLAN (p0 OUTER p1 INNER p11), which does not parse back to the same\nplan tree -- a dump/restore hazard. Parenthesize the child whenever it\nis not a bare path name, matching the logic already used for the\noperands of sibling joins.\n\nReported-by: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv7aZGSExnbjJRw8eKkoXbu34TdoKLLA2gPye3aHjO5OSA@mail.gmail.com", "completion": "Fix JSON_TABLE PLAN deparse to keep parentheses around nested joins"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ngenerateJsonTablePathName() produced names of the form\n\"json_table_path_N\" in the same namespace as user-supplied path and\ncolumn names, without checking whether the name was already in use.\nWhen an unnamed NESTED path's generated name happened to match a\nuser-supplied path name that a PLAN clause referenced, two sibling paths\nmatched the same plan entry and one of them, together with its columns,\nwas silently dropped from the output.\n\nBump the counter until the generated name is unused, so a generated name\ncan no longer coincide with a user-supplied one. The still-uncovered\npath is then correctly reported as not found in the plan.\n\nThe row pattern (root) path is named before the user-supplied column and\npath names are collected, so when it is left unnamed its generated name\ncould not avoid them either, and a user column or path named like a\ngenerated name, e.g.\n\n SELECT * FROM JSON_TABLE(jsonb '1', '$'\n COLUMNS (json_table_path_0 int PATH '$')) jt;\n\nwas rejected with a bogus \"duplicate JSON_TABLE column or path name\"\nerror. Collect the user-supplied names first and generate the row\npattern path's name afterwards, so that it avoids all of them. An\nexplicit root path name is still seeded into the namespace, so a column\nduplicating it is still correctly rejected.\n\nReported-by: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv7aZGSExnbjJRw8eKkoXbu34TdoKLLA2gPye3aHjO5OSA@mail.gmail.com\nDiscussion: https://postgr.es/m/CAA-aLv5U94KD4C%2BLhAPYcCeGvs1xBMngcS5oEkZHN9YWwXUHsA%40mail.gmail.com", "completion": "Make JSON_TABLE generated path names avoid collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCorrect the JSON_TABLE synopsis to place the ON ERROR clause after the\nPLAN clause, matching the grammar (the previous order could not be\ntyped). Replace a dangling reference to json_path_specification with\npath_expression, the term the synopsis actually defines. Mark up the\nPLAN DEFAULT keywords with and fix a couple of wording issues.\nAlso list OUTER before INNER consistently, including in the parent/child\njoin description, where OUTER is the default.\n\nAuthor: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv5PGAFmAEpbhKQz8wppoOOTHfo-=LJb2sAB3974-9QtOw@mail.gmail.com", "completion": "Fix and polish JSON_TABLE documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n86ab7f4c721d makes JSON_TABLE with a NESTED PATH re-ran the nested path's\njsonpath expression several times for each parent row. That makes such\nqueries significantly slower as the nested arrays grew, even without a PLAN\nclause.\n\nTwo leftovers from the plan/join executor rework were responsible.\nJsonTablePlanScanNextRow() still reset and advanced the nested plan\nitself, although JsonTablePlanNextRow() now does that; and\nJsonTableResetNestedPlan() eagerly called JsonTableResetRowPattern()\n(which evaluates the path) in addition to setting the reset flag that\nmakes JsonTablePlanNextRow() evaluate it again. Together these caused\nthe nested path to be evaluated multiple times per parent row.\n\nReduce JsonTablePlanScanNextRow() to advancing its own row pattern\niterator, and have JsonTableResetNestedPlan() only reset the transient\nscan state (so a not-yet-advanced sibling still reads as NULL) while\ndeferring the actual path evaluation to the reset flag. The nested path\nis now evaluated exactly once per parent row, as before the PLAN clause\nfeature; results are unchanged and are covered by the existing tests.\n\nReported-by: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv5U94KD4C%2BLhAPYcCeGvs1xBMngcS5oEkZHN9YWwXUHsA%40mail.gmail.com", "completion": "Avoid redundant re-evaluation of JSON_TABLE nested paths"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ntransformJsonTableNestedColumns() looked up the nested column named by a\nJSON_TABLE PLAN node and raised \"invalid JSON_TABLE plan clause / PATH\nname was %s not found in nested columns list\" if none was found. That\nlookup cannot fail: validateJsonTableChildPlan() runs first, at every\nplan level, and already matches the plan's sibling path names one-to-one\nagainst the nested columns (reporting any uncovered nested path or any\nextra or duplicate sibling node). The check has been unreachable since\nthe PLAN clause code was first written.\n\nReplace it with an Assert documenting the invariant, which also removes\na user-facing message that could never be emitted.\n\nReported-by: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv5_9%3DzgA_Y7aoFp-%2BQSeh0kx4dfbAas9Wx%3DyrweQSqa6Q%40mail.gmail.com", "completion": "Remove unreachable error check in JSON_TABLE plan transform"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 62c3b4cd9ddc taught postgres_fdw to push down ArrayCoerceExpr, but\nforeign_expr_walker() only recursed into the input array expression and\nnever examined elemexpr, the per-element conversion that gives the\ncoercion its semantics. deparseArrayCoerceExpr() then shipped a bare\n\"arg::resulttype\" cast, or nothing at all for an implicit-format\ncoercion, leaving the remote server to re-resolve the element conversion\nagainst its own catalogs and session state.\n\nThis produced wrong results or remote errors whenever the element\nconversion was not a plain relabeling, and it was inconsistent with how\npostgres_fdw treats the equivalent scalar coercions. An ArrayCoerceExpr\nwas shipped even when its elemexpr was a cast function (whose\nshippability was never checked), a CoerceViaIO (e.g. float8out or\nbyteaout, which depend on extra_float_digits / bytea_output that\npostgres_fdw sets differently on the remote session), or a\nCoerceToDomain (which pushes domain enforcement to the remote catalog).\nBy contrast, a scalar CoerceViaIO is never shipped, and a scalar cast\nfunction is shipped only when it is shippable.\n\nRestrict pushdown to element coercions that are a plain relabeling, that\nis, elemexpr is a RelabelType or a bare CaseTestExpr. Any other element\ncoercion is now evaluated locally. This keeps the common\nbinary-coercible case pushed down, including \"col = ANY($1)\" with a\nvarchar[]-to-text[] relabeling, which is the case 62c3b4cd9ddc set out to\noptimize.\n\nPushing down shippable element cast functions, to reach parity with the\nscalar case, is left out here for simplicity.\n\nReported-by: Noah Misch \nDiscussion: https://postgr.es/m/20260711024234.43.noahmisch%40microsoft.com\nBackpatch-through: 19", "completion": "postgres_fdw: don't push down non-relabeling ArrayCoerceExpr"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n\"In `ul_parallel`, `max_parallel` is computed using\n`self._download_parallel` instead of `self._upload_parallel`. This\ncauses the upload parallelism to incorrectly follow the download\nparallel setting. It should use `self._upload_parallel` to be consistent\nwith how `uploads()` computes `max_parallel`.\"\n\nReported by GitHub Code Quality\n\nFollow-up to 30ef79ed937ca0fc7592ff73d162398773c6a5aa #17295\n\nCloses #22421", "completion": "scorecard: fix `max_upload` init value in `ul_parallel()`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 9a60f295b stripped the stale PlaceHolderVars left behind by\nleft-join removal from the surviving rels' baserestrictinfo and from\nEquivalenceClass member expressions, but it overlooked join clauses.\nA PlaceHolderVar embedded in a join clause can likewise retain the\nremoved rel and join in its phrels, since remove_rel_from_query()\nfixes up the RestrictInfo's own relid sets but not the PHVs inside its\nexpression.\n\nAs before, this is normally harmless, because later processing\nconsults those relid sets rather than the embedded PHVs. However, a\nrestriction clause derived from such an OR join clause inherits the\nstale PlaceHolderVar, and when the derived clause is translated for an\nappendrel child, pull_varnos() recomputes its relids and folds the\nremoved relation back in. The rebuilt clause then references a\nno-longer-existent relation, tripping an assertion during path\ngeneration.\n\nFix by also stripping the removed relation from the PlaceHolderVars in\nthe surviving rels' join clauses, including the sub-clauses of any OR\nclause.\n\nLike 9a60f295b, this is only reachable on v18 and later, where\nmatch_index_to_operand() began ignoring PlaceHolderVars.\n\nAuthor: Arne Roland \nReviewed-by: Tender Wang \nReviewed-by: Richard Guo \nDiscussion: https://postgr.es/m/27a44087-3d65-473e-8d88-7c12228e0d7e@malkut.net\nBackpatch-through: 18", "completion": "Strip removed-relation references from PHVs in join clauses"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n\"The check `i > 256` permits `i == 256` to pass through. When `i` is\nthen cast to `uint8_t` in `blob_add(b, (uint8_t)i)`, the value wraps to\n0, silently encoding a zero-length ALPN entry instead of rejecting it.\nThe condition should be `i > 255` (or equivalently `i >= 256`) to\ncorrectly reject any length that does not fit in a single byte.\"\n\nReported by GitHub Code Quality\n\nFollow-up to 86f1e5b3f6c90e453368fdf23c366c1d4a8c953b #21299\n\nCloses #22420", "completion": "dnsd: fix bounds check in `read_https_alpn_part()`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nequalPolicy() is used in the relation cache to check if two policy\ndefinitions are equivalent, but missed to check for polpermissive.\n\nALTER POLICY cannot switch a policy to be PERMISSIVE or RESTRICTIVE, so\nthis would need a dropped and then re-created policy, which would\ntrigger a relcache invalidation. Anyway, there is no harm in being\nconsistent in the check, and if one decides to add an ALTER POLICY to\nswitch PERMISSIVE or RESTRICTIVE, we would be silently in trouble.\n\nAuthor: Andreas Lind \nReviewed-by: Laurenz Albe \nDiscussion: https://postgr.es/m/CAMxA3rv1CS6R7JR5ojz-3CmCEnZEFrqu+XXTnGbLRWrjJRH7sA@mail.gmail.com\nBackpatch-through: 14", "completion": "Include check on polpermissive relcache for policies"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nContrary to the from_serialized_data callback used by the pgstats reads\nat startup, the to_serialized_data callback used for the pgstats writes\nmatched with pgstat_write_statsfile(), by not returning a boolean\nstatus, expecting a ferror() failure to deal with the discard of the\nstats file should an error happen while writing the stats. This was\nslightly confusing designed this way.\n\nThings are changed in this commit with:\n- to_serialized_data now returns a boolean status on a write failure.\npgstat_write_statsfile() detects that and switches to failure mode\ninstead of continuing to process the entries to write, speeding up the\nshutdown.\n- pgstat_write_statsfile() now uses STATS_DISCARD if a failure happens,\nto let the registered callbacks directly know that something is wrong,\nand that things need to be cleaned up. This gives a better error path\ndetection for custom stats kinds. For example, they do not have to rely\nsolely on the expectation of an ferror() for an auxiliary file.\n\nThis new set of behaviors matches with what is already done in\npgstat_read_statsfile() for the finish() callback (DISCARD on failure,\nREAD on success) and the from_serialized_data with a status returned.\n\nAuthor: Sami Imseih \nDiscussion: https://postgr.es/m/CAA5RZ0sMgOvuhpb2P=KSJOjgjC6AfUu+GYcu9mHar-y_Xtd=Pg@mail.gmail.com\nBackpatch-through: 19", "completion": "Rework pgstat_write_statsfile() in combination with to_serialized_data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe return type is ssize_t, not int, but some callers didn't handle\nthis properly.\n\nThe BIO callbacks are constrained by the OpenSSL API, so they take int\nfor the length and return int. This is safe, since the return value\ncan't be greater than the input length. To make it more clear that\nthis is intentional, cast the result of the\nsecure_read()/secure_write() call to int explicitly.\n\nReviewed-by: Heikki Linnakangas \nDiscussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406@eisentraut.org", "completion": "Clean up secure_read()/secure_write() return type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFixes a regression from #34486\nFix #40745\n\n(cherry picked from commit 39bc59a8f1c0eacea60e47b3a8b0422bbbbb8cd6)", "completion": "fix(floatwin): don't use same window as altwin"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFixes a regression from #34486\nFix #40745", "completion": "fix(floatwin): don't use same window as altwin"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe test provider's fake AES-128-GCM cipher works by running the real\nsub-cipher for its side effects and then copying the memdup'd input\nback over the output buffer, so the \"encrypted\" record is really the\nplaintext.\n\nIn a TLS record the buffer handed to the cipher reserves an\nuninitialised 8-byte explicit IV at the front and a 16-byte auth tag\nat the end for the cipher to fill. OPENSSL_memdup() duplicated those\nuninitialised IV/tag regions, and the subsequent memcpy(out, inbuf, inl)\ncopied them into out. That output was then written to the socket,\ntriggering valgrind's \"Syscall param write(buf) points to uninitialised\nbyte(s)\":\n\n at sock_write (bss_sock.c:155)\n by bwrite_conv (bio_meth.c:79)\n by BIO_write (bio_lib.c:397)\n by statem_flush (statem.c:963)\n by ossl_statem_client_post_work (statem_clnt.c:881)\n ...\n\nTrack whether EVP_CTRL_AEAD_TLS1_AAD was set (recorded in\nset_ctx_params) and, when encrypting a TLS record, copy only the\nplaintext payload back, leaving the explicit IV and tag that the real\nsub-cipher actually produced intact.\n\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Neil Horman \nMergeDate: Mon Jul 20 09:07:08 2026\n(Merged from https://github.com/openssl/openssl/pull/31961)", "completion": "test/p_ossltest: fix uninitialised bytes written in TLS1-AAD GCM mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nand analogously for pg_pread() and FileRead()\n\nBe sure to store the return value in a variable of type ssize_t, not\nint.\n\nAlso make the error messages for short reads consistent. They should\nalways be like \"read %zd of %zu\". Appearance of other placeholders\nindicates the types are probably wrong (although in some cases some\ncasts are added to make macros have the right type and keep the\nstrings consistent, and it some cases it's left as \"%zu of %zu\", which\nis close enough).\n\nIn several cases, the input length is derived from struct stat\nst_size, which has type off_t, which is neither size_t nor ssize_t.\nTo keep the type handling clearer, this introduces intermediate\nvariables in these cases.\n\nIn SendTimeLineHistory() in walsender.c, we need to adjust the logic a\nbit to over underflow wrap if we end up reading more from the file\nthan expected. This is believed to be a theoretical problem only.\nAlternatively, we could treat this as an error. Note that the\nprevious code would have processed the extra data but only up to a\nfull block, which seems wrong in any case.\n\nReviewed-by: Heikki Linnakangas \nDiscussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406@eisentraut.org", "completion": "Clean up read() return type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAppend the %p (process ID) placeholder to valgrind's --log-file in\nboth app() and test(). When a test spawns multiple processes sharing\nthe same result index, they previously wrote to the same log file and\nclobbered each other's output. Using %p gives each process its own\nlog, so no valgrind findings are lost.\n\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Neil Horman \nMergeDate: Mon Jul 20 09:07:07 2026\n(Merged from https://github.com/openssl/openssl/pull/31961)", "completion": "test: include PID in valgrind log file names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe result from pg_preadv() or pg_pwritev(), which is of type ssize_t,\nis assigned to PgAioHandle.result, which is of type int. This should\nbe ok because the maximum result is limited by PG_IOV_MAX times\nBLCKSZ. Add an assertion and a code comment to explain and check\nthis.\n\nReviewed-by: Heikki Linnakangas \nDiscussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406@eisentraut.org", "completion": "Add assertion about ssize_t narrowing in AIO code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nand analogously for pg_pwrite() and FileWrite()\n\nBe sure to store the return value in a variable of type ssize_t, not\nint.\n\nSome callers of FileWrite() did not have a separate error message for\na short write. This is okay in practice because FileWriteV() sets\nENOSPC for all non-error returns, so you'll get a reasonable error\nmessage either way. But callers handled this inconsistently, and this\nbehavior isn't really prominently documented and commit 871fe4917e1\nseems to frown upon it, so it seems better to make all callers handle\nthis consistently by adding the separate error message.\n\nReviewed-by: Heikki Linnakangas \nDiscussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406@eisentraut.org", "completion": "Clean up write() return type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe QUIC radix test creates a new thread-local key for each script but\nonly clears the associated value during teardown. The key itself\nis never deleted.\n\nDelete the thread-local key after all child threads have joined and the\nmain-thread value has been cleared.\n\n 1,536 bytes in 3 blocks are still reachable in loss record 873 of 915\n at 0x488D0B0: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-arm64-linux.so)\n by 0x49561CF: pthread_setspecific@@GLIBC_2.34 (in /usr/lib64/libc.so.6)\n by 0x5C0FD7: CRYPTO_THREAD_set_local (threads_pthread.c:1030)\n by 0x41132F: radix_thread_init (quic_bindings.c:570)\n by 0x4114F7: bindings_process_init (quic_bindings.c:604)\n by 0x422563: test_script (main.c:28)\n by 0x5152DF: run_tests (driver.c:518)\n by 0x517447: main (main.c:52)\n\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Neil Horman \nMergeDate: Mon Jul 20 09:07:10 2026\n(Merged from https://github.com/openssl/openssl/pull/31961)", "completion": "test: clean up thread-local key in QUIC radix tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBackpatch-through: 19", "completion": "doc PG 19 relnotes: remove duplicate word"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe internal provider test intentionally retains its configured provider\nwhen OPENSSL_cleanup() is skipped under OSSL_USE_VALGRIND. The existing\nsuppression accounts for this state but no longer matches the provider\nactivation stack because provider_init() appears between\nOSSL_provider_init() and provider_activate().\n\nAdd the missing frame so the provider context and its diagnostic strings\nare correctly suppressed.\n\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Neil Horman \nMergeDate: Mon Jul 20 09:07:11 2026\n(Merged from https://github.com/openssl/openssl/pull/31961)", "completion": "test: update provider Valgrind suppression"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nMoved to source code section.\n\nReported-by: Andreas Karlsson\n\nDiscussion: https://postgr.es/m/f5f129c3-88fa-43dc-a23a-75155fa10be3@proxel.se\n\nBackpatch-through: 19 only", "completion": "doc PG 19 relnotes: \"OAUTH validators to supply failure item\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIf a directive has an input declared as `dismissible = input(true, {transform: booleanAttribute});` then the following templates were not compiling:\n\n```\n
\n
\n```\n\nThis commit fixes the issue, without breaking contravariant consumers.\n\n(cherry picked from commit 0ae6d81ed2a83b1ebbb75dabc53af77b8db86c41)", "completion": "fix(core): preserve explicit input transform write type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIf a directive has an input declared as `dismissible = input(true, {transform: booleanAttribute});` then the following templates were not compiling:\n\n```\n
\n
\n```\n\nThis commit fixes the issue, without breaking contravariant consumers.", "completion": "fix(core): preserve explicit input transform write type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nReported-by: Andreas Karlsson\n\nDiscussion: https://postgr.es/m/f5f129c3-88fa-43dc-a23a-75155fa10be3@proxel.se\n\nBackpatch-through: 19 only", "completion": "doc PG 19 relnotes: swap OAUTH hook and validator items"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n- No UI for listing extmarks.\n- `:marks` doesn't support cmdline-completion.\n\nSolution:\n- Add completion and extmarks support to `:marks`.\n- Update `get_buf_local_marks` to include the \":\" (prompt-buffer) mark.", "completion": "feat(marks): :marks completion, list extmarks #40743"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n'ALTER SUBSCRIPTION ... REFRESH SEQUENCES' can race with an already\nrunning sequence synchronization worker. If a second refresh request\nresets the synchronization state while the worker has already fetched\nsequence values from the publisher but has not yet applied them to the\nsubscriber, the worker can overwrite the subscriber with stale values\nand mark the synchronization as complete.\n\nAvoid this race by rejecting 'ALTER SUBSCRIPTION ... REFRESH SEQUENCES'\nwhen a sequence synchronization worker is already running for the\nsubscription. The command reports an error asking the user to rerun it\nafter the current synchronization completes.\n\nAlso add a wait for the re-added 'regress_s4' sequence to finish\nsynchronizing in 036_sequences.pl, so the subsequent test does not race\nagainst its sequencesync worker.\n\nReported-by: Noah Misch \nAuthor: vignesh C \nReviewed-by: Shveta Malik \nReviewed-by: Hayato Kuroda \nReviewed-by: Amit Kapila \nBackpatch-through: 19, where it was introduced\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Reject concurrent sequence refreshes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:52:08 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:51:03 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:49:45 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:48:20 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:02:43 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe CMS_AuthenticatedData ASN.1 template declared the authAttrs and\nunauthAttrs fields as X509_ALGOR, whereas per RFC 5652 section 9.1 they\nare [2] and [3] IMPLICIT SET OF Attribute and the CMS_AuthenticatedData\nstructure already declares them as STACK_OF(X509_ATTRIBUTE). The implicit\ntags [2] and [3] were already correct, so only the element type was wrong.\n\nAn Attribute (SEQUENCE { type, SET OF value }) is structurally accepted as\nan AlgorithmIdentifier (SEQUENCE { algorithm, ANY OPTIONAL }), so parsing\ndid not fail; the attributes were merely misinterpreted, e.g. cms -cmsout\n-print rendered them as algorithm/parameter instead of decoding them as\nattributes. Use X509_ATTRIBUTE with the existing tags so the template\nmatches the structure.\n\nAdd a parse test using a BouncyCastle-generated AuthenticatedData message\ncarrying an authenticated and an unauthenticated attribute, asserting both\nare decoded as SET OF Attribute.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 10:02:08 2026\n(Merged from https://github.com/openssl/openssl/pull/31960)", "completion": "cms: fix AuthenticatedData authAttrs and unauthAttrs element type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem\nThe current list of properties for inlay hint resolve support includes a\nnon-existent \"location\". This field should be \"label.location\" according\nto the specification. Tooltips and commands for inlay hint \"parts\"\naren't advertised as being resolvable.\n\nSolution\nRemove \"location\" and add \"label.location\", \"label.tooltip\", and\n\"label.command\".\n\nCloses #40740\n\n(cherry picked from commit 4bc30d6e1024788c6acf54cf3e4a98618123482e)", "completion": "fix(lsp): improve inlayHint.resolveSupport in client capabilities #40741"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem\nThe current list of properties for inlay hint resolve support includes a\nnon-existent \"location\". This field should be \"label.location\" according\nto the specification. Tooltips and commands for inlay hint \"parts\"\naren't advertised as being resolvable.\n\nSolution\nRemove \"location\" and add \"label.location\", \"label.tooltip\", and\n\"label.command\".\n\nCloses #40740", "completion": "fix(lsp): improve inlayHint.resolveSupport in client capabilities #40741"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Every LSP capability that sends a request on a document change\nto update its state was using its own buffer-local autocmd to do so.\nThat means there is a separate autocmd per buffer per active\ncapability/feature, and the actual code inside the autocmd callback was\nvirtually identical. The same problem occurred for capabilities that had\ncomponents to draw on the screen that had their own decoration providers.\n\nSolution: Introduce a central `LspNotify` autocmd and decoration\nprovider in the capability module itself. New base class methods\n`on_close` and `on_change` that take a client_id have been provided, for\n`didClose` and `didOpen`/`didChange` notifications respectively. New\nbase class method `on_win` that takes topline and botline has been\nprovided to add extmarks or perform other work when lines of a buffer\nare being drawn.\n\nThe autocmd callback loops through each active capability instance for\nthe buffer and calls a corresponding method with the triggering\nclient_id if it is currently attached to the buffer that triggered the\nautocmd. The decoration provider just calls on_win for all active\ncapabilities on the buffer.\n\nThis slightly tweaks folding range to make use of these new client-id\nspecific callbacks.", "completion": "refactor(lsp): unify LspNotify, decor provider for capabilities #40691"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Closing a floating window from a non-current tab frees its grid\nwithout removing it from the compositor's `layers` table, so the next\n`ui_comp_put_grid()` walks a dangling pointer (UAF).\n\nSolution: Call `ui_comp_remove_grid()` (and `ui_call_win_close()` for\nmultigrid UIs) before `win_free_mem()`, matching `win_close()` since\nPR #21551.\n\n(cherry picked from commit 6f370f34f2c24aed0d2acebab23c4bcc86a06d69)", "completion": "fix(window): remove float grid from compositor layers before free #40731"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Closing a floating window from a non-current tab frees its grid\nwithout removing it from the compositor's `layers` table, so the next\n`ui_comp_put_grid()` walks a dangling pointer (UAF).\n\nSolution: Call `ui_comp_remove_grid()` (and `ui_call_win_close()` for\nmultigrid UIs) before `win_free_mem()`, matching `win_close()` since\nPR #21551.", "completion": "fix(window): remove float grid from compositor layers before free #40731"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nquiche 0.29.3 started enforcing a default\n`SETTINGS_MAX_FIELD_SECTION_SIZE` of 32 KiB, so larger response headers\nnow shut down the whole connection with `CURLE_HTTP3`. curl accepts up\nto 300 KiB of response headers with every other backend and HTTP\nversion. Tell quiche to allow what curl itself allows. This keeps\ntest_01_11 passing with quiche 0.29.3 and it also advertises our real\nlimit to servers, which the RFC encourages.\n\nRef: 899e2edec95b3df01db63ad219d3c5547a3e3ae5 #22333\nRef: #22329\nRef: #22325\nRef: https://github.com/cloudflare/quiche/commit/9be0e4fa18594a5cca00120f6ae392e217e837e5\nRef: https://github.com/cloudflare/quiche/releases/tag/0.29.3\n\nCloses #22331", "completion": "quiche: set the max field section size"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUse `_TEXT()` when interacting with CRT functions (also prefer over\nsynonym `_T()`), `TEXT()` for Win32 functions.\n\nWithin curl, they mean the same because CRT/Win32 Unicode mode are\nalways enabled in sync.\n\nRef: https://devblogs.microsoft.com/oldnewthing/20040212-00/?p=40643/\n\nCloses #22334", "completion": "tidy-up: `TEXT()` vs `_TEXT()` vs `_T()` use (Windows)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the template parser to detect and ignore processing instruction syntax (e.g. `` or ``). Currently it is being printed out as text.\n\nFixes #34371.\n\n(cherry picked from commit 68ac20407466f0d3e6f5c5016f1273672b5d2b34)", "completion": "fix(core): ignore processing instruction syntax in templates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the template parser to detect and ignore processing instruction syntax (e.g. `` or ``). Currently it is being printed out as text.\n\nFixes #34371.", "completion": "fix(core): ignore processing instruction syntax in templates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npg_clear_attribute_stats() checks its required arguments manually\nbecause the function is not strict. Previously, when schemaname or\nrelname was passed as NULL, the error incorrectly reported the\nargument name as \"relation\" in both cases:\n\n ERROR: argument \"relation\" must not be null\n\nThis was misleading, especially for schemaname, and inconsistent with\nthe function's SQL-visible argument names.\n\nThe cause is that cleararginfo[] in attribute_stats.c used\n\"relation\" for both the schema-name and relation-name arguments.\n\nThis commit fixes the issue by using \"schemaname\" and \"relname\" instead,\nmatching the function's declared argument names so that the error reports\nthe correct argument name.\n\nBackpatch to v18, where pg_clear_attribute_stats() was introduced.\n\nAuthor: Ilia Evdokimov \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/4bf66c5e-8dd7-4ef3-8691-db67ecff6f16@tantorlabs.com\nBackpatch-through: 18", "completion": "Fix argument names in pg_clear_attribute_stats() errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n\"Supported browsers\" page got moved from\nhttps://web-platform-dx.github.io/web-features/supported-browsers to https://web-platform-dx.github.io/supported-browsers/\n\nThere's a redirect in place, but it drops the query parameter with the date, so all versions link to the current browser set.\n\n(cherry picked from commit ea83f13388470ceb981b1130fdb2cc6b79e299fc)", "completion": "docs: update \"browser set\" links to avoid bad redirect"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n\"Supported browsers\" page got moved from\r\nhttps://web-platform-dx.github.io/web-features/supported-browsers to https://web-platform-dx.github.io/supported-browsers/\r\n\r\nThere's a redirect in place, but it drops the query parameter with the date, so all versions link to the current browser set.", "completion": "docs: update \"browser set\" links to avoid bad redirect"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCo-authored-by: Andrew Dinh \n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:49 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)\n\n(cherry picked from commit 33482fbddcf137dde9bd84ae12f2f02cbc358c78)", "completion": "Apply suggestion from @andrewkdinh"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCo-authored-by: Andrew Dinh \n\nReviewed-by: Andrew Dinh \nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 17:04:49 2026\n(Merged from https://github.com/openssl/openssl/pull/31957)", "completion": "Apply suggestion from @andrewkdinh"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nrevert #14793\nVapor cannot distinguish between slots.default() calls used for VNode\ninspection and calls used for actual rendering. Eager slot collection can\ntherefore execute user code or claim hydration nodes before rendering.", "completion": "fix(runtime-vapor): remove unsafe slot dry runs from vdom interop"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFor function `quiche_h3_config_set_max_field_section_size()`.\n\nRef: #22331\nRef: https://github.com/curl/curl/pull/22331#issuecomment-4981647189\nRef: https://github.com/cloudflare/quiche/releases/tag/0.20.0\n\nCloses #22333", "completion": "INTERNALS.md: require quiche 0.20.0+"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe DevTools state screens (Angular not detected, unsupported version,\nproduction build) showed a plain Material icon above the message. Show\nthe Angie mascot instead, matching the treatment already used across\nangular.dev (the 404 page, empty search, the preview error state).\n\nEach screen uses a pose that fits its message: the dizzy `error` pose for\n\"application not detected\", `coding-01` for the version-upgrade prompt,\nand `sad` for the production build notice.\n\n(cherry picked from commit d4f2313e4d6700011ec42979f4b2ca4756bc7e56)", "completion": "feat(devtools): show Angie on the empty-state screens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe DevTools state screens (Angular not detected, unsupported version,\nproduction build) showed a plain Material icon above the message. Show\nthe Angie mascot instead, matching the treatment already used across\nangular.dev (the 404 page, empty search, the preview error state).\n\nEach screen uses a pose that fits its message: the dizzy `error` pose for\n\"application not detected\", `coding-01` for the version-upgrade prompt,\nand `sad` for the production build notice.", "completion": "feat(devtools): show Angie on the empty-state screens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUse separate dns cache entries for addresses (A+AAAA) and HTTPS-RR\nresults. That makes also \"negative\" results independent of each other.\nDns cache entries, once in use, can no longer be modified safely, as\nconcurrent use would require each access then to be done under lock. By\nusing separate entries, we can update a HTTPS entry without needing to\nduplicate an existing address entry for the same host+port.\n\nConnection filters can now ask for DNS resolves. This works at any time\nduring connection setup and while connect is going on.\n`Curl_conn_dns_add_addr_resolve()` and\n`Curl_conn_dns_add_https_resolve()` are used for that. They check if the\nresolve is already ongoing, can be added to a resolve not started yet\nor, as last resort, create a new filter instance and add it to the\nconnection (it's easier to add more filters than making the same filter\nhandle multiple resolves. Since DNS filters are removed once the\nconnection is established, there is no later penalty).\n\nHTTPS-RR queries are added by the `HTTPS-CONNECT`, `SSL` and `QUIC`\nfilters. The latter will only do that when ECH is configured and\nsupported. That means we trigger HTTPS-RR queries only when the results\nmatter.\n\nAdd test_22_06 for ALPN influenced via HTTPS-RR when tunneling through a\nproxy. This did not work before.\n\nAdjust test2100 to use https: as the previous http: URL no longer\ntriggers HTTPS-RR resolves.\n\nCloses #22216", "completion": "cf-dns: resolve on filter demand"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReported by GitHub Code Quality\nFollow-up to 0fdf96512613574591f501d63fe49495ba40e1d5 #5193\n\nCloses #22415", "completion": "schannel: fix error check logic in `get_client_cert()` file reader"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFormat DevTools TypeScript files.", "completion": "refactor(devtools): format code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCode elsewhere in the system assumes that fork numbers and chunk sizes\nare within bounds, so the code that reads those quantities from disk\nshould validate that they are. Without these additional checks, a\ncorrupted file can cause us to index off the end of fork number or chunk\nentry arrays, potentially resulting in a crash.\n\nReported-by: oxsignal (chunk sizes)\nReported-by: Robert Haas (fork numbers)\nReviewed-by: Daniel Gustafsson \nDiscussion: http://postgr.es/m/CA+TgmoYP8RKoBGosS7C6Fdr-GNCfyz_W1zmK=Tx1Fe0ZvzGh0g@mail.gmail.com\nBackpatch-through: 17", "completion": "Add additional sanity checks when reading a blkreftable."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIt was possible to trigger read_stream_begin_relation's\nassertion that it calculated nonzero max_pinned_buffers,\nin scenarios with unreasonably small numbers of buffers.\nThere seems to be no visible problem in non-Assert builds.\n\nThe bug occurs only in v17 (the first branch containing\nthis logic), because commit 92fc6856c replaced that Assert\nwith a runtime clamp. I won't risk back-patching that entire\ncommit, but let's copy just this minimal fix.\n\nBug: #19551\nReported-by: Roman Zharkov \nAuthor: Thomas Munro \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/19551-d4a55b8fe81db4f2@postgresql.org\nBackpatch-through: 17 only", "completion": "Make max_pinned_buffers be > 0, don't just Assert that it is."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBind spyOn explicitly to Window so Jasmine uses the DOM setTimeout signature that returns a number instead of the Node.js Timeout type. Remove the unsafe any cast and the obsolete TODO.\n\n(cherry picked from commit 24a3c63976390f3370d85b147379c66fc0e0802d)", "completion": "test(elements): disambiguate the setTimeout spy type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBind spyOn explicitly to Window so Jasmine uses the DOM setTimeout signature that returns a number instead of the Node.js Timeout type. Remove the unsafe any cast and the obsolete TODO.", "completion": "test(elements): disambiguate the setTimeout spy type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRevamp the highlighter by introducing a completely new mechanism.", "completion": "refactor(devtools): revamp highlighter"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.1.0-next.4"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.0.7"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA wrong calculation introduced by 9c8de15969 could cause trailing\ncharacters from the prefix to be passed to like_selectivity() rather\nthan just the \"rest\".\n\nDiscussion: https://postgr.es/m/c7334a7a44243d2e4ec5e83747589908b3787491.camel@j-davis.com\nBackpatch-through: 19", "completion": "Fix like_fixed_prefix_ci() selectivity."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Bob Beck \nReviewed-by: Norbert Pocs \nMergeDate: Tue Jul 21 14:12:07 2026\n(Merged from https://github.com/openssl/openssl/pull/31964)", "completion": "CHANGES.md updates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 6f164e6d17616 accidentally mistyped --client as --clients in\nthe error message. Backpatch down to v15 where the it was introduced.\n\nAuthor: Semih Doğan \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CALOtZ7tuWisV=v0cUY_q6PLHJ-fOiQ7ZN476JwmM0PyV0t5i7Q@mail.gmail.com\nBackpatch-through: 15", "completion": "pgbench: Fix incorrect parameter name in error message"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen bulk-extending a relation, we add the newly-added blocks that we\nwon't immediately use to the free space map and then call\nFreeSpaceMapVacuumRange() to propagate that free space up the FSM tree,\nso other backends can find and reuse it.\n\nHowever, the end block argument to FreeSpaceMapVacuumRange() is\nexclusive, and we passed the number of the last added block (since\n00d1e02be24). If that block was the first one covered by a new FSM page,\nits free space wasn't propagated up the tree and was therefore invisible\nto FSM searches until the next FSM vacuum.\n\nFix by passing the block number one past the last added block, so the\nfull range is vacuumed.\n\nAuthor: Jingtang Zhang \nReviewed-by: Melanie Plageman \nDiscussion: https://postgr.es/m/flat/CAPsk3_Bx_vdybN%3D-DZu8HLStf%2BXnuFUBkLwxouONSMkWuO9oug%40mail.gmail.com\nBackpatch-through: 16", "completion": "Include last block in FSM vacuum of bulk extended relation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nHeap WAL records that clear bits on the visibility map (like inserts and\ndeletes) did not register the visibility map blocks they modified.\nBecause the WAL summarizer only records registered blocks, an\nincremental backup taken over such operations would omit the changed VM\npages. On restore, the VM would retain stale all-visible/all-frozen\nbits, which can cause wrong results from index-only scans and incorrect\nrelfrozenxid advancement due to vacuum page skipping.\n\nNot registering the VM buffer also meant we never emitted FPIs of VM\npages when clearing bits. A torn VM page won't raise an error because\nthe VM is read with ZERO_ON_ERROR; with checksums on, it would be\ndetected and zeroed, but with checksums off, it is accepted as-is and\ncan lead to data corruption.\n\nFix this by registering the VM buffer in the WAL record when clearing VM\nbits. The VM buffer must now be locked throughout the critical section\nthat modifies the VM and heap pages and emits the WAL record. This can\nslow down operations that clear the VM, since the VM lock is held longer\nand VM FPIs may be emitted, but it is required for correctness.\n\nNote that this fix does not repair existing incremental backups.\n\nBumps XLOG_PAGE_MAGIC.\n\nAuthor: Melanie Plageman \nAuthor: Andres Freund \nReviewed-by: Robert Haas \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/flat/CAAKRu_bn%2Be7F4yPFBgFbnP%2BsyJRKyNK092bjD2LKvZW7O4Svag>\nBackpatch-through: 17", "completion": "Fix VM clear WAL logging by registering VM blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis brings it in line with visibilitymap_set(). An upcoming commit will\nstart reading visibility map buffers with XLogReadBuffer*() functions,\nso we no longer require a relation object to pin the visibility map,\nallowing us to remove this fake relcache business altogether.\n\nWhile we're at it, remove a spurious const qualifier from the\nRelFileLocator parameter to visibilitymap_set().\n\nAuthor: Melanie Plageman \nDiscussion: https://postgr.es/m/flat/CAAKRu_bn%2Be7F4yPFBgFbnP%2BsyJRKyNK092bjD2LKvZW7O4Svag%40mail.gmail.com", "completion": "Make VM clear take a RelFileLocator and not fake relcache"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nHeap WAL records that clear bits on the visibility map (like inserts and\ndeletes) did not register the visibility map blocks they modified.\nBecause the WAL summarizer only records registered blocks, an\nincremental backup taken over such operations would omit the changed VM\npages. On restore, the VM would retain stale all-visible/all-frozen\nbits, which can cause wrong results from index-only scans and incorrect\nrelfrozenxid advancement due to vacuum page skipping.\n\nNot registering the VM buffer also meant we never emitted FPIs of VM\npages when clearing bits. A torn VM page won't raise an error because\nthe VM is read with ZERO_ON_ERROR; with checksums on, it would be\ndetected and zeroed, but with checksums off, it is accepted as-is and\ncan lead to data corruption.\n\nFix this by registering the VM buffer in the WAL record when clearing VM\nbits. The VM buffer must now be locked throughout the critical section\nthat modifies the VM and heap pages and emits the WAL record. This can\nslow down operations that clear the VM, since the VM lock is held longer\nand VM FPIs may be emitted, but it is required for correctness.\n\nNote that this fix does not repair existing incremental backups.\n\nBumps XLOG_PAGE_MAGIC. Though it is late in the cycle (post-beta 2) to\nbe doing so, that seemed better than maintaining the backwards\ncompatability code in yet another branch.\n\nAuthor: Melanie Plageman \nAuthor: Andres Freund \nReviewed-by: Robert Haas \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/flat/CAAKRu_bn%2Be7F4yPFBgFbnP%2BsyJRKyNK092bjD2LKvZW7O4Svag>\nBackpatch-through: 17", "completion": "Fix VM clear WAL logging by registering VM blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe WAL summarizer only tracks registered buffers, so unregistered VM\nclears are ommitted from incremental backups, corrupting the restored\nvisibility map. Test those cases are now fixed.\n\nAuthor: Melanie Plageman \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/oqcsevg35xjan2327x5kdfth6q4fgeqboxfo3v3imeyih2uiny%406sez5dzxl6nt\nBackpatch-through: 17", "completion": "Test that VM clear registers VM buffers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nHeap WAL records that clear bits on the visibility map (like inserts and\ndeletes) did not register the visibility map blocks they modified.\nBecause the WAL summarizer only records registered blocks, an\nincremental backup taken over such operations would omit the changed VM\npages. On restore, the VM would retain stale all-visible/all-frozen\nbits, which can cause wrong results from index-only scans and incorrect\nrelfrozenxid advancement due to vacuum page skipping.\n\nNot registering the VM buffer also meant we never emitted FPIs of VM\npages when clearing bits. A torn VM page won't raise an error because\nthe VM is read with ZERO_ON_ERROR; with checksums on, it would be\ndetected and zeroed, but with checksums off, it is accepted as-is and\ncan lead to data corruption.\n\nFix this by registering the VM buffer in the WAL record when clearing VM\nbits. The VM buffer must now be locked throughout the critical section\nthat modifies the VM and heap pages and emits the WAL record. This can\nslow down operations that clear the VM, since the VM lock is held longer\nand VM FPIs may be emitted, but it is required for correctness.\n\nNote that this fix does not repair existing incremental backups.\n\nAuthor: Melanie Plageman \nAuthor: Andres Freund \nReviewed-by: Robert Haas \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/flat/CAAKRu_bn%2Be7F4yPFBgFbnP%2BsyJRKyNK092bjD2LKvZW7O4Svag>\nBackpatch-through: 17", "completion": "Fix VM clear WAL logging by registering VM blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen registering a buffer with the WAL machinery, the caller assigns it a\nblock reference ID, and replay must read each block back by that same ID.\nToday these IDs are bare integers assigned by convention (0, 1, 2, ...),\nwhich is easy to follow when a record registers a single block, or when the\nblocks are handled during replay in their registration order.\n\nAn upcoming bug fix registers up to two visibility map blocks in addition\nto the heap block(s) when clearing the VM, and these are not handled during\nreplay in a straightforward 1:1, in-registration-order fashion. Relying on\nbare integers for the block IDs in that case is error-prone.\n\nIntroduce macros naming the block reference IDs for the heap record types\nthat the upcoming commit extends to register visibility map blocks, so the\nregistration and replay sites refer to the same block by a meaningful name.\n\nAuthor: Melanie Plageman \nReviewed-by: Robert Haas \nDiscussion: https://postgr.es/m/66mqpfyti3qhfttcsv6r2lbvqqd32rrmpn6i47ovrsnvguts46%40gou54xc>\nBackpatch through: 17", "completion": "Introduce macros for WAL block reference IDs of some heap record types"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a subtest exercising the code path in the req app that rewrites the\nsubject of an existing certificate request loaded via -in, i.e. when\n-subj is given without -new/-newkey/-x509.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Matt Caswell \nReviewed-by: Ryan Hooper \nMergeDate: Mon Jul 27 10:19:06 2026\n(Merged from https://github.com/openssl/openssl/pull/31965)", "completion": "apps: cover the req -subj modification of an existing request"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve raw native input text while editing so parsed model values are not written back on every keystroke.\n\n(cherry picked from commit 2e32872720ee95f24029d20e24e91edbc2054b1e)", "completion": "fix(forms): preserve intermediate number values in signal forms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve raw native input text while editing so parsed model values are not written back on every keystroke.", "completion": "fix(forms): preserve intermediate number values in signal forms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 4f1ef2dec1f867c934a42728b69806ffdfecb4db)", "completion": "fix(restart): keep :restart error message concise #40746"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: LSP completion commitCharacters are not handled. Typing a\ncommit character (e.g. `.`, `(`, `;`) while a completion item is\nselected does not accept the item first.\n\nSolution: Store commit characters as a flat string in complete-items.\nCheck it before completion stops, accept the match and let\nthe character be inserted normally.", "completion": "feat(completion): commitCharacters #38417"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: #40731 may still crash if close_buffer autocmds reinsert the float's\ngrid. Plus removing the grid (and posting win_close) is unneeded if\nwin_close_othertab refuses to close the window later, which is possible.\n\nSolution: do the stuff before freeing the window, like win_close.\n(cherry picked from commit 1741da8412134fc5a2f83e509da925c4e2d65034)", "completion": "fix(window): yeet grid later when closing float in other tabpage #40758"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: #40731 may still crash if close_buffer autocmds reinsert the float's\ngrid. Plus removing the grid (and posting win_close) is unneeded if\nwin_close_othertab refuses to close the window later, which is possible.\n\nSolution: do the stuff before freeing the window, like win_close.", "completion": "fix(window): yeet grid later when closing float in other tabpage #40758"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15009", "completion": "fix(runtime-dom): respect current select model type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n`$el`'s type param (`TypeEl`) lives in `@vue/runtime-core`, which is\nrenderer-agnostic, yet it's constrained to the DOM `Element` interface.\nCustom renderers (TUI, canvas, native, …) have host nodes that aren't DOM\n`Element`s, so they can't type `$el` without laundering through `& Element`.\n\nRelax the `TypeEl` bound to unconstrained (default stays `any`): DOM\nelements still qualify, non-DOM host nodes now do too. Backward compatible —\nit only widens accepted inputs.", "completion": "fix(types): don't constrain component $el type to Element"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nRefs GHSA-9rff-vwfp-83hv.", "completion": "fix(shared): prevent SSR comment escaping from creating closing delimiters"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nfix #15070", "completion": "fix(runtime-core): unwind dangling blocks when slot content throws"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #12575", "completion": "fix(server-renderer): handle errors in optimized component renders"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15081\nclose #15050", "completion": "fix(hydration): pass namespace when patching dynamic props"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15083", "completion": "fix(reactivity): handle effect removal during scope stop"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15091", "completion": "fix(runtime-core): skip lazy hydration for detached roots"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15048", "completion": "fix(compiler-core): avoid leaking slot branch keys"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* style(Button): align loading icon styles\n\n* chore: retrigger CI", "completion": "style(Button): align loading icon styles"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe documentation for log_parameter_max_length said it affects messages\ngenerated by log_duration. However, log_duration alone does not log bind\nparameter values, so this is misleading.\n\nThis commit updates the documentation to reference log_min_duration_statement,\nwhich can log bind parameters, to better reflect actual behavior.\n\nBackpatch to all supported versions.\n\nAuthor: Fujii Masao \nReviewed-by: Surya Poondla \nDiscussion: https://postgr.es/m/CAHGQGwGnCVMVz8-LU9F8Sh57bkQX3jMZzx7age7M0LFEz5=Fog@mail.gmail.com\nBackpatch-through: 14", "completion": "doc: Fix log_parameter_max_length docs to reference log_min_duration_statement"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nREPACK requires the MAINTAIN privilege, but it was omitted from the\nlists of commands covered by that privilege in ddl.sgml and the\ndescription of the predefined pg_maintain role in user-manag.sgml.\nThis was an oversight in commit ac58465e061, which introduced\nREPACK.\n\nAdd REPACK to both documentation lists, and update the corresponding\ncomment in aclchk.c.\n\nAuthor: Shinya Kato \nReviewed-by: Ewan Young \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAOzEurRJOVokiB2J8nrF569nX-ZMb0oRSB0C=yZQ17mZxd4_BQ@mail.gmail.com\nBackpatch-through: 19", "completion": "doc: Mention REPACK in MAINTAIN privilege descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, libpqrcv_create_slot() checked only that\nCREATE_REPLICATION_SLOT returned PGRES_TUPLES_OK before reading\nvalues from the first row. If the server unexpectedly returned an\ninvalid result, such as zero rows, PQgetvalue() could return NULL,\nleading to a crash while parsing the LSN.\n\nOther replication commands, such as IDENTIFY_SYSTEM, already validate\nthe response shape before accessing result values, but\nCREATE_REPLICATION_SLOT did not.\n\nFix this by verifying that CREATE_REPLICATION_SLOT response contains\nexactly one row with four fields, and report a protocol violation otherwise.\n\nBackpatch to all supported versions.\n\nBug: #19547\nReported-by: Yuelin Wang <1217816127@qq.com>\nAuthor: Kenny Chen \nReviewed-by: Hayato Kuroda \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/19547-f7986f668f71e788@postgresql.org\nDiscussion: https://postgr.es/m/CAPXstDtW2iqe+DJAOTQTX+rRziJp2UhZSo1+HRj1COAtbu+nKw@mail.gmail.com\nBackpatch-through: 14", "completion": "Check CREATE_REPLICATION_SLOT response shape in libpqwalreceiver"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe `inlineStyleLanguage` build option has existed since v12 but was\nnever listed in the workspace configuration reference. Add it to the\n\"Extra build and test options\" table alongside the other style options,\ndocumenting its accepted values (css, less, sass, scss) and default.\n\nFixes #69801\n\n(cherry picked from commit f032f5ac1ff9f9ce771dd700f6306ab3c2c1d37d)", "completion": "docs: document the inlineStyleLanguage workspace config option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe `inlineStyleLanguage` build option has existed since v12 but was\nnever listed in the workspace configuration reference. Add it to the\n\"Extra build and test options\" table alongside the other style options,\ndocumenting its accepted values (css, less, sass, scss) and default.\n\nFixes #69801", "completion": "docs: document the inlineStyleLanguage workspace config option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-sonnet-4-6\nSigned-off-by: Shreenidhi Shedi \n\nReviewed-by: Andrew Dinh \nReviewed-by: Matt Caswell \nMergeDate: Fri Aug 7 13:29:42 2026\n(Merged from https://github.com/openssl/openssl/pull/31445)", "completion": "Update tsget man page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update actions/setup-node action to v7"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a subtest exercising the informational print options of the x509 app\nthat operate on any certificate: -serial, -next_serial, -subject_hash\n(and its -hash alias), -issuer_hash, -subject_hash_old, -issuer_hash_old\nand -fingerprint (default SHA-1 and -sha256). These branches of the print\nloop were previously not exercised.\n\nThe expected values are those of the committed test/certs/ca-cert.pem;\nthe fingerprints are the SHA-1 and SHA-256 digests of its DER encoding.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Matt Caswell \nMergeDate: Mon Jul 27 10:14:18 2026\n(Merged from https://github.com/openssl/openssl/pull/31967)", "completion": "apps: cover the x509 -serial, name-hash and -fingerprint print options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ncheck_cert_might_be_valid() called X509_VERIFY_PARAM_set_trust() with\nX509_TRUST_OK_ANY_EKU, which is a trust_flags bit (1 << 4), not a valid\ntrust id (1..8). The call therefore failed with X509_R_INVALID_TRUST and\nleft that error on the error stack, which was then printed via\nERR_print_errors() for every certificate loaded by the x509 app, even on\nsuccess.\n\nThe intended liberal behavior is already provided by X509_PURPOSE_ANY and\nby suppressing X509_V_ERR_CERT_REJECTED, so just remove the bogus call.\n\nAdd a test checking that printing certificate info emits nothing on stderr.\n\nAssisted-by: Claude:claude-opus-4-8\nSigned-off-by: Norbert Pocs \n\nReviewed-by: Matt Caswell \nReviewed-by: Ryan Hooper \nMergeDate: Mon Jul 27 11:50:39 2026\n(Merged from https://github.com/openssl/openssl/pull/31968)", "completion": "apps: drop invalid trust setting in check_cert_might_be_valid()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a subtest exercising the -crlnumber and -issuer print options of the\ncrl app: with a CRL that carries a CRL Number extension (printed as a hex\nvalue), with a CRL that has none (printed as ), and checking the\nprinted issuer DN in both cases.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Matt Caswell \nMergeDate: Mon Jul 27 10:15:03 2026\n(Merged from https://github.com/openssl/openssl/pull/31969)", "completion": "apps: cover the crl -crlnumber and -issuer print options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n## Summary\n\nThis PR adds v22.x and v23 release dates. It also changes Angular's release cadence to a yearly cycle.\n\n## Why we are making this change\n\nThe community has long requested less frequent major releases due to the impact of breaking changes and upgrades for their projects as well as for enterprise customers. Additionally, a longer release cycle provides increased API stability for developers using agentic workflows, while still delivering a reasonable cadence of API upgrades and migrations.\n\n(cherry picked from commit 25dbe795079d4b57ba7f334013a399aff640f5e2)", "completion": "docs: add v23 release and change to yearly release cycle"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n## Summary\n\nThis PR adds v22.x and v23 release dates. It also changes Angular's release cadence to a yearly cycle.\n\n## Why we are making this change\n\nThe community has long requested less frequent major releases due to the impact of breaking changes and upgrades for their projects as well as for enterprise customers. Additionally, a longer release cycle provides increased API stability for developers using agentic workflows, while still delivering a reasonable cadence of API upgrades and migrations.", "completion": "docs: add v23 release and change to yearly release cycle"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Tree): restore deprecated rootStyle compatibility\n\n* fix(Tree): constrain semantic style types", "completion": "fix(Tree): restore rootStyle compatibility"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nI need to make further changes, and to do so, need the documentation\nof the current functions to be a bit better organized.\n\nThis extracts the documentation for the verify parameter reference id\nsetters to a dedicated page, and cleans it up to prepare for later\nchanges in the area. It should not have any funcitonal change, it\nonly documents them as they exist today.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMergeDate: Tue Aug 18 15:17:02 2026\n(Merged from https://github.com/openssl/openssl/pull/31972)", "completion": "Extract the documentation for reference id setters"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe seeding macro logic was mixed up and incompletely applied. The\nmacro logic was also cleaned up.\n\nCo-authored-by: Paul Dale \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMergeDate: Fri Jul 17 04:47:07 2026\n(Merged from https://github.com/openssl/openssl/pull/31970)", "completion": "rand: fix jitter seed macro logic"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- keep pause state at request\n- keep presense of content decoding writers at request\n- only add cw-pause writer when content decoding happens\n- define macro for passing data down the writer chain\n\nscorecard: add option to test with h2o server\n\nCloses #22335", "completion": "lib: client writer tweaks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSupport for older versions is removed. Since we no longer support\nRHEL 7, we don't need to support these old versions anymore. This\nallows a fair amount of code cleanup, including some code blocks that\nspecifically catered to old versions that probably received very\nlittle actual testing and use.\n\nReviewed-by: Jelte Fennema-Nio \nDiscussion: https://www.postgresql.org/message-id/flat/CA+hUKGL7trhWiJ4qxpksBztMMTWDyPnP1QN+Lq341V7QL775DA@mail.gmail.com", "completion": "Require ICU 55 or later"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSupport for Tcl 8.5 and 8.4 is removed. Since we no longer support\nRHEL 7, we don't need to support these old versions anymore. This\nallows some small amount of code cleanup.\n\nReviewed-by: Jelte Fennema-Nio \nDiscussion: https://www.postgresql.org/message-id/flat/CA+hUKGL7trhWiJ4qxpksBztMMTWDyPnP1QN+Lq341V7QL775DA@mail.gmail.com", "completion": "Make PL/Tcl require Tcl 8.6 or later"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit aa7c8685234 added a workaround for _MSC_VER less than 1933,\nwhich is Visual Studio 2022 version 17.3. Since we dropped support\nfor Visual Studio before 2022, and the versions up to 17.3 are long\nEOL, we can drop this extra code.\n\nReviewed-by: Jelte Fennema-Nio \nDiscussion: https://www.postgresql.org/message-id/flat/CA+hUKGL7trhWiJ4qxpksBztMMTWDyPnP1QN+Lq341V7QL775DA@mail.gmail.com", "completion": "Drop support for _MSC_VER less than 1933"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe use of _Generic from commit \"Replace __builtin_types_compatible_p\nwith _Generic\" causes compiler errors from VS 2019. Apparently, that\ncompiler is just broken for that (even though it appears to support\n_Generic in general, for example in commit 59c2f03d1ec).\n\nPer discussion, just drop support for VS 2019 and require at least VS\n2022. This just updates the documentation about that. In passing,\nsome information about VS 2026 is added.\n\nReviewed-by: Jelte Fennema-Nio \nDiscussion: https://www.postgresql.org/message-id/flat/CA+hUKGL7trhWiJ4qxpksBztMMTWDyPnP1QN+Lq341V7QL775DA@mail.gmail.com", "completion": "Raise requirement to Visual Studio 2022"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMove X509_VERIFY_PARAM_set_hostflags() and _get_hostflags() into a\ndedicated X509_VERIFY_PARAM_set_hostflags.pod, then reorganize and\ncorrect what remains on the set_flags page (flag sections, the\nmissing SUITEB flags, and the trust/time/policy/depth descriptions).\n\nDocumentation only; no behavioural change.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMergeDate: Tue Aug 18 15:17:09 2026\n(Merged from https://github.com/openssl/openssl/pull/31972)", "completion": "Separate out the host flag documentation and tidy set_flags.pod"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nfile_lshift1() now mirrors bntest.c's file_lshift1() where OSSL_FN\nprimitives allow: it cross-checks LShift1 against A + A and A * 2,\nthen round-trips LShift1 >> 1 back to A with OSSL_FN_rshift1.\n\nThe LShift1 / 2, LShift1 % 2, and set-LSB rshift1-flooring checks\nfrom bntest.c are deferred to a future commit: they need\nOSSL_FN_div() and OSSL_FN_set_bit(), neither of which exists yet.\n\nIssue: https://github.com/openssl/project/issues/2015\nAssisted-by: Pi:z-ai/glm-5.2\nSigned-off-by: Richard Levitte \n\nReviewed-by: Igor Ustinov \nReviewed-by: Tomas Mraz \nMergeDate: Thu Jul 23 14:15:42 2026\n(Merged from https://github.com/openssl/openssl/pull/31830)", "completion": "OSSL_FN: Add lshift1 round-trip checks to fntest"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSpell out that the X509_TRUST_* selectors do not check the extKeyUsage\nextension they appear to name: they match only auxiliary trust\ninformation attached to the in-memory certificate from outside, so absent\nthat they have no effect. Mark the selector as a legacy mechanism and\npoint callers at X509_VERIFY_PARAM_set_purpose() instead.\n\nDocumentation only; no behavioural change.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMergeDate: Tue Aug 18 15:17:16 2026\n(Merged from https://github.com/openssl/openssl/pull/31972)", "completion": "Clarify the X509_VERIFY_PARAM_set_trust() documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nThe poke_eventloop() and screen:expect() sometimes don't run the test\nrunner's event loop long enough for the data to arrive at the reading\nend of the pipe. Use a screen:expect_unchanged() so that the event loop\ncan run a bit longer.\n\nFAILED ...ovim/build/Xtest_xdg_api/test/functional/api/ui_spec.lua @ 105: nvim_ui_send works with stdout_tty\nExpected values to be equal.\nExpected:\n\"\\27]11;?\\7Hello world\"\nActual:\n\"\\27]11;?\\7\"\nstack traceback:\n\t...ovim/build/Xtest_xdg_api/test/functional/api/ui_spec.lua:138: in function <...ovim/build/Xtest_xdg_api/test/functional/api/ui_spec.lua:105>", "completion": "test(api/ui_spec): fix flaky test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCoverity (CID 1696969, CHECKED_RETURN) flagged the ignored return value of\nossl_quic_srtm_remove() in ch_enqueue_retire_conn_id(). The return value\ncould not be usefully checked because 0 was overloaded to mean both \"no\nmatching entry\" and a genuine internal failure (alloc_failed or an\nlhash consistency error).\n\nGive the return value a single meaning (1 on success, 0 on internal\nerror) and report whether a matching entry was found through a new\nuint8_t *match output argument, which may be NULL if the caller does not\nneed it.\n\nResolved: https://scan5.scan.coverity.com/#/project-view/65138/10222?selectedIssue=1696969\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Bob Beck \nReviewed-by: Paul Dale \nReviewed-by: Neil Horman \nMergeDate: Tue Jul 21 09:24:45 2026\n(Merged from https://github.com/openssl/openssl/pull/31974)", "completion": "quic: report SRTM entry match status via an output argument"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22336", "completion": "http: stop dropping large custom headers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAllow the hidden utility function to be called without a configuration object to make fields permanently hidden.", "completion": "feat(forms): allow permanent hidden fields in signal forms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDrive the match matrix primarily through SAN dNSName/rfc822Name rather\nthan subject CN/emailAddress (subject setters cut to one each, decoy\nmulti-SAN variants added). Add explicit coverage of ALWAYS/NEVER_CHECK_\nSUBJECT and the non-matching-SAN-plus-matching-subject case, and a\nlong-name test for the 64/68-byte dNSName boundary and truncation guards.\n\nTest only; no behavioural change.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMergeDate: Thu Jul 30 09:11:28 2026\n(Merged from https://github.com/openssl/openssl/pull/31981)", "completion": "Rework v3nametest for SAN-first matching, add flag and long-name coverage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 67846550dc6d removed the xreflabels for initdb options, which\nturned the sentence \"The second field contains the page checksum if\ndata checksums are enabled\" into \"The second field contains the page\nchecksum if -k are enabled\", as well \"Only has effect if data checksums\nare enabled\" into \"Only has effect if -k are enabled\".\n\nFix by setting an explicit link text, and while there also change the\nlink to point to the data checksum page which has more information\nthan just the initdb option.\n\nThe original report was for one instance, further inspection turned\nup quite a few more cases. Also redirect the link in the amcheck\ndocs which albeit was reading right, but will be more helpful if\nlinking to the main page on data checksums. Backpatch to v18 where\nthe xreflabels were removed.\n\nAuthor: Daniel Gustafsson \nReported-by: y.saburov@gmail.com\nReviewed-by: Laurenz Albe \nDiscussion: https://postgr.es/m/178350739237.73862.4549076173872335741@wrigleys.postgresql.org\nBackpatch-through: 18", "completion": "doc: Fix link text for data checksums"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ndo_x509_check() now matches the subject commonName (host checks) and\nemailAddress (email checks) only when X509_CHECK_FLAG_ALWAYS_CHECK_SUBJECT\nis set, rather than whenever no matching subjectAltName is present.\n\nUpdate v3nametest to request ALWAYS_CHECK_SUBJECT for its subject-DN cases.\n\nFixes: openssl/project#1897\n\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMergeDate: Wed Aug 26 15:21:48 2026\n(Merged from https://github.com/openssl/openssl/pull/31982)", "completion": "Stop consulting the subject DN by default in X509 name checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCo-authored-by: Matthieu Riegler \n\nPR Close #69822", "completion": "docs: modernize directives guides"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22338", "completion": "http: avoid length underflow in Curl_compareheader"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe regression test for postgres_fdw_get_connections(true) assumed that\na terminated remote connection would still remain visible in the FDW\nconnection cache long enough to be reported as closed with a nonzero\nremote_backend_pid.\n\nThat assumption is not always valid. postgres_fdw_get_connections()\nreports only entries that are still present in ConnectionHash, while\npgfdw_inval_callback() may immediately discard an idle cached connection\n(xact_depth == 0) when a relevant invalidation arrives. In CI, that can\nhappen between terminating the remote backend and querying\npostgres_fdw_get_connections(true), causing the function to return no\nrows.\n\nAdjust the idle-connection test to accept either outcome: if the cache\nentry is still present, verify that it reports the expected server name,\nclosed status, and nonzero remote backend PID; otherwise treat zero rows\nas a legitimate result.\n\nTo preserve coverage of the terminated-backend reporting path, add a\nseparate check inside an explicit transaction. In that case, concurrent\ninvalidation may mark the connection invalid but cannot discard it\nbefore transaction end, so postgres_fdw_get_connections(true) should\nstill report the terminated connection as in-use, closed, and associated\nwith a nonzero remote backend PID.\n\nBackpatch to v18, where the affected postgres_fdw_get_connections(true)\ntest was introduced.\n\nReported-by: Robert Haas \nAuthor: Fujii Masao \nReviewed-by: Robert Haas \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CA+Tgmoax3cHXHsm9OidN4F-xiu16y8q2W8T5dTNFic1Zoo2cOw@mail.gmail.com\nBackpatch-through: 18", "completion": "postgres_fdw: stabilize terminated-connection regression tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit d4a657b0a4d added a call to has_sequence_privilege() while\nfetching sequence information from the publisher, so that\npublisher-side permission failures could be distinguished from missing\nsequences. It also assumed that has_sequence_privilege() could never\nreturn NULL, and asserted accordingly.\n\nHowever, that assumption was incorrect. If a sequence is dropped after\nthe synchronization worker collects its metadata but while fetching the\nsequence information, has_sequence_privilege() can return NULL.\nThis can trigger the assertion failure. This was also reported in\na buildfarm failure on member culicidae.\n\nFix this by treating a NULL result from has_sequence_privilege() as\nindicating that the sequence was dropped concurrently, and report it as\na missing sequence instead of asserting that the result is never NULL.\n\nReported-by: Noah Misch \nAuthor: Vignesh C \nReviewed-by: Hayato Kuroda \nReviewed-by: Zsolt Parragi \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com\nDiscussion: https://postgr.es/m/CALDaNm2fHGLeiQKj0r6OG7N9QeayxSmpLrWYJRyt4dL_m3VRWw@mail.gmail.com\nBackpatch-through: 19", "completion": "Handle concurrent sequence drops during synchronization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nProcess these just like the adjacent loop for expressions in regular\nindex columns. This logic was originally omitted because there was\nno intention of supporting index expressions in INCLUDING.\nThere's still no near-term intention of that, but without this change\nthe ChooseIndexExpressionName code added by 181b6185c spits up on\nexpressions in INCLUDING: that expects to handle parse-transformed\nexpressions, and it runs before we reach the place that is currently\nsupposed to throw the \"not supported\" error. We could fix this\nproblem in other ways, but this way avoids contorting the logic,\nand it results in less code to be revised not more if we ever get\naround to supporting INCLUDING expressions.\n\nReported-by: Maaz Syed Adeeb \nAuthor: Tom Lane \nTest-authored-by: Maaz Syed Adeeb \nDiscussion: https://postgr.es/m/CAG+FJqOxYj=sVyHcys64h9DbvzP6EUPGHJ7oKj-PW=Qp5Ebk_g@mail.gmail.com", "completion": "In transformIndexStmt, transform index expressions in INCLUDING."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nA value whose first byte is ':' or '<' is not a SAFE-INIT-CHAR per RFC\n2849 and must be base64-encoded, but ldap_value_needs_base64() and the\ninline check in oldap_recv() only encoded on a control byte or\nleading/trailing blank. Such a value was emitted verbatim, producing\nLDIF that strict parsers reject.\n\nCloses #22339", "completion": "ldap: base64-encode LDIF values beginning with colon or less-than"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(demo): migrate styles from markdown to CSS-in-JS\n\n* update snap\n\n* update snap\n\n* update snap\n\n* update snap\n\n* update snap\n\n* update", "completion": "refactor(demo): migrate styles from markdown to CSS-in-JS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThird-party directory browsers do not have a documented way to take over local\ndirectory buffers from nvim.dir.\n\nSolution:\nDocument deleting the nvim.dir augroup and handling FileType directory as the\nafter-startup handoff, and avoid installing the built-in buffer-local \"-\" mapping\nwhen \"-\" is already mapped.", "completion": "fix(dir): custom 3P directory-browser #40725"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nuuidv7(interval) shifts the current time by the given interval before\nencoding it into the 48-bit Unix-millisecond timestamp field of the\ngenerated UUID. Two cases were mishandled:\n\nAn infinite interval ('infinity' or '-infinity') produced an infinite\ntimestamp, which overflowed during the conversion to Unix-epoch\nmicroseconds and yielded a garbage UUID. Reject infinite intervals up\nfront, before any timestamp arithmetic.\n\nA shift that moved the timestamp outside the range representable by\nthe 48-bit field was silently accepted. Timestamps before the Unix\nepoch wrapped when cast to unsigned, and timestamps beyond\napproximately year 10889 overflowed the field; both produced UUIDs\nwith bogus timestamps that break sort ordering. Reject any shifted\ntimestamp outside the supported range.\n\nAlso document that infinite intervals and out-of-range shifts are\nrejected.\n\nAlthough raising a new error changes behavior in a stable branch, this\nis back-patched to 18 (where uuidv7(interval) was introduced) because\nthe previous behavior can silently corrupt data. Failing loudly is far\nsafer than silently accepting the wraparound; otherwise users may not\ndiscover that their UUIDv7 values are no longer sortable until years\nlater, when recovery is painful. It also matches how PostgreSQL\nalready handles timestamp + interval overflow, which raises an\nerror. The change only affects applications passing an interval large\nenough to push the result outside the representable range.\n\nBackpatch to 18, where uuidv7(interval) was introduced.\n\nReported-by: Christophe Pettus \nAuthor: Baji Shaik \nReviewed-by: Masahiko Sawada \nReviewed-by: Zsolt Parragi \nReviewed-by: Tristan Partin \nReviewed-by: Kyotaro Horiguchi \nDiscussion: https://www.postgresql.org/message-id/799A70FA-6E5C-4118-99EB-2FBBE1CBAC54@thebuild.com\nBackpatch-through: 18", "completion": "Reject infinite and out-of-range interval shifts in uuidv7()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCrash recovery running with wal_level='minimal' can replay an\nXLOG_LOGICAL_DECODING_STATUS_CHANGE record that activates logical\ndecoding, if the server previously ran with a higher wal_level and\ncrashed after the last logical slot was dropped but before the\ncheckpointer deactivated logical decoding. Replaying such a record is\ncorrect since it reflects the status at the time it was\nwritten. However, UpdateLogicalDecodingStatusEndOfRecovery() asserted\nthat logical decoding is never active with wal_level='minimal',\ncausing an assertion failure at the end of recovery. In production\nbuilds, logical decoding would remain active while running with\nwal_level='minimal'.\n\nInstead of special-casing wal_level='minimal', recompute the status at\nthe end of recovery as usual: no logical slot can exist with\nwal_level='minimal' as RestoreSlotFromDisk() would have rejected it,\nso the recomputation always deactivates logical decoding in this case,\nalso writing the corresponding status change record.\n\nOversight in 67c20979ce7.\n\nReviewed-by: Guoqing Yang \nReviewed-by: Hayato Kuroda \nDiscussion: https://postgr.es/m/CAD21AoAnPAugUnDic+ESvrfXjXHk2bss9eHAD7zP0-Chy2UabA@mail.gmail.com\nBackpatch-through: 19", "completion": "Correct logical decoding status at end of recovery with minimal WAL level."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe logical decoding status is stored in checkpoint records and used\nto restore the status at server startup, but pg_controldata did not\nshow it. This information is useful for diagnosing issues around the\ndynamic activation and deactivation of logical decoding.\n\nOversight in 67c20979ce7.\n\nReviewed-by: Guoqing Yang \nReviewed-by: Hayato Kuroda \nDiscussion: https://postgr.es/m/CAD21AoAnPAugUnDic+ESvrfXjXHk2bss9eHAD7zP0-Chy2UabA@mail.gmail.com\nBackpatch-through: 19", "completion": "pg_controldata: Show logical decoding status."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nNormalize value-specific HttpHeaders deletions before filtering. The string overload previously used String#indexOf and removed shorter values contained within the requested deletion value, potentially widening outgoing request metadata.\n\nPreserve delete-all behavior only when no value is supplied, and cover string, array, and empty-string deletion.", "completion": "fix(http): match header values exactly when deleting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nNormalize value-specific HttpHeaders deletions before filtering. The string overload previously used String#indexOf and removed shorter values contained within the requested deletion value, potentially widening outgoing request metadata.\n\nPreserve delete-all behavior only when no value is supplied, and cover string, array, and empty-string deletion.\n\n(cherry picked from commit f33ee95045ac3ab1e96baa41f44dd130ef3724ab)", "completion": "fix(http): match header values exactly when deleting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nDefensively make sure that all hash index atomic actions use a fake LSN\nwith an unlogged relation.\n\nOversight in commit e5836f7b, which added fake LSN support to the hash\nindex AM, but missed log_split_page.\n\nAuthor: Peter Geoghegan \nReviewed-by: Ewan Young \nDiscussion: https://postgr.es/m/CAH2-WzkC-opX8iS6X=a470DDC31er_x5rzPw=HjRxha9N8brZw@mail.gmail.com\nBackpatch-through: 19", "completion": "Use fake LSNs consistently in hash index AM."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSince 457ac0331cd3, current_user() is the recommended way to get access\nto this information, and getpgusername() was marked as deprecated since,\nwithout being documented.\n\nBump catalog version.\n\nReported-by: Thom Brown \nDiscussion: https://postgr.es/m/CAA-aLv44sPoKhHZqBvhqRdrFUEKwatGEmXBtqC360UuD5Lt7Nw@mail.gmail.com", "completion": "Remove SQL function getpgusername()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit c7aeb775 rewrote the HOT-chain offset sanity checks in three\nplaces, but in heap_get_root_tuples it accidentally tested offnum -- the\nouter loop variable, which is already bounded by the loop condition --\ninstead of nextoffnum, the offset actually passed to PageGetItemId. The\npre-c7aeb775 check tested nextoffnum.\n\nWith the check ineffective, a stale t_ctid could make PageGetItemId read\npast the end of the line pointer array (which is data corruption that we\nexpect to be able to catch here).\n\nAuthor: Peter Geoghegan \nReported-by: Konstantin Knizhnik \nDiscussion: https://postgr.es/m/87c7d8a4-3a82-4334-bee6-e8c2ad3f3293@garret.ru\nBackpatch-through: 15", "completion": "Fix wrong variable offset sanity check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe previous text claimed that once the slot is disassociated with\nALTER SUBSCRIPTION ... SET (slot_name = NONE), DROP SUBSCRIPTION \"will no\nlonger attempt any actions on a remote host\". That is inaccurate:\nDROP SUBSCRIPTION may still connect to the publisher to drop\ninternally-created table synchronization slots when some table\nsynchronization is left unfinished. Reword to describe this, and note\nthat if the publisher is unreachable those slots (and the main slot, if\nit still exists) must be dropped manually to avoid indefinitely reserving\nWAL.\n\nReported-by: Jeff Davis \nAuthor: Amit Kapila \nBackpatch-through: 14\nDiscussion: https://postgr.es/m/CAA4eK1+tyYSpPxMBy1974kjivuGeR7YY=yopwRGrK3+vCTysdg@mail.gmail.com\nDiscussion: https://postgr.es/m/D908370F-2695-4231-851D-17179A6A6F2A@gmail.com", "completion": "Doc: Clarify DROP SUBSCRIPTION behavior after SET (slot_name = NONE)."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStore the trigger kind before each switch and assign the value to `never` in the fallback branch.\n\nThis removes the `any` casts and makes the switches exhaustive. Adding a new `DeferTriggerKind` without handling it in either phase now produces a TypeScript compilation error.\n\nRuntime behavior and error messages remain unchanged.\n\n(cherry picked from commit 8201cebc49c2d43307731191479749fb4dc3e854)", "completion": "refactor(compiler): enforce exhaustive defer trigger handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStore the trigger kind before each switch and assign the value to `never` in the fallback branch.\n\nThis removes the `any` casts and makes the switches exhaustive. Adding a new `DeferTriggerKind` without handling it in either phase now produces a TypeScript compilation error.\n\nRuntime behavior and error messages remain unchanged.", "completion": "refactor(compiler): enforce exhaustive defer trigger handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd file_modinv() to bntest.c, driven by a new bnmodinv.txt corpus and\nwired into 10-test_bn.t.\n- Positive tests assert equalBN and a mult sanity check\n- Negative tests assert NULL return plus the BN_R_NO_INVERSE error\nCorpus covers:\n- in-range A\n- out-of-range A\n- positive and negative A for both of the above\n- degenerate moduli M = 0 and M = 1\n- RFC 4754 sourced KATs\n- RFC 7091 sourced KATs\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Tim Hudson \nReviewed-by: Richard Levitte \nMergeDate: Thu Jul 23 14:20:08 2026\n(Merged from https://github.com/openssl/openssl/pull/31985)", "completion": "[test] bntest: add ModInv file tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Typography): restore ellipsis Tooltip popup interaction\n\n* fix(Typography): delay Tooltip restore after actions hover", "completion": "refactor(Typography): simplify ellipsis Tooltip control"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n- Add wheel prop to PreviewType for controlling mouse wheel zoom\n- Add wheel prop to PreviewGroupType for preview group\n- Set default value to true to keep backward compatibility", "completion": "docs(Image): add wheel prop for mouse wheel zoom control"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFilter out `#ifdef` line changes when analyzing C files (*.c, *.h)\nvia git \"-I\" flag.\n\n```\n-I\n--ignore-matching-lines=\nIgnore changes whose all lines match . This option may be specified more than once.\n```\n\n- https://git-scm.com/docs/diff-options#Documentation/diff-options.txt--Iregex", "completion": "build(vim-patch): '#ifdef FEAT_' tweaking is N/A #40785"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe data checksums launcher and workers were exposed in pg_stat_io\nwith the same broad set of object/context combinations as general\nbackground workers. However, several of those entries can never\naccumulate I/O statistics for these processes, such as bulkwrite,\nrelation init, temporary relation, and launcher vacuum entries.\n\nTeach pgstat_tracks_io_object() and pgstat_tracks_io_op() about the\nactual I/O performed by the data checksum processes. Keep the entries\nneeded for catalog scans, including bulkread catalog scans, worker\nrelation processing with a vacuum access strategy, and WAL writes and\ninitialization, while excluding WAL reads and other object/context\ncombinations that can never be used.\n\nAuthor: Fujii Masao \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAHGQGwHz_-nt+YkHDMRZNBZrnoHro8cMOgSwuXEmSYT6vxgQ=w@mail.gmail.com\nBackpatch-through: 19", "completion": "Restrict pg_stat_io entries for data checksum processes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFix chunk allocations by reusing existing empty chunks when a new offset\nis needed. Before this fix, spbsets would only ever grow with added\nnumbers outside the range of existing chunks.\n\nCloses #22340", "completion": "uint-spbset: reused empty chunks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit e1d917182 added support for base64url encoding, a base64 variant\nintended to be safe for usage in URLs and filenames. The padding rules\nfor base64url and base64 differ in that base64url require no extra '='\npadding, but the commit unintentionally relaxed this requirement for\nbase64 as well. Fix by making sure that the truncation logic check\nfor the encoding and add a test to make sure.\n\nBackpatch down to v19 where support for base64url was introduced.\n\nAuthor: Daniel Gustafsson \nReviewed-by: David E. Wheeler \nDiscussion: https://postgr.es/m/3258FC72-F5E1-40B9-B5D7-64478CAF7728@yesql.se\nBackpatch-through: 19", "completion": "Fix truncation rules for base64 encoding"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe identifier \"order\" needs to be quoted, just like in the example a\nlittle bit earlier.\n\nAuthor: Thom Brown \nDiscussion: https://www.postgresql.org/message-id/CAA-aLv4xyAaxm8vq5LEhznh-SGphs4wUAGC6Vpas%2B1hHZzzD7A%40mail.gmail.com", "completion": "doc: Fix SQL quoting in example"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRenumber OSSL_FN_RAND_TOP_ANY / _ONE / _TWO from -1 / 0 / 1 to\n0 / 1 / 2, so each value is the number of high bits the result is\nforced to set. This matches the already-count-based\nOSSL_FN_RAND_BOTTOM_* (0 = unconstrained, 1 = force the low bit),\nmaking the whole selector family read the same way.\n\nThis is a deliberate departure from the BN counterpart: BN_RAND_TOP_*\nstays -1 / 0 / 1, but OSSL_FN_RAND_TOP_* has no legacy tier and no\nneed for a sentinel, so the values are the counts themselves.\nCallers that use the symbolic macros are unaffected; only raw-literal\ncallers would notice, and there are none in tree.\n\nAssisted-by: Pi:z-ai/glm-5.2\nSigned-off-by: Richard Levitte \n\nReviewed-by: Igor Ustinov \nReviewed-by: Tomas Mraz \nMergeDate: Thu Jul 23 14:17:18 2026\n(Merged from https://github.com/openssl/openssl/pull/31959)", "completion": "OSSL_FN: Make RAND top selector count-based"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: babel\nChanges:\n* fix(register): do not inherit parent execArgv\n\nPer https://nodejs.org/api/worker_threads.html#launching-worker-threads-from-preload-scripts, new Worker threads will inherit command line flags, including `-e` and `-r`.\n\nWhen they are combined with the `--input-type`, Node.js somehow hangs and the worker does not start.\n\n* feat: resolve token in process tests\n\n* add tests\n\n* fix: ensure args are always string\n\n* replace rootDir by file:// url\n\n* test: use for --import tests", "completion": "fix(register): do not inherit parent execArgv"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nThe dev + prod esm-browser builds are useful for direct browser/CDN\nusage of @vue/reactivity, so publish them again instead of building\nthe prod bundle on demand for benchmarks only.", "completion": "build(reactivity): restore published esm-browser bundles"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- compiler-dom, runtime-dom: esm-only published output; remove the\n unpkg/jsdelivr fields since there is no browser-loadable bundle left\n- reactivity: point unpkg/jsdelivr at the esm-browser build instead\n- size-global: build each target separately so runtime-dom and\n compiler-dom global prod sizes stay tracked via the on-demand\n single-target format override in build.js (bundles are no longer\n published but remain the size-regression signal per package)\n- buildOptions.name kept: scripts/dev.js still uses it for local\n global-format dev builds", "completion": "build: drop global/iife bundles for all packages except vue"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe Transfer State and signal-graph tabs render bare-text placeholders\nwhen there's nothing to show. Add the Angie mascot to both, matching the\npattern already shipped on the top-level DevTools screens (#69786):\n\n- Transfer State \"isn't using Transfer State\" card: replace the\n swap_horiz icon with the teaching pose.\n- Signal graph \"No signals in this component\": add the orthos-back pose\n above the message.", "completion": "feat(devtools): show Angie on tab empty states"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nUnfortunately the combination of gcc, precompiled headers, ccache and meson\ncurrently is not safe without further options. The dependencies emitted by gcc\nare insufficient to trigger rebuilds when headers \"below\" the precompiled\nheaders are changed. Whether that's a ccache, gcc or meson bug is\ndebatable. Luckily gcc's -fpch-deps option fixes the issue.\n\nThis problem occasionally leads to build failures, e.g. if only c.h,\npostgres.h or pg_config_manual.h change. That's e.g. the case when creating a\nnew major version branch.\n\nReviewed-by: Nazir Bilal Yavuz \nReviewed-by: Jelte Fennema-Nio \nDiscussion: https://postgr.es/m/CAN55FZ0tqR6Xz%3DiVFLc1BBoLOEHU775ARhcGYwggHA3XLA%3DoQg%40mail.gmail.com\nDiscussion: https://postgr.es/m/CA+hUKG+s7Yvt0PUnSQUEjCjysV-7-51n9B1h468Le3VJi0x4ZQ@mail.gmail.com\nDiscussion: https://postgr.es/m/phsrssp75npoyalqsolcd7fmnmlbzbmquc2p7w7mqjlw7432jk@bzskz3luyjvb\nDiscussion: https://github.com/ccache/ccache/issues/1686\nBackpatch-through: 16, where meson support was added", "completion": "meson: Fix ccache issues when using precompiled headers with gcc"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis configures cdb.exe to log all crashes to\n\"\\crashlogs\\crashlog-.txt\" (as it was previously set up\nfor cirrus-ci based CI). The upload logs step already collects these logs.\n\nThe logic is copied from the generation of Postgres CI Windows images for\ncirrus-ci [1]. Since this would be too long to include inline in pg-ci.yml,\nit is implemented as 'src/tools/ci/gha_setup_windows_debugger.ps1' script.\n\n[1] https://github.com/anarazel/pg-vm-images/blob/main/scripts/windows_install_dbg.ps1\n\nAuthor: Nazir Bilal Yavuz \nReviewed-by: Andres Freund \nDiscussion: https://postgr.es/m/CAN55FZ1BgsXSTzOpehnMa4NzWL8Aivsxx-di7-VT6bZ3j2Omow%40mail.gmail.com\nDiscussion: https://postgr.es/m/iggjozfshwbqpv33x5jqwtju5k5zrkyu3257dlifxkhtpg7eoq@k2ccyrdi5dtu\nBackpatch-through: 19, where GHA CI was added", "completion": "ci: Generate crashlogs on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe test runtime dominates over the compile time on GHA. Note that we just\nneed to remove options, as postgres's default is debugoptimized.\n\nReviewed-by: Nazir Bilal Yavuz \nDiscussion: https://postgr.es/m/a2ejn7lfqolutzz7kozalbhy3bixdrujb4buc3pgbtlk4am2ba@wbv6v7riia33\nBackpatch-through: 19, where GHA CI was added", "completion": "ci: Use optimized build for mingw"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(demo): migrate styles from markdown to CSS-in-JS\n\n* update", "completion": "refactor(demo): migrate styles from markdown to CSS-in-JS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCoverity flagged a location where we didn't check this return code, fix\nit up.\n\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1696759\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Jul 23 08:24:22 2026\n(Merged from https://github.com/openssl/openssl/pull/31992)", "completion": "Add return check to OSSL_DECODER_up_ref"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a cmocka based unit test for the file BIO covering BIO_new_file,\nBIO_new_fp and the file method callbacks, with stdio and openssl_fopen.\n\nAdditionally add a Windows-only Detours based side test for the\nWindows specific branches.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Andrew Dinh \nMergeDate: Sat Aug 8 15:26:34 2026\n(Merged from https://github.com/openssl/openssl/pull/31991)", "completion": "Add BIO bss_file test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFixes #25919\n\nReplace EVP_get_cipherbynid()/EVP_get_digestbynid() with\nEVP_CIPHER_fetch()/EVP_MD_fetch() when building SMIMECapabilities\nattributes, so that only algorithms available in the active providers\nare advertised. This prevents RC2, DES, and GOST from appearing by\ndefault when only the default provider is loaded.\n\nAdd CMS_add_standard_smimecap_ex() as a provider-aware replacement\nfor the newly-deprecated CMS_add_standard_smimecap().\n\nAdds missing documention and new unit-tests validating the new behavior.\n\nSigned-off-by: Todd Short \n\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Jakub Zelenka \nMergeDate: Mon Aug 3 07:06:44 2026\n(Merged from https://github.com/openssl/openssl/pull/31990)", "completion": "CMS/PKCS7: use EVP_CIPHER_fetch() for SMIMECapabilities"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a file_modinv() stanza handler to test/fntest.c, exercising\nOSSL_FN_mod_inverse() through the BIGNUM/OSSL_FN bridge. It reuses\nthe bntest ModInv corpus (test/recipes/10-test_bn_data/bnmodinv.txt),\nso 11-test_fn.t now feeds that file to fntest.\n\nThe handler mirrors bntest's file_modinv(): a ModInv value of -1 marks\na negative test that expects OSSL_FN_mod_inverse() to fail with\nOSSL_FN_R_NO_INVERSE (covering a == 0, non-coprime pairs, and the\ndegenerate moduli M = 0 and M = 1), while a non-negative ModInv is\nchecked against the computed inverse and verified by A * inv(A) == 1\n(mod M).\n\nOSSL_FN is unsigned, so OSSL_FN_mod_inverse() computes the inverse of\n|A|; for negative A the result is adjusted to M - r before the\ncomparison, matching the sign convention of the corpus.\n\nAssisted-by: Pi:z-ai/glm-5.2\n\nReviewed-by: Igor Ustinov \nReviewed-by: Tomas Mraz \nMergeDate: Fri Jul 31 09:32:20 2026\n(Merged from https://github.com/openssl/openssl/pull/32027)", "completion": "OSSL_FN: Add mod_inverse stanza tests to fntest"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit ed5dcc0edf2ebea02c4c5d667a612cd6fb23cf81)", "completion": "fix(restart): messages EXX error codes #40759"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nExpanding an unknown ~user path falls back to the shell. In a fast event,\nthis re-enters the event loop and aborts Nvim.\n\nSolution:\nLeave unknown users unexpanded when the system account lookup fails.", "completion": "fix(path): avoid shell fallback for unknown users #40757"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCoverity caught some potential overflows in do_name_ex. Seems unlikely\nto occur, but lets just do all the adds under safe_math to ensure we\ndon't overflow our buffer length.\n\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1695278\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Jul 23 08:24:23 2026\n(Merged from https://github.com/openssl/openssl/pull/31992)", "completion": "use safe_math on do_name_ex"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nNot easy for one UI to kick the others off a shared Nvim server.\n\nSolution:\nTreat `:%detach` as detach-other-UIs.", "completion": "feat(ui): \":%detach!\" detaches all other UIs #39216"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAn index-only scan filled its result slot from the HeapTuple an index AM\nreturns in scan->xs_hitup by deforming it with the virtual slot's own\ntuple descriptor (during GiST and SP-GiST index-only scans). But index\nAMs form that heap tuple using their own descriptor, scan->xs_hitupdesc.\nThe AM's descriptor may disagree with the IoS virtual slot's descriptor\nabout each column's precise alignment, leading to \"can't happen\" errors\nin certain rare edge cases. Hard crashes were possible but much less\nlikely.\n\nTo fix, deform the tuple with the descriptor it was formed with. This\nis simpler, and makes xs_hitup handling (used by GiST and SP-GiST)\nuniform with the nearby existing xs_itup handling (used by nbtree).\n\nIn practice this issue was very unlikely to be hit (it was found during\ntesting of a patch that will change the table AM API used during index\nscans). The only currently affected core opclass is GiST's range_ops.\nIt was only possible for the datum to be accessed at an incorrectly\naligned offset when reading the second or subsequent column from a\nmulticolumn GiST index. This couldn't happen in the common case where\nthe datum used an unaligned short varlena header. Moreover, an earlier\ncolumn had to leave the range datum at an offset where the two\nalignments actually disagree (e.g., an odd-length varlena datum).\n\nAuthor: Peter Geoghegan \nReviewed-by: Tomas Vondra \nDiscussion: https://postgr.es/m/CAH2-WzkGXa2SKnebdW29RT1hCcQBo_p03v3iqif2u9bjzLB-aQ@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix GiST index-only scan column alignment issue."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nReported-by: Jacob Champion\n\nAuthor: Jacob Champion\n\nDiscussion: https://postgr.es/m/CAOYmi+k5h_w5p6HsVJF5k+bNGmChMAhpGU_1gjJMxHg080XibA@mail.gmail.com\n\nBackpatch-through: 19", "completion": "doc PG 19 relnote: move Oauth items"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`nvim__ui_detach` was added in 85e0559d46c7 in order to implement\n`detach_others` from Lua. Using Lua in this case is doing more harm than\ngood.\n\nSolution:\nExtract `ui_detach_channel`, which also allows it to be used for the\n\"self detach\" path from `ex_detach`.\n\nBonus: the old MSWIN path always called `os_swap_to_hidden_console()`;\nnow `ui_detach_channel` only does so for a stdio channel. For the common\nstdio TUI this is identical; for a socket UI it's more correct (no\nparent console to swap).", "completion": "refactor(detach): eliminate `nvim__ui_detach` #40793"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nTest still unreliable.\n\nSolution:\nDon't require both 'busy' pulses to coincide.\n\nfollowup to #40775", "completion": "test: unreliable \"bumps 'busy' on each watched buffer\" #40794"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit ed62d26caca fixed a bug in clearing the visibility map and, while\ndoing so, made some incidental changes to visibilitymap_clear(). One of\nthem replaced the error thrown when the wrong buffer is passed to\nvisibilitymap_clear() with an Assert().\n\nWhile anyone adding a new visibilitymap_clear() caller should be running\nassert-enabled builds, visibilitymap_set() still reports the same\nwrong-buffer condition with an elog(ERROR), so visibilitymap_clear()\nshould also do so for consistency. This change was also unrelated to\nthe bug fix and is better made as a separate commit. Restore the error.\n\nReported-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwF_PzOv5y7ucFh7Fqqqa8ar83zYwvWugqarRD6%2B7GCtEQ%40mail.gmail.com\nBackpatch-through: 19", "completion": "Turn visibilitymap_clear() Assert back into an error"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe Angie illustrations on the DevTools empty-state screens (added in\n#69786) shipped with an empty `alt` and `aria-hidden=\"true\"`. Give them\ndescriptive alt text and drop `aria-hidden` to improve accessibility.\n\n(cherry picked from commit 00699f3e66bf5b1a48590410c2390f95a7988950)", "completion": "refactor(devtools): add alt text to the empty-state screen illustrations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe Angie illustrations on the DevTools empty-state screens (added in\n#69786) shipped with an empty `alt` and `aria-hidden=\"true\"`. Give them\ndescriptive alt text and drop `aria-hidden` to improve accessibility.", "completion": "refactor(devtools): add alt text to the empty-state screen illustrations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit b3d26e438a (\"merge feature/removesslv3\", PR #29338) renamed SSL3\nerror codes to TLS equivalents and updated the string descriptions in\ncrypto/ssl_err.c (e.g. from \"ssl/tls alert bad certificate\" to\n\"tls alert bad certificate\"), but did not update the corresponding\nstrings in crypto/err/openssl.txt.\n\nThis caused a latent divergence: running mkerr.pl -rebuild would\nregenerate ssl_err.c with the old openssl.txt strings, undoing the\nintentional name cleanup. Similarly, adding any new SSL error code\ntriggers a full SSL regeneration that would revert the strings and\nreorder entries to their correct alphabetical positions, producing\nspurious changes unrelated to the new code.\n\nUpdate openssl.txt to match the strings already in ssl_err.c, which\nalso happen to be the auto-generated strings derived from the reason\ncode names. Regenerate ssl_err.c and sslerr.h with the correct\nalphabetical ordering so that future make update runs are idempotent:\nadding and removing a new SSL error code now produces only the expected\nchanges to the generated files, with no side-effect reordering or\nstring reversions.\n\nFixes: b3d26e438a (\"Rename SSL3 error codes to TLS equivalents\")\nSigned-off-by: Todd Short \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nMergeDate: Tue Jul 21 14:28:22 2026\n(Merged from https://github.com/openssl/openssl/pull/31993)\n\n(cherry picked from commit ba2f3b557a660cbe2a0fc0e99b1830cb930a090f)", "completion": "errors: fix stale string overrides in openssl.txt for renamed SSL error codes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit b3d26e438a (\"merge feature/removesslv3\", PR #29338) renamed SSL3\nerror codes to TLS equivalents and updated the string descriptions in\ncrypto/ssl_err.c (e.g. from \"ssl/tls alert bad certificate\" to\n\"tls alert bad certificate\"), but did not update the corresponding\nstrings in crypto/err/openssl.txt.\n\nThis caused a latent divergence: running mkerr.pl -rebuild would\nregenerate ssl_err.c with the old openssl.txt strings, undoing the\nintentional name cleanup. Similarly, adding any new SSL error code\ntriggers a full SSL regeneration that would revert the strings and\nreorder entries to their correct alphabetical positions, producing\nspurious changes unrelated to the new code.\n\nUpdate openssl.txt to match the strings already in ssl_err.c, which\nalso happen to be the auto-generated strings derived from the reason\ncode names. Regenerate ssl_err.c and sslerr.h with the correct\nalphabetical ordering so that future make update runs are idempotent:\nadding and removing a new SSL error code now produces only the expected\nchanges to the generated files, with no side-effect reordering or\nstring reversions.\n\nFixes: b3d26e438a (\"Rename SSL3 error codes to TLS equivalents\")\nSigned-off-by: Todd Short \n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nMergeDate: Tue Jul 21 14:28:22 2026\n(Merged from https://github.com/openssl/openssl/pull/31993)", "completion": "errors: fix stale string overrides in openssl.txt for renamed SSL error codes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe DTLS unknown-record-type tests in 70-test_sslrecords.t checked only\nthat s_client exited non-zero, which does not distinguish a genuine\nrejection of the record from an unrelated failure (or a crash).\n\nCapture s_client's stdout+stderr in TLSProxy and parse the alerts it\nlogs via the -msg message callback, exposing them through new accessors:\nclientoutput, client_alerts and client_sent_fatal_alert(). The check\nreflects the alert s_client generated locally and so does not depend on\nthe peer receiving it, keeping the test deterministic.\n\nIn the DTLS cases add -msg to the client flags and assert that s_client\ngenerated the fatal unexpected_message alert and exited cleanly with a\nfailure, using a new client_failed() helper that decodes the child\nstatus so a signal death is not mistaken for a rejection. On failure\nthe captured client output is dumped for diagnostics.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Tomas Mraz \nReviewed-by: Ryan Hooper \nReviewed-by: Neil Horman \nMergeDate: Thu Sep 10 21:33:34 2026\n(Merged from https://github.com/openssl/openssl/pull/32135)", "completion": "test: assert the specific alert in DTLS sslrecords tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nÁlvaro reported offlist that his machine was passing the new-in-v19\nnls.sql test in \"make check\" but not in \"make installcheck\". On\ninvestigation, the cause turned out to be that he has LANGUAGE set in\nhis environment, and with (at least recent versions of) glibc that\noverrides LC_MESSAGES and friends, as per previous research by Bryan\nGreen. \"make check\" works because pg_regress unsets LANGUAGE before\nstarting the postmaster, but in installcheck mode we're exposed to\nthe prevailing value and we lose.\n\nWe're already hacking the value of LANGUAGE in this test for Solaris,\nso let's just extend that to unsetting LANGUAGE on every other platform.\n\nReported-by: Álvaro Herrera \nDiagnosed-by: Andrew Dunstan \nAuthor: Tom Lane \nDiscussion: https://postgr.es/m/a337896e-5bff-490b-afc9-c545f06c014c@gmail.com\nBackpatch-through: 19", "completion": "Fix yet another portability problem in new NLS test."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe msg_cb message callback used by the -msg option only recognised\nDTLSv1.0 among the DTLS versions, so DTLSv1.2 records were logged as\n\"Not TLS data or unknown version\" instead of being decoded. Add\nDTLS1_2_VERSION to the recognised version check and to the ssl_versions\nlookup table, and wrap the now-overlong condition.\n\nAdd a test that runs s_client against s_server over TLSv1.2, TLSv1.3 and\nDTLSv1.2, logging the protocol messages via -msg, and checks that every\nrecord is decoded (no \"Not TLS data or unknown version\" lines).\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Mon Jul 20 09:09:23 2026\n(Merged from https://github.com/openssl/openssl/pull/31994)", "completion": "apps: decode DTLSv1.2 records in s_client/s_server -msg output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe msg_cb message callback used by the -msg option only recognised\nDTLSv1.0 among the DTLS versions, so DTLSv1.2 records were logged as\n\"Not TLS data or unknown version\" instead of being decoded. Add\nDTLS1_2_VERSION to the recognised version check and to the ssl_versions\nlookup table, and wrap the now-overlong condition.\n\nAdd a test that runs s_client against s_server over TLSv1.2, TLSv1.3 and\nDTLSv1.2, logging the protocol messages via -msg, and checks that every\nrecord is decoded (no \"Not TLS data or unknown version\" lines).\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Tim Hudson \nReviewed-by: Paul Dale \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Mon Jul 20 09:09:07 2026\n(Merged from https://github.com/openssl/openssl/pull/31994)", "completion": "apps: decode DTLSv1.2 records in s_client/s_server -msg output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nTo ensure we do not overflow a size_t while case mapping on a 32-bit\nplatform, we need to know the maximum amount a UTF8 string can expand.\n\nCalculate that maximum while generating unicode tables as a part of\nthe update-unicode target, and output into a new header\nunicode_limits.h. Minor refactoring along the way.\n\nAdd a StaticAssertDecl to check that a MaxAllocSize text value\nexpanded by that amount would still have a length that fits in\nsize_t. (We couldn't actually create a new text value out of that, but\nwe still need to avoid overflow.)\n\nReported-by: Tom Lane \nDiscussion: https://postgr.es/m/3213927.1783950167@sss.pgh.pa.us", "completion": "Generate unicode_limits.h."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: babel\nChanges:\n* chore: fix @babel/eslint-plugin peer deps\n\n* chore: update lock file", "completion": "chore: fix @babel/eslint-plugin peer deps"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 64d4f5c4b660be112a02be104e7314e8bf264caa #20852\n\nCloses #22346", "completion": "timeval: make `Curl_freq` variable static (Windows)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: values from completionList.itemDefaults always replace the\nitem's own commitCharacters and data. Since 3.18 a server can ask for\nthem to be merged instead.\n\nSolution: Handle CompletionList.applyKind and advertise applyKindSupport.\nDrop itemDefaults once folded into the items: get_items() runs twice on\nthe same result and a Merge isn't idempotent.\n\nhttps://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/#completionItemApplyKinds", "completion": "feat(completion): support completionList.applyKind #40769"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nurxvt doesn't support resetting to default cursor style like we assumed.\nhttps://github.com/neovim/neovim/issues/38987#issuecomment-5004636437\n\nSolution:\nInstead of the reset sequence, always set it to steady block. This will\nstill be wrong for users who configured their initial cursor to\nunderline, but it's about the best we can do.\n\n(cherry picked from commit 28818702e94de0a606afb9d3fe39a76c1a37d026)", "completion": "fix(tui): urxvt reset cursor style #40800"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nurxvt doesn't support resetting to default cursor style like we assumed.\nhttps://github.com/neovim/neovim/issues/38987#issuecomment-5004636437\n\nSolution:\nInstead of the reset sequence, always set it to steady block. This will\nstill be wrong for users who configured their initial cursor to\nunderline, but it's about the best we can do.", "completion": "fix(tui): urxvt reset cursor style #40800"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIt's no longer a global variable.\n\nFollow-up to 1027d07704836c8d642abbed34ab98535de47433 #22346\n\nCloses #22347", "completion": "timeval: rename timer frequency variable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCLA: trivial\n\nReviewed-by: Andrew Dinh \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Paul Dale \nMergeDate: Thu Jul 23 08:30:57 2026\n(Merged from https://github.com/openssl/openssl/pull/31871)", "completion": "Fix capitalization of 'Swiss Army knife' in README"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that a generated key is returned separately from its generation\ncontext and that a new key-bound context is needed for subsequent\noperations. Correct the encrypt and decrypt initialization descriptions\nand examples accordingly.\n\nCorrect two copy-and-paste errors in the verify-recover documentation:\ndescribe its initializer as starting a verify-recover operation and refer\nto EVP_PKEY_verify_recover() when discussing its input.\n\nFixes #31989\n\nAssisted-by: Grok:Grok-4.5\n\nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Thu Jul 23 08:29:41 2026\n(Merged from https://github.com/openssl/openssl/pull/31995)", "completion": "docs: clarify EVP_PKEY context workflow and operation descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that a generated key is returned separately from its generation\ncontext and that a new key-bound context is needed for subsequent\noperations. Correct the encrypt and decrypt initialization descriptions\nand examples accordingly.\n\nCorrect two copy-and-paste errors in the verify-recover documentation:\ndescribe its initializer as starting a verify-recover operation and refer\nto EVP_PKEY_verify_recover() when discussing its input.\n\nFixes #31989\n\nAssisted-by: Grok:Grok-4.5\n\nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Thu Jul 23 08:29:24 2026\n(Merged from https://github.com/openssl/openssl/pull/31995)", "completion": "docs: clarify EVP_PKEY context workflow and operation descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 12e8db38471eacd12da28d42103d67619ea9af0f)", "completion": "fix(restart): distinguish v:exitreason for :restart! #40801"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- Remove old help tags: they add noise to cmdline completion.", "completion": "docs: misc, remove some old help tags #40214"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSampling a transient busy=1 pulse is racy under load.\n\nSolution:\nSet a long debounce, assert the stable state, then use a short debounce\nto let the reload clear it.", "completion": "test: unreliable \"bumps 'busy' on each watched buffer\" #40804"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n\n FAILED …/terminal/buffer_spec.lua @ 348: :terminal buffer is refreshed with partial mappings in Normal mode\n …/terminal/buffer_spec.lua:348: Row 2 did not match.\n Expected:\n |tty ready |\n |*^jjjjjjjjjj |\n | |\n | |\n | |\n | |\n | |\n Actual:\n |tty ready |\n |*^jjjjjjjjj |\n | |\n | |\n | |\n | |\n | |\n\nSolution:\nIncrease sleep time.", "completion": "test: unreliable \":terminal buffer … partial mappings\" #40806"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n\n FAILED …/put_spec.lua:894: …/put_spec.lua @ 898: put command . register special tests should ring the bell when deleting if not appropriate\n …/put_spec.lua:894: …/put_spec.lua:898: Bell was not rung after action\n\n Snapshot:\n screen:expect([[\n ^ine of words 1 |\n Line of words 2 |\n {1:~ }|*4\n {3:[No Name] [+] }|\n |\n {1:~ }|*4\n {UNKNOWN_HL_ID(4):[No Name] }|\n {UNKNOWN_HL_ID(1): }|\n ]])\n stack traceback:\n …/ui/screen.lua:917: in function '_wait'\n …/ui/screen.lua:540: in function 'expect'\n …/editor/put_spec.lua:894: in function 'bell_test'\n …/editor/put_spec.lua:940: in function <…/editor/put_spec.lua:932>\n\nAnalysis:\nThe bell was asserted via the UI 'bell' event (screen.bell), but\nvim_beep() rate-limits that to 3 per 500ms. These tests share one\nlong-lived session, so beeps from earlier tests could exhaust the window\nand drop the asserted beep.\n\nSolution:\nUse assert_beeps()/assert_nobeep(), which check called_vim_beep (set\nbefore the rate-limit gate).", "completion": "test: unreliable \"put command . register special … ring the bell\" #40812"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRSA_private_encrypt() and RSA_public_decrypt() support both PKCS#1 v1.5\nand no padding, but the migration guide currently describes their EVP\nreplacements as using no padding only.\n\nDocument direct mappings to EVP_PKEY_sign() and\nEVP_PKEY_verify_recover(), and explain that compatibility requires no\nsignature digest and the same legacy padding mode, RSA_PKCS1_PADDING or\nRSA_NO_PADDING.\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:54:00 2026\n(Merged from https://github.com/openssl/openssl/pull/31996)", "completion": "doc: clarify raw RSA migration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nremoveOverlappedRoutes builds one regex per parameterized route and\nreuses it while filtering every route. The regexes were created with the\ng flag, and a global regex advances lastIndex on a successful test(), so\nthe next call resumed mid-string and failed the ^ anchor.\n\nOverlap detection therefore depended on iteration order: with cats/:id,\ncats/1, cats/2 and cats/3, the filter kept ['cats/:id', 'cats/2'] and\nthe middleware ran twice for /cats/2.\n\nThe pattern is anchored and only ever used with test(), so the flag\nbought nothing. Without it the same input collapses to ['cats/:id'].\n\nFixes #17334", "completion": "fix(core): drop the g flag from middleware overlap regexes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNote this doesn't find new N/A patches by itself\nand this is to align with ':h dev-vimpatch'.\nI use the 'vim_na_*' files to debug the filtered diff of files\nthat seem N/A but contain relevant code.\nI can't blacklist the entire file.", "completion": "build(vim-patch): alloc.c N/A functions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSince 28179061bf a zero-length ASN1_STRING has data == NULL in\nfuzzing builds instead of a 1-byte allocation. Several call sites\ndid pointer arithmetic or memcpy on the data pointer before any\nlength check, which is undefined behaviour for NULL even with a\nzero offset and aborts the fuzz targets under UBSan:\n\n- asn1_string_canon: skip canonicalisation of empty values\n- do_buf, do_hex_dump: return early on an empty buffer\n- i2d_ocsp_nonce: skip the memcpy for an empty nonce\n\nThe loops at these sites were already no-ops for zero length, so\nthere is no behaviour change outside sanitizer builds.\n\nAssisted-By: Claude:claude-fable-5\n\nSigned-off-by: Norbert Pocs \n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMergeDate: Tue Jul 21 12:54:48 2026\n(Merged from https://github.com/openssl/openssl/pull/31998)", "completion": "Guard against NULL data in empty ASN1_STRINGs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblems:\n1. Can't get individual parts of a key-chord separately: modifiers, key.\n2. Can't separate a key-combo into individual key-chords.\n\nSolution:\nEnhance `vim.keycode()` to optionally return a structured parse result\nas a list of key-chords:\n- `key_raw` the key-chord (problem 2)\n- `mod` the modifiers of `key_raw` (problem 1)\n- `key_orig` the key part of the key-chord, only here if differing from `key`\n (this doesn't solve any of the above mentioned problems, but it may provide\n useful and it's (in terms of code) free)\n- `key` a normalized version of `key_orig` (solving problem 1), example(the\n first is `key_orig` and second is `key`): `lt` and `<`, `Bar` and `|` (in\n ``)", "completion": "feat(lua): vim.keycode() gets structured parse result #38636"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSubscription objects are conceptually database-local objects, but\npg_subscription is a shared catalog so that the launcher process can\nscan it.\n\nCheck readers of pg_subscription to ensure that, unless it's the\nlauncher process, it filters by MyDatabaseId. Most readers were\nalready doing so, but this commit fixes REASSIGN OWNED and adds guards\nto catch other problems in the future. Also, clarify documentation.\n\nAuthor: Dilip Kumar \nReported-by: Noah Misch \nReviewed-by: shveta malik \nDiscussion: https://postgr.es/m/20260710192533.4f.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Fix REASSIGN OWNED for subscriptions in other databases."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 2f094e7ac changed the parser to treat these as built-in\noperator names, where before they were just generic Op. While\nit correctly gave them the same precedence as Op and added new\nproductions to allow them to still be used as infix operators,\nit missed allowing them to still be used as prefix operators.\nAt least one extension expects to be able to do that, so add\nthe necessary productions.\n\nBug: #19558\nReported-by: Pierre Senellart \nAuthor: Pierre Forstmann \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/19558-ad1fca59a3a471a0@postgresql.org\nBackpatch-through: 19", "completion": "Restore the ability to use | and -> as prefix operators."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nfind_dependent_phvs() and find_dependent_phvs_in_jointree() decide\nwhether a PlaceHolderVar depends on the RTE_RESULT rel we're\nconsidering removing by comparing the PHV's phrels to a singleton set\ncontaining that rel's RT index, reasoning that if phrels contains any\nother relid bits then those define an appropriate place where we can\nevaluate the PHV. But since this code was originally written, we've\nredefined phrels to include outer-join relids, and that breaks this\nlogic, potentially allowing us to remove an RTE_RESULT that leaves no\nvalid place to evaluate the PHV. The planner doesn't throw an error\nwhen that happens, but it does produce an incorrect plan that will not\nreplace the PHV's value with NULL when needed.\n\nIn the known test case for this bug, the \"extra\" OJ relid is one that\nwe've actually decided to remove but haven't yet cleaned out of the\nquery's PHVs. It's not entirely clear though that that would always\nbe the case. Let's restore this code to the way it was designed to\nwork, by considering only base relids within the PHV's phrels.\n\nBug: #19553\nReported-by: Viktor Leis \nAuthor: Matheus Alcantara \nCo-authored-by: Richard Guo \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/19553-4561747f93f368a7@postgresql.org\nBackpatch-through: 16", "completion": "Fix edge case in remove_useless_result_rtes() with outer joins."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 54cd6fc83 set the version argument for the stats-import functions\nintroduced by that commit, which is of type int, using UInt32GetDatum,\nnot Int32GetDatum. This would be completely harmless as it's positive\nand currently ignored in the functions, but let's fix that code to use\nInt32GetDatum for consistency.\n\nAuthor: Etsuro Fujita \nDiscussion: https://postgr.es/m/CAPmGK14aremJGrPezVwFqWt7dnrMhD3KF1DgzsRygAUPETBU7w%40mail.gmail.com\nBackpatch-through: 19", "completion": "Further cleanup for commit 54cd6fc83."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe MCP server setup guide linked to /ai/skills, which 404s. The\npage lives at /ai/agent-skills. Update the link to point to the\ncorrect route.\n\nFixes #69838\n\n(cherry picked from commit d6cad90b3a865cbedc9575a1966192720c4014ea)", "completion": "docs: fix broken link to Angular AI Skills page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe MCP server setup guide linked to /ai/skills, which 404s. The\npage lives at /ai/agent-skills. Update the link to point to the\ncorrect route.\n\nFixes #69838", "completion": "docs: fix broken link to Angular AI Skills page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Page Not Found\" page always rendered the sentence \"We have\ninitiated a search for the term extracted from the URL\", but the\nNotFound component only runs a search when a term can be extracted,\nand only renders results when there is at least one hit. On a 404\nwith no extractable term or no matching results, the page asserted\na search it never backed up.\n\nGate the sentence behind the same searchResults() check that guards\nthe results list, so the empty state simply reads \"We couldn't find\nwhat you were looking for.\"\n\n(cherry picked from commit 79fe1c3a058a2380aabcf7b0d0cf5401425cb6bc)", "completion": "fix(docs-infra): only claim a search on the 404 page when results exist"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Page Not Found\" page always rendered the sentence \"We have\ninitiated a search for the term extracted from the URL\", but the\nNotFound component only runs a search when a term can be extracted,\nand only renders results when there is at least one hit. On a 404\nwith no extractable term or no matching results, the page asserted\na search it never backed up.\n\nGate the sentence behind the same searchResults() check that guards\nthe results list, so the empty state simply reads \"We couldn't find\nwhat you were looking for.\"", "completion": "fix(docs-infra): only claim a search on the 404 page when results exist"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNote this doesn't find new N/A patches by itself\nand this is to align with ':h dev-vimpatch'.\n\nNeovim refactored Vim's \"char/string\" functions to be either safer\n(ie. xstrlcat) or target Unicode.", "completion": "build(vim-patch): \"vim_\" char/string N/A funcs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\ntest: unreliable \"put command . register special … ring the bell\"\n\nProblem:\n\n FAILED …/put_spec.lua:894: …/put_spec.lua @ 898: put command . register special tests should ring the bell when deleting if not appropriate\n …/put_spec.lua:894: …/put_spec.lua:898: Bell was not rung after action\n\n Snapshot:\n screen:expect([[\n ^ine of words 1 |\n Line of words 2 |\n {1:~ }|*4\n {3:[No Name] [+] }|\n |\n {1:~ }|*4\n {UNKNOWN_HL_ID(4):[No Name] }|\n {UNKNOWN_HL_ID(1): }|\n ]])\n stack traceback:\n …/ui/screen.lua:917: in function '_wait'\n …/ui/screen.lua:540: in function 'expect'\n …/editor/put_spec.lua:894: in function 'bell_test'\n …/editor/put_spec.lua:940: in function <…/editor/put_spec.lua:932>\n\nAnalysis:\nThe bell was asserted via the UI 'bell' event (screen.bell), but\nvim_beep() rate-limits that to 3 per 500ms. These tests share one\nlong-lived session, so beeps from earlier tests could exhaust the window\nand drop the asserted beep.\n\nSolution:\nUse assert_beeps()/assert_nobeep(), which check called_vim_beep (set\nbefore the rate-limit gate).", "completion": "backport: test: unreliable \"put command . register special … ring the bell\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nfix(path): avoid shell fallback for unknown users\n\nProblem:\nExpanding an unknown ~user path falls back to the shell. In a fast event,\nthis re-enters the event loop and aborts Nvim.\n\nSolution:\nLeave unknown users unexpanded when the system account lookup fails.\n\n(cherry picked from commit 9d3edf345f8e25f1a7976efff54818a426661802)", "completion": "backport: fix(path): avoid shell fallback for unknown users"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nPatch 9.1.1363 is N/A after ignoring whitespace.\n\n-----\n\nUnrelated N/A patches\nvim-patch:8.1.1985: code for dealing with paths is spread out\n\nhttps://github.com/neovim/neovim/pull/36125#issuecomment-5012670153", "completion": "build(vim-patch): ignore amount of whitespace change"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBackpatch-through: 19 only", "completion": "doc PG 19 relnotes: \\crosstab to \\crosstabview"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_verify_recover() with RSA PKCS#1 v1.5 padding and no configured\nsignature digest rejected a valid signature whose recovered payload is\nempty, instead of returning success with a recovered length of zero.\n\nRSA_public_decrypt() returns -1 on error and otherwise the number of\nrecovered bytes, which may legitimately be zero for a raw PKCS#1 v1.5\nsignature that encodes an empty payload. Pull request #28306 (\"Make\nerror checks on RSA_public_decrypt() consistent\") changed the error\ncheck in the raw, no-digest verify-recover path from \"ret < 0\" to\n\"ret <= 0\", so a valid zero recovered length was mistaken for an error.\n\nRestore the \"< 0\" check in that branch only, leaving the digest-aware\nPKCS#1, X9.31, PSS and ordinary verification paths untouched.\n\nAdd test_RSA_verify_recover_empty_payload, which performs a complete\nzero-length raw PKCS#1 v1.5 sign-and-recover round trip through EVP and\nfails on the unmodified implementation specifically at the\nEVP_PKEY_verify_recover() call. OpenSSL 3.0.13 recovers the same\nsignature and reports a zero-byte result.\n\nThe behavior regressed as a result of #28306.\n\nFixes #32000\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Paul Dale \nReviewed-by: Jakub Zelenka \nMergeDate: Fri Jul 24 13:06:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32001)\n\n(cherry picked from commit 5f48317d6d847e555bf788f8b71d51ac032a6344)", "completion": "Restore empty raw PKCS#1 verify-recover behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_verify_recover() with RSA PKCS#1 v1.5 padding and no configured\nsignature digest rejected a valid signature whose recovered payload is\nempty, instead of returning success with a recovered length of zero.\n\nRSA_public_decrypt() returns -1 on error and otherwise the number of\nrecovered bytes, which may legitimately be zero for a raw PKCS#1 v1.5\nsignature that encodes an empty payload. Pull request #28306 (\"Make\nerror checks on RSA_public_decrypt() consistent\") changed the error\ncheck in the raw, no-digest verify-recover path from \"ret < 0\" to\n\"ret <= 0\", so a valid zero recovered length was mistaken for an error.\n\nRestore the \"< 0\" check in that branch only, leaving the digest-aware\nPKCS#1, X9.31, PSS and ordinary verification paths untouched.\n\nAdd test_RSA_verify_recover_empty_payload, which performs a complete\nzero-length raw PKCS#1 v1.5 sign-and-recover round trip through EVP and\nfails on the unmodified implementation specifically at the\nEVP_PKEY_verify_recover() call. OpenSSL 3.0.13 recovers the same\nsignature and reports a zero-byte result.\n\nThe behavior regressed as a result of #28306.\n\nFixes #32000\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Paul Dale \nReviewed-by: Jakub Zelenka \nMergeDate: Fri Jul 24 13:06:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32001)", "completion": "Restore empty raw PKCS#1 verify-recover behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 25a30bbd423 (IGNORE NULLS / RESPECT NULLS for window functions)\nmade ExecInitWindowAgg() treat two otherwise-equal window functions as\nduplicates only when their ignore_nulls settings also matched:\n\n if (i <= wfuncno && wfunc->ignore_nulls == perfunc[i].ignore_nulls)\n\nThat extra term reads WindowStatePerFuncData.ignore_nulls, but the field\nwas never populated when a per-function entry was filled in, so it stayed\nzero from palloc0_array(). Consequently a duplicate call carrying\nIGNORE NULLS or an explicit RESPECT NULLS never matched an identical\nearlier entry and was needlessly given its own per-function slot and\nevaluated twice. (Results stayed correct; this was a missed sharing, not\na wrong answer.)\n\nThe extra term is in fact redundant. WindowFunc.ignore_nulls is a plain\nscalar field with no pg_node_attr, so _equalWindowFunc() already compares\nit; the preceding equal() call therefore never matches two WindowFuncs\nthat differ only in null treatment. If equal() matches, ignore_nulls\nnecessarily matched too, so the term can never change the outcome, and\nWindowStatePerFuncData.ignore_nulls existed only to feed it.\n\nRather than populate the shadow field, drop the redundant term and the\nfield (and adjust the now-stale comment) and let equal() do the work.\nThat fixes the same bug while removing the hand-maintained duplicate\nstate that caused it, so it cannot silently drift again.\n\nAuthor: Chao Li \nCo-authored-by: Ewan Young \nReviewed-by: Tatsuo Ishii \nDiscussion: https://postgr.es/m/5D2C9081-5DFE-4E27-AB14-7358238EA1BC%40gmail.com\nBackpatch-through: 19", "completion": "Remove redundant null-treatment check in window function dedup."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(demo): migrate styles from markdown to CSS-in-JS\n\n* update\n\n* update\n\n* update\n\n* update", "completion": "refactor(demo): migrate styles from markdown to CSS-in-JS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* chore(demo): set transition to none when type=editable-card\n\n* update", "completion": "chore(demo): set transition to none when type=\"editable-card\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, the `pending()` status on a field's `ValidationState` only checked if the field itself or its immediate children had a pending asynchronous validator by directly inspecting `asyncErrors()`. This meant that a pending asynchronous validator deep within a nested form (e.g. on a grand-child) would not correctly bubble the `pending` state up to the root form.\n\nfixes #69840\n\n(cherry picked from commit 3497c9b943748d0f21587fcdc1482215f857fa28)", "completion": "fix(forms): ensure `pending` status propagates to the root form in signal forms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, the `pending()` status on a field's `ValidationState` only checked if the field itself or its immediate children had a pending asynchronous validator by directly inspecting `asyncErrors()`. This meant that a pending asynchronous validator deep within a nested form (e.g. on a grand-child) would not correctly bubble the `pending` state up to the root form.\n\nfixes #69840", "completion": "fix(forms): ensure `pending` status propagates to the root form in signal forms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nCID 651340: Security best practices violations (STRING_OVERFLOW)\n /src/nvim/keycodes.c: 383 in get_special_key()\n 377 data->key = *s;\n 378 data->key_alt = (String){ NULL, 0 };\n 379 }\n 380 }\n 381\n 382 if ((int)s->size + idx + 2 <= MAX_KEY_NAME_LEN) {\n >>> CID 651340: Security best practices violations (STRING_OVERFLOW)\n >>> You might overrun the 33-character fixed-size string \"string + idx\" by copying \"s->data\" without checking the length.\n 383 STRCPY(string + idx, s->data);\n 384 idx += (int)s->size;\n 385 }\n 386 }\n 387 string[idx++] = '>';\n 388 string[idx] = NUL;", "completion": "fix(coverity): STRING_OVERFLOW #40835"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nFloat border highlight groups (FloatBorder, FloatTitle and FloatFooter)\nfall back to Normal background highlight if no background color set.\n\nSolution:\nCombine border colors with window-local Normal highlight.\n\nFix #38330", "completion": "fix(ui): combine float border with window background #40796"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(demo): replace hardcoded styles with design tokens\n\n* update\n\n* update snap", "completion": "refactor(demo): replace hardcoded styles with design tokens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nnvim_create_autocmd() isn't |api-fast|, so modules that create autocmds\n(e.g. vim.treesitter.query) can't be require()d in a fast event context.\n\nSolution:\nMark it |api-fast|. Compile autocmd patterns with RE_NOBREAK so\naucmd_next() won't os_breakcheck() mid-iteration, where a fast\nnvim_create_autocmd() could realloc the autocmds vector and dangle the\ncaller's AutoPat/AutoCmd.\n\nRE_NOBREAK is low-risk because:\n- aucmd_next()'s loop checks CTRL-C: `(for (… i < apc->ausize && !got_int; …)`.\n- `line_breakcheck()` (`autocmd.c:1912`) runs once per matched autocmd.\n- Each autocmd _execution_ runs through `do_cmdline`, which has its own\n breakchecks.\n\nHowever this does admit risk of a pathological case:\na catastrophic-backtracking glob matched against a very long `User`\nevent-pattern.", "completion": "feat(api): mark nvim_create_autocmd as api-fast #40836"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* docs: Fix typos and grammar in glossary\n\n* docs: Include TypeScript config file extensions in glossary", "completion": "docs: Fix typos and grammar in glossary"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nMysterious Windows CI failure points to resource exhaustion, but we have\nno visibility/instrumentation:\n\n RUN T610 nvim_set_keymap, nvim_del_keymap can set mappings with special characters, lhs: , rhs: : 93.70 ms OK\n RUN T611 nvim_set_keymap, nvim_del_keymap can set mappings with special characters, lhs: , rhs: : 49.48 ms FAIL\n …\\testnvim.lua:144: EOF was received from Nvim. Likely the Nvim process crashed.\n stack traceback:\n D:/a/neovim/neovim/test/functional/testnvim.lua:144: in function 'nvim_set_keymap'\n …/api/keymap_spec.lua:769: in function <…/api/keymap_spec.lua:768>\n RUN T612 nvim_set_keymap, nvim_del_keymap can set mappings with special characters, lhs: , rhs: : 18.49 ms FAIL\n …\\testnvim.lua:144: EOF was received from Nvim. Likely the Nvim process crashed.\n stack traceback:\n D:/a/neovim/neovim/test/functional/testnvim.lua:144: in function 'nvim_set_keymap'\n …/api/keymap_spec.lua:769: in function <.../build/Xtest_xdg_api/test/functional/api/keymap_spec.lua:768>\n\nSolution:\nAppend the child exit-code and signal to the \"EOF … crashed\" message.\n\nExample:\n\n Nvim EOF (crash?) exit code: 42 (0x0000002A)\n\nOn the next failing Windows run, the first crash line will classify the failure:\n- 0xC0000005 → access violation (nvim bug)\n- 0xC0000374 → heap corruption (nvim bug)\n- spawn/resource error or \"clean\" exit-code → system resource exhaustion", "completion": "test: improve Nvim EOF handling (for Windows CI) #40841"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWe have 5 \"labeler\" jobs, this is kind of nuts, it bloats the CI report,\nand also introduces race conditions...\n\nSolution:\nMerge 3 jobs into 1 `label` job with multiple sequential steps.\n- Eliminates the `needs` chain\n- Drops unused `contents:write` permission.\n- GITHUB_TOKEN is scoped to the single `gh` step.\n - Note: is the automatic job token (`contents:read` + `pull-requests:write`,\n not a PAT), so worst case is PR/label mischief.\n\nThe `ai-assisted` and `request-reviewer` jobs stay separate, bc they are\ntriggered on different events (not only \"opened\").", "completion": "ci: combine PR-labeler jobs #40842"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: when PR #40621 removed a 50 cell restriction to item group\nminwid, a possible integer overflow was introduced when the added\npadding is multiplied with the number of fillchar bytes.\n\nSolution: when there is not enough buffer capacity left, reduce the\nnumber of added fillchars before calculating the number of added bytes.", "completion": "fix(statusline): prevent integer overflow with huge item groups #40837"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vitest\nChanges:\nIntroduce a `benchmark.provider` config option that lets a plugin own\nbenchmark execution end to end. A provider receives the expanded\nregistrations of a single test and returns the results Vitest reports;\nthe returned array is the sole source of results, matched to\nregistrations by name.\n\nThe built-in tinybench execution moves behind a default provider,\nselected when `benchmark.provider` is `'default'`. A custom provider is\na module path whose default export exposes `getProvider()`; it is\nresolved to an absolute path during config resolution and imported once\nper worker. `createBench` now runs every path — `bench().run()`,\n`bench.compare()`, `writeResult` and comparison storage — through the\nprovider instead of reading results back off the tinybench instance.\n\nThe benchmark name used for reporting and the getter-overuse warning now\ncomes from `options.name` when set, falling back to the full test name,\ndropping the previous per-run index suffix.", "completion": "feat(benchmark): add pluggable benchmark provider API"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblems:\nOn Windows, `:w somedir` (where somedir is an existing directory\nin pwd) shows the misleading `E13: File exists (add ! to override)`\ninstead of `E17: \"somedir\" is a directory`.\n\nSolution:\ndrop unnecessary `#ifdef` guard.", "completion": "fix(write): show E17 on all platforms #40595"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe pg_plan_advice scanner recognizes underscores as digit separators\njust like the core parser, but used strtoint() to convert occurrence\nnumbers which does not support underscores. Consequently, advice such\nas SEQ_SCAN(x#1_0) failed to parse. Fix by using pg_strtoint32_safe()\nlike the core scanner, and also add regression test coverage.\n\nThis bug was independently found and reported by Lukas Fittl and Chao\nLi. Backpatch down to v19 where pg_plan_advice was introduced.\n\nAuthor: Chao Li \nCo-authored-by: Daniel Gustafsson \nReported-by: Lukas Fittl \nReported-by: Chao Li \nReviewed-by: Daniel Gustafsson \nReviewed-by: Lukas Fittl \nDiscussion: https://postgr.es/m/22E2ECE0-B768-43D5-8575-61C3EBC2E4E8@gmail.com\nDiscussion: https://postgr.es/m/CAP53PkzKeD=t90OfeMsniYrcRe2THQbUx3g6wV17Y=ZtiwmWTQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix parsing of underscores in pg_plan_advice occurrence numbers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nA floating preview window (hover, signature help) converted to a normal\nwindow (e.g. with CTRL-W_H or nvim_win_set_config()) is still closed by\nthe open_floating_preview() autocommands, and a later preview may focus\nor close it as if it were still a float.\n\nSolution:\nWhen the preview window is no longer floating, remove its auto-close\nautocommands and stop tracking it as the buffer's floating preview.\n\nCloses #36659", "completion": "fix(lsp): preview window converted to normal window is auto-closed"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe clean target's find command intended -prune to apply to the whole\n-o chain of excluded submodule paths, but -prune only binds to the\nimmediately preceding -path, so only the last path (wycheproof) was\nactually protected from recursion. Earlier\nsubmodules (cloudflare-quiche, pkcs11-provider, etc.) were still\ndescended into, letting make clean delete vendored symlinks inside\nthem. Move -prune outside the parenthesized path list so it applies\nwhenever any excluded path matches.\n\nAssisted-by: Claude:claude-sonnet-5\nFixes: 70741ee62a50 \"Configurations/unix-Makefile.tmpl: make cleanup faster\"\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nReviewed-by: Milan Broz \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Tue Jul 21 09:21:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32006)", "completion": "Fix clean target find/-prune precedence bug"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 1e4e5783e added the src/test/modules/nbtree test module, but only\nregistered it in the meson build, not in the module list in\nsrc/test/modules/Makefile. As a result, autoconf builds never ran the\nmodule's tests.\n\nTo fix, add the module to the Makefile's lists of\ninjection-point-dependent modules.\n\nOversight in commit 1e4e5783e.\n\nAuthor: Peter Geoghegan \nReviewed-by: Michael Paquiër \nDiscussion: https://postgr.es/m/CAH2-Wz=JchiD5ksiT35p8Ar02gaNv8_y6w2wBAST+Zzen-eNjw@mail.gmail.com\nBackpatch-through: 19", "completion": "Run nbtree test module tests under autoconf builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdded documentation of the addition of group tuples in openSSL 3.5\nin HISTORY section of SSL_CTX_set1_curves.pod.\n\nCLA: trivial\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Nikola Pajkovsky \nMergeDate: Fri Jul 24 13:13:26 2026\n(Merged from https://github.com/openssl/openssl/pull/32007)\n\n(cherry picked from commit 971b8d060e52499d6ffd2f9ca697fe23f72a629a)", "completion": "Update SSL_CTX_set1_curves.pod for OpenSSL 3.5 additions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdded documentation of the addition of group tuples in openSSL 3.5\nin HISTORY section of SSL_CTX_set1_curves.pod.\n\nCLA: trivial\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Nikola Pajkovsky \nMergeDate: Fri Jul 24 13:13:26 2026\n(Merged from https://github.com/openssl/openssl/pull/32007)", "completion": "Update SSL_CTX_set1_curves.pod for OpenSSL 3.5 additions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 1df9e8d96 made remove_useless_result_rtes() compute the set of\nbaserels in the jointree, to pass down to the find_dependent_phvs()\nchecks. But those checks are no-ops when the query contains no PHVs,\nsince find_dependent_phvs() and find_dependent_phvs_in_jointree() both\nreturn early in that case. So we can avoid the\nget_relids_in_jointree() scan altogether when root->glob->lastPHId is\nzero, leaving baserels as NULL.\n\nAuthor: Richard Guo \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/CAMbWs49H275KzgZr3Cd1Hy+6Lmwp35bZ+5PrVc62k3HDLj6hNQ@mail.gmail.com\nBackpatch-through: 16", "completion": "Skip unnecessary get_relids_in_jointree() when there are no PHVs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n'ALTER SUBSCRIPTION ... REFRESH SEQUENCES' can race with a running\nsequence synchronization worker. If the worker has fetched a sequence's\nvalue from the publisher but not yet marked it READY, a concurrent refresh\nthat resets the sequence to INIT can be overwritten by the worker's stale\nvalue, silently losing the refresh request.\n\nHandle this by stopping any running sequence sync worker before resetting\nthe sequences to INIT. This is race-free because AlterSubscription()\nalready holds AccessExclusiveLock on the subscription object. That lock\nblocks a running worker's UpdateSubscriptionRelState(), which takes\nAccessShareLock on the object, and also any worker the apply worker\nre-launches, because a new worker takes AccessShareLock on the object in\nInitializeLogRepWorker() before it reads pg_subscription_rel. Such a\nworker cannot act on the sequence states until the refresh commits, by\nwhich time they are reset to INIT and it will synchronize the latest\npublisher values.\n\nReported-by: Noah Misch \nAuthor: Amit Kapila \nReviewed-by: vignesh C \nReviewed-by: Shveta Malik \nReviewed-by: Hayato Kuroda \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Handle concurrent sequence refreshes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(alert): fix wording in demos\n\n* docs(alert): fix spacing\n\n* docs(alert): fix typo\n\n* docs(Alert): improve wording", "completion": "docs(Alert): fix spacing and typos"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nUPDATE/DELETE FOR PORTION OF may insert leftover rows to preserve the\nparts of the old row that are outside the target range. Those inserts\ngo through ExecInsert(), which checks RLS policies using\nWCO_RLS_INSERT_CHECK.\n\nHowever, the rewriter only added RLS WITH CHECK options for the\noriginal statement command. For UPDATE, that meant only\nWCO_RLS_UPDATE_CHECK options were available, so ExecInsert() skipped\nthem. For DELETE, no RLS WITH CHECK options were added at all. As a\nresult, leftover rows could be inserted even when they violated INSERT\nRLS policies.\n\nFix this by adding INSERT RLS WITH CHECK options for UPDATE/DELETE FOR\nPORTION OF target relations. Also add regression coverage for both\nUPDATE and DELETE, including cases where allowed leftovers still\nsucceed and disallowed leftovers are rejected.\n\nAuthor: Chao Li \nCo-authored-by: Paul A Jungwirth \nReviewed-by: Paul A Jungwirth \nReviewed-by: Ayush Tiwari \nReviewed-by: Dean Rasheed \nDiscussion: https://www.postgresql.org/message-id/flat/6C34A987-AC50-4477-BD71-2D4AFEE1A589%40gmail.com\nDiscussion: https://www.postgresql.org/message-id/flat/CAJTYsWWdeBkoH5g8D-k9LDw9ciqsMxb21EJSiFXAzP4J%3DXyxOQ%40mail.gmail.com", "completion": "Fix RLS checks for FOR PORTION OF leftover rows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA failure in allocating a new cache entry in the backend-level hash\ntable holding references to shared stats entries would leave the table\nin an inconsistent state, crash or FATAL at session exit, depending on\nif there are pending stats.\n\nRather than leaving things in an inconsistent state on OOM, the code is\nswitched to use MemoryContextAllocExtended(MCXT_ALLOC_NO_OOM), so as an\nallocation failure leads to a cleanup of the hash table before issuing\nthe allocation error.\n\nThe problem is unlikely going to show up in practice, so no backpatch is\ndone. Note that shared memory is not impacted, only a backend-level\nhash table.\n\nReported-by: Alex Masterov \nDiscussion: https://postgr.es/m/CA+8z=zumV9sscgK=j1Es+-564maVoO9CMDdB9CsW9=FCziCj3w@mail.gmail.com", "completion": "Improve pgstat_get_entry_ref_cached() behavior on out-of-memory errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_CIPHER_CTX_ctrl() casts the signed int arg to size_t before\ndispatching. For EVP_CTRL_AEAD_SET_IV_FIXED the value -1 is an\nintentional sentinel (\"copy full IV\"), so it must be preserved, but\nany value below -1 wraps to a near-SIZE_MAX size_t. The two guards\ninside gcm_tls_iv_set_fixed() both fail to catch this:\n\n * the sentinel check tests for SIZE_MAX (i.e. (size_t)-1), not\n SIZE_MAX-1 or lower;\n * the bounds check back-casts len to int, undoing the wrap and\n making the comparison evaluate to false.\n\nThe result is memcpy(ctx->iv, iv, SIZE_MAX-1) — a heap overflow.\n\nFix the root cause in EVP_CIPHER_CTX_ctrl() by rejecting any arg\nbelow -1 for EVP_CTRL_AEAD_SET_IV_FIXED, consistent with the guards\nalready present for EVP_CTRL_SET_KEY_LENGTH, EVP_CTRL_AEAD_SET_IVLEN,\nEVP_CTRL_GCM_SET_IV_INV and others.\n\nAs a defense-in-depth measure, also replace the (int) back-cast in\ngcm_tls_iv_set_fixed() with a safe size_t upper-bound check so that\nthe provider itself rejects any out-of-range length independently of\nthe caller.\n\nCo-authored-by: Tomáš Mráz (comment fix)\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nMerge-date: Tue Aug 18 07:41:57 2026\nMerged-from: https://github.com/openssl/openssl/pull/31879", "completion": "EVP_CTRL_AEAD_SET_IV_FIXED: reject arg values below -1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe function appends list tail to list head. List tail becomes\nempty after the function returns.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Aug 6 11:59:15 2026\n(Merged from https://github.com/openssl/openssl/pull/32031)", "completion": "Add ossl_list_TYPE_join(head, tail) function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe function appends list tail to list head. List tail becomes\nempty after the function returns.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Aug 6 11:58:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32031)", "completion": "Add ossl_list_TYPE_join(head, tail) function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe function appends list tail to list head. List tail becomes\nempty after the function returns.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Aug 6 11:58:45 2026\n(Merged from https://github.com/openssl/openssl/pull/32031)", "completion": "Add ossl_list_TYPE_join(head, tail) function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe function appends list tail to list head. List tail becomes\nempty after the function returns.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Aug 6 11:58:31 2026\n(Merged from https://github.com/openssl/openssl/pull/32031)", "completion": "Add ossl_list_TYPE_join(head, tail) function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe function appends list tail to list head. List tail becomes\nempty after the function returns.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Aug 6 11:57:39 2026\n(Merged from https://github.com/openssl/openssl/pull/32031)", "completion": "Add ossl_list_TYPE_join(head, tail) function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit a787a314900ecf98c759a82030ac28992896cc88)", "completion": "fix(window): avoid UAF in `close_windows`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRequires a supported filesystem, i.e. NTFS.\n\nExample:\n```console\n> curl.exe https://curl.se/index.html --output test.txt --xattr --referer https://curl.se/\n> cat < test.txt:Zone.Identifier\n\n[ZoneTransfer]\nHostUrl=https://curl.se/index.html\nReferrerUrl=https://curl.se/\n```\n\nWhere newlines are CLRF, `ReferrerUrl` is set when using `--referer`\noption.\n\nAlso:\n- test688: make it test `--referer`.\n- document `user.xdg.referrer.url` in `--xattr` man page.\n\nRefs:\nhttps://en.wikipedia.org/wiki/Mark_of_the_Web\nhttps://en.wikipedia.org/wiki/NTFS#Alternate_data_stream_(ADS)\nhttps://learn.microsoft.com/en-us/windows/win32/fileio/file-streams\nhttps://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/c54dec26-1551-4d3a-a0ea-4fa40f848eb3\n\nRef: #22345\n\nCloses #22354", "completion": "tool_xattr: add support for Windows alternate data stream"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdd a doc describing the settings mechanism and the process of updating the settings options.", "completion": "docs(devtools): add a settings doc"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe list-item indentation logic in `gen_help_html.lua` tracks `opt.indent` that\nonly decrements by one level when a list item is less indented than its sibling.\nDedenting across multiple nesting levels at once produces the wrong left margin.\n\nSolution:\nTrack the exact leading whitespace for each indent level in a `opt.indent_ws` stack:\n- On reset or a top-level item initialize the stack with the current item's\n whitespace.\n- When indenting deeper push the current whitespace at the new level.\n- When dedenting pop every level whose tracked whitespace is deeper than the\n current item (reaching the correct ancestor level).", "completion": "fix(docs): multi-level list dedent indentation #40850"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Transfer): preserve custom action disabled state\n\n* fix(Transfer): prevent disabled custom action clicks\n\n* fix(Transfer): prevent disabled custom action navigation", "completion": "fix(Transfer): preserve custom action disabled state"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Jul 20 10:19:08 2026\n(Merged from https://github.com/openssl/openssl/pull/32014)", "completion": "test_ocsp: bump test number"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`makeCacheKey` joined the request fields with `|` before hashing. The url\nand the serialized body can contain `|` themselves, so a shifted field\nboundary (url `/items/a` + body `b|c` vs url `/items/a|b` + body `c`)\nproduced the same joined string and the same key, letting two distinct\nrequests share a transfer cache slot.\n\nJoin with `\\0` instead, which cannot occur in a valid url or in encoded\nparams, so the field boundaries cannot be forged by field content.\n\n(cherry picked from commit 3192dccaa3e1488f8bf351864ea48e44a21246aa)", "completion": "fix(http): prevent transfer cache key collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`makeCacheKey` joined the request fields with `|` before hashing. The url\nand the serialized body can contain `|` themselves, so a shifted field\nboundary (url `/items/a` + body `b|c` vs url `/items/a|b` + body `c`)\nproduced the same joined string and the same key, letting two distinct\nrequests share a transfer cache slot.\n\nJoin with `\\0` instead, which cannot occur in a valid url or in encoded\nparams, so the field boundaries cannot be forged by field content.", "completion": "fix(http): prevent transfer cache key collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSome of its code was pointlessly in its caller. This makes it better\ncontained and clearer.\n\nBackpatch to 19, to avoid having two different copies in case we have to\nmodify it again later.\n\nAuthor: Álvaro Herrera \nReviewed-by: Bharath Rupireddy \nReviewed-by: ChangAo Chen \nDiscussion: https://postgr.es/m/alD9l-XlCuu3eUEe@alvherre.pgsql", "completion": "Move code to get_tables_to_repack_partitioned"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCurrently, the SVG sanitizer checks a static set of candidate attribute\nnames (`attributeName` and `attributename`). This approach misses other case\nvariations (such as `attributenAme` or others), which could potentially\nbypass sanitization when binding sensitive attributes like `href` on\n`` or `` elements.\n\nThis change retrieves all attribute names of the SVG element, performs a\ncase-insensitive comparison with `'attributename'`, and sanitizes the value\nif a match is found.\n\n(cherry picked from commit 3499a1321bfe4801c38744ddb500715486680366)", "completion": "fix(core): ensure SVG animation attributeName is checked case-insensitively"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCurrently, the SVG sanitizer checks a static set of candidate attribute\nnames (`attributeName` and `attributename`). This approach misses other case\nvariations (such as `attributenAme` or others), which could potentially\nbypass sanitization when binding sensitive attributes like `href` on\n`` or `` elements.\n\nThis change retrieves all attribute names of the SVG element, performs a\ncase-insensitive comparison with `'attributename'`, and sanitizes the value\nif a match is found.", "completion": "fix(core): ensure SVG animation attributeName is checked case-insensitively"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`vim.diagnostic.handlers.underline.show` throws `E565: Index out of bounds` when\nit tries to underline a diagnostic whose `lnum` is past the end of the buffer.\nThis happens with stale diagnostics set on an unloaded buffer (e.g. via\n`bufadd()`) that are drawn only after the buffer is loaded: by then the file on\ndisk can be shorter than the `lnum` the diagnostic carried. File pickers\n(snacks.nvim) that open files via `bufadd` + `:buffer` hit this whenever an LSP\nserver has already emitted diagnostics for that URI.\n\nSolution:\nSkip diagnostics with an out-of-range `lnum` in the underline handler.\n\nOther handlers `M.virtual_text.show()`, `M.signs.show()`, have a similar condition.", "completion": "fix(diagnostic): skip out-of-range lnum in underline handler #40839"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nw_float_is_info conflates a window's role with its floating layout,\nwhich are orthogonal properties.\n\nSolution:\nReplace w_float_is_info with a w_kind enum for the window's role.", "completion": "refactor(window): extract w_kind for window role #40830"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFixes #22344\nReported-by: Carlos Henrique Lima Melara\nCloses #22355", "completion": "test: adjust test_06_13 for 0100::/64 being blackholed"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 6f6f284c7ee4 introduced use of LSN_FORMAT_ARGS across the whole\ntree to remove use of manual bit-shifting, and commit 2633dae2e487\nchanged the printf format to be %X/%08X; however commit 28d534e2ae0a\nviolated both conventions by reintroducing the old manual-shift style\nwith the deprecated %X/%X format in one debug message. Make that new\nmessage conform to our style.\n\nAuthor: kenny \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/CAPXstDuWD8jg0=C8PXTXGSTTsZcjqJ+u+xKCrMpN99CXsxQzCg@mail.gmail.com", "completion": "Fix LSN format in REPACK worker debug message"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_msg_check_update() converts an unexpected CMP response sender DN with\nX509_NAME_oneline() and passes that peer-controlled string directly as the\nformat argument to ERR_raise_data(). Printable percent characters survive the\nDN conversion, so a sender such as CN=%s%n reaches vsnprintf() as active format\nsyntax without matching varargs.\n\nFixes: CVE-2026-63073\n\nOriginal patch by: Filipe Casal of Trail of Bits in collaboration with OpenAI\n\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:02:29 2026", "completion": "CMP unexpected sender DN used as format string in ERR_raise_data()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_msg_check_update() converts an unexpected CMP response sender DN with\nX509_NAME_oneline() and passes that peer-controlled string directly as the\nformat argument to ERR_raise_data(). Printable percent characters survive the\nDN conversion, so a sender such as CN=%s%n reaches vsnprintf() as active format\nsyntax without matching varargs.\n\nFixes: CVE-2026-63073\n\nOriginal patch by: Filipe Casal of Trail of Bits in collaboration with OpenAI\n\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:02:10 2026", "completion": "CMP unexpected sender DN used as format string in ERR_raise_data()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_msg_check_update() converts an unexpected CMP response sender DN with\nX509_NAME_oneline() and passes that peer-controlled string directly as the\nformat argument to ERR_raise_data(). Printable percent characters survive the\nDN conversion, so a sender such as CN=%s%n reaches vsnprintf() as active format\nsyntax without matching varargs.\n\nFixes: CVE-2026-63073\n\nOriginal patch by: Filipe Casal of Trail of Bits in collaboration with OpenAI\n\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:01:47 2026", "completion": "CMP unexpected sender DN used as format string in ERR_raise_data()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_msg_check_update() converts an unexpected CMP response sender DN with\nX509_NAME_oneline() and passes that peer-controlled string directly as the\nformat argument to ERR_raise_data(). Printable percent characters survive the\nDN conversion, so a sender such as CN=%s%n reaches vsnprintf() as active format\nsyntax without matching varargs.\n\nFixes: CVE-2026-63073\n\nOriginal patch by: Filipe Casal of Trail of Bits in collaboration with OpenAI\n\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:00:49 2026", "completion": "CMP unexpected sender DN used as format string in ERR_raise_data()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_msg_check_update() converts an unexpected CMP response sender DN with\nX509_NAME_oneline() and passes that peer-controlled string directly as the\nformat argument to ERR_raise_data(). Printable percent characters survive the\nDN conversion, so a sender such as CN=%s%n reaches vsnprintf() as active format\nsyntax without matching varargs.\n\nFixes: CVE-2026-63073\n\nOriginal patch by: Filipe Casal of Trail of Bits in collaboration with OpenAI\n\nSigned-off-by: Norbert Pocs \nReviewed-by: Andrew Dinh \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 12:53:37 2026", "completion": "CMP unexpected sender DN used as format string in ERR_raise_data()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nForward only the app error code from the receiving side to the h3 layer.\n\nThis only takes effect when building against ngtcp2 v1.25.0 or higher.\n\nFixes #22270\n\nCloses #22356", "completion": "vquic: use ngtcp2 v1.25.0 new close2 callback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, tests that needed extra postmaster command-line options had\nto invoke pg_ctl start directly, because\nPostgreSQL::Test::Cluster::start() provided no way to pass them. That\nbypassed the test framework's postmaster PID tracking, so a postmaster\ncould be left running if the test failed after startup.\n\nAdd an options parameter to\nPostgreSQL::Test::Cluster::start(), which is passed to pg_ctl's\n--options argument. This allows tests to use start() while\npreserving the framework's normal cleanup behavior.\n\nAuthor: Fujii Masao \nReviewed-by: JoongHyuk Shin \nDiscussion: https://postgr.es/m/CAHGQGwEpfE0CDUUODjBt7GO9U4ZF11hqga_Ci3wP8=O49oFKVw@mail.gmail.com", "completion": "Allow PostgreSQL::Test::Cluster::start() to pass postmaster options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nRecovery target parameters are postmaster-startup GUCs, but their\nassign hooks previously did more than assign individual parameter\nvalues. They also updated the global recoveryTarget state and raised\nERROR if more than one recovery target appeared to be set.\n\nThis was not a good fit for GUC assign hooks. Assign hooks should not\nthrow ERROR, and deriving cross-parameter state while individual GUCs\nare still being assigned makes the result depend on assignment order\nrather than the final configuration.\n\nFor example, setting one recovery target and then setting another\nrecovery_target_* parameter to an empty string could clear\nrecoveryTarget, causing recovery to proceed with no target even\nthough a valid target remained configured.\n\nFix this by having the assign hooks only store their own parameter\nvalues. The effective recoveryTarget is now derived once from the\nfinal recovery_target* settings in\nvalidateRecoveryParameters(), which also rejects configurations that\nspecify more than one recovery target with FATAL. This preserves the\nexpected behavior for repeated assignments of the same GUC, treats empty\nvalues as \"not set\", and removes cross-GUC validation from the assign\nhooks.\n\nAuthor: JoongHyuk Shin \nReviewed-by: Greg Lamberson \nReviewed-by: Michael Paquier \nReviewed-by: Scott Ray \nReviewed-by: Álvaro Herrera \nReviewed-by: Kyotaro Horiguchi \nReviewed-by: Henson Choi \nReviewed-by: Zsolt Parragi \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CACSdjfPUa4UvKjADgOERXoxNYmCg2mqqiqKkiJk6mX6E4qgVFw@mail.gmail.com", "completion": "Avoid ERROR in recovery target GUC assign hooks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis commit updates the pnpm-lock.yaml to reflect differences in node and https-proxy-agent transitive dependencies.", "completion": "build: update pnpm-lock.yaml"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nLSP hover erroneously drops blank lines before a 4-space-indented\ncodeblock, which is not valid Markdown. This causes incorrect parsing\nand wrong display.\n\nSolution:\nFix `split_lines` so that it doesn't drop the blank line just before\na 4-space-indented codeblock.\n\nfix https://github.com/neovim/neovim/issues/40860\n\n(cherry picked from commit 317c5ddda6c71d1e7709c7066c91522ecaeb081a)", "completion": "fix(lsp): incorrect rendering of markdown codeblock #40861"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nLSP hover erroneously drops blank lines before a 4-space-indented\ncodeblock, which is not valid Markdown. This causes incorrect parsing\nand wrong display.\n\nSolution:\nFix `split_lines` so that it doesn't drop the blank line just before\na 4-space-indented codeblock.\n\nfix https://github.com/neovim/neovim/issues/40860", "completion": "fix(lsp): incorrect rendering of markdown codeblock #40861"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nExtend the Angie illustrations to the empty states that were still plain\ntext: the injector providers \"No such providers\" result, the injector tree\nunsupported-version notice, the two profiler timeline placeholders, and the\nrouter tree unsupported-version notice.\n\nAdds the magnifying-glass and question poses as assets; the orthos-back\nand sad poses are already in the tree.", "completion": "feat(devtools): show Angie on the remaining empty-state screens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n\n FAILED …/cursorhold_spec.lua @ 73: CursorHold is not triggered after only K_EVENT on startup\n Expected values to be equal.\n Expected:\n 1\n Actual:\n 0\n stack traceback:\n …/cursorhold_spec.lua:79: in function <…/cursorhold_spec.lua:73>\n\nSolution:\nRetry instead of hardcoding sleep(50).", "completion": "test: unreliable \"CursorHold not triggered after only K_EVENT on startup\" #40863"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe magic globals `it`, `describe`, etc., are more trouble than they are\nworth.\n\n- Hooking into `after_each` requires `getfenv()` hacks.\n- They confuse luals/emmylua, because the top-level `.luarc.json` isn't\n merged with `test/.luarc.json` (apparently a luals limitation?)\n- They totally defeat discoverability because the user just has to\n \"know\" about the various magic symbols.\n\nSo they harm DX, which means they serve no purpose at all.\n\nSolution:\n- Expose the test API from `testutil`, so tests can call `t.it()`,\n `t.describe()`, etc., in the conventional way.\n- Drop `getfenv()` hacks.\n- Drop the `setfenv()` injection in `load_chunk`.\n- Drop `test/_meta.lua`.", "completion": "test(harness): migrate away from magic globals"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 8c852ba9a4 allowed exclusion constraints to be added to\npartitioned tables, but wasn't careful to verify that pg_restore worked\ncorrectly for them. Fix that by making CompareIndexInfo() more\nselective about what needs to be rejected.\n\nAuthor: Japin Li \nReported-by: Keith Paskett \nDiscussion: https://postgr.es/m/2A40921D-83AB-411E-ADA6-7E509A46F1E4@logansw.com", "completion": "Fix restore of partitions with exclusion constraints"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen only some NgClass usages are migrated (partial migration),\nthe NgClass import should be preserved in the module/component\nimports if it is still used elsewhere.\n\n(cherry picked from commit 223e40279f3f6df979a323f79cb370528366c24a)", "completion": "fix(migrations): preserve NgClass import on partial migration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen only some NgClass usages are migrated (partial migration),\nthe NgClass import should be preserved in the module/component\nimports if it is still used elsewhere.", "completion": "fix(migrations): preserve NgClass import on partial migration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo allow any full path lengths, beyond the 260 characters allowed by\n`_MAX_PATH`.\n\nFollow-up to fa0ccd9f1fbbbd77bf50b26e3ba231ea6c729474 #15774\n\nCloses #22357", "completion": "vtls_scache: allocate absolute filename on heap (Windows)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nOnly touch tsconfig files for targets that use an Angular builder, including community ones like Nx, so non-Angular projects in mixed workspaces are left alone.\n\nFixes #69837\n\n(cherry picked from commit f72600eaddfa6a299526e922eb9ad5356be821a6)", "completion": "fix(migrations): skip tsconfig files of non-Angular projects"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nOnly touch tsconfig files for targets that use an Angular builder, including community ones like Nx, so non-Angular projects in mixed workspaces are left alone.\n\nFixes #69837", "completion": "fix(migrations): skip tsconfig files of non-Angular projects"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nMagic-string is now ESM only.", "completion": "build: update dependency magic-string to v1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nTo make it in line with ASN1_BIT_STRING_get_length() and other (size)\ngetters. The majority of the changes was done by\n\n for i in `git grep -l ASN1_STRING_length_ex`; do \\\n sed -i 's/ASN1_STRING_length_ex/ASN1_STRING_get_length/g' \"$i\"; \\\n done\n\nwith a manual touch-up in util/libcrypto.num.\n\nComplements: 28179061bfcd \"Prepare a now opaque ASN1_STRING for the size_t rapture.\"\nSigned-off-by: Eugene Syromiatnikov \n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Tue Aug 11 13:56:42 2026\n(Merged from https://github.com/openssl/openssl/pull/32015)", "completion": "Rename ASN1_STRING_length_ex() to ASN1_STRING_get_length()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nTo comply with the naming guidelines for the API functions that transfer\nownership of the data. The majority of the changes was done by\n\n for i in `git grep -l ASN1_STRING_set_data`; do \\\n sed -i 's/ASN1_STRING_set_data/ASN1_STRING_set1_data/g' \"$i\"; \\\n done\n for i in `git grep -l ASN1_STRING_set_string`; do \\\n sed -i 's/ASN1_STRING_set_string/ASN1_STRING_set1_string/g' \"$i\"; \\\n done\n\nwith a manual touch-up in util/libcrypto.num.\n\nComplements: 28179061bfcd \"Prepare a now opaque ASN1_STRING for the size_t rapture.\"\nSigned-off-by: Eugene Syromiatnikov \n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Tue Aug 11 13:56:44 2026\n(Merged from https://github.com/openssl/openssl/pull/32015)", "completion": "Change set suffix in ASN1_STRING_set_{data,string} to set1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIt's always been the case that granting these privileges to users that\nyou don't fully trust was a bad idea, but it hasn't always been\nobvious to people reading the documentation that this is the case.\nTo prevent confusion, and also repeated reports to pgsql-security,\nmention it explicitly.\n\nDiscussion: http://postgr.es/m/CA+TgmobrjCHBuWHrvX3=2vndUCO2thUOdevrCcMDFW86cqCYvw@mail.gmail.com\nReviewed-by: Nathan Bossart \nBackpatch-through: 14", "completion": "doc: Granting TRIGGER or REFERENCES on table is dangerous."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Fix applied in b2bb60d7 does not properly replace the normal command.\nSolution: Restore normal command with `noautocmd` to resolve #40780.", "completion": "fix(ui2): position message windows without autocmds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBuildfarm member skink reported a failure in\nrecovery/003_recovery_targets after commit d5751c33cc3. The newly\nadded recovery_target_xid set-then-cleared test could time out while\nwaiting for pg_last_wal_replay_lsn() to reach the expected LSN.\n\nThe test recorded lsn6 after calling pg_switch_wal(). As a result,\nlsn6 pointed into the next WAL segment, but pg_switch_wal() only\narchived the previous one. Since the standby in this test restores WAL\nfrom the archive only, it could not obtain the segment containing\nlsn6 and waited indefinitely.\n\nFix this by recording lsn6 before calling pg_switch_wal(), so the\narchived WAL contains the LSN that the standby is waiting for.\n\nPer buildfarm member skink.\n\nReported-by: Álvaro Herrera \nAuthor: Fujii Masao \nDiscussion: https://postgr.es/m/al5Y2mWffRs1NP34@alvherre.pgsql", "completion": "Fix recovery target test waiting on unavailable WAL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe title is combined with window's attributes only if the title is a\nstring (which implies the FloatTitle / FloatFooter highlight groups),\nbut not when the title is text-hl chunks.\n\nSolution:\nCombine specified highlight group with window-local Normal highlight as\nwell.", "completion": "fix(ui): handle combining chunked float titles"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe default 'ruler' is implemented in C instead of the 'statusline' DSL.\n\nSolution:\nReplace the C implementation with a default 'rulerformat' expression.\nThis is a continuation of #1248 and #33036.\n\nAdvantages:\n- configuration is more discoverable, the default being a useful example\n- users and plugins can augment the default\n- code reuse and less C code to maintain\n- ui2: due to the use of an item group with `minwid`, it can expand\n instead of truncating when the content gets too long, which is\n particularly useful for locales with long translations of Top/Bot/All\n\nImplementation details:\nAs is the case for 'statusline', when trying to set 'rulerformat' to an\nempty string, the default expression is restored instead, mimicking how\npreviously the default C implementation would have been activated.\nJust like before, `:set rulerformat=` and `:set rulerformat&` have the\nsame effect, and the ruler is disabled with `:set noruler`.\n\nThe default expression uses an item group with `%=`, unlike the fallback\nin the previous default statusline `%-14.(%l,%c%V%) %P`, because the\ntotal width and how it is configured is immediately clear without\ndocumentation, it is a more useful pattern in general that works when\nboth sides have flexible width, and it also works for vim, which is\nuseful for configuration sharing/reuse.\n\nA truncation marker `%<` is added at the end to mimic how at small\nscreen widths, the scroll percentage would disappear first, so that the\ncursor position can remain fully visible.\n\nBREAKING CHANGES:\n- `&rulerformat` can no longer be set to an empty string\n- ui2: the default ruler is no longer of fixed width, but can expand\n- at very small screen widths (< 36 columns)\n - ui2: it will no longer try to shrink white-space before truncating\n - it truncates gradually from the right, whereas previously, the\n scroll percentage would disappear all at once\n- l10n can no longer add a space after the comma between line and column\n (this was only done for one", "completion": "refactor(ruler)!: replace C implementation with 'rulerformat' expression"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a test that exercises the encoder and decoder chain processing in\nencoder_lib.c and decoder_lib.c through a built-in test provider\nimplementing a two-stage encoder chain (\"TEST-KEY\" -> \"inter\" -> \"pem\")\nand the mirrored decoder chain.\n\nThis covers previously untested code paths:\n\n- encoder chaining through abstract objects, including the intermediate\n memory BIO handling in encoder_process()\n- OSSL_ENCODER_to_fp() and OSSL_DECODER_from_fp()\n- OSSL_ENCODER_to_data() edge cases (size query, pre-allocated buffer,\n too small buffer)\n- OSSL_DECODER_CTX_add_decoder() and OSSL_DECODER_export()\n- decoding from a non-seekable BIO (BIO_f_readbuffer wrapping)\n- various error paths and NULL argument checks in both APIs\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 13:45:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32019\n(cherry picked from commit b542f2545cc10f6b481fd70600bcb0b8523e09a9)", "completion": "test: add low-level OSSL_ENCODER / OSSL_DECODER API test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a test that exercises the encoder and decoder chain processing in\nencoder_lib.c and decoder_lib.c through a built-in test provider\nimplementing a two-stage encoder chain (\"TEST-KEY\" -> \"inter\" -> \"pem\")\nand the mirrored decoder chain.\n\nThis covers previously untested code paths:\n\n- encoder chaining through abstract objects, including the intermediate\n memory BIO handling in encoder_process()\n- OSSL_ENCODER_to_fp() and OSSL_DECODER_from_fp()\n- OSSL_ENCODER_to_data() edge cases (size query, pre-allocated buffer,\n too small buffer)\n- OSSL_DECODER_CTX_add_decoder() and OSSL_DECODER_export()\n- decoding from a non-seekable BIO (BIO_f_readbuffer wrapping)\n- various error paths and NULL argument checks in both APIs\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 13:45:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32019", "completion": "test: add low-level OSSL_ENCODER / OSSL_DECODER API test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplaces the temporary `promiseWithResolvers` polyfill with the\nnative `Promise.withResolvers()` API in test files and Updates the TypeScript configuration to include the `es2024.promise`.\n\n(cherry picked from commit b5ce15c659b76e7c25e8cd98358ffd44a24cdea2)", "completion": "refactor(core): use native `Promise.withResolvers()` in tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplaces the temporary `promiseWithResolvers` polyfill with the\nnative `Promise.withResolvers()` API in test files and Updates the TypeScript configuration to include the `es2024.promise`.", "completion": "refactor(core): use native `Promise.withResolvers()` in tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe existing `showmode` overlay can immediately cover messages emitted while\nVisual mode is active, including the `g CTRL-G` word count.\n\nSolution:\nProtect Visual mode messages with the existing message delay and temporarily\nhide the previous last-line overlay until it is restored.", "completion": "fix(ui2): preserve Visual mode messages #40828"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe tutorial intro and \"next steps\" pages were plain headings with no\nsend-off. Bookend each tutorial with Angie: a greeting pose welcoming\nlearners on the intro page, and a superhero pose congratulating them on\nthe completion page, each beside a speech bubble.\n\nThe bubble treatment from the 404 page lived inside the not-found\ncomponent, so it's extracted into a reusable docs-content style\n(docs-tutorial-mascot) usable from tutorial markdown, and applied to the\nintro and completion pages of the Learn Angular, Signals, and Signal\nForms tutorials.\n\n(cherry picked from commit d2c0e1ec77c352e07a13647dde153bf83fca603e)", "completion": "feat(docs-infra): bookend the tutorials with Angie"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe tutorial intro and \"next steps\" pages were plain headings with no\nsend-off. Bookend each tutorial with Angie: a greeting pose welcoming\nlearners on the intro page, and a superhero pose congratulating them on\nthe completion page, each beside a speech bubble.\n\nThe bubble treatment from the 404 page lived inside the not-found\ncomponent, so it's extracted into a reusable docs-content style\n(docs-tutorial-mascot) usable from tutorial markdown, and applied to the\nintro and completion pages of the Learn Angular, Signals, and Signal\nForms tutorials.", "completion": "feat(docs-infra): bookend the tutorials with Angie"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve NgClass import on partial migration and increment\nskippedNgClassCount when an unmigrable mixed binding is encountered.\n\n(cherry picked from commit 49672c437b440564e9c20b77a7ff151fbf316706)", "completion": "fix(migrations): correctly migrate ngClass with mixed space-separated keys"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve NgClass import on partial migration and increment\nskippedNgClassCount when an unmigrable mixed binding is encountered.", "completion": "fix(migrations): correctly migrate ngClass with mixed space-separated keys"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds a compliance case pinning the instruction-set selection for a\ndirective-free standalone component:\n\n - full compile: the compiler can prove the template has no directive\n dependencies, so it takes the DOM-only fast path\n (`ɵɵdomElementStart`/`ɵɵdomElementEnd`).\n - local compile: the compiler cannot inspect dependencies, so\n `hasDirectiveDependencies` is forced true and the full instruction\n set is emitted (`ɵɵelementStart`/`ɵɵelementEnd`).\n\nThis mode-dependent switch was previously only exercised incidentally by\nthe `foreign_component` case, which couples it with foreign-component\ncompilation. The new case isolates it.\n\n(cherry picked from commit eb3e480360d0f24a725bb453af49bd9072fdc87e)", "completion": "test(compiler-cli): cover DOM-only vs full instruction set across compilation modes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds a compliance case pinning the instruction-set selection for a\ndirective-free standalone component:\n\n - full compile: the compiler can prove the template has no directive\n dependencies, so it takes the DOM-only fast path\n (`ɵɵdomElementStart`/`ɵɵdomElementEnd`).\n - local compile: the compiler cannot inspect dependencies, so\n `hasDirectiveDependencies` is forced true and the full instruction\n set is emitted (`ɵɵelementStart`/`ɵɵelementEnd`).\n\nThis mode-dependent switch was previously only exercised incidentally by\nthe `foreign_component` case, which couples it with foreign-component\ncompilation. The new case isolates it.", "completion": "test(compiler-cli): cover DOM-only vs full instruction set across compilation modes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nImplement \\`toggleWatchSignal(id)\\` in \\`signal_debug.ts\\` to enable toggling reactive watch listeners on individual signal graph nodes.\n- Create reactive \\`Watch\\` instances using \\`createWatch\\` to log signal value/state changes to the console when active.\n- Use \\`WeakRef\\` mapping and \\`FinalizationRegistry\\` (\\`watchCleanupRegistry\\`) so active watches do not retain strong references to signal nodes or prevent garbage collection.\n- Expose \\`watched\\` status on \\`DebugSignalGraphNode\\` and publish \\`toggleWatchSignal\\` onto \\`window.ng\\` in development mode.\n- Add acceptance tests covering watch activation, signal mutation logging, manual disposal, GC cleanup, and safe invalid ID handling.", "completion": "refactor(core): implement toggleWatchSignal for DevTools signal debugging"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdd a \"Watch signal\" button to the signal-details component to allow users to \"watch\" changes to the associated signal.", "completion": "feat(devtools): add \"Watch signal\" button to signal-details component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn encoder_process(), the data type (the name of the encoder\nimplementation that produced the current encoding) is determined at the\ndeepest recursion level, but was not propagated up through the\nrecursion together with the other results of the recursive call. As a\nconsequence, the abstract object handed to a chained encoder\nimplementation contained an OSSL_OBJECT_PARAM_DATA_TYPE parameter with\nNULL data, in violation of provider-object(7), which specifies it as a\nUTF8 string carrying the type of the object content.\n\nThis went unnoticed because no encoders provided by OpenSSL itself are\never chained.\n\nAlso extend endecode_api_test to verify that a chained encoder\nimplementation receives the correct data type.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 13:45:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32019\n(cherry picked from commit 13b0be7cb62e21c23916937999446c00a6cd31f9)", "completion": "encoder: pass the data type up through the encoder chain"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn encoder_process(), the data type (the name of the encoder\nimplementation that produced the current encoding) is determined at the\ndeepest recursion level, but was not propagated up through the\nrecursion together with the other results of the recursive call. As a\nconsequence, the abstract object handed to a chained encoder\nimplementation contained an OSSL_OBJECT_PARAM_DATA_TYPE parameter with\nNULL data, in violation of provider-object(7), which specifies it as a\nUTF8 string carrying the type of the object content.\n\nThis went unnoticed because no encoders provided by OpenSSL itself are\never chained.\n\nAlso extend endecode_api_test to verify that a chained encoder\nimplementation receives the correct data type.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 13:45:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32019", "completion": "encoder: pass the data type up through the encoder chain"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFuzz OSSL_ECHSTORE_read_echconfiglist with raw\nfuzzer input in stage 1. Then fixup the starting\nbytes to reach deeper code withotu relying only on\ncorpus. Fixup is done for binary encoding only (not base64).\n\nAssisted-by: ChatGPT:gpt-5.5\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Jul 23 13:57:54 2026\n(Merged from https://github.com/openssl/openssl/pull/32021)", "completion": "Add OSSL_ECHSTORE_read_echconfiglist fuzzer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nPointed out by the GitHub AI thing\n\nCloses #22360", "completion": "cf-quiche.c: minor tidy-ups"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAuto-rejected streams remain in the stream map until garbage collection, but\nthey are never linked to the incoming accept queue. Connection-level reads\ncurrently treat such a stream as a default stream candidate and try to remove\nits unlinked accept node, which aborts in debug builds and dereferences NULL\nwhen assertions are disabled.\n\nOnly select peer streams that are still linked to the accept queue, and add\na regression test requiring SSL_ERROR_WANT_READ after the peer stream is\nrejected.\n\nFixes #31685\n\nAssisted-by: Codex:GPT-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Jakub Zelenka \nMergeDate: Tue Aug 11 07:15:53 2026\n(Merged from https://github.com/openssl/openssl/pull/32020)", "completion": "QUIC: ignore rejected default stream candidates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe code comes from David Gwynne .\nThe same implmentation can be found in OpenBSD.\n\nSeveral minor adjustments have been done to include the code\ninto OpenSSL:\n * the prefix has been changed to OSSL_RBT_,\n * the support augment is removed,\n * _RBT_CHECK()/_RBT_POISON() got removed too,\n * _RB_REMOVE() resets link pointer to NULL in debug build,\n\nThe documentation is based on tree(3) from OpenBSD, originally authored\nby Niels Provos .\n\nCo-Authoerd-by: David Gwynne \nCo-Authored-by: Niels Provos \nCo-Authored-by: Andrew Dinh \n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Bob Beck \nReviewed-by: Norbert Pocs \nMergeDate: Tue Aug 11 19:17:41 2026\n(Merged from https://github.com/openssl/openssl/pull/32033)", "completion": "Add a red-black tree implementation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe code comes from David Gwynne .\nThe same implmentation can be found in OpenBSD.\n\nSeveral minor adjustments have been done to include the code\ninto OpenSSL:\n * the prefix has been changed to OSSL_RBT_,\n * the support augment is removed,\n * _RBT_CHECK()/_RBT_POISON() got removed too,\n * _RB_REMOVE() resets link pointer to NULL in debug build,\n\nThe documentation is based on tree(3) from OpenBSD, originally authored\nby Niels Provos .\n\nCo-Authoerd-by: David Gwynne \nCo-Authored-by: Niels Provos \nCo-Authored-by: Andrew Dinh \n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Bob Beck \nReviewed-by: Norbert Pocs \nMergeDate: Tue Aug 11 19:15:59 2026\n(Merged from https://github.com/openssl/openssl/pull/32033)", "completion": "Add a red-black tree implementation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nExposes the internal fn reference of effect reactive nodes on DebugSignalGraphNode as debuggableFn. This allows Angular DevTools to inspect and set breakpoints on effect callbacks.", "completion": "refactor(core): expose debuggableFn for effects in signal debug graph"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nIn case of an overflow, the iteration will\nbreak before the grid_line_puts call.", "completion": "perf(ui): defer title attr resolution"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 8108765f04b added the logical decoding status to the\npg_controldata output, but overlooked the pg_control_checkpoint() SQL\nfunction, which reports the same checkpoint information. This commit\nadds a logical_decoding column to pg_control_checkpoint(), placed\nafter full_page_writes to match the pg_controldata output order.\n\nOversight in 8108765f04b.\n\nBump catalog version.\n\nReported-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwEkp1-1n5iC38+yHSNh955+KshwtCL6DzA0vk_vuUF_Eg@mail.gmail.com\nBackpatch-through: 19", "completion": "Add logical decoding status to pg_control_checkpoint()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n* feat(compiler-vapor): make event delegation opt-in\n\nAttach Vapor DOM event listeners directly by default and use the\nVapor-only .delegate modifier to opt into document-level delegation.\n\nWarn and fall back to direct listeners for dynamic or unsupported\nevents, and remove the eventDelegation compiler option.\n\nThis prevents ancestor stopPropagation() calls from blocking delegated\nchild handlers while retaining delegation as an explicit optimization.\n\nBREAKING CHANGE: Vapor event listeners are no longer delegated by\ndefault, and the eventDelegation compiler option has been removed.", "completion": "feat(compiler-vapor): make event delegation opt-in"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCleaned up the generated files so that they only #include dependencies once\nrather than once per generated parser.\n\nFlagged the generated OSSL_PARAM list and parsing function with ossl_unused\nso that they won't generate warnings if compilation unit doesn't use them.\nThis is necessary if the generated parser is included from different files.\n\nReviewed-by: Shane Lontis \nReviewed-by: Mounir Idrassi \n(Merged from https://github.com/openssl/openssl/pull/32502)", "completion": "param parsing: cleaned generated file includes, flagged things as unused"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSequence synchronization updates sequence state via setval(), which\nexplicitly calls PreventCommandIfReadOnly(). If\ndefault_transaction_read_only is enabled on the subscriber, this causes\nsequencesync workers to fail with \"cannot execute setval() in a read-only\ntransaction\". Apply and tablesync workers are not affected, since they\nwrite via direct heap access rather than through these read-only-checked\nfunctions.\n\nRather than special-casing sequencesync, override\ndefault_transaction_read_only to \"off\" for all logical replication workers\nin InitializeLogRepWorker(), the same way session_replication_role and\nsearch_path are already forced there. This keeps the initialization\nuniform.\n\nFor PG-19, we kept the fix narrow by overriding\ndefault_transaction_read_only to \"off\" only for sequencesync workers.\n\nReported-by: Noah Misch \nAuthor: vignesh C \nReviewed-by: Amit Kapila \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Allow logical replication workers to ignore default_transaction_read_only."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- Vim version header (date)\n- N/A Vimscript functions\n - \"listener_\" and \"redraw_listener_\" API\n- N/A line changes\n - \"^.*{.* compiled with .*}$\"", "completion": "build(vim-patch): n/a runtime/doc/*.txt updates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIf a BEFORE trigger changes NEW.valid_at, what is the interaction with\nFOR PORTION OF? This commit gives a test to capture our current\nbehavior: The trigger's change replaces the value we computed\nautomatically, but it does not change the bounds of the temporal\nleftovers.\n\nThis matches the behavior of MariaDB. On the other hand, DB2 rejects\nchanging the start/end columns of a PERIOD. Since we don't have\nPERIODs, we can't reject the change at trigger definition time as DB2\ndoes, but we could reject it at run time by comparing the values\nbefore and after running triggers.\n\nAuthor: Paul A. Jungwirth \nDiscussion: https://www.postgresql.org/message-id/CA%2BrenyV3Cr9BvWsPeb1t8b%3DPk24apuzyGbubAEs_YsgLUTfXpg%40mail.gmail.com", "completion": "Test what BEFORE UPDATE triggers do to FOR PORTION OF"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdate devinfra sha to latest version.", "completion": "build: update devinfra commit and correct module file reference in ts version validation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAn in-flight failure when trying to set rd_partcheckcxt or\nrd_partcheck, while for example doing an allocation in copyObject(),\nwould leave a backend cache in a corrupted state. The operations are\nnow ordered so as we avoid a leak in the cache memory context and a\nsemi-filled cache state when an allocation failure happens.\n\nThis is unlikely going to be hit in practice. Like the other\nimprovements of this kind, no backpatch is done.\n\nReported-by: Alexander Lakhin \nAuthor: Matthias van de Meent \nDiscussion: https://postgr.es/m/95c64dc2-3abe-4f4e-b285-4c681f565d9f@gmail.com", "completion": "Improve generate_partition_qual()'s cache handling on out-of-memory errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- clear writer paused bit when destroying writer stack\n- remove the reader paused bit that turned out not to be a good idea\n\nfollow-up to b41c28e70af47e1\n\nCloses #22361", "completion": "lib: reader/writer fixes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:28 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:12 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:10:52 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:10:00 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:12:03 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:44 2026", "completion": "Add test for CVE-2026-63076"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:29 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:13 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:10:53 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:10:03 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:12:04 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_cmp_calc_protection() only checked whether the protectionAlg parameter\n(ppval) was NULL before treating it as a PBMParameter ASN1_STRING.\n\nX509_ALGOR_get0() does not validate the ASN.1 type of the parameter against what\nthe caller expects. For id-PasswordBasedMAC, a crafted message can encode the\nparameter as a BOOLEAN instead of the expected PBMParameter SEQUENCE. Because\nthe ASN1_TYPE value union overlays the boolean int on the pointer field, ppval\ncomes back as a bogus non-NULL pointer (e.g. 0xff).\n\nFixes CVE-2026-63076\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Sat Aug 22 06:11:45 2026", "completion": "Fix Remote NULL deref in ossl_cmp_calc_protection() via crafted protectionAlg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update devinfra digest to 24f9214"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nGenerated API bindings for Lua contain unused jump labels when the API\nfunction has a non-KeyDict (e.g., Array) param after a KeyDict param, causing\nthe build to fail.\n\nSolution:\nDon't output a label when the current parameter is not a KeyDict but the\nprevious one is.", "completion": "build(api): unused labels in generated Lua bindings #40880"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen the threaded resolver gets AAAA results that carry a link-local\naddress without scope-id, it now re-queues a query with AF_UNSPEC and\nstrips ipv4 addresses from that result. Whatever the resulting addresses\nand scope-ids are, this becomes the result of the resolve.\n\nFixes #22330\nReported-by: Bartel Sielski\nCloses #22368", "completion": "asyn-thrdd: retry link-local ipv6 if missing scope id"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nrand_get0_primary() created the seed source ahead of the primary DRBG\nand stored both under the write lock at the end. When two threads\nraced to create the primary DRBG and one of them failed after having\ncreated and stored the seed source, the other thread overwrote the\nstored seed source with its own instance, leaking the previous one.\n\nFactor the get-or-create logic out into rand_get0_seed() which\nrechecks the global under the write lock, so exactly one instance is\nkept and returned to every racing thread, and the seed source is\nstored independently of the primary DRBG creation outcome.\n\nAdd a regression test checking that creating the primary DRBG creates\nand stores the seed source and that later use keeps returning the same\ninstance.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Paul Dale \nReviewed-by: Matt Caswell \nReviewed-by: Ryan Hooper \nMergeDate: Mon Jul 27 09:13:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32029)", "completion": "rand: factor out seed source creation and fix store race"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nrand_get0_primary() created the seed source ahead of the primary DRBG\nand stored both under the write lock at the end. When two threads\nraced to create the primary DRBG and one of them failed after having\ncreated and stored the seed source, the other thread overwrote the\nstored seed source with its own instance, leaking the previous one.\n\nFactor the get-or-create logic out into rand_get0_seed() which\nrechecks the global under the write lock, so exactly one instance is\nkept and returned to every racing thread, and the seed source is\nstored independently of the primary DRBG creation outcome.\n\nAdd a regression test checking that creating the primary DRBG creates\nand stores the seed source and that later use keeps returning the same\ninstance.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Paul Dale \nReviewed-by: Matt Caswell \nReviewed-by: Ryan Hooper \nMergeDate: Mon Jul 27 09:13:12 2026\n(Merged from https://github.com/openssl/openssl/pull/32029)", "completion": "rand: factor out seed source creation and fix store race"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWhen 'shellslash' is set, exepath() returns forward-slashed paths.\nPassing that path to vim.system() can prevent cmd.exe from launching.\n\nSolution:\nConvert the resolved executable path to native separators before spawning.\nAdd a Windows regression test for cmd.exe with 'shellslash' enabled.", "completion": "fix(system): use native path for Windows executables #40885"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nemmylua reports `unresolved-require` for `require('test.testutil')` and\nfriends, and a file under `test/` cannot even resolve its own siblings.\n\nThis happens because `test/.emmyrc.json` and `test/.luarc.json`, cause\nvim.lsp to root the workspace at `test/` instead of the repo top-level.\n\nSolution:\nDrop the nested configs:\n\n src/.luarc.json\n test/.luarc.json\n test/.emmyrc.json\n\nOutcomes:\n- No \"libraries\" needed: luv types come from `runtime/lua/uv/_meta.lua`,\n not `${3rd}/luv` (which would only duplicate them).\n- Drop `test/` from the root `.luarc.json` `ignoreDir` so its modules are\n resolvable by LuaLS/Emmylua.\n - Note: this means that LuaLS diagnostics will now be reported for\n `test/`, but that is not a bad thing...", "completion": "build(luals): drop src/.luarc.json, test/.luarc.json #40887"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nChange DETAIL messages to conform to the style guide by capitalizing\nthe first word of sentences and ending sentences with a period.\n\nAuthor: Peter Smith \nReviewed-by: Chao Li \nReviewed-by: vignesh C \nReviewed-by: Xiaopeng Wang \nReviewed-by: Peter Eisentraut \nDiscussion: https://www.postgresql.org/message-id/flat/CAHut%2BPszSntkUgN%2BQa9matGY6MLEoFGSuVbuKDgnnTdZ7YPRwg%40mail.gmail.com", "completion": "Message style fixes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe angle-guessing minigame's result popup personifies your score with a\nhand-drawn stick-figure that changes expression by accuracy. Now that Angie\nappears across adev — the 404 page, docs search, the embedded editor, the\ntutorial intros and completions — give the minigame the same treatment so\nits result feels consistent with the rest of the docs.\n\nReplace the result reactor's stick-figure illustration with an Angie pose\nkeyed to accuracy (seven tiers, superhero down to angry). She is revealed\nonce the accuracy counter finishes counting up, popping in beside a speech\nbubble that carries the round's existing quote. The result popup is widened\nso Angie and the bubble sit side by side, and the share link is moved from\ntwitter.com to x.com.\n\nThis removes the previous hand-drawn stick-figure result art. NG the Angle,\nthe interactive character in the play area, is unchanged.\n\n(cherry picked from commit 8422da814d8311d605eaba8b99bf3bc63c21241a)", "completion": "feat(docs-infra): react with Angie in the playground minigame"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe angle-guessing minigame's result popup personifies your score with a\nhand-drawn stick-figure that changes expression by accuracy. Now that Angie\nappears across adev — the 404 page, docs search, the embedded editor, the\ntutorial intros and completions — give the minigame the same treatment so\nits result feels consistent with the rest of the docs.\n\nReplace the result reactor's stick-figure illustration with an Angie pose\nkeyed to accuracy (seven tiers, superhero down to angry). She is revealed\nonce the accuracy counter finishes counting up, popping in beside a speech\nbubble that carries the round's existing quote. The result popup is widened\nso Angie and the bubble sit side by side, and the share link is moved from\ntwitter.com to x.com.\n\nThis removes the previous hand-drawn stick-figure result art. NG the Angle,\nthe interactive character in the play area, is unchanged.", "completion": "feat(docs-infra): react with Angie in the playground minigame"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nFor internally consistent terminology", "completion": "pg_upgrade: Message wording fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWe've got no reports of problems. Get rid of it.\n\nAuthor: Álvaro Herrera \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/alewd1f2G0kKeM1i@alvherre.pgsql", "completion": "Remove assertion added by commit 7dcea51c2a4d"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nChange formatting and chars to be less of a match against actual\nformatting characters.\n\nReported-by: Phil\n\nDiscussion: https://postgr.es/m/177801333530.795.16999885814007014333@wrigleys.postgresql.org\n\nBackpatch-through: 19", "completion": "doc: clarify to_char(\"OF\") HH/MM doesn't represent actual chars"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nMention \"time zone conversion\" as a way to clarify the time zone is not\nstored in the database.\n\nReported-by: Richard Neill\n\nDiscussion: https://postgr.es/m/ddf41f033a8add84e1f28a095defafae@richardneill.org\n\nBackpatch-through: 19", "completion": "doc: clarify how TIMESTAMP WITH TIME ZONE behaves"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nOptions parsing is still painful for dict-style options.\n\nSolution:\nschema-maxxing => better `opt:get()` (will be the basis for `vim.o()`),\nunified (and more-detailed) err msgs.\n\n- Drop bespoke structure-builder in `_core/options.lua`.\n- Define `schema` for all non-primitive options (except 'guicursor' and\n statusline-style options); generate reified keysets `OptKeyDict`).\n - Generate 'fillchars' => `fcs_tab`, 'listchars' => `lcs_tab`.\n- `nvim_set_option_value`:\n - Return the improved structures. Also from `vim.opt.x:get()`.\n - Eliminate api <=> lua roundtrip, centralize option structure\n handling.\n- Improve/unify errors.\n - Bump ERR_BUFLEN 80 → 256 so the \"one of\" list isn't truncated.\n- Eliminate old 'diffopt' order-dependence (`iwhiteall` before `iwhite`)\n\nError samples:\n\n Typed-key path (opt_strings_check → diffopt/mousescroll/breakindentopt):\n E474: Unknown item 'foo'\n E474: 'context' requires a number\n E474: 'ver' number is out of range\n E474: 'algorithm' must be one of: myers, minimal, patience, histogram\n E474: 'filler' does not take a value\n\nRelated:\n\n- #31084\n- #34661\n- #31820\n- #14739\n- #20107\n- fix #18875\n - :get() returns `{ sbr = true, shift = '3' }` (reified-keyset) instead of `{'sbr', 'shift:3'}`\n - Setting via table now works too. `object_as_optval_for` `is_map` now recognizes struct options.\n- fix #30296\n - instead of `E474: Invalid argument`, errors now look like:\n ```\n E474: Invalid value 'x', expected one of: single, double: ambiwidth=x\n E474: Unknown item 'foo': diffopt=foo\n E474: 'context' requires a number: diffopt=context:x\n ```\n\nsimplify `win_float_parse_option` from #26799.", "completion": "feat(options): schema, \"dict\" options, messages"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\non_attach() calls refresh(), but there is no guarantee the attached\nbuffer is the current buffer. This can make linked editing request\nhandling assume the wrong window.\n\nSolution:\nCall refresh() only if the current buffer is attached. This keeps the\ninitial highlighting behavior while avoiding making incorrect request.", "completion": "fix(lsp): guard linked_editing_range refresh on attach"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFrees the memory allocated by `ngtcp2_crypto_ossl_init`, thus making\nValgrind happy. Works for versions of ngtcp2 >= 1.24.0.\n\nRef: https://github.com/ngtcp2/ngtcp2/issues/2207\n\nCloses #22363", "completion": "ngtcp2: clean up after ngtcp2 in `curl_global_cleanup`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1695905\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Thu Jul 23 08:24:25 2026\n(Merged from https://github.com/openssl/openssl/pull/31992)", "completion": "Fix missing NULL check in statem_clnt_construct_test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd coverage for the coreutils style output of `openssl dgst -r`,\nincluding the newline escaping done by newline_escape_filename() when\nthe digested file name contains a newline, and for the colon separated\noutput of `openssl dgst -c`.\n\nThe newline in file name part is skipped where such a file cannot be\ncreated.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Ryan Hooper \nMergeDate: Mon Jul 27 10:19:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32035)", "completion": "apps: test dgst -r and -c output formats"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 738b8fe9d2a9c164f3601b123cbdbb33bb9a0a04)", "completion": "docs: update attribute testing guide to include canonical example with local component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 7ad33fe56f25424fb51a1040\n\nPointed out by Zeropath\n\nCloses #22364", "completion": "dnscache: avoid double unlock"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwitter is now X. In the custom-route-matcher guide, point the author-credit\nlink at x.com and refer to an \"X (formerly Twitter) handle\" (clarified once,\nthen \"X handle\"), matching the \"X (formerly Twitter)\" wording already used in\nthe footer, navigation, and update guide.\n\n(cherry picked from commit 6557df5dbec8e205a5cecfc7039d76928ee4000e)", "completion": "docs: update stale Twitter reference to X in the URL matcher guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwitter is now X. In the custom-route-matcher guide, point the author-credit\nlink at x.com and refer to an \"X (formerly Twitter) handle\" (clarified once,\nthen \"X handle\"), matching the \"X (formerly Twitter)\" wording already used in\nthe footer, navigation, and update guide.", "completion": "docs: update stale Twitter reference to X in the URL matcher guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\napp_params_new_from_opts() returns NULL when a key option cannot be\nconverted, either because the key management does not settle the\nparameter or because the opt:value separator is missing. skeyutl\nignored that and generated the key without the requested options, only\nprinting the parameter error to stderr and still exiting successfully.\n\nBail out instead, the way the mac, kdf and enc applications do. A NULL\nreturn is only an error when key options were actually given, as\napp_params_new_from_opts() also returns NULL for an empty option list.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:06:03 2026\n(Merged from https://github.com/openssl/openssl/pull/32036)", "completion": "apps: fail skeyutl -genkey on bad -skeyopt"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe fake cipher key management accepted a key name and raw key bytes on\ngeneration and import, but did not advertise them as settable\nparameters, so applications converting opt:value strings with\nOSSL_PARAM_allocate_from_text() had nothing to look them up in.\n\nAdd the settable parameter table for both generation and import, and\nreport the key name as the key id, so that setting it has an observable\neffect.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:06:05 2026\n(Merged from https://github.com/openssl/openssl/pull/32036)", "completion": "test: support key options in the fake cipher provider"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCover the -skeyopt option of skeyutl using the fake cipher provider: a\nkey name passed as a key option shows up in the reported key id, while\nan option unknown to the key management and an option missing the\nopt:value separator both make the command fail.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:06:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32036)", "completion": "apps: test skeyutl -skeyopt handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nConditionally update the browser DevTools tab name to \"Angular & Wiz\" if the user is identified as a Google employee via internal corp network detection.", "completion": "feat(devtools): rename DevTools tab to \"Angular & Wiz\" for Googlers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit adds pgstat_prep_pending_from_entry_ref(), a new pgstats\nroutine that is able to prepare an existing PgStat_EntryRef to receive\npending stats. This split gives a way for callers to obtain first a\nreference via pgstat_get_entry_ref(), then set up pending data as two\nseparate, distinctive, steps.\n\nPreviously, the only way to get an entry reference with pending data\nready was pgstat_prep_pending_entry(), which bundles lookup, creation,\nand pending setup in a single call. Callers that need finer control\nover the entry creation had no way to attach pending data to an\nalready-obtained entry reference. One case where this has shown to\nmatter for a stats kind is where one wants to check some capacity (for\nexample where a GUC bounds the maximum numer of entries allowed) before\ndeciding if a new entry should be created. So this split can help in\nreducing calls to pgstat_get_entry_ref(), meaning less shmem hash table\nlookups.\n\nThe only logical ordering change is that pgStatPendingContext is\ninitialized after calling pgstat_get_entry_ref() in\npgstat_prep_pending_entry(). This does not matter in practice.\n\npgstat_prep_pending_entry() is refactored to use the new function\ninternally. All the existing callers are unchanged. Existing\nout-of-core custom stats kinds should see no impact.\n\nAuthor: Sami Imseih \nReviewed-by: Kyotaro Horiguchi \nReviewed-by: Michael Paquier \nDiscussion: https://postgr.es/m/CAA5RZ0sV+TsLejUMhAM=PJoOm8u-t8ru7B67KvyLCy=19sM87g@mail.gmail.com", "completion": "Add new pgstats routine to split pending data setup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIf an error happens during the initialization of the TYPEOID catcache,\nas part of lookup_type_cache(), the error handling of that lookup would\ncause an assertion failure via finalize_in_progress_typentries(), called\nduring error recovery, the presence of an in-progress type OID causing\na catcache initialization outside of a transaction context.\n\nThe in-progress list is now delayed to happen after the initial entry\nlookup. Alexander Lakhin has found a fancy way to reproduce the\nproblem, with the injection of probabilistic memory allocation failures.\n\nThis problem is unlikely going to show up in practice. Like the other\nchanges of this kind, no backpatch is done.\n\nReported-by: Alexander Lakhin \nAuthor: Matthias van de Meent \nDiscussion: https://postgr.es/m/95c64dc2-3abe-4f4e-b285-4c681f565d9f@gmail.com", "completion": "Improve lookup_type_cache() handling on out-of-memory errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- transfer the last located logical child when mismatch recovery replaces nodes\n- maintain the cache during Transition template unwrapping and fragment cleanup", "completion": "fix(runtime-vapor): update logical child cache after hydration mutations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nConvert the doc comment for ossl_quic_srtm_remove() from backslash-style\nDoxygen tags (\\brief, \\param, \\return) to the @-style equivalents\n(@brief, @param, @returns), matching the STYLE.md convention.\n\nComplements: 63afe639141f \"quic: report SRTM entry match status via an output argument\"\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Saša Nedvědický \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 12:03:18 2026\n(Merged from https://github.com/openssl/openssl/pull/32037)", "completion": "quic: use @-style Doxygen tags in ossl_quic_srtm_remove doc comment"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit cb1841d10ba96df1e058b4c3a3778d7a3157a2a2)", "completion": "docs: outdated section in the `Signal Forms | Custom controls` page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:19:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32043)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:18:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32042)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:17:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32041)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:17:15 2026\n(Merged from https://github.com/openssl/openssl/pull/32040)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:15:56 2026\n(Merged from https://github.com/openssl/openssl/pull/32039)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a previously missing CHANGES.md/NEWS.md entry for the Hollowbyte fix.\n\nReviewed-by: Paul Dale \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:15:32 2026\n(Merged from https://github.com/openssl/openssl/pull/32039)", "completion": "Update CHANGES/NEWS to mention the HollowByte fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vitest\nChanges:\nAddress review feedback on the pluggable benchmark provider API. The\ninitial design mirrored the coverage provider (a `getProvider` factory\nplus a `BenchmarkProviderModule` wrapper), which was a special case that\nbenchmarks — running only in tests — don't need.\n\n- Drop `BenchmarkProviderModule` and `getProvider`: a custom provider\n module now default-exports a `BenchmarkProvider` directly.\n- Reuse the existing `TestModuleRunner` interface instead of the bespoke\n `BenchmarkProviderLoader`.\n- Remove the `TestRunner.runBenchmarks` override hook, now redundant with\n the provider API, and inline `tinybench.run()` in the default provider.", "completion": "refactor(benchmark): simplify provider contract to a default export"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nTruthy checks omitted retry: 0, so clients never received an explicit zero reconnection delay. Use isNil like other MessageEvent fields.", "completion": "fix(core): serialize SSE retry field when value is zero"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAdd a property to easy/multi API calls that prohibit calling\nthe function when the involved SSL session cache is under lock\nby the current thread.\n\nChecks are only in effect when pthreads/Windows threads are\navailable.\n\nCloses #22367", "completion": "api-guard: check lock on session cache"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- use a live comment placeholder while async setup is pending\n- avoid duplicate dependency registration during hydration\n- clean up pending placeholders during unmount\n- preserve first-mount and active state for cached pending components", "completion": "fix(runtime-vapor): preserve pending async component position"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral guides, examples, and the update-guide recommendations linked to\nexternal resources over insecure http. Switch them to https.\n\n(cherry picked from commit 28d59e8d6357b6f5015657f06ecd7b543f00aba0)", "completion": "docs: use https for external links in adev"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral guides, examples, and the update-guide recommendations linked to\nexternal resources over insecure http. Switch them to https.", "completion": "docs: use https for external links in adev"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIt makes these scripts require Git 2.24.0+ (2019-11-04).\n\nRefs:\nhttps://git-scm.com/docs/gitcli\nhttps://nesbitt.io/2026/07/21/end-of-options.html\nhttps://github.com/git/git/commit/19e8789b236dfe33667747d5523d6689bb59b5ef\n\nCloses #22369", "completion": "scripts: replace/extend `--` with `--end-of-options` in git commands"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPropagate the crossorigin attribute from priority NgOptimizedImage hosts to SSR-generated preload links. Keep preload and image requests in the same credentials mode to avoid an anonymous image issuing an earlier credentialed request.\n\n(cherry picked from commit d14696e4308c5cd95cf2184cae3582b52f7c7cf3)", "completion": "fix(common): preserve crossorigin on image preloads"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPropagate the crossorigin attribute from priority NgOptimizedImage hosts to SSR-generated preload links. Keep preload and image requests in the same credentials mode to avoid an anonymous image issuing an earlier credentialed request.", "completion": "fix(common): preserve crossorigin on image preloads"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the missing params argument for OSSL_FUNC_kem_decapsulate_init(),\nremove stale name references, and fix the malformed provider-keymgmt(7) link.\n\nComplements: 78c44b05945b Add HPKE DHKEM provider support for EC, X25519 and X448.\nSigned-off-by: olszomal \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:57:46 2026\n(Merged from https://github.com/openssl/openssl/pull/32045)", "completion": "DOCS: Fix KEM init function documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the missing params argument for OSSL_FUNC_kem_decapsulate_init(),\nremove stale name references, and fix the malformed provider-keymgmt(7) link.\n\nComplements: 78c44b05945b Add HPKE DHKEM provider support for EC, X25519 and X448.\nSigned-off-by: olszomal \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:57:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32045)", "completion": "DOCS: Fix KEM init function documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the missing params argument for OSSL_FUNC_kem_decapsulate_init(),\nremove stale name references, and fix the malformed provider-keymgmt(7) link.\n\nComplements: 78c44b05945b Add HPKE DHKEM provider support for EC, X25519 and X448.\nSigned-off-by: olszomal \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:57:23 2026\n(Merged from https://github.com/openssl/openssl/pull/32045)", "completion": "DOCS: Fix KEM init function documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the missing params argument for OSSL_FUNC_kem_decapsulate_init(),\nremove stale name references, and fix the malformed provider-keymgmt(7) link.\n\nComplements: 78c44b05945b Add HPKE DHKEM provider support for EC, X25519 and X448.\nSigned-off-by: olszomal \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:57:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32045)", "completion": "DOCS: Fix KEM init function documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the missing params argument for OSSL_FUNC_kem_decapsulate_init(),\nremove stale name references, and fix the malformed provider-keymgmt(7) link.\n\nComplements: 78c44b05945b Add HPKE DHKEM provider support for EC, X25519 and X448.\nSigned-off-by: olszomal \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Mon Jul 27 07:57:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32045)", "completion": "DOCS: Fix KEM init function documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\non_attach() calls refresh(), but there is no guarantee the attached\nbuffer is the current buffer. This can make linked editing request\nhandling assume the wrong window.\n\nSolution:\nCall refresh() only if the current buffer is attached. This keeps the\ninitial highlighting behavior while avoiding making incorrect request.\n\n(cherry picked from commit 9180c6e093391969b2751d09b6fa0397dbfc7882)", "completion": "backport: fix(lsp): guard linked_editing_range refresh on attach"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n* fix(help): preserve multi-letter CTRL modifiers in :help subject\n\nProblem: After PR 39537 normalized `CTRL-U-default` by excluding\n`-` from the trigger char class, the regex `(CTRL%-[^{])([^-_\\\\])`\nalso fires between `CTRL-S` and the `H` of the `SHIFT` modifier\nin tags like `c_CTRL-SHIFT-V`, splitting it into the non-existent\n`c_CTRL-S_HIFT-V`.\n\nSolution: Exclude uppercase letters from the char class so a\nmulti-letter modifier following `CTRL-X` (e.g. `SHIFT`, `ALT`) is\nno longer split. The `-` exclusion from 39537 is preserved so\n`i_CTRL-U-default` still works.\n\n* fix(help): escape ~ in expr-=~? exception to keep regex valid\n\nProblem: The `expr-=~?` exception in the tag alias table maps to\n`=~?`, but in Vim's regex engine `~` refers to the previous\nsubstitute pattern. With no prior substitute the pattern fails to\ncompile, so `:help expr-=~?` returns E149 even though the tag exists.\n\nSolution: Escape `~` as \\\\\\~` so the alias expands to a valid\nregex (`=\\\\\\~?`) that substring-matches the `expr-=~?` tag. Other\n`expr-X?` entries are unaffected since they don't contain `~`.\n\n* fix(help): don't insert _ before CTRL- when preceded by -\n\nProblem: The rule `([^_])CTRL%- -> %1_CTRL-` inserts an underscore\nbetween any non-underscore char and `CTRL-`, which wrongly rewrites\ntags like `map-CTRL-C` and `telnet-CTRL-]` (where `CTRL-` is\nliteral text in the tag, not a key chord).\n\nSolution: Exclude `-` from the trigger char class so a hyphen\nimmediately before `CTRL-` is preserved. The existing behavior for\n`iCTRL-GCTRL-J` -> `i_CTRL-G_CTRL-J` is unaffected because the\n`G` before `CTRL-J` is not `-`.\n\n* fix(help): only treat ^X as caret notation for valid control chars\n\nProblem: The regex `%^([^_])` converts any `^X` to `CTRL-X`,\nincluding `:set^=` where `^=` is literal text in the tag, not a\ncaret-notation control character.\n\nSolution: Restrict the transformation to caret-notation chars\n(`%a` or one of `?@[\\\\]^{}`). This matches the C reference\nbehavior where `^X` is only conv", "completion": "fix(help): handle escape edge cases #40901"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe ng-container and binding template guide files each began with a\nUTF-8 BOM (EF BB BF) before the leading `#`. The docs markdown parser\nonly promotes `#` to an H1 when it is the first character on the line,\nso the BOM demoted the title to paragraph text (`

# ...

`) and the\nstandard docs header (breadcrumbs, page title, edit button) never\nrendered.\n\nStripping the BOM restores `#` as the first character, so both pages\nnow generate the proper `
` block. Verified\nby rebuilding //adev/src/content/guide/templates:templates and\ninspecting the generated HTML.\n\nFixes #69889\n\n(cherry picked from commit f12db896597f246cea7b26dda43c776d8a1e8595)", "completion": "docs: fix first heading rendering as paragraph on two template guides"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe ng-container and binding template guide files each began with a\nUTF-8 BOM (EF BB BF) before the leading `#`. The docs markdown parser\nonly promotes `#` to an H1 when it is the first character on the line,\nso the BOM demoted the title to paragraph text (`

# ...

`) and the\nstandard docs header (breadcrumbs, page title, edit button) never\nrendered.\n\nStripping the BOM restores `#` as the first character, so both pages\nnow generate the proper `
` block. Verified\nby rebuilding //adev/src/content/guide/templates:templates and\ninspecting the generated HTML.\n\nFixes #69889", "completion": "docs: fix first heading rendering as paragraph on two template guides"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCorrect the OSSL_FUNC_keyexch_derive_skey() return type, derive_skey\nreturn-value descriptions, stale function names, and broken links.\n\nSigned-off-by: olszomal \nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 28 11:13:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32046", "completion": "DOCS: Fix derive_skey provider documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCorrect the OSSL_FUNC_keyexch_derive_skey() return type, derive_skey\nreturn-value descriptions, stale function names, and broken links.\n\nSigned-off-by: olszomal \nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 28 11:13:19 2026\nMerged-from: https://github.com/openssl/openssl/pull/32046", "completion": "DOCS: Fix derive_skey provider documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCorrect the OSSL_FUNC_keyexch_derive_skey() return type, derive_skey\nreturn-value descriptions, stale function names, and broken links.\n\nSigned-off-by: olszomal \nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 28 11:13:06 2026\nMerged-from: https://github.com/openssl/openssl/pull/32046", "completion": "DOCS: Fix derive_skey provider documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nA leading UTF-8 byte order mark (U+FEFF) before the first `#` stops the\nMarkdown parser from recognizing the heading, so the guide renders its\ntitle as a paragraph and drops the standard docs header. The character\nis invisible, so it cannot be caught in review.\n\nAdd a check in the guides generation pipeline that throws when a source\nfile starts with a BOM, failing the build with the offending file name.\nThis sits alongside the existing unknown-anchor check and prevents the\nregression fixed in #69889 from recurring.\n\n(cherry picked from commit ab52df470a3be72d5d08d88af0c026cbf2ce8ee3)", "completion": "fix(docs-infra): fail the guide build when a markdown file starts with a BOM"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nA leading UTF-8 byte order mark (U+FEFF) before the first `#` stops the\nMarkdown parser from recognizing the heading, so the guide renders its\ntitle as a paragraph and drops the standard docs header. The character\nis invisible, so it cannot be caught in review.\n\nAdd a check in the guides generation pipeline that throws when a source\nfile starts with a BOM, failing the build with the offending file name.\nThis sits alongside the existing unknown-anchor check and prevents the\nregression fixed in #69889 from recurring.", "completion": "fix(docs-infra): fail the guide build when a markdown file starts with a BOM"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: do_sub() only checks the timeout limit after finishing a line.\n A pathological regex will run on a single line input unbounded\n until the compute is completed.\n\nSolution: Pass the timeout limit to `vim_regexec_multi()` so the\n computation on the regex engine is bounded per-line.\n\nSigned-off-by: XiaowenHu96 \n(cherry picked from commit bd73d8c01146695b727849e67fc1f1f209d5884f)", "completion": "fix(inccommand): enforce timeout during matching, not just after a line #40892"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: do_sub() only checks the timeout limit after finishing a line.\n A pathological regex will run on a single line input unbounded\n until the compute is completed.\n\nSolution: Pass the timeout limit to `vim_regexec_multi()` so the\n computation on the regex engine is bounded per-line.", "completion": "fix(inccommand): enforce timeout during matching, not just after a line #40892"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSummarizeWAL documents that maximum_lsn should be passed as \"the switch\npoint when reading a historic timeline, or the most-recently-measured end of\nWAL when reading the current timeline.\" But the caller always passed the\nmost recently measured end-of-WAL even when reading from a historic\ntimeline, due to an oversight on my part. Fix that.\n\nAs far as I can determine, for this to become an issue in practice, it's\nnecessary to have a corrupted WAL file in the archive. SummarizeWAL checks\nthat every record it processes both starts and ends before switch_lsn; so if\nall the WAL files in the archive are valid, SummarizeWAL will still discover\nwhere it should stop summarizing and do the right thing. However, if\nthere's a corrupted file in the WAL archive, and if it is also the case that\nthe end of the current timeline has advanced past the switch point, then the\nincorrect maximum_lsn value can result in trying to read an invalid record\nand erroring out, which leads repeatedly retrying and failing with an error\nevery time.\n\nOne way this could occur is if a new primary is promoted and creates a\n.partial file, and the user manually renames that file to remove the suffix,\nand it is then archived. In that situation, the tail end of the file need\nnot be valid WAL, and that could lead to a stuck WAL summarizer.\n\nReported-by: Fabrice Chapuis \nAnalyzed-by: Thom Brown (using claude)\nDiscussion: http://postgr.es/m/CAA5-nLDdvGMkN6Z-GaHGHG5T7QWEgv4YoHO7XvOJbeD00cghNg@mail.gmail.com\nBackpatch-through: 17", "completion": "walsummarizer: Guard against WAL files whose tail ends are not valid."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdate pnpm lock after it got desychronized in\n791b0646c8 build: update all non-major dependencies", "completion": "build: update pnpm-lock.yaml"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nRedundant code.\n\nSolution:\nCombine path_has_wildcard() and path_has_exp_wildcard(). They have similar logic.\nAlso, the latter operates on whatever wildcards remain after shell/env/backtick\nexpansion, so the two felt somewhat related.\n\nAlso drop some unnecessary MB_PTR_ADV calls.", "completion": "refactor(path): path_has_wildcard() #40893"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix: avoid memoizing Form warning hook\n\n* test: harden Form compiler regression test\n\n* fix: avoid memoizing Form warning hooks\n\n* fix: expose Form warning helper as hook", "completion": "fix: avoid Form warning hook compiler memoization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nx509_name_encode() cleared the modified flag before x509_name_canon().\nIf canonicalization then failed, later encodes reused the DER cache while\ncanonical state was absent, allowing a malformed name to compare and hash\nas an empty name.\n\nClear modified only after both cache representations succeed. Validate both\noutput-pass encodes and propagate nested ASN.1 encoding failures so partial\noutput is not reported as success.\n\nAdd malformed-name cache regression coverage and multi-valued RDN\nallocation-failure coverage.\n\nRefs #32010\n\nAssisted-by: OpenAI Codex:gpt-5.6-sol\nReviewed-by: Jakub Zelenka \nReviewed-by: Mounir Idrassi \nMerge-date: Mon Sep 14 14:13:33 2026\nMerged-from: https://github.com/openssl/openssl/pull/32047\n(cherry picked from commit 4fc10a5bfe8658d080a44b08fb6229fa666949ac)", "completion": "X509: keep names modified until canonicalization succeeds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nx509_name_encode() cleared the modified flag before x509_name_canon().\nIf canonicalization then failed, later encodes reused the DER cache while\ncanonical state was absent, allowing a malformed name to compare and hash\nas an empty name.\n\nClear modified only after both cache representations succeed. Validate both\noutput-pass encodes and propagate nested ASN.1 encoding failures so partial\noutput is not reported as success.\n\nAdd malformed-name cache regression coverage and multi-valued RDN\nallocation-failure coverage.\n\nRefs #32010\n\nAssisted-by: OpenAI Codex:gpt-5.6-sol\nReviewed-by: Jakub Zelenka \nReviewed-by: Mounir Idrassi \nMerge-date: Mon Sep 14 14:13:33 2026\nMerged-from: https://github.com/openssl/openssl/pull/32047", "completion": "X509: keep names modified until canonicalization succeeds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWhen buffer is open in multiple windows and its line count changes, any\n'statusline' or 'rulerformat' items depending on it (e.g. %P) will\nbecome invalid in non-current windows because w_redr_status is only set\non first change.\n\nSolution:\nSet w_redr_status on all windows with the buffer when the line count\nchanges.", "completion": "fix(ui): invalid ruler items in other windows #40891"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a test recipe subtest checking that 'openssl rsa -modulus' prints the\nexpected modulus for both a private key and a -pubin public key, mirroring\nthe existing dsa -modulus test.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Paul Dale \nReviewed-by: Paul Yang \nReviewed-by: Daniel Kubec \nMergeDate: Mon Jul 27 09:08:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32048)", "completion": "apps: test rsa -modulus output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe core behaviors of `nvim.dir` cannot be reused by consumers\nsuch as the archive plugin, ssh browser, etc.\n\nSolution:\n- Define a basic \"provider\" shape.\n- Extract the filesystem provider.", "completion": "feat(dir): provider framework #40738"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve createUrlTree command semantics, including custom serializer inputs, while keeping the single-leading-slash guarantee at the default serialization boundary.\n\nExpand coverage for command forms, public UrlTree values, secondary outlets, and preserved query parameters and fragments.\n\nFixes #69700\n\n(cherry picked from commit 435f8b2b8b67277fc69888911251d14b32705828)", "completion": "fix(router): limit protocol-relative URL handling to serialization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreserve createUrlTree command semantics, including custom serializer inputs, while keeping the single-leading-slash guarantee at the default serialization boundary.\n\nExpand coverage for command forms, public UrlTree values, secondary outlets, and preserved query parameters and fragments.\n\nFixes #69700", "completion": "fix(router): limit protocol-relative URL handling to serialization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 90ac011fa92d28d5b681998e60029e2ee6a2695a)", "completion": "docs: clarify behavior of credentials option during SSR on Node.js"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd test recipe subtests for the pkey app format options: the public key\nPEM/DER round-trip, format detection when -inform is omitted, rejection of\na mismatching -inform, the restriction of -outform to PEM and DER, and\nreading a private key from a PKCS#12 file with -inform P12.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Paul Dale \nMergeDate: Thu Jul 30 08:54:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32049)", "completion": "apps: test pkey -inform and -outform handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:02:30 2026", "completion": "Add test for CVE-2026-63073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:02:11 2026", "completion": "Add test for CVE-2026-63073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:01:48 2026", "completion": "Add test for CVE-2026-63073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \nReviewed-by: Milan Broz \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 13:00:50 2026", "completion": "Add test for CVE-2026-63073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Norbert Pocs \nReviewed-by: Andrew Dinh \nReviewed-by: Igor Ustinov \nMerge-date: Mon Aug 24 12:53:37 2026", "completion": "Add test for CVE-2026-63073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- make `const` data `static`, where missing and possible.\n- replace `strlen()` on literal or const strings with `sizeof()`.\n While the latter is optimized by popular C compiler, e.g. MSVC only\n does it with `/O2`.\n- replace magic numbers with `sizeof()`, where missing.\n- introduce `CURL_CSTRLEN()` macro for `sizeof(char[]) - 1`.\n- use `CURL_CSTRLEN()` macro.\n- move `const` before integer types, where missing.\n- replace `char *var` with `var[]`, where missing and possible.\n- use double const, where missing.\n `static const char *` -> `static const char * const`.\n- lib1514: constify pointers.\n- unit3205: drop redundant cast, avoid another one.\n- unit1666: map `OID()` macro to identical `STRCONST()`.\n\nCloses #22406", "completion": "tidy-up: use more `static`, `sizeof()`, `char[]`, double-const"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:38:35 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:38:16 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:37:11 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim's code and test for channel,job API are already N/A.\nBlacklisting runtime/doc/channel.txt ensures most patches for it\nwill be detected as N/A.\nVim's API that is too incompatible with Neovim must be handled\noutside vim-patch.sh .", "completion": "build(vim-patch): n/a doc for channel,job api"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nlonewolfyx:correct-placeholder-type", "completion": "docs(Select): correct placeholder type to `ReactNode`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd the following helper functions:\n * create_quic_ctx_pair() - creates pair of SSL_CTX (server, client).\n * create_quic_conn_objects() - creates pair of SSL objects, client\n and listener. They both are 'connected' by BIO_dgram_pair.\n * create_quic_client() - creates SSL QUIC client object bound to BIO\n object provided by caller.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:27 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit f20e51341d3134bed58e6bb18475b80bfd5712ce)\n(cherry picked from commit 50c55eed777b1f9041256399f9cc6b3cc0c91f23)", "completion": "test/quictestlib.c: add functions to create QUIC objects on dgram bio"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd the following helper functions:\n * create_quic_ctx_pair() - creates pair of SSL_CTX (server, client).\n * create_quic_conn_objects() - creates pair of SSL objects, client\n and listener. They both are 'connected' by BIO_dgram_pair.\n * create_quic_client() - creates SSL QUIC client object bound to BIO\n object provided by caller.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:27 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit f20e51341d3134bed58e6bb18475b80bfd5712ce)", "completion": "test/quictestlib.c: add functions to create QUIC objects on dgram bio"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd the following helper functions:\n * create_quic_ctx_pair() - creates pair of SSL_CTX (server, client).\n * create_quic_conn_objects() - creates pair of SSL objects, client\n and listener. They both are 'connected' by BIO_dgram_pair.\n * create_quic_client() - creates SSL QUIC client object bound to BIO\n object provided by caller.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:27 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)", "completion": "test/quictestlib.c: add functions to create QUIC objects on dgram bio"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSequence synchronization requires the page_lsn field returned by\npg_get_sequence_data(), which was added in PostgreSQL 19. Previously,\nrequesting sequence synchronization against an older publisher (via\nALTER SUBSCRIPTION ... REFRESH SEQUENCES or by running\nALTER SUBSCRIPTION ... CONNECTION on a disabled subscription with\nsequences in the INIT state and subsequently enabling the subscription)\nwould cause the sequence synchronization worker to repeatedly fail with a\nconfusing \"invalid query response\" error.\n\nCheck the publisher's server version up front in both\nAlterSubscription_refresh_seq() and copy_sequences(), and error out\nimmediately when it predates PostgreSQL 19.\n\nAlso document the PostgreSQL 19 publisher requirement for sequence\nreplication in the logical replication documentation and in\nALTER SUBSCRIPTION ... REFRESH SEQUENCES.\n\nReported-by: Noah Misch \nAuthor: vignesh C \nReviewed-by: Shveta Malik \nReviewed-by: Hayato Kuroda \nReviewed-by: Amit Kapila \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Reject sequence synchronization against pre-PostgreSQL 19 publishers."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ninjection_wait() only clears its slot in the waiter array after the\nwait loop finishes. When the waiting query is canceled or the backend\nis terminated (wait look has a CHECK_FOR_INTERRUPS), the slot leaks.\nLater wakeups of the same point then bump the counter of the leaked slot\ninstead of the real waiter, that sleeps forever. Repeated leaks can\nexhaust all the slots.\n\nThe code is changed so as the waiting loop is wrapped with\nPG_ENSURE_ERROR_CLEANUP, so as the injection point slots, that are\nshared resources, can be cleaned up on ERROR as much as a FATAL.\n\nAn isolation test is added: cancel one waiter, terminate another waiter,\nthen check that a later waiter still receives a wakeup. Without the\nfixed code, the test would fail on timeout.\n\nAuthor: Zsolt Parragi \nDiscussion: https://postgr.es/m/CAN4CZFO+KF=cc0-iEg28RhqRBp_fTs6D4b8b7D7DB-pGYP3Ccg@mail.gmail.com\nBackpatch-through: 17", "completion": "injection_points: Clear waiter slot on error and exit"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim channel API logging is N/A.", "completion": "build(vim-patch): logfile.c is N/A"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22371", "completion": "ctype: exclude control bytes from ISPRINT and ISGRAPH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe documentation of pg_stat_activity used an incomplete list of values\nfor backend_type. While on it, it is improved to use an itemized list,\nnow ordered alphabetically, with a short description about each item.\n\nAuthor: Laurenz Albe \nReviewed-By: Michael Paquier \nReviewed-By: Fujii Masao \nDiscussion: https://postgr.es/m/5e94c0196084f648ae6a00107125494f5804318a.camel@cybertec.at", "completion": "doc: Improve description of pg_stat_activity.backend_type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCurrently, there is no limit for pending QUIC connections. The port\ndefault packet handler creates channel for every valid initial packet\nwhich does belong to existing channel (a.k.a. connection). The newly\ncreated channel is inserted to list of pending channels where it waits\nto be accepted by local application by call\nto SSL_accept_connection(3ossl).\n\nThis change introduces a limit for pending connection. The pending\nqueue is limited to 256 pending connections. Applications may change\nthe limit by calling SSL_set_feature_request_uint(3ossl)\non SSL server listener object with configurable value\nSSL_VALUE_QUIC_MAX_PENDING_CONNS.\n\nFixes: CVE-2026-14456\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit 9416706d408bb84deb7cee4647bff3045d2dc7ba)\n(cherry picked from commit 4084152e040329ca0194c4c1750b9b46d00a5b6b)", "completion": "QUIC server: limit number of pending QUIC channels/connections"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCurrently, there is no limit for pending QUIC connections. The port\ndefault packet handler creates channel for every valid initial packet\nwhich does belong to existing channel (a.k.a. connection). The newly\ncreated channel is inserted to list of pending channels where it waits\nto be accepted by local application by call\nto SSL_accept_connection(3ossl).\n\nThis change introduces a limit for pending connection. The pending\nqueue is limited to 256 pending connections. Applications may change\nthe limit by calling SSL_set_feature_request_uint(3ossl)\non SSL server listener object with configurable value\nSSL_VALUE_QUIC_MAX_PENDING_CONNS.\n\nFixes: CVE-2026-14456\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit 9416706d408bb84deb7cee4647bff3045d2dc7ba)", "completion": "QUIC server: limit number of pending QUIC channels/connections"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCurrently, there is no limit for pending QUIC connections. The port\ndefault packet handler creates channel for every valid initial packet\nwhich does belong to existing channel (a.k.a. connection). The newly\ncreated channel is inserted to list of pending channels where it waits\nto be accepted by local application by call\nto SSL_accept_connection(3ossl).\n\nThis change introduces a limit for pending connection. The pending\nqueue is limited to 256 pending connections. Applications may change\nthe limit by calling SSL_set_feature_request_uint(3ossl)\non SSL server listener object with configurable value\nSSL_VALUE_QUIC_MAX_PENDING_CONNS.\n\nFixes: CVE-2026-14456\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)", "completion": "QUIC server: limit number of pending QUIC channels/connections"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nsocket_putmessage_noblock() used pq_putmessage(), which redirects to\nPqCommMethods->putmessage. In the common cases, this points to\nsocket_putmessage(), but it would become incorrect if PqCommMethods\npoints to a different implementation.\n\nThis change may look like a bug, but as far as I can see this is mostly\ncosmetic. The code is able to work currently, as the repalloc() done in\nthe noblock() call ensures that the blocking path of internal_putbytes()\nis never reached. The issue has gone unnoticed since 2bd9e412f92b.\n\nAuthor: Anthonin Bonnefoy \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAO6_Xqpf5+Rzw_-XOOz-d-R5x6_2JHtpnzXP0nrYWiHyZokA_Q@mail.gmail.com", "completion": "Fix socket_putmessage_noblock() to call socket_putmessage()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is a regression test for CVE-2026-14456.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:30 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit 0461a5636deca9af034db70ff017ad1138836c8c)\n(cherry picked from commit d446963b2622ee371df76971e5e2ddc7289839c4)", "completion": "test/quicapitest.c: add test for pending connections limit enforcement"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is a regression test for CVE-2026-14456.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:30 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)\n\n(cherry picked from commit 0461a5636deca9af034db70ff017ad1138836c8c)", "completion": "test/quicapitest.c: add test for pending connections limit enforcement"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is a regression test for CVE-2026-14456.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Wed Aug 12 15:00:30 2026\n(Merged from https://github.com/openssl/openssl/pull/32052)", "completion": "test/quicapitest.c: add test for pending connections limit enforcement"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- track adopted SSR ranges while async setup is pending\n- move, resolve, and unmount ranges from their live DOM position\n- align Vapor and VDOM interop ownership with regression coverage", "completion": "fix(runtime-vapor): preserve pending async hydration ranges"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe were raising the suggestion about enabling `strictTemplates` when `strictTemplates` is ommitted, however the option is now enabled by default.\n\nFixes #69905.\n\n(cherry picked from commit e606a020e90cf130f3ab532a7be553bf899313c2)", "completion": "fix(language-service): account for strictTemplates being enabled by default"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe were raising the suggestion about enabling `strictTemplates` when `strictTemplates` is ommitted, however the option is now enabled by default.\n\nFixes #69905.", "completion": "fix(language-service): account for strictTemplates being enabled by default"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:44:54 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:44:05 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:42:04 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:38:35 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:38:16 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMerge-date: Mon Aug 24 14:37:11 2026", "completion": "Add test for CVE-2026-63072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFix handling of DoH response that only asks for HTTPS records.\n\nAdd test 2117 for checking that a HTTPS-RR resolve is processed,\neven though the actual answer is invalid.\n\nCloses #22372", "completion": "httpsrr: DoH with HTTPS, fix response handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdditive: schedule and bare-manual runs unchanged. Adds validated,\nfail-closed pr/head_sha/check_run_id inputs so a caller can dispatch against\nan exact commit; run-name echoes them back for correlation.\n\nCo-Authored-By: Claude Opus 4.8 (1M context) \n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:16:54 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: allow ct-validation-daily to be dispatched against a PR head SHA"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nImprove the documentation for pg_stat_recovery in several ways:\n\n- Mention the view in high-availability.sgml as a way to monitor\n recovery state and replay progress, alongside the existing recovery\n information functions.\n- Clarify that the view returns at most one row, not exactly one row,\n and no rows to users who lack the pg_read_all_stats privilege.\n- Correct the description of last_replayed_end_lsn to clarify that it\n is the end LSN of the last replayed record plus one.\n- Document that replay_end_tli equals last_replayed_tli when no WAL\n record is currently being replayed.\n- Clarify that current_chunk_start_time is NULL until streaming WAL\n has been received.\n\nBackpatch to v19, where pg_stat_recovery was introduced.\n\nAuthor: Fujii Masao \nReviewed-by: Michael Paquier \nDiscussion: https://postgr.es/m/CAHGQGwGRavm18HqnQn_f68QB96qk6arhjET1V93OJH09Mgojkg@mail.gmail.com\nBackpatch-through: 19", "completion": "doc: Improve pg_stat_recovery documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nFor subscriptions using SERVER, changing the owner can change the\neffective connection string. However, ALTER SUBSCRIPTION ... OWNER TO\ndid not validate the generated conninfo for the new owner.\n\nAs a result, ownership could be transferred to a non-superuser whose\ngenerated connection string did not satisfy password_required=true.\nThe ownership change succeeded, but the subscription would fail later\nwhen the worker or another command tried to connect.\n\nFix this by making ALTER SUBSCRIPTION ... OWNER TO validate the new\nowner's generated conninfo with walrcv_check_conninfo().\n\nBackpatch to v19, where SERVER subscriptions were introduced.\n\nAuthor: Fujii Masao \nReviewed-by: Yuanchao Zhang <145zhangyc@gmail.com>\nReviewed-by: Hayato Kuroda \nDiscussion: https://postgr.es/m/CAHGQGwFGa6+wWVgUmZPFwN=fBY59mYPkMK3=TxT=Pv5C1mNNRQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Validate subscription conninfo on owner change"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_keygen() and the related keygen helpers take an EC curve name\nas a string parameter, but the page did not point to any way of\ndiscovering the accepted names. Add a reference to\nEC_get_builtin_curves(3), which lists the built-in curve NIDs, and\nOSSL_EC_curve_nid2name(3), which converts a NID to the name string\naccepted by the keygen functions.\n\nCo-Authored-By: Claude Opus 4.8 \nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 13:47:47 2026\nMerged-from: https://github.com/openssl/openssl/pull/29912", "completion": "doc: add reference to how to list EC curve names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_keygen() and the related keygen helpers take an EC curve name\nas a string parameter, but the page did not point to any way of\ndiscovering the accepted names. Add a reference to\nEC_get_builtin_curves(3), which lists the built-in curve NIDs, and\nOSSL_EC_curve_nid2name(3), which converts a NID to the name string\naccepted by the keygen functions.\n\nCo-Authored-By: Claude Opus 4.8 \nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 13:47:16 2026\nMerged-from: https://github.com/openssl/openssl/pull/29912", "completion": "doc: add reference to how to list EC curve names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_keygen() and the related keygen helpers take an EC curve name\nas a string parameter, but the page did not point to any way of\ndiscovering the accepted names. Add a reference to\nEC_get_builtin_curves(3), which lists the built-in curve NIDs, and\nOSSL_EC_curve_nid2name(3), which converts a NID to the name string\naccepted by the keygen functions.\n\nCo-Authored-By: Claude Opus 4.8 \nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 13:45:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/29912", "completion": "doc: add reference to how to list EC curve names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_keygen() and the related keygen helpers take an EC curve name\nas a string parameter, but the page did not point to any way of\ndiscovering the accepted names. Add a reference to\nEC_get_builtin_curves(3), which lists the built-in curve NIDs, and\nOSSL_EC_curve_nid2name(3), which converts a NID to the name string\naccepted by the keygen functions.\n\nCo-Authored-By: Claude Opus 4.8 \nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 13:45:31 2026\nMerged-from: https://github.com/openssl/openssl/pull/29912", "completion": "doc: add reference to how to list EC curve names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEVP_PKEY_keygen() and the related keygen helpers take an EC curve name\nas a string parameter, but the page did not point to any way of\ndiscovering the accepted names. Add a reference to\nEC_get_builtin_curves(3), which lists the built-in curve NIDs, and\nOSSL_EC_curve_nid2name(3), which converts a NID to the name string\naccepted by the keygen functions.\n\nCo-Authored-By: Claude Opus 4.8 \nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Paul Dale \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 13:45:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/29912", "completion": "doc: add reference to how to list EC curve names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdditive: schedule and bare-manual runs unchanged. Adds validated,\nfail-closed pr/head_sha/check_run_id inputs so a caller can dispatch each\nagainst an exact commit; run-name echoes them back for correlation.\n\nCo-Authored-By: Claude Opus 4.8 (1M context) \n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:16:55 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: allow run-checker-daily and valgrind-daily to be dispatched against a PR head SHA"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`:restart` on Windows always forces `AllocConsole`, even though we could\nreuse old server's existing console + unnecessary env.\n\nAnalysis:\nAfter d5516daf121aa718e79bcd423ee24c24492893c0 changed the restart\nlifecycle and 789741bb83d1f31b7162cd8944bc2d846fa2fa51 separated the\nWindows console paths, we no longer need to force `AllocConsole()` for\n`:restart`. The `:detach` path now allocates its own console when it\nactually runs.\n\nSolution:\nTry to attach the replacement server to its parent’s console and fall\nback to `AllocConsole()` if attachment fails. Drop the restart-specific\nenv that forced allocation.\n\nAs documented by Microsoft, [“A console is closed when the last process\nattached to it terminates or calls\n`FreeConsole`.”](https://learn.microsoft.com/en-us/windows/console/attachconsole)\n\nBtw, this way we can preserve `io.stdout:write()`, though if for some\nreason `AttachConsole` would fail then it won't work; but now at least\nit's not always not rendering on `:restart`.", "completion": "refactor(:restart): unnecessary console allocation on Windows #40919"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nOnly look for gethostbyname in libwatt in $WATT_ROOT/lib if WATT_ROOT\nhas actually been set. This avoids configure trying to search in /lib,\nwhich won't every succeed and can cause problems in cross builds which\ncheck that host paths are not being searched.\n\nCloses #22380", "completion": "configure: only check in the watt library if WATT_ROOT is set"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- connclose/streamclose/connkeep() remove description string that was\n never used anywhere. Add trace statements where reasons for closing\n were not already traced and maybe not obvious.\n- multi_remove_handle: only lookup former connection in pool when\n transfer is set to connect only\n- test1554: adapt expectations now that pool is less often locked\n\nCloses #22379", "completion": "connect: connection close tweaks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nClarify the bot-only workflow inputs and validate any supplied tuple through\na shared reusable workflow without interpolating input values into shell source.\n\nCo-Authored-By: Claude Opus 4.8 (1M context) \n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:16:56 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: centralize dispatch input validation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:16:57 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: allow dispatch cancellation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:16:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: preserve valgrind fork runs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nVisual Studio 2013 does not provide the C99 __func__ predefined identifier in C mode. Use OPENSSL_FUNC, which maps to the compiler-supported equivalent.\n\nThis is the only source change required to compile current master with VS2013 Update 5 (cl 18.00.40629), on both x86 and x64.\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Fri Jul 31 13:13:04 2026\nReviewed-by: Bob Beck \nReviewed-by: Nikola Pajkovsky \nMerged-from: https://github.com/openssl/openssl/pull/32419", "completion": "Fix VS2013 build of QUIC radix tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nVisual Studio 2013 does not provide the C99 __func__ predefined identifier in C mode. Use OPENSSL_FUNC, which maps to the compiler-supported equivalent.\n\nThis is the only source change required to compile current master with VS2013 Update 5 (cl 18.00.40629), on both x86 and x64.\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Fri Jul 31 13:13:04 2026\n(Merged from https://github.com/openssl/openssl/pull/31988)", "completion": "Fix VS2013 build of QUIC radix tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe Visual Studio 2013 CRT does not support the C99 z, t and j length modifiers. Passing such formats to _vsnprintf_s invokes the invalid-parameter path and normally terminates the process.\n\nFor _MSC_VER < 1900, translate z and t to the pointer-sized I modifier and j to I64 before calling the CRT. Allocate a translated format only when needed, leaving newer MSVC versions and unaffected formats unchanged. Delegate BIO_snprintf to BIO_vsnprintf so all BIO formatting entry points use the same compatibility path.\n\nAdd focused coverage for BIO_snprintf, BIO_vsnprintf and BIO_printf, including the large-output allocation path and truncation behavior.\n\nFixes #31645\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Fri Jul 31 13:13:06 2026\nReviewed-by: Bob Beck \nReviewed-by: Nikola Pajkovsky \nMerged-from: https://github.com/openssl/openssl/pull/32419", "completion": "Fix C99 printf length modifiers with VS2013 CRT"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe Visual Studio 2013 CRT does not support the C99 z, t and j length modifiers. Passing such formats to _vsnprintf_s invokes the invalid-parameter path and normally terminates the process.\n\nFor _MSC_VER < 1900, translate z and t to the pointer-sized I modifier and j to I64 before calling the CRT. Allocate a translated format only when needed, leaving newer MSVC versions and unaffected formats unchanged. Delegate BIO_snprintf to BIO_vsnprintf so all BIO formatting entry points use the same compatibility path.\n\nAdd focused coverage for BIO_snprintf, BIO_vsnprintf and BIO_printf, including the large-output allocation path and truncation behavior.\n\nFixes #31645\n\nAssisted-by: OpenCode:GLM-5.2\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Fri Jul 31 13:13:06 2026\n(Merged from https://github.com/openssl/openssl/pull/31988)", "completion": "Fix C99 printf length modifiers with VS2013 CRT"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFuzz PKCS7_verify with PKCS7_NOVERIFY flag\nto exercise signature verification without\nrequiring a trusted certificate store.\n\nMotivated by CVE-2026-45447.\n\nAssisted-by: ChatGPT:gpt-5.6\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Fri Aug 7 13:36:57 2026\n(Merged from https://github.com/openssl/openssl/pull/32093)", "completion": "Add PKCS7_verify fuzzer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nASAN and jemalloc both replace `malloc` with their version.\n\nPreviously, configuring with `--enable-asan` on macOS would enable both\njemalloc and ASAN. I'm not sure which one won, but seemed undesired.", "completion": "configure.ac: don't enable jemalloc if ASAN enabled on macOS, error if both enabled"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 7e39b4aedb386e5e69a8c317987d4efb71f9756d)", "completion": "docs: update signal forms skill to match the current implementation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReformats the TEST_CASES.json files touched by the following change so they\nsatisfy the repo's prettier check (short inputFiles/files arrays collapsed to a\nsingle line). Pure formatting; the parsed JSON is unchanged. Split into its own\ncommit so the coverage change that follows is easy to review.\n\n(cherry picked from commit 5245ca5ba72fd165b839d0c45b98f7b50d13a4d5)", "completion": "test(compiler-cli): format compliance TEST_CASES.json with prettier"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReformats the TEST_CASES.json files touched by the following change so they\nsatisfy the repo's prettier check (short inputFiles/files arrays collapsed to a\nsingle line). Pure formatting; the parsed JSON is unchanged. Split into its own\ncommit so the coverage change that follows is easy to review.", "completion": "test(compiler-cli): format compliance TEST_CASES.json with prettier"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe control flow migration determines whether an `*ngIf` uses a `then`\nand/or `else` clause by regex matching the raw microsyntax string for\nthe literal keywords `then`/`else`. The regexes only checked that the\nkeyword was preceded by a non-word character, but not that it was\nfollowed by one.\n\nAs a result, a template reference name that merely starts with `then`\n(e.g. `else thenBlock`) or `else` was misidentified as the `then`/`else`\nkeyword itself. This caused the migration to take the wrong code path\n(e.g. then+else instead of else-only), which in turn made\n`getTemplateName()` compute a `slice(start, end)` with `start > end`,\nproducing an empty template name. That empty placeholder was never\nresolved and was silently emitted as an invalid\n``, dropping the\noriginal template content without any warning.\n\nAdd a negative lookahead `(?![\\w\\d])` to both regexes so `then`/`else`\nare only matched as whole keywords, not as a prefix of a longer\ntemplate reference name.\n\nFixes #69914\n\n(cherry picked from commit 5ad823139758b4d3a8a021d378b008c3457f8689)", "completion": "fix(migrations): correctly detect `then`/`else` keywords in control flow migration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe control flow migration determines whether an `*ngIf` uses a `then`\nand/or `else` clause by regex matching the raw microsyntax string for\nthe literal keywords `then`/`else`. The regexes only checked that the\nkeyword was preceded by a non-word character, but not that it was\nfollowed by one.\n\nAs a result, a template reference name that merely starts with `then`\n(e.g. `else thenBlock`) or `else` was misidentified as the `then`/`else`\nkeyword itself. This caused the migration to take the wrong code path\n(e.g. then+else instead of else-only), which in turn made\n`getTemplateName()` compute a `slice(start, end)` with `start > end`,\nproducing an empty template name. That empty placeholder was never\nresolved and was silently emitted as an invalid\n``, dropping the\noriginal template content without any warning.\n\nAdd a negative lookahead `(?![\\w\\d])` to both regexes so `then`/`else`\nare only matched as whole keywords, not as a prefix of a longer\ntemplate reference name.\n\nFixes #69914", "completion": "fix(migrations): correctly detect `then`/`else` keywords in control flow migration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument internal subdirectory in doc/README.md.\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Norbert Pocs \nMergeDate: Fri Aug 7 13:30:30 2026\n(Merged from https://github.com/openssl/openssl/pull/32058)", "completion": "Add a note about internal documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nThe parent commit made a valiant effort to store \"dict options\" in their\nreified form, but this is more trouble than it's worth:\n- inconsistent model for developers to understand.\n- string lifetime issues (the \"varp\" convention is to pass around an\n aliased, long-lived option value).\n- lots of extra plumbing to deal with the 2 different option-storage\n paradigms.", "completion": "refactor(options): store dict options in :set-string form"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe preview-window (:pedit, etc.) always uses a split, but it would be\nuseful as a floatwin (or \"popup\").\n\nSolution:\nSupport Vim's 'previewpopup' option.", "completion": "feat(float): 'previewpopup' option #26799"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a test recipe subtest checking that 'openssl ec -check' reports a\nvalid key and an invalid one, using a new data file that combines the\ntestec-p256.pem private scalar with the group generator as the public\nkey, so it loads but fails the pairwise consistency check.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Paul Dale \nMergeDate: Thu Jul 30 08:53:23 2026\n(Merged from https://github.com/openssl/openssl/pull/32059)", "completion": "apps: test ec -check key consistency reporting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nUse a schema instead of manual parsing.", "completion": "refactor(options): 'previewpopup' validation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit c9a2ce61118c7f73bc4898eedec64c2bde8bb7a0 introduced some code\ninto the drbg in an effort to get it to select the same provider as is\nspecified for the drbg. Unfortunately this creates a problem when a\nuser has altered the identity of a predefined provider (in this case\nfips).\n\nThe DRBG is passed a set of parameters when instantiating, which\nincludes the name of the provider. This provider uses the name that the\ncore knows it as, which may be different than \"fips\", which the fips\nprovider always referrs to itself as.\n\nFix it by skipping the provider name check when operating in the fips\nmodule, as we should only ever get fips approved algs from within that\nspace\n\nFixes a customer issue, who noted that since this was introduced, using\nidentity configurations no longer works.\n\n(cherry picked from commit 71ec72702be26ef9130530624fada6038e59fc01)\nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMerge-date: Fri Aug 21 11:51:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32357", "completion": "Rework how to fetch components in the drbg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit c9a2ce61118c7f73bc4898eedec64c2bde8bb7a0 introduced some code\ninto the drbg in an effort to get it to select the same provider as is\nspecified for the drbg. Unfortunately this creates a problem when a\nuser has altered the identity of a predefined provider (in this case\nfips).\n\nThe DRBG is passed a set of parameters when instantiating, which\nincludes the name of the provider. This provider uses the name that the\ncore knows it as, which may be different than \"fips\", which the fips\nprovider always referrs to itself as.\n\nFix it by skipping the provider name check when operating in the fips\nmodule, as we should only ever get fips approved algs from within that\nspace\n\nFixes a customer issue, who noted that since this was introduced, using\nidentity configurations no longer works.\n\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:01 2026\n\n(cherry picked from commit 71ec72702be26ef9130530624fada6038e59fc01)\n\nReviewed-by: Mounir Idrassi \nReviewed-by: Andrew Dinh \n(Merged from https://github.com/openssl/openssl/pull/32355)", "completion": "Rework how to fetch components in the drbg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit c9a2ce61118c7f73bc4898eedec64c2bde8bb7a0 introduced some code\ninto the drbg in an effort to get it to select the same provider as is\nspecified for the drbg. Unfortunately this creates a problem when a\nuser has altered the identity of a predefined provider (in this case\nfips).\n\nThe DRBG is passed a set of parameters when instantiating, which\nincludes the name of the provider. This provider uses the name that the\ncore knows it as, which may be different than \"fips\", which the fips\nprovider always referrs to itself as.\n\nFix it by skipping the provider name check when operating in the fips\nmodule, as we should only ever get fips approved algs from within that\nspace\n\nFixes a customer issue, who noted that since this was introduced, using\nidentity configurations no longer works.\n\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32060)\n\n(cherry picked from commit 71ec72702be26ef9130530624fada6038e59fc01)", "completion": "Rework how to fetch components in the drbg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit c9a2ce61118c7f73bc4898eedec64c2bde8bb7a0 introduced some code\ninto the drbg in an effort to get it to select the same provider as is\nspecified for the drbg. Unfortunately this creates a problem when a\nuser has altered the identity of a predefined provider (in this case\nfips).\n\nThe DRBG is passed a set of parameters when instantiating, which\nincludes the name of the provider. This provider uses the name that the\ncore knows it as, which may be different than \"fips\", which the fips\nprovider always referrs to itself as.\n\nFix it by skipping the provider name check when operating in the fips\nmodule, as we should only ever get fips approved algs from within that\nspace\n\nFixes a customer issue, who noted that since this was introduced, using\nidentity configurations no longer works.\n\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32060)", "completion": "Rework how to fetch components in the drbg"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd test recipe subtests for the ecparam format options: the PEM/DER\nparameter roundtrip, rejection of DER input without -inform as the input\nformat defaults to PEM, the restriction of -outform to PEM and DER, and\nthe -conv_form selection of the generator point encoding in explicit\nparameters including that it has no effect on named curve parameters.\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Daniel Kubec \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 16:55:11 2026\n(Merged from https://github.com/openssl/openssl/pull/32061)", "completion": "apps: test ecparam -inform, -outform and -conv_form handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDefines the id-alg-unsigned and id-rdna-unsigned OIDs from RFC 9925\n\nCLA: trivial\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Wed Aug 19 10:46:43 2026\nMerged-from: https://github.com/openssl/openssl/pull/32062", "completion": "Add OIDs specified by RFC 9925"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- 'null-terminate', sync casing.\n- add an `#endif` comment.\n- avoid a few instances of 'will'.\n- configure: 'aws' -> 'aws-sigv4', where missing.\n- unfold/fold lines.\n- update memzero/strzero comments.\n- uppercase 'CRLF'.\n\nCloses #22443", "completion": "tidy-up: comments, messages, formatting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(theme): support focusOutline token for borderless controls\n\n* feat(theme): support focusOutline for borderless controls and Rate\n\n* feat(theme): use shared focus outline for Steps and Splitter", "completion": "feat: extend global focusOutline support to more components"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDTLSv1_listen() copied the ClientHello record sequence into the\nHelloVerifyRequest, but after a valid cookie it advanced the write\nsequence by one. If the client retransmitted ClientHello, the following\nServerHello could be sent with the wrong record sequence.\n\nSeed the DTLS write record sequence from the valid-cookie ClientHello\nbefore continuing the handshake. Also make DTLS 1.2 write sequence\nincrements fail at the 48-bit wire sequence boundary instead of carrying\ninto the unused high bytes.\n\nAdd tests for the ServerHello record sequence and DTLS 1.2 sequence wrap\nhandling.\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Mounir Idrassi \nMerge-date: Mon Sep 7 08:15:23 2026\nMerged-from: https://github.com/openssl/openssl/pull/32064", "completion": "dtls: fix DTLSv1_listen record sequence after cookie verify"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAfter incremental hydration became tree-shakable, application bootstrap could finish before a routed component activated the runtime. The one-time trigger scan was then skipped, leaving routed and nested hydration triggers uninitialized.\n\nCoordinate application bootstrap with runtime activation and initialize once both have occurred.\n\nFixes #69908\n\n(cherry picked from commit cfe2cda1100bb84e2ecf954687126c4d30212d07)", "completion": "fix(core): initialize hydration triggers after late runtime activation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAfter incremental hydration became tree-shakable, application bootstrap could finish before a routed component activated the runtime. The one-time trigger scan was then skipped, leaving routed and nested hydration triggers uninitialized.\n\nCoordinate application bootstrap with runtime activation and initialize once both have occurred.\n\nFixes #69908", "completion": "fix(core): initialize hydration triggers after late runtime activation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nmutcbk_inject_frames returned 0 once its one-time mutation was applied, which\ntells the QTX the packet send failed and tears down the connection instead of\ncontinuing the test with unmutated packets. Now it passes subsequent packets\nthrough unmodified by returning the input header, iovec, and count unchanged.\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 14:02:07 2026\n(Merged from https://github.com/openssl/openssl/pull/32065)", "completion": "Fix mutcbk_inject_frames after mutation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nmutcbk_inject_frames returned 0 once its one-time mutation was applied, which\ntells the QTX the packet send failed and tears down the connection instead of\ncontinuing the test with unmutated packets. Now it passes subsequent packets\nthrough unmodified by returning the input header, iovec, and count unchanged.\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 14:01:46 2026\n(Merged from https://github.com/openssl/openssl/pull/32065)", "completion": "Fix mutcbk_inject_frames after mutation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nmutcbk_inject_frames returned 0 once its one-time mutation was applied, which\ntells the QTX the packet send failed and tears down the connection instead of\ncontinuing the test with unmutated packets. Now it passes subsequent packets\nthrough unmodified by returning the input header, iovec, and count unchanged.\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 14:01:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32065)", "completion": "Fix mutcbk_inject_frames after mutation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nmutcbk_inject_frames returned 0 once its one-time mutation was applied, which\ntells the QTX the packet send failed and tears down the connection instead of\ncontinuing the test with unmutated packets. Now it passes subsequent packets\nthrough unmodified by returning the input header, iovec, and count unchanged.\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 14:00:23 2026\n(Merged from https://github.com/openssl/openssl/pull/32065)", "completion": "Fix mutcbk_inject_frames after mutation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit fd366065e06 added tests intended to verify that rows inserted\non the publisher are replicated to the subscriber when using multiple\npublications, with one excluding the target table via EXCEPT and\nanother including it.\n\nHowever, the tests queried the publisher instead of the subscriber.\nSince the rows were inserted directly into the publisher, the checks\nwould always succeed, providing no coverage of replication.\n\nFix this by querying the subscriber so the tests verify the replicated\nstate.\n\nAuthor: Fujii Masao \nReviewed-by: Ayush Tiwari \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/CAHGQGwGfXUO7f4t6KNGurYwg6QsnLtpP0K3EACbAwYWtxGfKfQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix EXCEPT publication test to check subscriber"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nDocument table_name, column_name, and schema_name in the CREATE\nPUBLICATION and ALTER PUBLICATION reference pages. Also add anchors for\nthe ALTER PUBLICATION parameter list, matching the style already used by\nCREATE PUBLICATION.\n\nAuthor: Peter Smith \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHut+Ptekz+TO4ui8-fiBm4Y+O2v=HQnkK_cW4G=w9ep8654EA@mail.gmail.com", "completion": "doc: Add missing CREATE/ALTER PUBLICATION parameter descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAligns our clone of the navigation API types with the built-in TypeScript types. This is related to an internal issue.\n\n(cherry picked from commit d79b3b65e9536accd825620331185706c3339714)", "completion": "refactor(core): align navigation types with built in ones"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAligns our clone of the navigation API types with the built-in TypeScript types. This is related to an internal issue.", "completion": "refactor(core): align navigation types with built in ones"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* docs: Correct operators in no-eq-null documentation\n\n* docs: Improve clarity in no-eq-null documentation\n\n* docs: correct no-eq-null operators and grammar\n\nCo-authored-by: lumir \n\n---------", "completion": "docs: Clarify `no-eq-null` description"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the strictTemplates documentation in Angular compiler options to note that the default is true, replacing the reference to the obsolete ng new --strict flag.\n\n(cherry picked from commit 2bcd12a6a59aea228eb112bec138fdbb0659f86f)", "completion": "docs: update default value for strictTemplates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the strictTemplates documentation in Angular compiler options to note that the default is true, replacing the reference to the obsolete ng new --strict flag.", "completion": "docs: update default value for strictTemplates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\ncreateMiddlewareFactory re-prefixed every non-prefixed middleware path, so a concrete\nroute excluded via setGlobalPrefix(prefix, { exclude }) (e.g. /graphql) was rewritten to\n${prefix}/. Route-scoped middleware was then registered on the wrong path and never\nran on the excluded route. Guard the re-prefix so only a path that collapsed to the root is\nexpanded, leaving concrete excluded routes unprefixed.\n\nFollow-up to #14895 / #14894. Preserves the exclude: ['/'] behavior from #13401.", "completion": "fix(fastify): run middleware on routes excluded from global prefix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* docs: fix broken Specify Parser Options anchor link\n\n* Update docs/src/rules/rest-spread-spacing.md\r\n\r\nThanks for the clarification. That makes sense.\n\nCo-authored-by: fnx <966276+DMartens@users.noreply.github.com>\n\n* Update docs/src/rules/rest-spread-spacing.md\n\nCo-authored-by: lumir \n\n---------", "completion": "docs: fix broken Specify Parser Options anchor link"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCo-Authored-By: Claude Opus 4.8 (1M context) \n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Mon Jul 27 10:17:00 2026\n(Merged from https://github.com/openssl/openssl/pull/32053)", "completion": "ci: accept uppercase hex in dispatch head_sha validation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Tomas Mraz \nReviewed-by: Norbert Pocs \nMergeDate: Wed Jul 29 09:24:40 2026\n(Merged from https://github.com/openssl/openssl/pull/32067)", "completion": "updating fuzz-corpora submodule"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nMake sure hostname used in URL to proxy is IDN decoded form, but keep\nthe original hostname in case it was ipv6.\n\nFixes #22382\nReported-by: RMMoreton on github\nCloses #22385", "completion": "http: fix non-tunneling proxy hostname use"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n\"vim-patch.sh -L\" includes gpg signature for \"log.showSignature=true\"\nin user's .gitconfig.\nvim-patch.sh expects no signature for 1-line output per patch.", "completion": "fix(vim-patch.sh): omit gpg for git-log #37173"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis fixes issue found by fuzz test in updated corpora for\nechconfiglist_parser.\n\nReviewed-by: Norbert Pocs \nReviewed-by: Paul Dale \nReviewed-by: Tomas Mraz \nMergeDate: Mon Jul 27 16:36:15 2026\n(Merged from https://github.com/openssl/openssl/pull/32070)\n\n(cherry picked from commit 544e28ee06ac247e8fa02b46e306145d1c52cf17)", "completion": "ech: check memory failure in vpm allocation in store final check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis fixes issue found by fuzz test in updated corpora for\nechconfiglist_parser.\n\nReviewed-by: Norbert Pocs \nReviewed-by: Paul Dale \nReviewed-by: Tomas Mraz \nMergeDate: Mon Jul 27 16:36:15 2026\n(Merged from https://github.com/openssl/openssl/pull/32070)", "completion": "ech: check memory failure in vpm allocation in store final check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs: update Ant Design 5.x site link\n\n* docs: correct Ant Design 5.x site URL\n\n* docs: add mirror links to English FAQ", "completion": "docs: update Ant Design 5.x site link"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nChanges:\n- Removed the blank line before the first healthcheck header.\n- Fixed a bug where the entire \"Terminal\" section of `vim.health` would\n not appear if the `infocmp` executable was not found.\n- Fixed a typo in `vim.lsp` when displaying the LSP log level.", "completion": "feat(health): improvements to :checkhealth #40935"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:04 2026\n\n(cherry picked from commit 42f8848ac6cbd727264fd3a9bfa97861e4ab71b5)\nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMerged-from: https://github.com/openssl/openssl/pull/32357", "completion": "add a test to exercize the identity config directive on fips"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:04 2026\n\n(cherry picked from commit 42f8848ac6cbd727264fd3a9bfa97861e4ab71b5)\n\nReviewed-by: Mounir Idrassi \nReviewed-by: Andrew Dinh \n(Merged from https://github.com/openssl/openssl/pull/32355)", "completion": "add a test to exercize the identity config directive on fips"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32060)\n\n(cherry picked from commit 42f8848ac6cbd727264fd3a9bfa97861e4ab71b5)", "completion": "add a test to exercize the identity config directive on fips"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Bob Beck \nReviewed-by: Simo Sorce \nMergeDate: Wed Aug 12 19:26:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32060)", "completion": "add a test to exercize the identity config directive on fips"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* test: pin `webpack` version to 5.108.4\n\n* remove caret", "completion": "test: pin `webpack` version to 5.108.4"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- drop w_maxwidth/w_maxheight, calculate them on-demand from\n 'previewpopup' (this is cheap bc of `opt_keyset`)", "completion": "refactor: 'previewpopup' #40945"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: scripts/genappimage.sh runs `make` with no extra flags and\nemits a fixed nvim-linux-.appimage filename, so packaging a\nvariant build (e.g. with the bundled PUC-Rio Lua interpreter)\nrequires editing the Makefile or post-renaming the AppImage, which\nbreaks the AppImage zsync URL.\n\nSolution: forward DEPS_CMAKE_FLAGS and CMAKE_EXTRA_FLAGS to `make`,\naccept OUTPUT so the AppImage (and its zsync Filename:) follows the\ncaller's chosen name, and mark CPACK_PACKAGE_FILE_NAME as CACHE\nSTRING on Linux so the resulting tarball/deb follow as well. Default\nbehavior is unchanged when none of these env vars are set.", "completion": "build: support variant builds via env-var and cpack overrides #40947"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the domino dependency to the latest version as used in the main branch.\n\nThis update contains fixes for https://github.com/angular/domino/pull/32.", "completion": "fix(platform-server): update domino to latest version"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo prevent merging large text files by accident.\n\nSet the cap at 10k lines. The current line number top list is:\n```\n 5577 configure.ac\n 5561 lib/vtls/openssl.c\n 5077 lib/http.c\n 4517 lib/ftp.c\n 4284 lib/multi.c\n```\n\nCloses #22387", "completion": "spacecheck: cap number of lines per file"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral external links pointed at locations that have moved or gone away:\n\n- ng-packagr, webpack, and node-glob renamed their default branch from\n master to main, so the deep links into those repos redirect.\n- The npm package pages moved from npmjs.org to www.npmjs.com.\n- The Angular Material and CDK docs moved from material.angular.io to\n material.angular.dev.\n- The semver reference pointed at the defunct semver.io service; point it\n at the SemVer spec at semver.org instead.\n- The MDN animationiteration event link had a typo (animationitration).\n- compiler-cli's metadata/schema.ts was removed after v12; pin the link to\n the 12.2.x tag where the file still exists.\n- The angularindepth.com article is gone (its domain is parked); link to its\n live home on the Angular In Depth Medium publication.\n- Google moved the Lighthouse user-timing docs to developer.chrome.com.\n\nPoint the links at their current, working locations.\n\n(cherry picked from commit 058c7f9b0c60c959ad441a43e1db4a782e7d5697)", "completion": "docs: update outdated and broken external links in adev"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral external links pointed at locations that have moved or gone away:\n\n- ng-packagr, webpack, and node-glob renamed their default branch from\n master to main, so the deep links into those repos redirect.\n- The npm package pages moved from npmjs.org to www.npmjs.com.\n- The Angular Material and CDK docs moved from material.angular.io to\n material.angular.dev.\n- The semver reference pointed at the defunct semver.io service; point it\n at the SemVer spec at semver.org instead.\n- The MDN animationiteration event link had a typo (animationitration).\n- compiler-cli's metadata/schema.ts was removed after v12; pin the link to\n the 12.2.x tag where the file still exists.\n- The angularindepth.com article is gone (its domain is parked); link to its\n live home on the Angular In Depth Medium publication.\n- Google moved the Lighthouse user-timing docs to developer.chrome.com.\n\nPoint the links at their current, working locations.", "completion": "docs: update outdated and broken external links in adev"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMirror the check from cms_kari.c in cms_kemri.c.\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 16:56:18 2026\n(Merged from https://github.com/openssl/openssl/pull/32072)\n\n(cherry picked from commit 14149949d5c13c12c92a17f1a9eb943a003d0f43)", "completion": "CMS: Guard against int overflow in cms_kek_cipher()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMirror the check from cms_kari.c in cms_kemri.c.\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nMergeDate: Wed Jul 29 16:56:18 2026\n(Merged from https://github.com/openssl/openssl/pull/32072)", "completion": "CMS: Guard against int overflow in cms_kek_cipher()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAdd support for signing outgoing HTTP requests per RFC 9421 using\nEd25519 or HMAC-SHA256 algorithms.\n\nNew libcurl options:\n - CURLOPT_HTTPSIG: signing algorithm (\"ed25519\" or \"hmac-sha256\")\n - CURLOPT_HTTPSIG_KEY: path to hex-encoded key file\n - CURLOPT_HTTPSIG_KEYID: key identifier for Signature-Input\n - CURLOPT_HTTPSIG_HEADERS: space-separated components to sign\n\nNew CLI flags: --httpsig, --httpsig-key, --httpsig-keyid,\n--httpsig-headers\n\nThe crypto layer follows the sha256.c multi-backend pattern with\nimplementations for OpenSSL (EVP_DigestSign) and wolfSSL\n(wc_ed25519_sign_msg). HMAC-SHA256 uses the existing Curl_hmacit()\ninfrastructure which works on all backends.\n\nVerified by test 5000 to 5021\n\nAssisted-by: Daniel Stenberg\nSigned-off-by: Sameeh Jubran \nCloses #22386\nCloses #21239", "completion": "httpsig: add RFC 9421 HTTP Message Signatures support"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nExercise the previously untested -commands, -1, -digest-commands,\n-options, -disabled and -objects options in list app.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Daniel Kubec \nReviewed-by: Paul Dale \nMerge-date: Fri Sep 4 15:08:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/32073", "completion": "apps: test info options of the list command"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nAutomated security fix generated by OrbisAI Security", "completion": "fix: package_managers.dependabot.dependabot-missing-cooldown.dependabot-missing-cooldown security vulnerability"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- schannel: drop redundant parentheses.\n- os400sys: drop redundant includes.\n Follow-up to ebc5212dacd3db8f5315b5a2d676415848e936d5 #22374\n- pytest: replace `()` with `[]` to match rest of tests.\n- libtests: constify some local pointers.\n- libtests: drop redundant `(long)` casts.\n- lib650: use `CURL_CSTRLEN()`.\n Follow-up to 59dc2bbe07c3b5889e0b380e5fa384d338d9d24e #22424\n\nCloses #22444", "completion": "tidy-up: minor code fixes and improvements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, if a sequence synchronization batch contained both a sequence\nthat had been dropped on the publisher and another for which the\nreplication role lacked SELECT privilege, the latter was reported\ntwice: once as a permission failure and again as missing on the\npublisher.\n\nThis happened because the permission-denied sequence was not marked as\nfound on the publisher. As a result, when another sequence in the batch\nwas genuinely missing, the later missing-sequence check incorrectly\nclassified the permission-denied sequence as missing as well.\n\nFix this by marking the permission-denied sequence as found before\nreporting the permission failure, so it is not later reported as\nmissing.\n\nReported-by: Noah Misch \nAuthor: Vignesh C \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CALDaNm3LsUjW7PahuCsbYAxajSF+S328tw5E9rF0erdh7dKOXw@mail.gmail.com\nBackpatch-through: 19", "completion": "Avoid reporting permission-denied publisher sequences as missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 3e7094b04991303b9636aa35c8629ee5ea7d5a5f)", "completion": "docs: correct Angular developer skill guidance"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe retro-themed aria autocomplete examples style the clear button with\nvar(--win95-gray), var(--win95-dark-gray), var(--win95-light), and\nvar(--win95-shadow), but none of the three example stylesheets defines\nthose custom properties. The variables resolve to nothing, so the button\nfalls back to inherited theme colors — color: var(--win95-shadow) becomes\nthe light-theme text color in dark mode, leaving the button unreadable.\n\nDefine the four variables in :host of each example, matching the values\nalready used by the sibling aria tree examples, so the clear button keeps\nits Windows 95 look in both light and dark themes.\n\n(cherry picked from commit 8cd4c89c298c63e3b2ad0313f76c3e46ea265fe2)", "completion": "fix(docs-infra): define missing win95 variables in aria autocomplete examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe retro-themed aria autocomplete examples style the clear button with\nvar(--win95-gray), var(--win95-dark-gray), var(--win95-light), and\nvar(--win95-shadow), but none of the three example stylesheets defines\nthose custom properties. The variables resolve to nothing, so the button\nfalls back to inherited theme colors — color: var(--win95-shadow) becomes\nthe light-theme text color in dark mode, leaving the button unreadable.\n\nDefine the four variables in :host of each example, matching the values\nalready used by the sibling aria tree examples, so the clear button keeps\nits Windows 95 look in both light and dark themes.", "completion": "fix(docs-infra): define missing win95 variables in aria autocomplete examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIn the light theme block of _colors.scss, --webgl-page-background and\n--webgl-gray-unfilled were written on a single line without a separating\nsemicolon, and --webgl-page-background wrapped --page-background in an\ninvalid nested var(). As a result --webgl-page-background got a garbage\nvalue and --webgl-gray-unfilled was never defined in the light theme.\n\nSplit them into two well-formed declarations and drop the nested var(),\nmatching the structure already used in the dark theme block.\n\n(cherry picked from commit 91822538fe78a02a0fdf59cfb29bf9d49ccd6a96)", "completion": "fix(docs-infra): fix malformed --webgl-page-background declaration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIn the light theme block of _colors.scss, --webgl-page-background and\n--webgl-gray-unfilled were written on a single line without a separating\nsemicolon, and --webgl-page-background wrapped --page-background in an\ninvalid nested var(). As a result --webgl-page-background got a garbage\nvalue and --webgl-gray-unfilled was never defined in the light theme.\n\nSplit them into two well-formed declarations and drop the nested var(),\nmatching the structure already used in the dark theme block.", "completion": "fix(docs-infra): fix malformed --webgl-page-background declaration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npg_database_size() allows access to users who have either CONNECT\nprivilege on the target database or privileges of the pg_read_all_stats\nrole. However, previously, psql's \\l+ checked only for CONNECT,\nso users with privileges of pg_read_all_stats still saw \"No Access\" for\ndatabases they could not connect to.\n\nFix this by making \\l+ also check\npg_has_role('pg_read_all_stats', 'USAGE'), matching\npg_database_size()'s permission rules.\n\nFor back branches, emit the pg_read_all_stats check only when\nconnected to PostgreSQL 10 or later, since earlier releases do not have\nthat predefined role.\n\nBackpatch to all supported versions.\n\nAuthor: Christoph Berg \nReviewed-by: Álvaro Herrera \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/amCo6qRmnfPVk4-V@msg.df7cb.de\nBackpatch-through: 14", "completion": "psql: Allow pg_read_all_stats to see database size in \\l+"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: `:browse edit` (and variants) without an argument fails instead\nof opening a browser.\n\nSolution: Dispatch to dir.lua using the cwd as the implied directory.\nReplace the inherited GUI-only documentation with the supported\nbehavior. Support vsplit, split, tabedit variants.", "completion": "fix(dir): `:browse edit` opens dir browser #40930"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFix test 1712 to pass curl C by setting `COLUMNS` to the highest\naccepted value, and adjust expected results. To avoid envs with varying\nlengths of `LOGDIR` affect the outcome.\n\nApply the same fix to test 459, though it wasn't affected in curl CI.\n\nAlso sync up test 433 `COLUMNS` value with these two tests for\nconsistency.\n\nRef: #22381\nFollow-up to 8e3a2a64d103a46508e17cde76595993de96ea6c #20666\n\nCloses #22388", "completion": "runtests: fix `mode=\"warn\"` tests passing unconditionally, fix test 1752"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22389", "completion": "runtests: allow comments in `setenv` section, merge sections in test433"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFixes #38777 in case 'rulerformat' is set.\n\nSee PR 38879. Original message:\nProblem: When the 'ruler' is in the last line of the screen, it takes\n local highlight definitions of the current window, tripping an\n assert (since c1648cf).\nSolution: Don't use window-local highlight definitions when the ruler is\n not part of a statusline.", "completion": "fix(ruler): no window-local highlights for last line 'rulerformat'"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nbuild: support variant builds via env-var and cpack overrides\n\nProblem: scripts/genappimage.sh runs `make` with no extra flags and\nemits a fixed nvim-linux-.appimage filename, so packaging a\nvariant build (e.g. with the bundled PUC-Rio Lua interpreter)\nrequires editing the Makefile or post-renaming the AppImage, which\nbreaks the AppImage zsync URL.\n\nSolution: forward DEPS_CMAKE_FLAGS and CMAKE_EXTRA_FLAGS to `make`,\naccept OUTPUT so the AppImage (and its zsync Filename:) follows the\ncaller's chosen name, and mark CPACK_PACKAGE_FILE_NAME as CACHE\nSTRING on Linux so the resulting tarball/deb follow as well. Default\nbehavior is unchanged when none of these env vars are set.", "completion": "backport: build: support variant builds via env-var and cpack overrides"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- docs/cmdline-opts/.gitignore: also ignore `manpage.tmp.*`.\n Follow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\n\n- ./.gitignore: drop obsolete entries.\n Follow-up to 4f38db1d28a971f938400f558e968fdffb9233a0 #1923\n\nCloses #22445", "completion": "gitignore: maintenance updates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- say 'experimental'.\n- cmake: add to documentation.\n- cmake: alpha-sort.\n\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386\n\nCloses #22391", "completion": "build: tidy up httpsig options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nVerified by test 5022\n\nCloses #22392", "completion": "curl: make --httpsig-key take a key OR a file name for key"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit f9b7fc65 fixed a race when predicate-locking completely empty\nbtrees: without a buffer lock held, a matching key could be inserted\nbetween _bt_search and the PredicateLockRelation call, so the scan would\nmiss concurrently inserted tuples while the writer wouldn't see the\nreader's predicate lock. That commit only fixed _bt_first's _bt_search\npath, though. Scans without useful insertion scan keys return early\nfrom _bt_first via _bt_endpoint, which still didn't recheck if the\nrelation was empty.\n\nTo fix, add handling to _bt_endpoint that is analogous to the handling\nadded to _bt_search by commit f9b7fc65.\n\nAuthor: Peter Geoghegan \nDiscussion: https://postgr.es/m/CAH2-WzkNoTn3yXY0iGkSuavJ+sL8EROf+kitW+_2v2tJVWuKmA@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix another empty nbtree index SSI race."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim patches for Vim help files must use Vim tags as diff hunk header\nto reliably detect if a hunk is N/A or not.\nGit does not know which files are Vim help files\nso that it can use custom \"diff..xfuncname\" regexp\nto create the header.\n\nUpdate Neovim's gitattributes to detect Vim help files\nand then use it on vim-patch.sh to scan Vim patches.\nAdd non-function tags from \":h vim_diff\"\nto detect N/A Vim runtime patches.", "completion": "build(vim-patch): detect N/A tags in vimhelp patches #40942"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(site): add deprecated Badge.Ribbon\n\n* update", "completion": "feat(site): add deprecated Badge.Ribbon"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReport an invalid content encryption key length instead of decrypting\nwith a random key when this cannot act as an MMA (Bleichenbacher)\noracle, that is with RSA-OAEP or when PKCS#1 v1.5 implicit rejection\nis in effect. Otherwise, such as with third party providers without\nimplicit rejection, keep the random key masking.\n\nThe same applies to a failure of the key decryption itself. With\nimplicit rejection in effect the RSA decryption can only fail for a\npublicly invalid ciphertext, such as a value not smaller than the\nmodulus, and with RSA-OAEP a padding check failure is safe to reveal,\nso the error is reported instead of falling back to the random key\nmasking. This also makes CMS_decrypt with a wrong key deterministic\nin those configurations, which the new test relies on.\n\nFixes #25875\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Alicja Kario \nReviewed-by: Tomas Mraz \nMerge-date: Thu Sep 17 09:29:58 2026\nMerged-from: https://github.com/openssl/openssl/pull/28038", "completion": "cms: correctly fail on invalid key length in CMS_decrypt"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOversight in commit fb23cc7e81db.\n\nReported-by: Anton Voloshin \nDiscussion: https://postgr.es/m/ad5d772e-09d9-4248-97a4-0011afab9e71@postgrespro.ru", "completion": "Add missing PGDLLIMPORT marker"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe retro variants of the toolbar, select, and multiselect aria examples\ntint the pressed button background with\ncolor-mix(in srgb, var(--retro-button-color) 60%, var(--gray-50)), but\n--gray-50 is defined nowhere. Per the CSS spec, a var() with no fallback\npointing at an undefined property invalidates the whole color-mix(), so the\ndeclaration is dropped and the pressed-state tint never applies.\n\nDefine a local --retro-pressed-tint token in each example's :host (#fbfbfb,\nthe value $gray-50 resolved to) with a :host-context(.docs-dark-mode) override\nto #151417, and use it for the pressed-state mix. This keeps the example\nself-contained rather than depending on adev's global token scope, while\nstaying theme-aware in both light and dark, following the same token-flipping\npattern used in code-editor.component.scss.\n\n(cherry picked from commit 48c1e5bb0f6cd40d543700c19975e644ac885790)", "completion": "fix(docs-infra): replace undefined --gray-50 in retro aria examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe retro variants of the toolbar, select, and multiselect aria examples\ntint the pressed button background with\ncolor-mix(in srgb, var(--retro-button-color) 60%, var(--gray-50)), but\n--gray-50 is defined nowhere. Per the CSS spec, a var() with no fallback\npointing at an undefined property invalidates the whole color-mix(), so the\ndeclaration is dropped and the pressed-state tint never applies.\n\nDefine a local --retro-pressed-tint token in each example's :host (#fbfbfb,\nthe value $gray-50 resolved to) with a :host-context(.docs-dark-mode) override\nto #151417, and use it for the pressed-state mix. This keeps the example\nself-contained rather than depending on adev's global token scope, while\nstaying theme-aware in both light and dark, following the same token-flipping\npattern used in code-editor.component.scss.", "completion": "fix(docs-infra): replace undefined --gray-50 in retro aria examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFix xfuncname to support tags that target Vim mappings, options.\n\n- events\n- options\n - *'luadll'*\n - *'mzschemedll'*\n - *'mzschemegcdll'*\n - *'perldll'*\n - *'pythondll'*\n - *'pythonthreedll'*\n - *'rubydll'*\n - *'tcldll'*\n - *'winptydll'*\n - t_.+, termcap opts\n- internal variables\n- cli flags\n- ':h emacs-tags'", "completion": "build(vim-patch): skip doc for n/a features"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAdd coverage for predicate locking of completely empty nbtree indexes,\nwhere we must predicate lock the entire relation (instead of some\nindividual leaf page). Both paths that can find the index empty (and\nmust consider whether it's still empty after PredicateLockRelation\nreturns) are covered by a new isolation test that uses injection points.\n\nCatalog relation scans skip the injection points. The waiting session\nruns catalog queries of its own after arming the (session-local) points,\nand could otherwise suspend itself with nothing lined up to wake it.\n\nFollow-up to bugfix commits ce3f19e2 (the _bt_endpoint fix) and f9b7fc65\n(the _bt_first/_bt_search fix).\n\nAuthor: Peter Geoghegan \nDiscussion: https://postgr.es/m/CAH2-WzkNoTn3yXY0iGkSuavJ+sL8EROf+kitW+_2v2tJVWuKmA@mail.gmail.com", "completion": "Add tests for nbtree empty index predicate locking."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: `q:` in visual mode does not insert `'<,'>` automatically in\nthe current line on cmdwin.\n\nSolution: Insert `'<,'>` in the current line on cmdwin when `q:` is used\nin visual mode.", "completion": "fix(cmdwin): q: in visual-mode does not insert visual range #40973"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n* Explicitly set \"check\" in subprocess.run() to raise an exception\n automatically, where it was done manually before\n* Use contextlib.suppress to ignore exceptions\n* Use custom exceptions for test errors for clarity and flexibility.\n* Replace IOError with OSError\n\nThis fixes ruff rules BLE001, PLW1510, S110, TRY201, TRY203, TRY002,\nUP024.", "completion": "tests: improve exception handling in Python test code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThey were previously only properly escaped for ~~~ quotes. Spotted for\nthe CURLOPT_HTTPSIG_KEY man page.\n\nCloses #22393", "completion": "cd2nroff: fix backslashes for 4-space indent lines"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nMark Python mutable class variables with ClassVar, to denote that the\ndanger this can cause has been considered. Since any change made to\nthese in any object affects all other objects, this can cause locality\nerrors. However, as used in the test suite, they are are never modified\nand so they are annotated as being intended.\n\nAlways set a timezone in datetime objects, as mixing naive and\ntimezone-aware object can cause errors.\n\nThese fix ruff rules DTZ005, RUF012.", "completion": "tests: address mutable class vars and naive datetime in Python code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThis version is already two releases out of support, but is \"only\" 7\nyears old so is probably still being used in the real world. Document\nthis version along with some other testing dependencies. Remove code\nsupport for earlier versions. Disable ruff checks that need a newer\nversion.", "completion": "tests: target Python 3.8 as the minimum Python version"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n* remove an unneeded ruff warning disable\n* remove coding: utf-8 from Python code; PEP 3120 makes UTF-8 the\n default encoding\n* remove unusable shebang lines from Python code\n* remove empty print strings\n* disable warnings when file objects are stored; these instances can't\n be handled with context managers\n* use more consistent whitespace in Python code, fixing flake8 warnings\n* set the executable bit on scorecard.py, making it easier to run\n\nThese fix ruff rules EXE001, FURB105, UP009, SIM115.", "completion": "tests: change whitespace and comments in Python test code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n* combine separate if statements\n* remove an unneeded encode() call\n* remove unneeded returns\n* simplify code when returning early\n\nThis fixes ruff rules SIM102, SIM114, UP012, PLR1711.", "completion": "tests: simplify by removing unneeded Python code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n* call super() without arguments\n* mark an unused variable as such\n* simplify by using dict getter for default values\n* use writelines() when possible\n* use dedent to simplify some text formatting\n* avoid items() on dict in a loop when unnecessary\n* replace most Python format() calls with f-strings\n* use capture_output in subprocess.run\n\nThis fixes ruff rules FLY002, FURB122, PERF102, RUF059, SIM401, UP008,\nUP022, UP030.", "completion": "tests: use simpler constructions in Python code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo hide it somewhat from process listings.\n\nCloses #22394", "completion": "tool_getparam: clear the --httpsig-key argument"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBackwards scans have unique concurrency rules: rather than unreservedly\ntrusting a saved left link, the scan optimistically rechecks its\npointed-to leaf page's right link (i.e. whether it still points back to\nthe page that _bt_readpage just read). Usually, the left sibling of the\njust-read page won't have changed, in which case the scan can proceed\nwith reading the left sibling as planned. But it's possible that the\nkey space that the scan needs to read next is no longer covered by the\noriginal left sibling page due to concurrent page splits and/or page\ndeletions. When that happens, the scan must recover by relocating the\nnew/current left sibling of the just-read page.\n\nTest coverage for backwards scans was limited to the happy path. Add an\nisolation test (and associated injection points) that test the recovery\npath. This covers several distinct recovery scenarios (concurrent page\nsplits, concurrent page deletions, and minor variants thereof).\n\nAuthor: Peter Geoghegan \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/CAH2-WzmD+jUBOpFS2jrnqqrdPSAjoxqyL9FPKaE1BtnY=8Nntg@mail.gmail.com", "completion": "Add test coverage for nbtree backwards scans."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nDo not let unrelated credentials from a redirected URL bypass the\ncross-host auth boundary\n\nVerified by test 5023 to 5025\n\nFollow-up to a55731050e8c3dbea0\n\nCloses #22395", "completion": "http: fix httpsig with auth-redir"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThis version enables many more warnings by default.\n\nCloses #22396", "completion": "tests: bump ruff version to 0.60.0"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nUse \"gO\" mapping instead.\nvim9script is N/A.\n\nDetect 'runtime/doc/helphelp.txt' N/A patches for helptoc.", "completion": "build(vim-patch): helptoc is 100% n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nhttps://github.com/open-quantum-safe/oqs-provider/pull/805#issuecomment-5034437500\n\nIts happening because, recently we made some fixes to account for\nproviders that request no-caching fetches, which all seems to work\nreasonably well.\n\nExcept for the corner case oqs recently exposed, in which the provider\nmay request the caching of some algorithms, but not others. When this\noccurs, the core libcrypto creates a temporary store for those\nrequested, but stored the cachable ones in the libctx store.\n\ninner_evp_generic_fetch treats the presence of an allocated tmp store as\nimplying that all algorithms fetched are non-cacheable, even if some\nare. The result is that, for those cacheable items, they also get\ntreated as non-cacheable, missing the extra ref count taken when they\nare added to the method store cache. As a result, they get freed while\nstill in use, and you get the issue referenced above.\n\nInstead of assuming that a tmp_store means all algorithms are\nnon-cacheable, instead, try to look the method up in the tmp_store\ncache, and cache it if its not found (i.e. its not in the temp store)\n\nFixes https://github.com/open-quantum-safe/oqs-provider/pull/805\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Andrew Dinh \nMergeDate: Sat Aug 1 14:30:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32077)", "completion": "oqs noted a double free recently:"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit ec87f0420000dd6f991b9190ad52754554403c92)", "completion": "refactor(common): replaces the deprecated positional `subscribe` arguments with the recommended observer object"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFixes #69785\n\nAdd an Angular SSR integration test in platform-server verifying that null input values do not render string attributes like value=\"null\" during server-side rendering, while normal non-empty string values like value=\"hello\" are properly preserved.\n\n(cherry picked from commit fb698d12cdda1b626d727b35e57411b2a7b75336)", "completion": "test(platform-server): add SSR integration test for null and normal input values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFixes #69785\n\nAdd an Angular SSR integration test in platform-server verifying that null input values do not render string attributes like value=\"null\" during server-side rendering, while normal non-empty string values like value=\"hello\" are properly preserved.", "completion": "test(platform-server): add SSR integration test for null and normal input values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Shortening the name of a buffer whose full name is the current\ndirectory + path sep yields empty string -> buf unnamed.\nThis doesn't interact well with things like `:mksession`, which\nfor example could `:badd` with no arg -> E471.\n\nSolution: Keep the full path when shortening yields an empty name, as\n`path_try_shorten_fname()` already does.", "completion": "fix(buffer): name becomes empty when it is the cwd #40980"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(site): add new component version Badge.Ribbon\n\n* update", "completion": "feat(site): add new component version Badge.Ribbon"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(website): migrate docs from dumi to Next.js\n\n* feat: update\n\n* type: export missing component props and ref types\n\n* chore: revert next.js", "completion": "type: export missing component props and ref types"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwo custom properties in the shared-docs styles reference tokens that are\ndefined nowhere, so the declarations are invalid at computed-value time.\n\n_kbd.scss sets the text color with var(---tertiary-contrast); the extra\nleading dash points at an undefined property with no fallback, so the color\nresolves to the inherited value instead of the intended --tertiary-contrast.\n\n_colors.scss builds --light-pink-to-light-purple-horizontal-gradient from\nvar(--light-purple), which is not defined anywhere (the sibling token is\n--light-violet, defined in the same file), invalidating the gradient. The\ngradient is not currently referenced, so this corrects a latent malformed\ndeclaration rather than a visible bug.\n\nPoint both at the defined tokens: --tertiary-contrast and --light-violet.\n\n(cherry picked from commit e70994bdc3181e82d8cd5108d6eb7f5942377012)", "completion": "fix(docs-infra): fix undefined CSS custom properties in shared-docs styles"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwo custom properties in the shared-docs styles reference tokens that are\ndefined nowhere, so the declarations are invalid at computed-value time.\n\n_kbd.scss sets the text color with var(---tertiary-contrast); the extra\nleading dash points at an undefined property with no fallback, so the color\nresolves to the inherited value instead of the intended --tertiary-contrast.\n\n_colors.scss builds --light-pink-to-light-purple-horizontal-gradient from\nvar(--light-purple), which is not defined anywhere (the sibling token is\n--light-violet, defined in the same file), invalidating the gradient. The\ngradient is not currently referenced, so this corrects a latent malformed\ndeclaration rather than a visible bug.\n\nPoint both at the defined tokens: --tertiary-contrast and --light-violet.", "completion": "fix(docs-infra): fix undefined CSS custom properties in shared-docs styles"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAfter expanding tabs with the `expandtab` option, if the old indent\nmatches the requested one, `vim.text.indent()` returns the input\nunchanged.\nThe optimization path assumes that if old_indent == size, the input\nwouldn't be changed, which is not correct when old_indent is formed by\nexpanded tabs.\n\nSolution:\nApply the optimization only when `expandtab` is not set.", "completion": "fix(text): indent() ignores `expandtab` when indent unchanged #40932"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe current check is intended to match DOS device paths starting with\n`\\\\?` or `\\\\.` but will match any path starting with `?` or `.`,\nincluding relative paths such as `.\\`.\nThis is because the leading slashes are removed before the comparison.\n\nSolution:\nChanges the check to include the path's prefix, assuring the path has\nthe correct amount of separators for a DOS device path.", "completion": "fix(path): DOS device path check #40976"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* chore: add missing backticks in `lib/languages/js/index.js`\n\n* chore: add missing backticks in `lib/config/config.js`", "completion": "chore: add missing backticks in JSDoc"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22399", "completion": "vquic: initialize new callback slot for nghttp3 v1.18.0+"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo avoid a breakage in CI and curl-for-win builds on upstream updates\nextending the callback lists. Each such breakage needed patching curl,\nrolling these patches into curl-for-win, and doing it in near real-time,\nto keep CI and builds working (and still causing some red CI jobs).\n\nBring calmness here by suppressing the warnings and allowing time to\nextend the callback tables as/if needed and at a convenient moment.\n\nCloses #22400", "completion": "vquic: silence `-Wmissing-field-initializers` for nghttp3/ngtcp2 callback tables"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace broken link with inline code\nformatting. The link was pointing to the page itself, as no dedicated block concept page exists at that URL.\ncorrects 'everytime' to 'every time'.\n\nUpdate tools/manual_api_docs/blocks/let.md\n\nCo-authored-by: Matthieu Riegler \n(cherry picked from commit 21eed5f8d4855e35f6de8cbfadc865c842d03b58)", "completion": "docs: fix self-referential link in defer block description"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace broken link with inline code\nformatting. The link was pointing to the page itself, as no dedicated block concept page exists at that URL.\ncorrects 'everytime' to 'every time'.\n\nUpdate tools/manual_api_docs/blocks/let.md", "completion": "docs: fix self-referential link in defer block description"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe code block query relied on a bug fixed in commit\n7ed5609439ba83d75e972beb859245d998df09ea, where a trailing newline was\nnot included in a node's text.\n\nSolution:\nFix the query to expect the newline.\n\n(cherry picked from commit fdc09be03cb10a1e11a31abd2ddd96d3f131b486)", "completion": "fix(help): g==: 'No code block found' #40990"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe code block query relied on a bug fixed in commit\n7ed5609439ba83d75e972beb859245d998df09ea, where a trailing newline was\nnot included in a node's text.\n\nSolution:\nFix the query to expect the newline.", "completion": "fix(help): g==: 'No code block found' #40990"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAdd pg_regress tests that exercise the row compare logic that commit\n7d9cd2df added to _bt_set_startikey. Also add tests that exercise the\n_bt_set_startikey SAOP array path.\n\nAuthor: Peter Geoghegan \nDiscussion: https://postgr.es/m/CAH2-Wz=KjQsD2W2a=b51uH905=0mF6Le4evhWkN2FL1+uRPhUg@mail.gmail.com\nBackpatch-through: 19", "completion": "Add _bt_set_startikey row compare test coverage."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReport unsupported style property binding values in development mode while preserving existing binding behavior. Unwrap trusted style values before appending unit suffixes and link NG0318 warnings to the corresponding error guide.\n\n(cherry picked from commit e43eb96341b692525743a1f3aa1380ce21a9dd02)", "completion": "fix(core): warn when style property bindings receive invalid values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReport unsupported style property binding values in development mode while preserving existing binding behavior. Unwrap trusted style values before appending unit suffixes and link NG0318 warnings to the corresponding error guide.", "completion": "fix(core): warn when style property bindings receive invalid values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22401", "completion": "cf-ngtcp2-cmn: de-duplicate `ngtcp2_conn_client_new()` call code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFixing:\n```\nFAILED ../../tests/http/test_02_download.py::TestDownload::test_02_36_looong_urls[65536-h3] -\n AssertionError: expected exit code 0, got 56\nFAILED ../../tests/http/test_14_auth.py::TestAuth::test_14_05_basic_large_pw[h3] -\n AssertionError: expected exit code 0, got 56\n```\nRef: https://github.com/curl/curl/actions/runs/30207198835/job/89807247058?pr=22400\n\nRefs:\nhttps://github.com/ngtcp2/nghttp3/pull/539\nhttps://github.com/ngtcp2/nghttp3/commit/a5872645446cdc07e897fea33b61a3c665563da9\n\nBug: https://github.com/curl/curl/pull/22397#issuecomment-5084927935\n\nCloses #22402", "completion": "pytest: update two H3 tests for nghttp3 1.18.0+"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n## Flicker cause\n\nui2's `check_targets()` function creates the hidden ui2 windows with this call chain:\n```\nnvim_open_win()\nwin_set_buf()\ndo_buffer()\nset_curbuf()\nenter_buffer()\n```\n\nand `enter_buffer()` sets `need_fileinfo`:\n\nhttps://github.com/neovim/neovim/blob/fdc09be03cb10a1e11a31abd2ddd96d3f131b486/src/nvim/buffer.c#L1837-L1839\n\nThis is then picked up by `normal_redraw`:\n\nhttps://github.com/neovim/neovim/blob/fdc09be03cb10a1e11a31abd2ddd96d3f131b486/src/nvim/normal.c#L1381-L1385\n\nThe fileinfo message then causes a ui2 window to appear to display it:\n\nhttps://github.com/neovim/neovim/blob/fdc09be03cb10a1e11a31abd2ddd96d3f131b486/runtime/lua/vim/_core/ui2/messages.lua#L325-L330\n\n... which ends up calling `set_pos`, which registers an `on_key` handler:\n\nhttps://github.com/neovim/neovim/blob/fdc09be03cb10a1e11a31abd2ddd96d3f131b486/runtime/lua/vim/_core/ui2/messages.lua#L726-L728\n\nThis handler closes the ui2 window when the user presses, for example, `l` (because the user's not focusing said window).\nThe handler eventually calls `check_targets()`:\n\nhttps://github.com/neovim/neovim/blob/fdc09be03cb10a1e11a31abd2ddd96d3f131b486/runtime/lua/vim/_core/ui2/messages.lua#L594-L595\n\nand `check_targets()` takes us back to the beginning, causing the ui2 window flicker\n\n## Repro\n\n```vim\n=require(\"vim._core.ui2\").enable()\nset ch=0 shm-=F ve=all\ne /tmp/x\n```\n\nThen hit `Ctrl-G` to show fileinfo (if not already shown) and hold `l`\n\n## Fix\n\nEffectively surround the ui2 window creating with `:silent`", "completion": "fix(ui2): avoid flickering fileinfo messages #41002"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis will prevent to polute the agent context with outdated/bad practices.\n\n(cherry picked from commit c1025a0510520fa4398705869bdc73613332b337)", "completion": "refactor(core): Migrate more tests off `fakeAsync`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis will prevent to polute the agent context with outdated/bad practices.", "completion": "refactor(core): Migrate more tests off `fakeAsync`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22403", "completion": "GHA/windows: bump stunnel to 5.79"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nReplace the placeholder polling implementation with a browser-backed libuv polling backend and add the required platform compatibility stubs for the WebAssembly build.", "completion": "build(wasm): update wasm_stubs with browser libuv polling support"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso:\n- add one debug option to pass the test.\n\nRef: https://github.com/curl/curl/discussions/14885#discussioncomment-10632311\n\nCloses #22404", "completion": "cmake: verify if options are listed in `INSTALL-CMAKE.md`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis replaces an O(N) hash_seq_search() loop by an O(1) lookup, removing\na TODO item, making the invalidation callback faster when dealing with\nmany relations. This can work because LogicalRepPartMap is keyed by a\npartition OID, and a relmapentry's localreloid matches with it.\n\nAn assertion is added in logicalrep_partition_open() to enforce the fact\nthat localreloid matches with the hash key.\n\nAuthor: DaeMyung Kang \nDiscussion: https://postgr.es/m/20260417174450.4158878-1-charsyam@gmail.com", "completion": "Use direct hash lookup in logicalrep_partmap_invalidate_cb()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nNoticed while doing some routine work.\n\nOversight in e395fbd32a07.", "completion": "Update .gitignore in test/modules/nbtree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 8d829f5a0 introduced the JSCTOR_JSON_ARRAY_QUERY constructor\ntype so that ruleutils.c could deparse JSON_ARRAY(subquery) using its\noriginal syntax, storing the transformed subquery in a new orig_query\nfield. However, the input FORMAT clause of JSON_ARRAY(subquery FORMAT\n...) was not preserved for deparsing. The format was recorded only in\nthe executable expression kept in the func field, which ruleutils.c\ndoes not inspect, so it is silently dropped.\n\nThis is more than cosmetic, because FORMAT JSON changes the result:\nwithout it a text value is treated as a string to be quoted, while\nwith it the value is treated as already-formatted JSON.\n\nTo fix, record the input FORMAT in a new deparse-only field of\nJsonConstructorExpr, alongside orig_query, and emit it in ruleutils.c.\n\nBump catalog version.\n\nAuthor: Chao Li \nReviewed-by: Ewan Young \nReviewed-by: Richard Guo \nDiscussion: https://postgr.es/m/4C89B193-7D54-4705-9CF9-F0D484B9E099@gmail.com\nBackpatch-through: 19", "completion": "Fix deparsing of JSON_ARRAY(subquery) with a FORMAT clause"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n1. Stop a running sequence synchronization worker when\nALTER SUBSCRIPTION ... DISABLE is executed. The worker did not reread its\nsubscription after starting a transaction, so it kept running with a stale\ncopy and missed the disable. It now calls maybe_reread_subscription()\nafter StartTransactionCommand(), matching the apply worker.\n\n2. Restore the invariant that publisher-side synchronization slots are\ndropped last during ALTER SUBSCRIPTION ... REFRESH PUBLICATION. The\nslot-drop loop now runs after the sequence-removal loop, so the\nnon-transactional slot drops happen only after all catalog changes that\ncould still be rolled back on error.\n\n3. Restore psql tab completion for\nALTER SUBSCRIPTION ... REFRESH PUBLICATION WITH (.\n\n4. Make pg_stat_subscription report NULL for the fields that do not apply\nto a sequence synchronization worker, which does not stream from a\nwalsender, and update the documentation accordingly.\n\n5. Update the pg_subscription_rel.srsublsn catalog documentation to\ndescribe its semantics for sequence rows.\n\nReported-by: Noah Misch \nAuthor: vignesh C \nReviewed-by: Hayato Kuroda \nReviewed-by: Amit Kapila \nBackpatch-through: 19, where it was introduced\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Fix issues in logical replication sequence synchronization."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRoute odd moduli in OSSL_FN_mod_exp() to a Montgomery sliding-window\npath, a faithful port of BN_mod_exp_mont() in crypto/bn/bn_exp.c. The\nfixed-width deviations, the constant-time caveat, the dispatcher\nrouting, and the OSSL_FN_mod_exp_ctx_size() sizing model are all\ndocumented in the respective function headers.\n\ntest_fn and test_fn_api pass on linux-x86_64 and linux-x86; the odd-\nmodulus cases (the stanza suite and the KAT/alias tests) now exercise\nthe Montgomery path against the BN_mod_exp oracle.\n\nAssisted-by: Pi:z-ai/glm-5.2\nAssisted-by: Pi:moonshotai/kimi-k3\nRelated-to: doc/designs/fixed-size-large-numbers.md\nIssue: https://github.com/openssl/project/issues/2025\nSigned-off-by: Richard Levitte \n\nReviewed-by: Jakub Zelenka \nReviewed-by: Igor Ustinov \nReviewed-by: Matt Caswell \nMergeDate: Fri Jul 31 09:38:11 2026\n(Merged from https://github.com/openssl/openssl/pull/31962)", "completion": "OSSL_FN: Add OSSL_FN_mod_exp_mont()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(DatePicker): prevent unconfirmed range submission\n\n* test(DatePicker): sync picker snapshots", "completion": "fix(DatePicker): prevent unconfirmed range submission"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- move `Curl_conn_seems_dead()` into conncache.c\n- move `Curl_conn_upkeep()` into conncache.c\n- when upkeep gives an error on a connection not in use,\n terminate it\n\nCloses #21806", "completion": "conncache: conn upkeep/alive: move and enhance"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nPOSIX-compatible Ex-mode requires special-cases all over the codebase to\nmatch various quirks that don't actually matter to users.\n- The main utility of *interactive* Ex-mode is its REPL behavior, and\n that can be achieved with `cmdwin`, which also gains extra UX\n benefits.\n- The main utility of *non-interactive* `nvim -es` is for shell\n scripting, where Ex-mode quirks are mostly unhelpful (e.g. the\n \"Entering Ex mode\" message).\n\nSolution:\n- Reimplement *interactive* Ex-mode as a \"persistent, insert-mode\n cmdwin\" in Lua.\n - \"nvim -e/-E\" is simply an alias to \"gQ\".\n- Reframe *non-interactive* Ex-mode (`nvim -es`) as \"script mode\".\n - Drop POSIX Ex-mode quirks.\n\nImprovements:\n- \"nvim -V1 -es\" output ends with a final newline!\n- \"nvim -V1 -es\" no longer shows the \"Entering Ex mode\" msg. (This was\n pointless noise, unwanted for scripting purposes.)\n- stdin is no longer typeahead. Scripts (\":lua io.read()\") can read\n stdin as data.\n- Empty line is a no-op: a stray blank line no longer moves the cursor\n (deviates from POSIX ex \"+1\"), no longer exits 1 at EOF (E501).\n\nPreserved behavior:\n- cursor starts at \"$\"\n- mode()==\"cv\" (for non-interactive)\n- multiline commands (:append/:function/heredoc pull continuation lines)\n- bare-range print\n- :print=>stdout\n- -V1=>stderr\n- CRLF input\n- continue-after-error and exit codes\n\nDropped (regressed) POSIX behavior (non-interactive):\n- Event loop only ticks while/between commands, not while blocked\n waiting for a stdin line.\n- \":g/pat/visual...Q\"\n- input()/getchar()/\":s/x/y/c\" no longer consume stdin lines as\n answers: Nvim stops at end-of-input, skipping the rest of the script,\n exit 0. Use \":lua io.read()\" instead.\n - If users care about this they should use interactive Ex-mode (`gQ`).\n- \":@r\" stops at end of the register instead of continuing to read\n cmdline input from stdin.", "completion": "refactor(exmode): Ex-mode as cmdwin + Lua #40991"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe subtests added in f26d632a0e assert that \"openssl enc -d\" exits\nnon-zero when the key derivation parameters do not match. enc has no\nMAC, so a wrong key is not detectable as such; the only signal is\nwhether the garbage happens to form valid PKCS#7 padding, which\nopenssl-enc(1) documents as passing better than one time in 256. With\na random salt the tests thus failed about 0.4% of the time.\n\nAssert instead that mismatching parameters do not recover the\nplaintext: the decryption must either fail or produce differing output.\n\nAssisted-by: Claude:claude-opus-5[1m]\n\nSigned-off-by: Norbert Pocs \n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nMergeDate: Mon Jul 27 12:17:21 2026\n(Merged from https://github.com/openssl/openssl/pull/32083)", "completion": "test: fix flaky -md and -iter mismatch checks in 20-test_enc.t"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 80cd48257721cb4261495131ea806020a309b9c4)", "completion": "fix(lua): vim.regex():match_str abort in Luv callback #41008"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nE.g. `TEST_DATA_STRING` in test 655.\n\nCherry-picked from #22406\n\nCloses #22409", "completion": "typecheck-gcc: allow passing `char[]` as callback data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nDefer the timing hook subscription until the timing API is explicitly enabled. Keep production module loading and development initialization covered by isolated browser test targets.", "completion": "fix(devtools): avoid initializing profiler in production mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOffset 0 is the \"invalid\" marker in pg_multixact/offsets since offsets\nwent 64-bit and the allocator stopped skipping it. pg_resetwal could\nstill produce it via -O 0 or guessed control values, breaking the first\nmultixact created after the reset (\"MultiXact n has invalid offset\",\nand vacuum of the affected table fails from then on). Reject -O 0 like\n-m and -o already do, and guess 1 like initdb does.\n\nAuthor: Zsolt Parragi \nDiscussion: https://www.postgresql.org/message-id/CAN4CZFNoO6MUkg526TmA=mC_RjY2gp4VKCnvK6y12v3ppOkhJA@mail.gmail.com\nBackpatch-through: 19", "completion": "pg_resetwal: do not allow zero next multixact offset"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: A preselected item is inserted even with \"noinsert\", and the\n first added preselected item wins over the first one shown\n in the menu.\nSolution: Use K_DOWN when \"noinsert\" is set; pick the first preselected\n item that made it into the menu.", "completion": "fix(completion): \"preselect\" ignores \"noinsert\", menu order #41007"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nOn NetBSD, `man -w open` can return the exact manpage path, but `:Man`\nmay still fail when man directories cannot be discovered from `manpath\n-q`, bare `man -w`, or `$MANPATH`.\n\nSolution:\nFall back to the direct manpage lookup when directory discovery fails.\nAdd a test for resolving `open(2)` through `goto_tag()` without manpath\ndata.", "completion": "fix(man): use direct lookup without manpath #40421"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 8e72d914c recorded the range column's name in ForPortionOfExpr\nand used that for deparsing FOR PORTION OF. This gives the wrong\nanswer if the ForPortionOfExpr is saved in a rule or SQL function and\nthen the column gets renamed. Drop the ForPortionOfExpr.range_name\nfield; instead fetch the current column name from the catalogs when\nneeded.\n\nAlso drop ForPortionOfState.fp_rangeName, which wasn't being used\nanywhere.\n\nFull disclosure: an earlier draft of this patch was made with\nClaude Opus 4.8.\n\nReported-by: John Naylor \nAuthor: Tom Lane \nReviewed-by: Richard Guo \nReviewed-by: Chao Li \nDiscussion: https://postgr.es/m/CANWCAZYFEpJ5Oi45gi4q9Y6LYa4_oiAXxuNNWe-1ym-i0fF8Pw@mail.gmail.com\nBackpatch-through: 19", "completion": "Deparse FOR PORTION OF using the range column's current name."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_set_bio() transfers ownership of cbio to the client SSL object.\nClear the local pointer after the handoff so the error path does not\nrelease an SSL-owned reference before SSL_free().\n\nFixes #32084\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Daniel Kubec \nMergeDate: Wed Jul 29 09:56:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32086)", "completion": "quic: fix BIO ownership in test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_set_bio() transfers ownership of cbio to the client SSL object.\nClear the local pointer after the handoff so the error path does not\nrelease an SSL-owned reference before SSL_free().\n\nFixes #32084\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Daniel Kubec \nMergeDate: Wed Jul 29 09:55:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32086)", "completion": "quic: fix BIO ownership in test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_set_bio() transfers ownership of cbio to the client SSL object.\nClear the local pointer after the handoff so the error path does not\nrelease an SSL-owned reference before SSL_free().\n\nFixes #32084\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Daniel Kubec \nMergeDate: Wed Jul 29 09:55:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32086)", "completion": "quic: fix BIO ownership in test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_set_bio() transfers ownership of cbio to the client SSL object.\nClear the local pointer after the handoff so the error path does not\nrelease an SSL-owned reference before SSL_free().\n\nFixes #32084\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Daniel Kubec \nMergeDate: Wed Jul 29 09:55:25 2026\n(Merged from https://github.com/openssl/openssl/pull/32086)", "completion": "quic: fix BIO ownership in test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_set_bio() transfers ownership of cbio to the client SSL object.\nClear the local pointer after the handoff so the error path does not\nrelease an SSL-owned reference before SSL_free().\n\nFixes #32084\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Daniel Kubec \nMergeDate: Wed Jul 29 09:55:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32086)", "completion": "quic: fix BIO ownership in test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- add CURLUE_BACKSLASH that can be returned when a backslash was used\n where a forward one probably was intended.\n\n- make CURLUE_NO_HOST higher priority than port number errors for URLs\n without hostname. Like in \"http://::1\"\n\n- shortened some URL parser error strings\n\nExtend test 1560 to verify.\n\nReported-by: kit-ty-kate on github\nFixes #22337\nCloses #22408", "completion": "urlapi: improved return codes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWant `gQ` for _le multicursor_.\n\nSolution:\n- Don't use `gQ` for exmode.\n- Introduce `:exmode`.\n- Introduce `[count]q:` as an alias to `:exmode`.", "completion": "feat(exmode): \"1q:\", :exmode #41010"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWith wal_level = 'replica', logical decoding is enabled on demand\nwhen the first logical replication slot is created:\n\nWhen enabling logical decoding, EnableLogicalDecoding() flips the\nshared logical_decoding_enabled flag and writes an\nXLOG_LOGICAL_DECODING_STATUS_CHANGE record so that standbys follow the\nstatus change. The initial \"already enabled?\" check and the WAL record\nwrite happen under two separate acquisitions of\nLogicalDecodingControlLock, since the lock must be released while\nwaiting for the ProcSignalBarrier: processes absorbing the barrier\nacquire the same lock in shared mode.\n\nConsequently, if two backends concurrently created the first logical\nslots, both could pass the initial check and both write a\nstatus-change record. The redundant record lands after the decoding\nstart point already reserved by the other backend's slot, so decoding\nthat slot processes the record and fails with \"unexpected logical\ndecoding status change\", as xlog_decode() assumes that no such record\ncan appear within the WAL range any slot decodes.\n\nFix by re-checking the status after re-acquiring the lock, so that\nonly the backend that actually performs the disabled->enabled\ntransition writes the WAL record.\n\nReported-by: Srinath Reddy Sadipiralla \nAuthor: Srinath Reddy Sadipiralla \nReviewed-by: Masahiko Sawada \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/CAFC+b6oYzmAgp7F0ivrhfZT46-CjvCTrU9pWuMNcem-52YjOTw@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix race condition when enabling logical decoding concurrently."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Igor Ustinov \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Fri Sep 4 09:14:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32092)\n\n(cherry picked from commit 573d671485940b68802325f6641005c67aa7abdb)", "completion": "add d2i regression test to asn1 decode test suite"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Igor Ustinov \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Fri Sep 4 09:14:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32092)", "completion": "add d2i regression test to asn1 decode test suite"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 181b6185c failed to do anything useful with a whole-row Var,\ndeeming it \"fishy\". But it is legal to put such a Var into an\nexpression index column, so let's expand it as the name of the table.\n\nAnother problem reachable via that one is that we could generate an\nempty index column name, which isn't really legal although by chance\nnothing complained about it. It's not clear whether any other such\ncases remain, but as cheap insurance let's use \"expr\" if the tree walk\nfails to generate any text.\n\nReported-by: Chauhan Dhruv \nAuthor: Chauhan Dhruv \nCo-authored-by: Tom Lane \nDiscussion: https://postgr.es/m/CANWwWcp_DCJjq8pomeqp6W=fbygvzXXQO028VDJ9_6sLPjQnVA@mail.gmail.com", "completion": "Further improve the names generated for indexes on expressions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22411", "completion": "EXPERIMENTAL.md: We do not accept vuln reports for experimental features"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nindex_create_copy is used to create copy definitions of existing indexes.\nCurrently, it passes 0 as constr_flags to index_create(), which results\nin the copied index to always be created as immediate (indimmediate set\nto true). For deferrable unique constraints, it means that the\ntransient index used during the phase 2 of REINDEX CONCURRENTLY forces\nimmediate constraint checks on concurrent inserts, which can cause\nunexpected constraint violations based on the definition of the parent\ntable, inconsistently set in the copied index.\n\nTo fix this without violating the contract of constr_flags (which should\nonly be used when creating constraints) and without relaxing the strict\nassertion in index_create(), this introduces a new index creation flag:\nINDEX_CREATE_DEFERRABLE. If set, a copied index's indimmediate is set\nto false, meaning that unique constraints are not enforced immediately\non insertion, but at transaction commit time.\n\nAn isolation test for REINDEX CONCURRENTLY is added, based on an\ninjection point waiting after phase 1 of the operation, where an index\ncopy has been built and is able to accept DMLs for its validation in\nphase 2. The test is tentatively backpatched down to v17.\nINJECTION_POINT() is outside a transaction context, which should be fine\non HEAD since 8daeaa9b642c but I suspect may cause issues in v19 and\nolder branches due to the wait facility depending on condition variables\nand a DSM setup, but let's see what the buildfarm tells.\n\nAuthor: Nitin Motiani \nDiscussion: https://postgr.es/m/CAH5HC97JmjPpgiQOqW9xm8qXhNiu7zZ1Qh+FfhEESJuDv69kuQ@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix propagation of indimmediate flag in index_create_copy()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nResolve VDOM slot output using the same child selection and transition hook\npreparation as BaseTransition. Prepare both the incoming and previously\nrendered branches so enter and leave transitions work correctly, including\nkeyed fragment identity.", "completion": "fix(runtime-vapor): support vdom slot content in Transition"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe mapped user name is built upon the OS user name of the environment\nwhere the test is run. Depending on the characters used in the OS user\nname, CREATE ROLE may not get parsed (the author has mentioned hyphens\nas one case), causing a failure of the test.\n\nLet's use double-quotes around the mapped user name, which should be a\nsolution good enough for the environments where this test tends to run.\nThe buildfarm issued no complaint over the years.\n\nOversight in 3c4e26a62c31, so backpatch down to v19. Perhaps\n3c4e26a62c31 and this commit should be backpatched further down, but\nlet's leave that for another day, if it proves necessary.\n\nAuthor: Yugo Nagata \nDiscussion: https://postgr.es/m/20260727133857.fbd23d43d422f10f376a8bee@sraoss.co.jp\nBackpatch-through: 19", "completion": "Fix portability issue in authentication test 003_peer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe internal provider test can retain provider-init allocations\nwhen the Valgrind suppression workflow intentionally skips OPENSSL_cleanup().\nIts stack calls OSSL_provider_init directly from provider_activate, without\nthe provider_init frame covered by the existing suppression.\n\nAdd a second exact suppression for that stack shape instead of broadening the\nexisting block with an ellipsis.\n\nReviewed-by: Paul Dale \nReviewed-by: Norbert Pocs \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMergeDate: Wed Jul 29 16:58:17 2026\n(Merged from https://github.com/openssl/openssl/pull/32094)", "completion": "test: add precise Valgrind provider init suppression"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nClose #15157", "completion": "fix(runtime-vapor): handle custom directives on fragment roots"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nTreat unresolved async wrappers as pending instead of warning about a\nnon-element root. Track fragment updates so directives are applied once\na renderable root becomes available.\n\nFor async setup under Suspense, retry from beforeMount after the resolved\nblock is created. This preserves lifecycle error handling and applies the\ndirective before the resolved child mounts.", "completion": "fix(runtime-vapor): handle custom directives on async components"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(demo): replace hardcoded styles with design tokens\n\n* test: update demo snapshots\n\n---------", "completion": "refactor(demo): replace hardcoded styles with design tokens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe current lockless design does not need this lock around objs anymore\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Bob Beck \nMergeDate: Thu Jul 30 06:12:46 2026\n(Merged from https://github.com/openssl/openssl/pull/32003)", "completion": "Remove unneeded lock"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 9373d22a48546bab8de1f4b28c158d6dea617fd8)", "completion": "docs: remove semicolon text node"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nTree-sitter uses UINT32_MAX for full-document ranges, which becomes -1 on 32-bit platforms and reaches _foldupdate as an invalid end row.\n\nSolution:\nTreat negative changed-range end rows as unbounded and clamp them to the buffer line count. Add a regression test that simulates the 32-bit sentinel.\n\nAI-assisted: Codex\n(cherry picked from commit 20ff82d9fcdeafe2cdf4824b8af1bdeeffb513b6)", "completion": "fix(treesitter): clamp unbounded fold ranges"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nTree-sitter uses UINT32_MAX for full-document ranges, which becomes -1 on 32-bit platforms and reaches _foldupdate as an invalid end row.\n\nSolution:\nTreat negative changed-range end rows as unbounded and clamp them to the buffer line count. Add a regression test that simulates the 32-bit sentinel.\n\nAI-assisted: Codex", "completion": "fix(treesitter): clamp unbounded fold ranges"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUpdate the `lastchecked` timestamp on connection health checks when\nsuccessful to prevent repeated recalcs for a second.\n\nRename `seems_dead` to `seems_healthy` because the world is already\ndepressing enough.\n\nConsider pending input on connection only unhealthy when the connection\nhas no transfers and is not multiplexed.\n\nCloses #22412", "completion": "conncache: connection healthiness fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nUPDATE/DELETE ... FOR PORTION OF inserts leftover rows for the\nuntouched parts of the original row. These hidden inserts should not\naffect the command tag or ROW_COUNT, so they call ExecInsert() with\ncanSetTag set to false.\n\nHowever, ExecInsert() still processed the RETURNING list whenever the\ntarget ResultRelInfo had ri_projectReturning set. That caused\nRETURNING expressions to be evaluated for leftover rows even though\ntheir results were discarded. As a result, expressions with side\neffects and information-leaking functions could be executed on the\nleftover rows, in addition to the visibly updated or deleted row.\n\nFix by having ExecInsert() skip RETURNING processing when it is\nhandling an internal FOR PORTION OF leftover insert. Use both the\npresence of a FOR PORTION OF clause and mtstate->operation ==\nCMD_INSERT for this check, so that the auxiliary INSERT of a\ncross-partition UPDATE with a FOR PORTION OF clause still processes\nRETURNING normally.\n\nBack-patch to v19, where support for FOR PORTION OF was added.\n\nAuthor: Chao Li \nReviewed-by: Dean Rasheed \nReviewed-by: Paul A Jungwirth \nDiscussion: https://postgr.es/m/07C125E5-F6ED-460C-A394-E6503DAE18FB@gmail.com\nBackpatch-through: 19", "completion": "Avoid RETURNING side effects for FOR PORTION OF leftovers."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit fd83c83d094 turned the recursive posting-tree cleanup in\nginVacuumPostingTreeLeaves() into an iterative sweep that follows the\ntree's leaf pages via their rightlinks. The recursive version called\nvacuum_delay_point() while processing the tree, but that call was removed\nand never re-added to the new loop. As that commit only set out to fix a\ndeadlock, the removal appears to have been unintentional.\n\nConsequently the leaf-page sweep of a single posting tree runs with no\nvacuum_delay_point(), and therefore no CHECK_FOR_INTERRUPTS(). A posting\ntree stores all the TIDs for one indexed key, so for a frequently\noccurring key it can span a large number of leaf pages. While such a\ntree is being vacuumed the operation ignores vacuum_cost_delay and does\nnot respond to query cancellation or statement_timeout; an autovacuum\nworker likewise cannot be interrupted mid-sweep when another backend\nrequests a conflicting lock.\n\nRestore the call, placed after the current page has been unlocked and\nreleased so that no buffer content lock is held across a potential delay\n(cf. 21c27af65fb). The sibling loops in ginbulkdelete() and\nginvacuumcleanup() already call vacuum_delay_point() once per page.\n\nAuthor: Paul Kim \nCo-authored-by: Alexander Korotkov \nReviewed-by: Michael Paquier \nReviewed-by: Andrey Borodin \nReviewed-by: solai v \nDiscussion: https://postgr.es/m/178447127453.110.12276981925360691905%40mail.gmail.com\nBackpatch-through: 14", "completion": "Restore vacuum_delay_point() in GIN posting-tree leaf vacuum"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe have `useAutoTick` in our private shared utils.\n\n(cherry picked from commit 36474f7011adf817c3efba841e8a1d630139aa43)", "completion": "refactor(common): remove duplicate helper function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe have `useAutoTick` in our private shared utils.", "completion": "refactor(common): remove duplicate helper function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- Attempt to fix the flakiness set in 9726fc8259ad7ebf1682\n- Reduce macro use\n\nCloses #22414", "completion": "lib2405: adjust for non-threaded builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nA Barrier created with targetCount 0 never settled its promise because\nsignal() was never called for classes with zero constructor or property\ndependencies, leaving one forever-pending promise per zero-dependency\nclass and tripping async-leak detection (e.g. Vitest detectAsyncLeaks).\nResolve eagerly in the constructor and make signal() idempotent past\nthe threshold to tolerate over-signaling from error paths.\n\nCloses #17392", "completion": "fix(core): resolve barrier immediately when target count is zero"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNvim diverged from Vim's \":version\".\n\n- no date\n- different compiled features list\n- different config file and directory\n- no compiler flags\n\n* build(vim-patch): n/a doc for balloon feature (8.2.3917)", "completion": "build(vim-patch): \":version\" doc is n/a #41018"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 59296a9fef42247f91567a77bd87edd34b14f6cc)", "completion": "fix(treesitter): incremental selection: \"vin\" not always starts \"v\" #41016"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit ae303c4a05be72a89b7a8b41736bf9da75c245a7)", "completion": "docs: document overlay stacking change in v21 update guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: complete_info() does not report \"equal\", \"preselect\" or \"commit_chars\".\n\nSolution: Report them for the items that set them.", "completion": "fix(eval): complete_info() equal, preselect, commit_chars #41022"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCursor-relative floats can use stale screen coordinates after a cursor move is restored without a redraw.\n\nSolution:\nValidate the current cursor before converting cursor-relative coordinates.\n\nCo-authored-by: zeertzjq \n(cherry picked from commit 089c415cb236512add6c29372e26640ff401d39b)", "completion": "fix(floatwin): relative='cursor' may use outdated cursor position #40768"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCursor-relative floats can use stale screen coordinates after a cursor move is restored without a redraw.\n\nSolution:\nValidate the current cursor before converting cursor-relative coordinates.", "completion": "fix(floatwin): relative='cursor' may use outdated cursor position #40768"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22418", "completion": "h2: bootstrap max streams from multi handle if in use"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUsing Apple's secret `SYS_recvmsg_x` and `SYS_sendmsg_x` syscalls for\nreceiving/sending batches of UDP packets.\n\nSince it uses undocumented calls, it's experimental and disabled by\ndefault.\n\nTo enable:\n- autotools: `--enable-apple-fast-udp`\n- cmake: `-DCURL_ENABLE_APPLE_FAST_UDP=ON`\n\nAlso:\n- enable in two H3 CI jobs with both build tools, pytest and clang-tidy.\n\nRefs:\nhttps://max-inden.de/post/fast-udp-io-in-firefox/\nhttps://www.macsyscalls.com/en/syscall/480-recvmsg-x\nhttps://www.macsyscalls.com/en/syscall/481-sendmsg-x\n\nC-code-authored-by: Stefan Eissing\nBuild-code-authored-by: Viktor Szakats\n\nCloses #22341\nCloses #22417", "completion": "vquic: add option to use Apple fast UDP"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCreate form controls before registering template listeners so custom control values are synchronized before user callbacks run. Cover Signal Forms, reactive forms, and template-driven forms.\n\n(cherry picked from commit 6688a3d5502f159479c4e71cbd44f6713a40fe25)", "completion": "fix(forms): create controls before listeners"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCreate form controls before registering template listeners so custom control values are synchronized before user callbacks run. Cover Signal Forms, reactive forms, and template-driven forms.", "completion": "fix(forms): create controls before listeners"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen writing a decoded chunk of websocket data, always flush the writer\nchain so that buffered data gets delivered before the ws meta data gets\nupdated.\n\nAdd client writer flags CURL_CW_FLAG_BLOWUP for writer types that may\nsignificantly enlarge write sizes. This flag causes the pause writer to\nbe added and shrinks the write chunk sizes. We do not want that for\ncontent decoders like WS that do not change the size.\n\nAdd test_20_13 to check that large frames are paused/unpaused correctly\nwith the matching meta data.\n\nFixes #22413\nReported-by: Hendrik Hübner\nCloses #22416", "completion": "websocket: pause writing and meta data fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nIntroduce an initial browser-based Neovim demo with automatic startup and UI integration. The demo is functional but still requires persistence, additional testing, and further stabilization.\n\nAcknowledgment: UiState in app.js is based on the implementation from github.com/MuNeNiCK/nvim-wasm, with additional modifications and updates", "completion": "feat(wasm): implement initial web demo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\ncommit_chars_str() reads a 0x80-0xBF byte as a 2-byte lead, so\n\"\\xA9x\" makes \"x\" a commit character. nvim_get_hl() returns\na dict, so `#` on it is 0 whether or not the group exists\n\nSolution:\nuse vim.str_utf_end() and drop entries that are not one whole\ncharacter. use next check dict length.", "completion": "fix(lsp): multibyte fragment treated as commit char #41019"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo make the minimum gap two spaces, so that we can separate the columns\nprogrammatically", "completion": "docs/INTERNALS.md: move a column one byte"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDirect access to `p7->d.sign->contents->d.data` skips the content-type\ncheck: if the inner eContentType is a non-standard OID the ADB sets\nd.other (16 bytes) instead of d.data (24 bytes), and the subsequent\nos->flags write lands out of bounds.\n\nReplace with `PKCS7_get_octet_string()`, which returns NULL for any type\nthat is not `NID_pkcs7_data`, matching the guard already used by\n`PKCS7_ctrl()` and `PKCS7_dataDecode()`.\n\nAdded a unit-test (`pkcs7_stream_non_data_test`) to validate the change.\n\nFixes #31681\n\nReviewed-by: Bob Beck \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMerge-date: Tue Aug 18 07:47:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/31722\n(cherry picked from commit eedaf1c2c46b5e511a603833a65a742085c01bb2)\n(cherry picked from commit 56c1e4fc7625295283c22108746cb974229d9575)", "completion": "pkcs7: use PKCS7_get_octet_string in PKCS7_stream signed arm"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDirect access to `p7->d.sign->contents->d.data` skips the content-type\ncheck: if the inner eContentType is a non-standard OID the ADB sets\nd.other (16 bytes) instead of d.data (24 bytes), and the subsequent\nos->flags write lands out of bounds.\n\nReplace with `PKCS7_get_octet_string()`, which returns NULL for any type\nthat is not `NID_pkcs7_data`, matching the guard already used by\n`PKCS7_ctrl()` and `PKCS7_dataDecode()`.\n\nAdded a unit-test (`pkcs7_stream_non_data_test`) to validate the change.\n\nFixes #31681\n\nReviewed-by: Bob Beck \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMerge-date: Tue Aug 18 07:47:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/31722\n(cherry picked from commit eedaf1c2c46b5e511a603833a65a742085c01bb2)", "completion": "pkcs7: use PKCS7_get_octet_string in PKCS7_stream signed arm"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDirect access to `p7->d.sign->contents->d.data` skips the content-type\ncheck: if the inner eContentType is a non-standard OID the ADB sets\nd.other (16 bytes) instead of d.data (24 bytes), and the subsequent\nos->flags write lands out of bounds.\n\nReplace with `PKCS7_get_octet_string()`, which returns NULL for any type\nthat is not `NID_pkcs7_data`, matching the guard already used by\n`PKCS7_ctrl()` and `PKCS7_dataDecode()`.\n\nAdded a unit-test (`pkcs7_stream_non_data_test`) to validate the change.\n\nFixes #31681\n\nReviewed-by: Bob Beck \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMerge-date: Tue Aug 18 07:47:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/31722", "completion": "pkcs7: use PKCS7_get_octet_string in PKCS7_stream signed arm"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis is a second attempt at scoping nested CSS rules after not being able to land #50693. I took some extra precautions to try and avoid the crash that was happening last time.", "completion": "fix(compiler): scope nested CSS rules"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdates the nested selector encapsulation logic so that it skips encapsulating child selectors if the parent contains `::ng-deep`. The reasoning is that `:host ::ng-deep { .foo {} }` should behave as `:host ::ng-deep .foo {}`.", "completion": "fix(compiler): do not encapsulate nested selectors if parent contains ::ng-deep"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n- remove NgModules\n- remove non-necessary TestBed.configureTestingModule\n- remove non-necessary Eager strategy\n- Drop usages of CommonModule\n\n(cherry picked from commit d8a570ec4e56565f4f0185500ebb9a206e894322)", "completion": "refactor(core): update acceptance test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n- remove NgModules\n- remove non-necessary TestBed.configureTestingModule\n- remove non-necessary Eager strategy\n- Drop usages of CommonModule", "completion": "refactor(core): update acceptance test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Installing plugins during lockfile synchronization always\n writes the lockfile, even though its content is used during install.\n This might be a problem if the lockfile (itself or its parent\n directory) is not writeable (can only be read).\n\nSolution: Do not write the lockfile when installing directly from it.\n This is okay since the `src` and `rev` are used directly from the\n lockfile and don't change at this step. While potential change in\n `version` (that must be written to the lockfile) is handled in other\n code path.\n(cherry picked from commit 4bba83b4b7363bc6b8da04cb1e13817473b028ec)", "completion": "fix(pack): do not write the lockfile when installing from it #41031"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Installing plugins during lockfile synchronization always\n writes the lockfile, even though its content is used during install.\n This might be a problem if the lockfile (itself or its parent\n directory) is not writeable (can only be read).\n\nSolution: Do not write the lockfile when installing directly from it.\n This is okay since the `src` and `rev` are used directly from the\n lockfile and don't change at this step. While potential change in\n `version` (that must be written to the lockfile) is handled in other\n code path.", "completion": "fix(pack): do not write the lockfile when installing from it #41031"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe ret argument is freed on failure which might be\nsurprising to callers.\n\nReported by: Minkyung Park (UNIST)\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Mon Aug 10 15:09:34 2026\n(Merged from https://github.com/openssl/openssl/pull/32099)\n\n(cherry picked from commit 6d250710fb8cfd5c9a41af373c0c1ca85ff836c2)", "completion": "Document the behavior of BN_generate_prime() on failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe ret argument is freed on failure which might be\nsurprising to callers.\n\nReported by: Minkyung Park (UNIST)\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Mon Aug 10 15:09:34 2026\n(Merged from https://github.com/openssl/openssl/pull/32099)", "completion": "Document the behavior of BN_generate_prime() on failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- update `GSS_C_DELEG_POLICY_FLAG` comment to include Apple GSS, add\n date, and amend MIT Kerberos version to 1.7+ (was: 1.8+)\n Ref: https://github.com/krb5/krb5/commit/45875a4d7bbd6bb8a943572d84fef5ca2bb18291\n Ref: https://github.com/apple-oss-distributions/Heimdal/commit/1635de38a813f6e1dd3f8fd270683187ad4f02be\n\n- document `HAVE_GSS_SET_NEG_MECHS`/`gss_set_neg_mechs()`.\n Ref: https://github.com/krb5/krb5/commit/079eed2cf749702f75ddc385cf943fbab931f9d8\n It's also committed to Heimdal, but not present in a release\n as of 7.8.0 (current latest).\n Ref: https://github.com/heimdal/heimdal/commit/735039dbdc3aa58d06afdefd214efe3f5e421244\n\nFollow-up to a8881e5e1d2e22d4b085d45ab6c8ce1df251d602 #21315 #22410\nFollow-up to d169ad68faa5ed5ba2375e7502307a6262466d88 #22052\n\nCloses #22419", "completion": "curl_gssapi: document/update feature availability"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nIn the close() method, if graceful shutdown is enabled and\ntryShutdown calls back with an error, the promise rejects and\nthis.grpcClient = null was skipped, leaving a dangling reference.\n\nWrapped the shutdown logic in try/finally to guarantee nullification\nregardless of success or failure.", "completion": "fix(microservices): nullify grpcclient on close when tryshutdown fails"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nReplace new Promise(async (resolve, reject) => { ... }) with\nasync IIFE or standard Promise constructor across 3 files:\n\n- nest-application-context.ts: init() method\n- client-kafka.ts: connect() method\n- module-ref.ts: instantiateClass() method\n\nAsync executors are an anti-pattern: the async function's returned\npromise is ignored, and errors must be manually caught and forwarded.\nThe IIFE form produces the same result with less indirection.", "completion": "refactor(core): remove async promise executor anti-patterns"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* chore: add allowScripts field to package.json\n\n* chore: remove version pinning from allowScripts\n\n* chore: set core-js allowScripts to false\n\n* chore: set cypress allowScripts to false\n\n* chore: install cypress binary before running browser tests\n\n* chore: add devEngines to warn on buggy npm versions\n\n* ci: update npm in browser test to avoid allowScripts bin-link bug\n\n* chore: remove devEngines from package.json\n\n* chore: update comment for npm version in CI workflow( test_on_browser)", "completion": "chore: add allowScripts field to package.json"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nCovers:\n- introspect() for DEFAULT, REQUEST, and TRANSIENT scopes\n- registerRequestByContextId() delegation\n- instantiateClass() with dependency resolution and error propagation\n- find() for single, request-scoped, and multi-instance lookups\n- resolve() for static, transient (unique per context), and\n request-scoped providers", "completion": "test(core): add unit tests for module-ref"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npg_get_publication_tables() collects the OIDs of the published tables\non its first call, without locking them, and then reopens each table\nlater, once per result row, to compute its column list and fetch its\nrow filter. The reopen used table_open(), which errors out with \"could\nnot open relation with OID\" if the table has been dropped in the\nmeantime. This could happen for any published table without an\nexplicit column list, which is every table in FOR ALL TABLES and FOR\nTABLES IN SCHEMA publications, but also FOR TABLE entries without a\ncolumn list. The failure is common in environments where many tables\nare created and dropped while publication tables are being queried,\ne.g. by table synchronization on a subscriber.\n\nFix by opening every table with try_table_open(), which returns NULL\nif the relation no longer exists, and skipping the table in that\ncase. Concurrently dropped tables are thus simply absent from the\nresult set, which is the expected point-in-time behavior.\n\nAs a side effect, tables with an explicit column list, which were\npreviously returned without being opened, are now also locked with\nAccessShareLock, so the function can block behind concurrent DDL on\nsuch tables where it previously did not.\n\nBackpatch to v16, where we added the table_open() call in\npg_get_publication_tables().\n\nAuthor: Bharath Rupireddy \nReviewed-by: Bertrand Drouvot \nReviewed-by: shveta malik \nReviewed-by: Ajin Cherian \nReviewed-by: Masahiko Sawada \nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/CALj2ACVYYooWH-5tJ6cPKkU%2BmutVxwb_z4S%2BqAi-zdrFqxXE2Q%40mail.gmail.com\nBackpatch-through: 16", "completion": "Fix pg_get_publication_tables() failure with concurrent DROP TABLE."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen hydration locates the DOM node for an ɵɵelementStart/ɵɵdomElementStart\ninstruction, locateOrCreateElementNodeImpl assumed the located node was\nalways an Element and called hasSkipHydrationAttrOnRElement(native), which\ndoes native.hasAttribute(...). The check that would normally catch this\nclass of mismatch, validateMatchingNode, is gated behind `ngDevMode &&` and\nis compiled out of production builds. So when a real SSR/hydration\nstructural mismatch located a Text or Comment node instead of the expected\nElement, production builds hit .hasAttribute on a node type that doesn't\nhave it and crashed with a raw, uncoded TypeError instead of a coded\nhydration-mismatch RuntimeError.\n\nAdd a cheap, always-on nodeType check ahead of that call. On mismatch it\nthrows RuntimeError(HYDRATION_NODE_MISMATCH, ngDevMode && '...'), the same\npattern used elsewhere in the codebase, so the descriptive message is only\nbuilt in dev mode and production keeps throwing just the bare NG0500 code\nwithout pulling validateMatchingNode's DOM-printing machinery into the\nproduction bundle (verified via the bundling/hydration golden-symbols test,\nwhich is unchanged).\n\n(cherry picked from commit 4560f4fdcda4d55c9234f71fda2e73938cb55ed6)", "completion": "fix(core): throw NG0500 instead of a raw TypeError on element hydration mismatch"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen hydration locates the DOM node for an ɵɵelementStart/ɵɵdomElementStart\ninstruction, locateOrCreateElementNodeImpl assumed the located node was\nalways an Element and called hasSkipHydrationAttrOnRElement(native), which\ndoes native.hasAttribute(...). The check that would normally catch this\nclass of mismatch, validateMatchingNode, is gated behind `ngDevMode &&` and\nis compiled out of production builds. So when a real SSR/hydration\nstructural mismatch located a Text or Comment node instead of the expected\nElement, production builds hit .hasAttribute on a node type that doesn't\nhave it and crashed with a raw, uncoded TypeError instead of a coded\nhydration-mismatch RuntimeError.\n\nAdd a cheap, always-on nodeType check ahead of that call. On mismatch it\nthrows RuntimeError(HYDRATION_NODE_MISMATCH, ngDevMode && '...'), the same\npattern used elsewhere in the codebase, so the descriptive message is only\nbuilt in dev mode and production keeps throwing just the bare NG0500 code\nwithout pulling validateMatchingNode's DOM-printing machinery into the\nproduction bundle (verified via the bundling/hydration golden-symbols test,\nwhich is unchanged).", "completion": "fix(core): throw NG0500 instead of a raw TypeError on element hydration mismatch"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 12 09:54:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32102\n(cherry picked from commit 0f5493e60b9e8ec500de5812fe28b9f564408608)", "completion": "storemgmt: Validate msblob length before buffer allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Paul Dale \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 12 09:54:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32102", "completion": "storemgmt: Validate msblob length before buffer allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless test scheduling instead of manually triggering change detection. Keep Signals Forms tests aligned with the async-first testing pattern.\n\n(cherry picked from commit 59f6ef690b82dab96ff8a29acc2a6aa06dcaad02)", "completion": "refactor(forms): modernize signal forms tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless test scheduling instead of manually triggering change detection. Keep Signals Forms tests aligned with the async-first testing pattern.", "completion": "refactor(forms): modernize signal forms tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA two-phase transaction that is assigned an XID but produces no change\nto be decoded -- for example, one that only acquires row locks via\nSELECT ... FOR SHARE -- has no base snapshot in the reorder\nbuffer. ReorderBufferReplay() already skips such a transaction at\nPREPARE time and never invokes the begin_prepare/change/prepare\ncallbacks for it, but ReorderBufferFinishPrepared() still called the\ncommit_prepared (or rollback_prepared) callback. As a result a\nspurious COMMIT/ROLLBACK PREPARED was sent to the output plugin with\nno preceding PREPARE. For the built-in subscriber this breaks\nreplication (the apply worker fails to find the prepared transaction),\nand test_decoding could even crash.\n\nFix this by detecting an empty transaction (base_snapshot == NULL) in\nReorderBufferFinishPrepared() and cleaning it up without invoking the\ncommit/rollback prepared callbacks, mirroring the existing empty\ntransaction handling in ReorderBufferReplay().\n\nOn v18 and newer versions, commit 072ee847ad4 changed\nReorderBufferPrepare() to send the prepare whenever it had not already\nbeen sent, which also fires for empty transactions and emits a\nspurious PREPARE. On those branches ReorderBufferPrepare() is\ntherefore additionally guarded with base_snapshot != NULL. This guard\nand the Assert(!rbtxn_sent_prepare()) added in\nReorderBufferFinishPrepared(), are not necessary on v17 and older\nversions: there ReorderBufferPrepare() only sends a prepare for\nconcurrently-aborted transactions (which never applies to an empty\ntransaction) and the RBTXN_SENT_PREPARE flag does not exist.\n\nBack-patch to v14, where decoding of two-phase transactions was\nintroduced.\n\nBug: #19556\nReported-by: Alexander Kozhemyakin \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/19556-daa6d7ea65054d48@postgresql.org\nBackpatch-through: 14", "completion": "Fix logical decoding of empty prepared transactions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`isEditingDirectiveState` used `!this.selectedNode` (a bare signal\nreference, always truthy) instead of `!this.selectedNode()`, so the\nguard was dead and ArrowDown with no selection threw a TypeError.", "completion": "fix(devtools): invoke selectedNode signal in directive tree keyboard guard"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe file_copy strategy check in createdb() runs during option\nvalidation, before the transaction has an XID and before the\npg_database row exists, so the datachecksumsworker launcher\ncan start in that window and see neither the new database nor\nthe transaction creating it. It then raw-copies a template\nthat was not processed yet, and those files stay unchecksummed,\nfailing verification from then on.\n\nRecheck the state in CreateDatabaseUsingFileCopy(): the XID is\nassigned by then, so a launcher starting after this point waits\nfor the transaction and finds the new database, and the copy\nerrors out instead. Add an injection point before the catalog\ninsert to test the window.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Zsolt Parragi \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAN4CZFPEBsz8JeY4ixQ1V4ZL_xOY6pJaZS8ZLGH7R+wF--pEtg@mail.gmail.com\nBackpatch-through: 19", "completion": "Recheck checksum state before file_copy during CREATE DATABASE"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nEnable errors out early with a hint when an invalid database exists,\nsince the worker cannot connect to it and its files stay on disk.\n\nA worker that started but failed gets the same dropped-database\nheuristic as one that failed to start, so a concurrent drop during\nprocessing no longer aborts the whole run. The existence check locks\nthe database first, otherwise a DROP DATABASE ... WITH (FORCE) which\nkilled the worker is still only halfway done and the database looks\nlike it is there to stay.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Zsolt Parragi \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAN4CZFOGdqxtZ5-6gb4apqmvoH=Z+TNH8RKJ3mVtoR1HirKQWg@mail.gmail.com\nBackpatch-through: 19", "completion": "Handle invalid and dropped databases during checksum enable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nfind_nonnullable_rels and find_nonnullable_vars mistakenly treated a\nScalarArrayOpExpr that could return FALSE as strict, but that's okay\nonly at top level of a qual expression; further down, we've got to\ninsist on a guaranteed-NULL result. The result was that we could draw\nmistaken conclusions about whether outer joins can be simplified, if\nthe decision hinged on a non-top-level ScalarArrayOpExpr with a\npotentially-empty array argument.\n\nI believe this error dates to commit 72a070a36, which taught\nfind_nonnullable_rels to descend into non-top-level parts of qual\nexpressions. is_strict_saop (added earlier by 72153c058) already had\nenough intelligence to do the case correctly, but it wasn't passed the\nproper flag, ie \"top_level\" needs to be passed for \"falseOK\".\ne006a24ad copied that mistake into find_nonnullable_vars.\n\nLater, over-eager refactoring in commit 2f153ddfd broke\ncontain_nonstrict_functions' handling of ScalarArrayOpExpr by treating\nit as though it were no different from an OpExpr. It is, because\nwe must also prove the array is non-empty before concluding that the\nexpression is strict. This could result in misclassifying an\nexpression as strict when it is not, leading to assorted planning\nmistakes such as inlining a SQL function that shouldn't be inlined.\nWe can almost fix this by just re-adding the previous handling of\nScalarArrayOpExpr in that function, but doing only that would lead to\nalso calling check_functions_in_node() and thus redundantly checking\nthe operator's strictness. Avoid that by turning the if-series into\nan else-if chain, as it arguably should have been all along.\n\nThe reason these errors have escaped detection for decades is that\nthey are exposed only in arcane corner cases. ScalarArrayOpExpr with\nan empty array isn't typical usage, and even when that's possible\nseveral other conditions apply before the planner can reach a mistaken\nconclusion. While it's possible to build test cases demonstrating\nthese mistakes, I (tgl) judged t", "completion": "Fix planner's nullability/strictness logic for ScalarArrayOpExpr."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe object subsystem has an intermediate representation for no real\nreason. Besides the code cost, this also adds an extra (api <=> OptVal)\nconversion step, which is a (small) perf cost.\n\nSolution:\nWe already have `Object`, so use it instead.\n\n- drop `OptVal`, `OptValData`, `OptValType`, and related boilerplate.\n- add `kObjectTypeUnset`.", "completion": "refactor(options): drop OptVal, use Object"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to e1450d8fdaf05f27ec75eb15df303fe931755a59 #22406\n\nCloses #22424", "completion": "tidy-up: use `CURL_CSTRLEN()` macro on more static strings"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nInstead suggest \"avoid contraction and rewrite to present tense\"\n\nReported-by: claudex on github\nFixes #22422\nCloses #22423", "completion": "scripts/badwords.txt: do not recommend using 'will' in rewrites"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe fallback path for cryptography < 42 was broken by commit e13362c2\nthat caused a comparison between offset-naive and offset-aware\ndatetimes. Use the positional form of tz in datetime.now() everywhere.\n\nRef: #22396\n\nPointed out by Codex Security\nCloses #22426", "completion": "tests: fix cert comparison with old cryptography"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit replaces two calls of strcpy() and one call of strncpy() to\nuse strlcpy(), which are patterns that static analyzers (mostly LLMs, it\nseems) have been complaining regarding buffer overflow risks.\n\nThe existing calls are safe, here are more details for each one of them:\n- MarkAsPreparingGuts()'s strcpy() was guarded by MarkAsPreparing().\n- PrepareRedoAdd()'s strcpy() is safe because the record-level CRC check\nprevents corrupted data from reaching it unless intentionally\ncrafted. The replay code also assumes that the GID is within the allowed\nbounds, as WAL records are trusted.\n- Similarly, ParsePrepareRecord() stores its GID in a buffer bounded by\nGIDSIZE while trusting the length provided by the record.\n\nAs a result, these changes are purely cosmetic. They adopt a more\ndefensive coding style and should also silence some of the static\nanalysis reports received recently.\n\nAuthor: Matt Suiche \nDiscussion: https://postgr.es/m/CAGf6Lfx2kbQfcEnCi99V2i65JSWD6ij_E29F+UkY=TyMUyeG6A@mail.gmail.com", "completion": "Use more strlcpy() in two-phase transaction code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`@HostListener` is not limited to methods — it is equally valid on a property\nholding a function, which is the idiomatic way to keep `this` bound:\n\n @HostListener('window:beforeunload', ['$event'])\n private onUnload = (event: BeforeUnloadEvent) => {...};\n\nEvery existing host-listener compliance case declares the handler as a method,\nso the property form was uncovered. This adds a case exercising both a public\nand a private function-valued property, one of them with a global (`window:`)\nevent target, and locks in the emitted chained `ɵɵlistener` calls plus\n`ɵɵresolveWindow`.\n\nVerified against all four compliance modes (full, partial/linked,\ndeclaration-only); GOLDEN_PARTIAL.js regenerated via the golden update rule.\n\n(cherry picked from commit d44b3224d960e6a0e3bdd72fa93761e78d47fff0)", "completion": "test(compiler-cli): add compliance case for @HostListener on a property"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`@HostListener` is not limited to methods — it is equally valid on a property\nholding a function, which is the idiomatic way to keep `this` bound:\n\n @HostListener('window:beforeunload', ['$event'])\n private onUnload = (event: BeforeUnloadEvent) => {...};\n\nEvery existing host-listener compliance case declares the handler as a method,\nso the property form was uncovered. This adds a case exercising both a public\nand a private function-valued property, one of them with a global (`window:`)\nevent target, and locks in the emitted chained `ɵɵlistener` calls plus\n`ɵɵresolveWindow`.\n\nVerified against all four compliance modes (full, partial/linked,\ndeclaration-only); GOLDEN_PARTIAL.js regenerated via the golden update rule.", "completion": "test(compiler-cli): add compliance case for @HostListener on a property"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix: hide Select suffix when clear icon appears\n\n* fix: avoid hiding suffix content when clear icon appears\n\n* fix: align Select clear suffix behavior with DatePicker\n\n* fix: align Select suffix transition easing\n\n* fix: handle Select clear icon edge cases\n\n* test(Select): cover clear suffix hover interactions\n\n* test(Select): group image tests by viewport\n\n---------", "completion": "fix: handle Select clear icon overlap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhile collecting the sequences to synchronize, the sequence sync worker\nopened each INIT sequence with RowExclusiveLock and held it until the\ntransaction committed. With many such sequences, this could exhaust the\nshared lock table and fail with \"out of shared memory\".\n\nThe worker only reads each sequence's identity (namespace and name) here\nand needs it to stay stable while read, for which AccessShareLock is\nenough, as it conflicts with the AccessExclusiveLock taken by DROP,\nRENAME, and SET SCHEMA. Take that lock instead and release it as soon as\nthe identity is read. The later synchronization re-opens each sequence, so\nit does not rely on the lock being retained.\n\nReported-by: Noah Misch \nAuthor: vignesh C \nReviewed-by: Hayato Kuroda \nReviewed-by: Amit Kapila \nBackpatch-through: 19, where it was introduced\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Avoid accumulating relation locks during sequence synchronization."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nShared API, documented in remote.txt, is surface-level.\nAssume 0% compatiblity from Vim.", "completion": "build(vim-patch): clientserver feature is N/A"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency chalk to v6"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral adev example and tutorial files read a signal input as a bare\nreference (this.foo) instead of invoking it (this.foo()). Because an\nInputSignal is a function object, the bare reference is always truthy\nand never yields the underlying value, so the surrounding guard or\nbinding silently did the wrong thing:\n\n- animations open-close(.1/.3): the `!this.logging` guard in\n onAnimationEvent was always false, so the early return never fired.\n- form-validation forbidden-name.directive: the `this.forbiddenName`\n ternary condition was always truthy, so validation ran even when no\n forbidden name was configured.\n- first-app steps 12 and 14 housing-location: `housingLocation.photo`\n read `.photo` off the signal function (undefined), leaving the\n listing image src empty.\n\nInvoke the signals so the examples reflect correct signal-input usage.\n\n(cherry picked from commit 0d26130a4ce34daf9fb62bb19984f263492a219f)", "completion": "docs: invoke signal inputs in adev examples and tutorials"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSeveral adev example and tutorial files read a signal input as a bare\nreference (this.foo) instead of invoking it (this.foo()). Because an\nInputSignal is a function object, the bare reference is always truthy\nand never yields the underlying value, so the surrounding guard or\nbinding silently did the wrong thing:\n\n- animations open-close(.1/.3): the `!this.logging` guard in\n onAnimationEvent was always false, so the early return never fired.\n- form-validation forbidden-name.directive: the `this.forbiddenName`\n ternary condition was always truthy, so validation ran even when no\n forbidden name was configured.\n- first-app steps 12 and 14 housing-location: `housingLocation.photo`\n read `.photo` off the signal function (undefined), leaving the\n listing image src empty.\n\nInvoke the signals so the examples reflect correct signal-input usage.", "completion": "docs: invoke signal inputs in adev examples and tutorials"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nTerminateBackgroundWorkersForDatabase() uses BackendPidGetProc() and,\nuntil now, accessed fields of the returned PGPROC after releasing\nProcArrayLock, including its database OID. If the PGPROC slot is\nrecycled during this window, the database OID being checked may belong\nto a different backend, causing an unrelated background worker to be\nterminated.\n\nTriggering this bug requires a very narrow race: the background worker\nidentified by BackendPidGetProc() must exit, its PGPROC slot must be\nreleased and reused, and only then must\nTerminateBackgroundWorkersForDatabase() examine the database OID.\n\nTerminateBackgroundWorkersForDatabase() holds BackgroundWorkerLock,\npreventing parallel workers and dynamically registered workers (such as\nthose created by worker_spi) from reusing the slot. As far as I know,\nthe only plausible scenario is a static background worker that exits and\nis restarted quickly enough to reuse the same PGPROC slot within the\nrace window. In practice, this race is extremely unlikely, still\nreachable in theory.\n\nOversight in f1e251be80a0.\n\nAuthor: Chao Li \nReviewed-by: Aya Iwata \nReviewed-by: Haibo Yan \nDiscussion: https://postgr.es/m/78E81763-EA1D-4788-9741-4092BCB997A5@gmail.com\nBackpatch-through: 19", "completion": "Protect PGPROC lookup when terminating background workers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFor visual review when necessary. For the three major platforms for\nsymmetry and good measure.\n\nCloses #22427", "completion": "GHA/configure-vs-cmake: dump `./configure --help`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe getdatabaseencoding function was added in bf00bbb0c494 in 1998 but\nwas never documented. While mostly used in tests, there is no reason\nnot to document it as this function isn't going anywhere and is already\nused in extensions.\n\nAuthor: Ian Barwick \nReviewed-by: Thom Brown \nReviewed-by: surya poondla \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAB8KJ=ij+pznQGub=DkyJuKL=tC=Q=07qSahTyw7TLb0DdNJsg@mail.gmail.com", "completion": "doc: Add getdatabaseencoding to function docs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\ncompl_leader is a String, but it is cleared with XFREE_CLEAR().\n\nSolution:\nReplace XFREE_CLEAR() with API_CLEAR_STRING().", "completion": "fix(insexpand): use String cleanup for compl_leader"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen sending with sendmsg_x(), fix handling of last gso chunk being\nsmaller. Handle partial results correctly. Ignore SOCKEMSGSIZE by\nreporting success which drops PMTUD probes into the void.\n\nCloses #22429", "completion": "apple-fast-udp: fix sendmsg_x partial results"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 079a11bcba5858ffab2cf6e810e9d980\n\nCloses #22428", "completion": "EXPERIMENTAL: Apple fast UDP"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22428", "completion": "EXPERIMENTAL: cleanups, unify on titles, merge quiche into a single segment"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n1. Vim9 error messages, ex commands, are N/A.\n2. \":scriptversion\" is N/A:\n3. Most `#.*define.*ex_ni$` are N/A\n because `FEAT_` compile guards are N/A.\n\n----\n\nTarget patch: v8.2.2238\n\nActual patch list:\n\n```\nvim-patch:8.2.4240: error for using flatten() in Vim9 script is unclear\nvim-patch:9.0.0170: various minor code formatting issues\nvim-patch:9.1.0356: MS-Windows: --remote may change working directory\nvim-patch:9.2.0251: Link error when building without channel feature\nvim-patch:9.2.0714: Coverity warns for NULL deref\nvim-patch:9.2.0818: tests: client-server test fails without X11 server\nvim-patch:9.2.0868: GTK: Window Manager hint prevents giving focus to dialog\n```\n\n----\n\nIgnore diff blanklines via regex (\"-I\"), not \"--ignore-blank-lines\".\nAlmost useless.\nI tried with/without \"--word-diff=porcelain\", \"--word-diff-regex\",\nand diff algorithms like `--histogram`.", "completion": "build(vim-patch): ':vim9' is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds the `isFieldTree` utility that allows users to assert whether a value is a field tree. This is something that has come up on Material recently and will be useful for users as well.\n\nFixes #69984.\n\n(cherry picked from commit 2a141847a5ea2f24a98d5cc672df4e7abe67ec2d)", "completion": "fix(forms): add utility to assert that value is a field tree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds the `isFieldTree` utility that allows users to assert whether a value is a field tree. This is something that has come up on Material recently and will be useful for users as well.\n\nFixes #69984.", "completion": "fix(forms): add utility to assert that value is a field tree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWith some minor cleanups\n\nCloses #22430", "completion": "docs/INTERNALS.md -> docs/DEPENDENCIES.md"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument the AVX-512 and VAES optimizations for AES-CBC decryption,\nwhich improve decryption performance for large inputs (1024 bytes or\nmore) by 3.5x to 3.8x.\n\nReviewed-by: Simo Sorce \nReviewed-by: Andrew Dinh \nMergeDate: Fri Jul 31 16:33:42 2026\n(Merged from https://github.com/openssl/openssl/pull/30902)", "completion": "Add CHANGES.md entry for AES-CBC AVX-512/VAES decryption"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nImplement an AVX-512 VAES-based bulk path for AES-CBC decryption that\nprocesses multiple blocks in parallel, improving decryption performance\nfor large inputs (1024 bytes or more) by 3.5x to 3.8x.\n\n- Add the VAES CBC decrypt intrinsic implementation\n (crypto/aes/aes_cbc_vaes_intrinsic.c) and wire it into the AES-NI\n provider cipher path.\n- Centralize the VAES_CBC_ELIGIBLE eligibility guard in\n include/crypto/aes_platform.h to keep the header and implementation in\n sync, and drop the redundant AES_BLOCK_SIZE define.\n- Guard the intrinsics with refined gcc, clang, and msvc compiler-version\n checks, ensuring clean builds in no-asm, no-deprecated, and Windows\n (shared/minimal) configurations.\n- Add an EVP-level AES-CBC decrypt test exercising the VAES bulk path\n across AES-128/192/256 and a range of input lengths.\n\nReviewed-by: Simo Sorce \nReviewed-by: Andrew Dinh \nMergeDate: Fri Jul 31 16:33:35 2026\n(Merged from https://github.com/openssl/openssl/pull/30902)", "completion": "Add AVX-512/VAES optimized AES-CBC decryption"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15174", "completion": "fix(compiler-sfc): avoid walking cached type references"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nDynamic filetypes defined by `vim.filetype.add` may show health warnings.\n\nSolution:\nDocument a way to suppress these harmless warnings.", "completion": "docs(health): avoid warnings for dynamic filetypes #41036"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nLatent bug from 7f6c14ed54a46e822b80134d39a89f97523a2706 (2015).\nIf an option default is \"false\" (`o.defaults.if_false = false`, e.g.\n'fileignorecase'), codegen does not give it a `.def_val` on the platform\nwhere its `#if` condition is undefined; it is zero-initialized.\n\nThis wasn't noticed until the parent commit, where zero value is\nkObjectTypeNil, which `set_option_varp()` rejects.\n\nSolution:\nCheck `if_false == nil` insteada of \"falsey\", so the `#else` branch gets\ngenerated.", "completion": "fix(options): latent codegen bug"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a fuzz target for parsing X509v3 configuration\nwith both empty and non-empty context.\n\nInspired by : https://github.com/google/boringssl/commit/33b569282ca124c81d9ba74df696a013cb9a80ae#diff-69cdea0423abe6dd8db9db93ce916f9576bf86988b2728ffa1a2178d5d94734b\n\nAssisted-by: ChatGPT:gpt-5.6\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:50:44 2026\nMerged-from: https://github.com/openssl/openssl/pull/32143", "completion": "Add X509V3_EXT_add_nconf fuzzer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22431", "completion": "sws: log the exact closing reason better, to help debugging tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReported by Copilot\nBug: https://github.com/curl/curl/pull/21637#pullrequestreview-4809702512\nFollow-up to 112a8b5adf36c17e7816a8db701b3e7a22958e52 #21637\nFollow-up to 7c34365ccea19949317878c7fcd5f7376e2e09f1 #21879\n\nCloses #22432", "completion": "urlapi: clear password buffer on error path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA cascading standby could fail to reconnect to its upstream standby with\n\"requested starting point ... is ahead of the WAL flush position\" after\nfalling back to archive recovery. This happened because archive\nrecovery processes whole segment files, so after replaying a segment the\ncascade's next read position lands at the start of the following\nsegment, which is ahead of the upstream's flush position reported by\nGetStandbyFlushRecPtr() (still inside the just-replayed segment).\n\nFix by having the walreceiver check the upstream's current WAL flush\nposition via IDENTIFY_SYSTEM before issuing START_REPLICATION.\nIDENTIFY_SYSTEM already returns this position (as xlogpos), but\nwalrcv_identify_system() previously discarded it; now we have a use for\nit. If the requested start point exceeds the upstream's flush position\non the same timeline, the walreceiver waits for\nwal_retrieve_retry_interval and retries.\n\nThe wait is limited to gaps of at most one WAL segment, which is the\nexpected case from the segment-granularity of archive recovery. Larger\ngaps indicate the upstream is genuinely behind, so START_REPLICATION is\nallowed to proceed (and fail) normally, letting the startup process fall\nback to other WAL sources. The first wait is logged at LOG level;\nsubsequent waits are demoted to DEBUG1 to avoid log noise. The\nwalreceiver honors wal_receiver_timeout during the wait, so it will exit\nif the upstream doesn't catch up in time.\n\nTo preserve ABI compatibility on back branches, the flush position from\nIDENTIFY_SYSTEM is communicated via a new global variable\n(WalRcvIdentifySystemLsn) rather than changing the signature of\nwalrcv_identify_system().\n\nThe bug was introduced in Postgres 9.3 by commit abfd192b1b5b, which\nadded a flush-position check in StartReplication() that rejects requests\nahead of the upstream server's WAL flush position.\n\nAuthor: Marco Nenciarini \nReviewed-by: Xuneng Zhou \nBackpatch-through: 14\nDiscuss", "completion": "Fix cascading standby reconnect failure after archive fallback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nTwo of the permutations in backwards-scan-concurrent-splits rely on\ntheir VACUUM step deleting the leaf pages that the waiting backwards\nscan will have to recover from. VACUUM can only do that when it's able\nto remove the index tuples whose heap tuples the concurrent session just\ndeleted. An autovacuum worker holding a snapshot holds back the\nremovable cutoff, which leaves the pages non-empty, and so undeleted,\ncausing the test to fail spuriously.\n\nTo fix, wait for the removable cutoff to advance past the deletions\nbefore the scan acquires its snapshot. This is much like commit\n1c64d2fc, which dealt with the same hazard in nbtree_half_dead_pages by\nadding the wait_prunable() helper that we reuse here.\n\nOversight in commit e395fbd3.\n\nAuthor: Peter Geoghegan \nReported-by: Alexander Lakhin \nDiscussion: https://postgr.es/m/b61d9944-d7a3-45f3-b69a-f18c8bfbbbd0@gmail.com", "completion": "Fix autovacuum-induced flakiness in backwards scan test."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 840f071566a0c5e44048051135da329e4e3ecaef)", "completion": "docs: Adds HTTP communication guidance to Angular Skills"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRename Timing API to Performance Track to better reflect the purpose of the actual feature;\nMigrate the settings data object to match the new name and drop some redundant keys.", "completion": "refactor(devtools): rename timing API to performance track"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nInclude the XSRF interceptor in the root token factory so the automatically provided HttpClient retains the documented default protection without requiring provideHttpClient().\n\n(cherry picked from commit de240a5d0eecdc0c895f581bf3f190f48ad68c18)", "completion": "fix(http): enable xsrf for root-provided HttpClient"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nInclude the XSRF interceptor in the root token factory so the automatically provided HttpClient retains the documented default protection without requiring provideHttpClient().", "completion": "fix(http): enable xsrf for root-provided HttpClient"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCURLOPT_RESOLVE and CURLOPT_CONNECT_TO were set twice.\nA happy little accident?\n\nCloses #22433", "completion": "tool: remove duplicate setopts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCmdline area shows stale \":\" after backspacing out of the command line.\n\nSolution:\nClear the command line for empty commands. Note that `:` will now\nclear the command line too.", "completion": "fix(ui2): clear empty cmdline after backspace #41043"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe comment claimed that a parallel vacuum worker has only the\nPROC_IN_VACUUM flag because parallel vacuum is not supported for\nautovacuum, but commit 1ff3180ca01 allowed autovacuum to use parallel\nvacuum workers.\n\nThe assertion itself still holds: the leader, whether a backend\nrunning VACUUM or an autovacuum worker, sets PROC_IN_VACUUM before\ntaking its snapshot, and a parallel worker inherits the flag when\nimporting the leader's snapshot. The leader's other flags don't reach\nthe worker, since the snapshot import copies only the PROC_XMIN_FLAGS\nbits and PROC_IS_AUTOVACUUM is never set on parallel workers, which\nrun as regular background workers. Reword the comment to explain that.\n\nOversight in commit 1ff3180ca01.\n\nAuthor: Bharath Rupireddy \nReviewed-by: Masahiko Sawada \nReviewed-by: Chao Li \nDiscussion: https://postgr.es/m/CALj2ACVwQ4WABqq8Lnf+VZEJ45jcTFhyFLFr_ctfS4=QLL-r5w@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix stale comment in parallel_vacuum_main()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe bundled `zip` plugin is implemented in Vimscript, making it harder to\nmaintain and build on with Nvim's Lua runtime infrastructure.\n\nSolution:\nAdd an opt-out `zip.lua` browser backed by `nvim.dir`, and disable the legacy\nVimscript implementation by moving it to `pack/dist/opt/zip/`. Load it with\n`:packadd zip`.", "completion": "refactor(zip)!: builtin zip.lua plugin #40846"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCannot assign Lua functions/closures to \"func\" ('completefunc',\n'tagfun', …) or \"expr\" ('foldexpr', 'indentexpr', …) options.\n\nSolution:\n- Store \"func\"/\"expr\" options as `Callback` instead of string.\n- Delete oceans of copy-pasted code.\n- BREAKING: LuaRef returned via RPC/Vimscript is now represented as\n `\"\"` (like what `:map` shows) instead of `nil`.\n- Note: `man.vim` still uses `v:lua` string, bc it's a vimscript ftplugin.", "completion": "feat(options): lua closure/function options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCmdline area shows stale \":\" after backspacing out of the command line.\n\nSolution:\nClear the command line for empty commands. Note that `:` will now\nclear the command line too.\n\n(cherry picked from commit 1dbc766fa71edee8d040815c5621b94c8ecdf68f)", "completion": "backport: fix(ui2): clear empty cmdline after backspace"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nRestructuring the tags makes the output consistent and doesn't require\nadded spaces.\n\nReported-by: Peter Smith\n\nAuthor: Peter Smith\n\nDiscussion: https://postgr.es/m/CAHut+Pu8JahGm76CMdpzH350pHJedA4R2b8JmOim3+m3yxft3Q@mail.gmail.com\n\nBackpatch-through: 19", "completion": "doc: remove added space within synopsis replaceable tags"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIf the TLS init hook is defined in conjunction with ssl_sni we\nissue a warning to help the user re-configure the cluster. To\navoid drowning the log in warnings, we log only once instead of\nonce per host. This removes the static variable tracking the\nwarning to aid future multithreading efforts.\n\nAuthor: Daniel Gustafsson \nReviewed-by: Tristan Partin \nReviewed-by: Andreas Karlsson \nReviewed-by: Yilin Zhang \nDiscussion: https://postgr.es/m/68B9881D-DAA8-467D-A251-C96E98E57BA0@yesql.se", "completion": "ssl: Remove static var tracking tls_init_hook warnings"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe SSLv23_method() function has been an alias for TLS_method since\n2015 (OpenSSL commit 32ec41539b5b) so we should use the appropriate\nname to avoid confusion.\n\nAuthor: Daniel Gustafsson \nReviewed-by: Tristan Partin \nReviewed-by: Andreas Karlsson \nReviewed-by: Yilin Zhang \nDiscussion: https://postgr.es/m/68B9881D-DAA8-467D-A251-C96E98E57BA0@yesql.se", "completion": "ssl: Use TLS_method instead of deprecated SSLv23_method"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nX509_NAME_get_text_by_NID was deprecated in OpenSSL 4.0.0, and could\nbe removed in a future version of OpenSSL. The replacement APIs are\navailable in all versions of OpenSSL and LibreSSL that we support so\nwe can easily change to make the code future proof.\n\nThe reason for the deprecation is that X509_NAME_get_text_by_NID can\nonly grab the first entry in a list, and doesn't handle multibyte\nstrings well. The fix is to get the index of the name entry with\nX509_NAME_get_index_by_NID and use X509_NAME_get_entry to extract\nthe data.\n\nAuthor: Daniel Gustafsson \nReviewed-by: Tristan Partin \nReviewed-by: Andreas Karlsson \nReviewed-by: Yilin Zhang \nDiscussion: https://postgr.es/m/68B9881D-DAA8-467D-A251-C96E98E57BA0@yesql.se", "completion": "ssl: Replace deprecated API to get commonName"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOur test for if the underlying TLS library supported a specific\nversion tested against the TLSX_Y_VERSION set of macros. These\nare however always defined, regardless of if the library was\nbuilt without support for the specific protocol version. Fix\nby using the feature test macros OPENSSL_NO_TLSX_Y which are\nintended for this usecase.\n\nThe previous coding held no risk of protocol downgrade against\nthe underlying library, a library not supporting the protocol\nversion selected would simply error out as the feature isn't\navailable. This can be easily verified using a modern version\nof LibreSSL, which in version 3.8 disabled TLS1 and 1.1 by\ndefault. Once we bump our minimum supported version of LibreSSL\nto 3.8+ we can add a test for this.\n\nAuthor: Daniel Gustafsson \nReviewed-by: Tristan Partin \nReviewed-by: Andreas Karlsson \nReviewed-by: Yilin Zhang \nDiscussion: https://postgr.es/m/68B9881D-DAA8-467D-A251-C96E98E57BA0@yesql.se", "completion": "ssl: Use the correct feature macros for TLS protocol support"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Input): correct OTP mask input type behavior\n\n* fix(Input): preserve OTP mask default type\n\n* test(Input): update OTP mask demo snapshot\n\n* test(Input): update OTP extended demo snapshot", "completion": "fix(Input): handle OTP mask input types consistently"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless scheduling throughout reactive forms tests instead of triggering change detection manually.\n\n(cherry picked from commit 6deb6afcd1af81357a146b51cdea109429af315a)", "completion": "refactor(forms): modernize reactive forms tests to rely on `whenStable`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless scheduling throughout reactive forms tests instead of triggering change detection manually.", "completion": "refactor(forms): modernize reactive forms tests to rely on `whenStable`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nrefint has been removed from the spi contrib module in v20. Add a note\nto the documentation of the still-supported back branches so that users\nare aware the module is going away.\n\nAuthor: Ayush Tiwari \nReported-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAJTYsWUHq8Ohc6-N-xamOPYz-q3qUYMtwQX-1=Zi=5N1Q_GSEQ@mail.gmail.com\nBackpatch-through: 14", "completion": "doc: Add a note that refint will be removed in v20"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nDetected by torture tests:\n```\ntest 5004...[HTTP RFC 9421 B.2.6: Ed25519 POST with headers (RFC test vector)]\n 105 functions found, but only fail 25 (23.81%)\n** MEMORY FAILURE\nLeak detected: memory still allocated: 99 bytes\nAt 6000022c9408, there is 36 bytes.\n allocated by /Users/runner/work/curl/curl/lib/slist.c:87\nAt 6000039c8e78, there is 31 bytes.\n allocated by /Users/runner/work/curl/curl/lib/slist.c:87\nAt 6000037dd688, there is 16 bytes.\n allocated by /Users/runner/work/curl/curl/lib/slist.c:62\nAt 6000037dd628, there is 16 bytes.\n allocated by /Users/runner/work/curl/curl/lib/slist.c:62\nLIMIT /Users/runner/work/curl/curl/lib/slist.c:62 malloc reached memlimit\n 5004: torture FAILED: function number 10 in test.\n```\nRef: https://github.com/curl/curl/actions/runs/30497660391/job/90730128599?pr=22437#step:16:2331\n\nAlso:\n- enable HTTPSIG in torture tests.\n- NULL check all `curl_slist_append()` results.\n- apply a NULL check to sibling test 5000 also.\n\nCo-authored-by: Daniel Stenberg\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\n\nCloses #22437", "completion": "lib5004: fix memleak on OOM, check all slist append results (httpsig)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen components pass arrays or readonly tuples to decorator metadata fields (such as ), typechecking generated decorator reflection metadata causes a TS2322 type mismatch error because previously only accepted mutable .\n\nThis change updates to accept , allowing arrays and readonly tuples to be assigned without TypeScript compilation errors.\n\n(cherry picked from commit eee9ef4d09c091e9066ed6074a19c0eee0e84da2)", "completion": "fix(core): allow readonly arrays in RawScopeInfoFromDecorator"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen components pass arrays or readonly tuples to decorator metadata fields (such as ), typechecking generated decorator reflection metadata causes a TS2322 type mismatch error because previously only accepted mutable .\n\nThis change updates to accept , allowing arrays and readonly tuples to be assigned without TypeScript compilation errors.", "completion": "fix(core): allow readonly arrays in RawScopeInfoFromDecorator"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen reflection metadata is emitted via setClassMetadata, passing readonly arrays or const tuples for the decorators parameter causes TypeScript type checking errors because setClassMetadata previously expected decorators to be a mutable any[] or null.\n\nThis change updates the setClassMetadata type signature to accept decorators as readonly any[] or null and casts the parameter internally when mutating the class metadata property.\n\n(cherry picked from commit dc65e3656ff56fc6c5c03cf59991a6e8760b5279)", "completion": "fix(core): accept readonly arrays for setClassMetadata decorators"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen reflection metadata is emitted via setClassMetadata, passing readonly arrays or const tuples for the decorators parameter causes TypeScript type checking errors because setClassMetadata previously expected decorators to be a mutable any[] or null.\n\nThis change updates the setClassMetadata type signature to accept decorators as readonly any[] or null and casts the parameter internally when mutating the class metadata property.", "completion": "fix(core): accept readonly arrays for setClassMetadata decorators"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo save work unnecessary in CI context, and to reduce log noise.\n\nCherry-picked from #22437\n\nCloses #22440", "completion": "GHA: set `HOMEBREW_NO_INSTALL_CLEANUP=1` where brew is used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWorking around:\n```\n==> Installing libngtcp2 dependency: ca-certificates\n==> Pouring ca-certificates--2026-07-16.all.bottle.1.tar.gz\nWarning: The post-install step did not complete successfully\n[...]\nError: Process completed with exit code 1.\n```\n\nRefs:\nhttps://github.com/Homebrew/homebrew-core/pull/295934\nhttps://github.com/Homebrew/brew/pull/23357\n\nBug: https://github.com/curl/curl/pull/22437#issuecomment-5124151490\n\nCloses #22438", "completion": "GHA: work around Homebrew `ca-certificates` install error"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nShow a warning and force-disable HTTPSIG when the TLS backend is not\nOpenSSL or wolfSSL. Before this patch this resulted in a mismatched\nfeature list in configure and `curl -V`.\n\nAlso enable HTTPSIG in more CI jobs to cover unsupported ones, Windows\ncompilers, clang-tidy, cmake.\n\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\nCherry-picked from #22437\n\nCloses #22439", "completion": "build: fix HTTPSIG option for unsupported TLS backends"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_rio_poll_builder_add_fd() documents duplicate registrations as\nequivalent to one registration with the logical OR of the requested\ndirections. The poll(2) backend instead cleared an existing entry,\nmaking duplicate registrations last-writer-wins. The select(2)\nbackend only adds bits to its fd_sets and already merges them.\n\nClear the mask only when populating a new or reusable slot so an\nexisting fd retains its previously requested events.\n\nFixes https://github.com/openssl/openssl/issues/32116\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Paul Yang \nReviewed-by: Jakub Zelenka \nMergeDate: Tue Aug 11 07:12:57 2026\n(Merged from https://github.com/openssl/openssl/pull/32117)\n\n(cherry picked from commit 363b604bffc131e2ccda48b89d2d3ebf5eb285ad)", "completion": "Merge event masks for duplicate fds in the RIO poll builder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_rio_poll_builder_add_fd() documents duplicate registrations as\nequivalent to one registration with the logical OR of the requested\ndirections. The poll(2) backend instead cleared an existing entry,\nmaking duplicate registrations last-writer-wins. The select(2)\nbackend only adds bits to its fd_sets and already merges them.\n\nClear the mask only when populating a new or reusable slot so an\nexisting fd retains its previously requested events.\n\nFixes https://github.com/openssl/openssl/issues/32116\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Paul Yang \nReviewed-by: Jakub Zelenka \nMergeDate: Tue Aug 11 07:12:57 2026\n(Merged from https://github.com/openssl/openssl/pull/32117)", "completion": "Merge event masks for duplicate fds in the RIO poll builder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a poll-backend unit test which registers the same fd first for\nreading and then for writing. Verify that the builder retains one\npollfd with both POLLIN and POLLOUT set.\n\nWithout the preceding fix, the test observes POLLOUT only. Wire the\ntest into the QUIC-gated test build and skip it on non-poll backends.\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Paul Yang \nReviewed-by: Jakub Zelenka \nMergeDate: Tue Aug 11 07:12:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32117)\n\n(cherry picked from commit 258f06b1ef57ce147ff2b1da5977d9e9adc55be7)", "completion": "test: cover duplicate fd event merging in RIO poll builder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd a poll-backend unit test which registers the same fd first for\nreading and then for writing. Verify that the builder retains one\npollfd with both POLLIN and POLLOUT set.\n\nWithout the preceding fix, the test observes POLLOUT only. Wire the\ntest into the QUIC-gated test build and skip it on non-poll backends.\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Paul Yang \nReviewed-by: Jakub Zelenka \nMergeDate: Tue Aug 11 07:12:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32117)", "completion": "test: cover duplicate fd event merging in RIO poll builder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommits ca326e903 and 1f8c504e3 widened the byte-count arguments of\nsmgr__md__read__done and smgr__md__write__done to \"long long int\".\nSystemTap's dtrace(1) fails on that specific spelling and falls back\nwith a warning (misreported near the previous probe). Use ssize_t\nand size_t instead, matching the md.c call sites.\n\nRevise probes.d's note about which types are usable as probe\narguments: recommend using system-supplied type names (macOS dtrace\nrejects names like PostgreSQL's uint64), and call out \"long long int\"\nas a known SystemTap failure case rather than a wider failure mode.\n\nAlso, update the monitoring.sgml entries for these probes,\nwhich were missed by the prior commits.\n\nReported-by: Laurenz Albe \nAuthor: Andrey Rachitskiy \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/697d3c88568442cd637d8453d129f1bb14bbd2a8.camel@cybertec.at", "completion": "Fix SystemTap dtrace warning about smgr probe argument types."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- preserve a shared baseline across overlapping async setup continuations\n- restore the baseline on each cleanup instead of restoring sibling state\n- add regression coverage for concurrent hydration and subsequent CSR mounts", "completion": "fix(runtime-vapor): restore concurrent async hydration context"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency jsdom to v30"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npg_dump in --binary-upgrade mode emits \"SUBSCRIPTION TABLE\" TOC entries to\npreserve pg_subscription_rel state across pg_upgrade. When such a dump\nwas restored with --no-subscriptions, _tocEntryRequired() skipped the\n\"SUBSCRIPTION\" entry but not the associated \"SUBSCRIPTION TABLE\" entries,\nso the restore would try to apply subscription-relation state for a\nsubscription that was never created.\n\nSkip \"SUBSCRIPTION TABLE\" entries as well when no_subscriptions is set.\n\nThis can happen when pg_subscription_rel has entries, the dump is taken\nwith --binary-upgrade, and it is restored with --no-subscriptions.\n\nReported-by: Hayato Kuroda \nAuthor: Hayato Kuroda \nReviewed-by: Shlok Kyal \nReviewed-by: Amit Kapila \nBackpatch-through: 17, where it was introduced\nDiscussion: https://postgr.es/m/OS9PR01MB121493DA4C1A7748B11A646D8F5C02@OS9PR01MB12149.jpnprd01.prod.outlook.com", "completion": "Skip SUBSCRIPTION TABLE TOC entries with --no-subscriptions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSo it concatenates into a properly type set message.\n\nSigned-off-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 10:35:53 2026\nMerged-from: https://github.com/openssl/openssl/pull/32119", "completion": "include/openssl/macros.h: add whitespace after semicolon in OSSL_DEPRECATED_FOR"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse lower case (as it is a continuation of a sentence after\na semicolon), no leading space (as it is added\nby OSSL_DEPRECATED_FOR()), and no terminating period (it is a message,\nalso, it mirrors OSSL_DEPRECATED() formatting). Also, shorten some\nmessages for brevity.\n\nSigned-off-by: Eugene Syromiatnikov \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 10:35:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32119", "completion": "include/openssl: harmonise formatting of OSSL_DEPRECATEDIN_._._FOR messages"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- queue structural anchors before updates triggered during async hydration\n- cover both async component and async setup hydration paths\n- add regression tests for beforeMount-triggered branch updates", "completion": "fix(runtime-vapor): schedule async hydration anchors before updates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nxterm doesn't reset to user configured default with the sequence `\\x1b[0 q`.\n\nSolution:\nRestore old behavior: if the reset cursor style terminfo entry is\nabsent, xterm's sequence should set the cursor to steady block, which is\nthe xterm default. In the near future, they may support another option\n(`\\x1b[7 q`) to reset to the user configured default.", "completion": "fix(tui): xterm default cursor style #41050"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Matt Caswell \nReviewed-by: Shane Lontis \nMergeDate: Fri Aug 7 13:35:40 2026\n(Merged from https://github.com/openssl/openssl/pull/32098)", "completion": "Commentary justifying non-constant-time memcmp"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNvim has sent CSI > 3 u since 4fb3b57a19, but tui.txt still documented\nCSI > 1 u.\n\n(cherry picked from commit c1a65ff353429a987630b926727616590a330539)", "completion": "docs(tui): kitty keyboard protocol flags #41056"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNvim has sent CSI > 3 u since 4fb3b57a19, but tui.txt still documented\nCSI > 1 u.", "completion": "docs(tui): kitty keyboard protocol flags #41056"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds `# main` version comments after SHA references for `angular/dev-infra` GitHub Actions across workflows so that Renovate tracks the main branch and proposes updates when digests change.\n\n(cherry picked from commit 32815d5472e10cfb4bab45308536baf092a0cdb7)", "completion": "ci: add branch tracking comments to dev-infra GitHub actions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds `# main` version comments after SHA references for `angular/dev-infra` GitHub Actions across workflows so that Renovate tracks the main branch and proposes updates when digests change.", "completion": "ci: add branch tracking comments to dev-infra GitHub actions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe new test for enabling data checksums with concurrent CREATE\nDATABASE calls use the same injection points as a previous test\nbut accidentally missed detaching the injection point first.\n\nFix by detaching the injection point in the PG_TEST_EXTRA SKIP\nblock to make it can be reused. Pointed out by buildfarm member\nporpoise which failed with:\n\n die: error running SQL: 'psql::1:\n\t ERROR: injection point \"datachecksumsworker-fake-temptable-wait\"\n\t\t already defined'\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Daniel Gustafsson \nReported-by: Buildfarm member porpoise\nReviewed-by: Jonathan Gonzalez V. \nDiscussion: https://postgr.es/m/28CF6FD9-E1C4-4C04-8270-E3305AC46171@yesql.se\nBackpatch-through: 19", "completion": "Make sure to detach injection points for re-attaching"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe button is not functional when there isn't a graph. No need to keep it.", "completion": "refactor(devtools): hide search button when there is not a signal graph"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vite\nChanges:\nSquash of the settle-harness branch rebased onto main after #23106:\na test-only plugin (watch-change acknowledgment, server-side reload\nledger split by decision kind, client instrumentation with loud-fail\ninstall checks), waitForBundledDevSettled, withPageReload, and a global\nafterEach settle guard. Zero production-source changes.", "completion": "test(bundled-dev): add deterministic settle harness for page reloads"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vite\nChanges:\nSince #23106 a reload-shaped edit produces exactly one navigation, sent\nonly after the rebuild completes. The helper now just registers the load\nlistener before the edit and waits for that navigation; the settle call\nand the watcher-acknowledgment pre-wait are gone with it.\n\nPlaywright findings behind this (verified against playwright-core 1.62.0\nand vitest 4.1.10, plus an empirical reload-hammer script):\n- selector reads (page.textContent, locator) retry internally through a\n navigation and never see \"Execution context was destroyed\"\n- expect.poll retries probes that throw, which covers evaluate-based\n helpers like getColor\n- the one unsafe pattern is polling an ElementHandle captured before the\n edit — the helper's doc comment now warns about it", "completion": "test(bundled-dev): reduce withPageReload to a load-event anchor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- add 'mqtt' as a category\n- add more protocol categories to several options\n- make --data worded better to also cover MQTT\n\nCloses #22447", "completion": "curl: help category cleanups"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRemoves unused/duplicate members in async/ares/doh structs.\n\nCloses #22446", "completion": "dnscache: use Curl_peer in resolve and dnscache operations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIndex builds update pg_class.reltuples for the table. In parallel GIN\nbuilds, workers track the number of processed rows, and report it to\nthe leader, who then updates the pg_class with a total. However,\ngin_parallel_build_main failed to initialize the bs_reltuples field,\nleaving it set to whatever happens to be on the stack (which may be\nbogus values like Infinity or NaN, or just impossibly high values).\n\nIf such values get reported to the leader and stored in pg_class, that\ncan have serious consequences. The pg_class.reltuples field is used to\ndecide when a table is due for autovacuum or autoanalyze, and if it\nhappens to be set to a bogus value, that may never happen. The field is\nalso used by the optimizer when calculating costs.\n\nFixed by initializing bs_reltuples together with the rest of the build\nstate. The bs_numtuples was initialized later, but it seems cleaner to\njust initialize all the fields at once.\n\nAfter a bogus value gets persisted in pg_class, affected systems are\nunlikely to self-heal. That would require an ANALYZE, but preventing\nthat is one of the consequences. We have considered forcing autoanalyze\nin these cases, but there's not a good way to reliably identify bogus\nvalues (except for a small minority like Infitiny/NaN).\n\nA manual ANALYZE on (possibly) affected tables is the only solution.\n\nBackpatch to 18, where parallel GIN builds were introduced.\n\nReported-by: Jan Nidzwetzki \nDiscussion: https://postgr.es/m/518BA772-8026-412A-AA8F-A7FE4C6B3717@planetscale.com\nBackpatch-through: 18", "completion": "Initialize bs_reltuples in parallel GIN builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor algorithms without NID (without registration via the engine), cms_enc attempts to fetch via OBJ_obj2txt.\n\npassing cipher instead of NULL in EVP_PKEY_CTX_ctrl in apps/cms.c\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nMergeDate: Sat Aug 1 03:02:06 2026\n(Merged from https://github.com/openssl/openssl/pull/31512)", "completion": "Fix encrypt decrypt fetch for cms from privoder side"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThis change effectively replaces an explicit compile-time #error with\na missing prototype error in environments not offering `select()`, and\nsaves curl-compatible systems from performing an explicit feature check.\n\nRefs:\nhttps://pubs.opengroup.org/onlinepubs/009695399/functions/pselect.html\nhttps://linux.die.net/man/2/select\n\nCloses #22448", "completion": "build: assume POSIX `select()` is available"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n- A public exponent <= 1\n- Ciphertext <= 1 or equal to n-1, where n is the public modulus.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMergeDate: Mon Aug 10 06:27:45 2026\n(Merged from https://github.com/openssl/openssl/pull/32124)\n\n(cherry picked from commit e5d2eaee133290cce1b01bc7cead839bd7e18b8e)\n(cherry picked from commit 69de45cd12e51d69a098b7c81c2bd7ee80f060b5)", "completion": "Reject clearly degenerate RSASVE parameters."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n- A public exponent <= 1\n- Ciphertext <= 1 or equal to n-1, where n is the public modulus.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMergeDate: Mon Aug 10 06:27:45 2026\n(Merged from https://github.com/openssl/openssl/pull/32124)\n\n(cherry picked from commit 69de45cd12e51d69a098b7c81c2bd7ee80f060b5)", "completion": "Reject clearly degenerate RSASVE parameters."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n- A public exponent <= 1\n- Ciphertext <= 1 or equal to n-1, where n is the public modulus.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMergeDate: Mon Aug 10 06:27:45 2026\n(Merged from https://github.com/openssl/openssl/pull/32124)\n\n(cherry picked from commit e5d2eaee133290cce1b01bc7cead839bd7e18b8e)", "completion": "Reject clearly degenerate RSASVE parameters."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n- A public exponent <= 1\n- Ciphertext <= 1 or equal to n-1, where n is the public modulus.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Bob Beck \nMergeDate: Mon Aug 10 06:27:45 2026\n(Merged from https://github.com/openssl/openssl/pull/32124)", "completion": "Reject clearly degenerate RSASVE parameters."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 14:00:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32249)\n\n(cherry picked from commit 28b27fe53b975e7a86310c9becffd738482b8ddb)", "completion": "Fix FIPS to require a derivation function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 14:00:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32249)", "completion": "Fix FIPS to require a derivation function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:38 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)\n\n(cherry picked from commit 3d8b51d27714921c74bdebc0b39e4b387c442a63)", "completion": "Fix FIPS to require a derivation function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:38 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)", "completion": "Fix FIPS to require a derivation function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMergeDate: Fri Aug 7 13:36:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32093)", "completion": "Update corpora submodule"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen restoring relation stats, pg_restore_relation_stats() rejected\ncalls with (reltuples < -1.0). But that is insufficient - Infinity and\nNaN values both pass that check, and get stored in pg_class verbatim.\nThis can have various undesirable consequences.\n\nFixed by rejecting non-finite reltuple values, in the same non-fatal way\nas for the existing checks (emit WARNING and skip the update). Adds a\nregression test to stats_import for these non-finite values, and to\ncheck the -1.0 special value is still accepted.\n\nBackpatch to 18, where pg_restore_relation_stats() was introduced.\n\nPatch by Jan Nidzwetzki, minor commit message tweaks by me.\n\nAuthor: Jan Nidzwetzki \nDiscussion: https://postgr.es/m/518BA772-8026-412A-AA8F-A7FE4C6B3717@planetscale.com\nBackpatch-through: 18", "completion": "Reject non-finite reltuples when restoring stats"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- \"obj\" refers to structured (non-scalar `Object`) option values.\n- \"optval\" generally refers to the internal scalar (legacy \":set\"-style)\n option value.", "completion": "refactor(options): naming #41046"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ncurrently those members are missing to be copied in SSL_dup(3ossl)\n - server_cert_type\n - client_cert_type\n - ct_validation_callback\n - retsc->ext.status_type (typically needed for OCSP)\n\nAll those missing members are usually set before handshake starts,\nso SSL_dup() needs to copy them so behavior of duplicated SSL\nobject is consistent with its original.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 14:26:25 2026\nMerged-from: https://github.com/openssl/openssl/pull/32122\n(cherry picked from commit 52ee7fdf278c2316f1ddd94526f8730e014dd58f)", "completion": "SSL_dup() should copy additional members"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ncurrently those members are missing to be copied in SSL_dup(3ossl)\n - server_cert_type\n - client_cert_type\n - ct_validation_callback\n - retsc->ext.status_type (typically needed for OCSP)\n\nAll those missing members are usually set before handshake starts,\nso SSL_dup() needs to copy them so behavior of duplicated SSL\nobject is consistent with its original.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 14:26:25 2026\nMerged-from: https://github.com/openssl/openssl/pull/32122", "completion": "SSL_dup() should copy additional members"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThey were caught by dev-infra which isn't the best scope for the imho\n\n(cherry picked from commit 613c51e324fd0b6a2c19aac940fb7608009f2b5b)", "completion": "ci: add local skills to the fw-general scope"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThey were caught by dev-infra which isn't the best scope for the imho", "completion": "ci: add local skills to the fw-general scope"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCompute host binding security contexts against concrete hosts, including host directives, inheritance, dynamic directives, and createComponent hostElement usage.", "completion": "fix(core): sanitize host bindings on concrete hosts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIntroduce a component that provides shared styling for Angie illustrations and predefined sizes for ease of use.", "completion": "refactor(devtools): create Angie component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless scheduling throughout reactive forms tests instead of triggering change detection manually.\n\n(cherry picked from commit d068fc1ea0314eaf81b5f02f170484018492e4e9)", "completion": "refactor(common): modernize pipes & non bindable tests to rely on `whenStable`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRely on zoneless scheduling throughout reactive forms tests instead of triggering change detection manually.", "completion": "refactor(common): modernize pipes & non bindable tests to rely on `whenStable`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22449", "completion": "h3-proxy: fix NULL deref when non-:status header arrives before :status"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22558", "completion": "tidy-up: comments and formatting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit a0f943d53da69c0ed756b12fb2e50fa833b6c796)", "completion": "docs: replace Firebase Studio references with Antigravity"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Customizing model inputs\" section linked \"standard input\" back to\nthe inputs guide itself, a dead-end self-link. Point the sentence at the\nrelevant in-page sections instead (#required-inputs and #input-aliases).\n\nAlso merge the two stacked intro TIP callouts into a single tip.\n\n(cherry picked from commit 5dd634d18d40f6085bbf93c2ad8ab19420adfd74)", "completion": "docs: fix self-referential link and merge intro tips in inputs guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Customizing model inputs\" section linked \"standard input\" back to\nthe inputs guide itself, a dead-end self-link. Point the sentence at the\nrelevant in-page sections instead (#required-inputs and #input-aliases).\n\nAlso merge the two stacked intro TIP callouts into a single tip.", "completion": "docs: fix self-referential link and merge intro tips in inputs guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit a37c79d7d4ce7fc5ad81396d2c968b72e06850e1)", "completion": "docs: remove duplicate aria-hidden attributes in aria examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nA tab `icon` from a third-party library renders as a bare `` inside\n`.ant-tabs-tab-icon`, which the `.anticon` reset never reaches. An `` has\nno baseline, so it is aligned by its bottom margin edge (CSS 2.1 §10.8.1) and\nrides above the label — by an amount that grows with icon size.\n\nCentre it with `vertical-align: middle` + `margin-block-end: 0.2em` (x-height\ncentre lifted onto the cap-height centre), which is size-independent. The\n`> svg` selector only matches a bare ``, never an `.anticon`.", "completion": "fix(Tabs): center bare `` icons at any size"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOn standbys, logical decoding can be deactivated while a logical slot\nis being created: either by replaying an\nXLOG_LOGICAL_DECODING_STATUS_CHANGE record, or by the end-of-recovery\ntransition upon promotion, which deactivates logical decoding if no\nvalid logical slot exists. Both could interleave with a check of the\nlogical decoding status performed before creating a new slot because\nthe slot invalidation executed as part of the deactivation cannot find\na slot being created.\n\nFor regular slot creation on standbys, EnsureLogicalDecodingEnabled()\nassumed that logical decoding must still be enabled during recovery\nsince the caller had already checked it, tripping an assertion failure\nif a concurrent deactivation interleaved.\n\nFor slot synchronization, the local slot could be created and\npersisted based on the remote slot information fetched before the\ndeactivation was replayed, leaving a valid slot whose restart_lsn\nprecedes the deactivation.\n\nFix both paths by re-checking the logical decoding status after the\nnew slot has been created: regular slot creation raises an error, and\nslot synchronization skips persisting the slot. If the deactivation\nhappens after the re-check instead, it is guaranteed to invalidate the\nnewly created slot.\n\nReviewed-by: Srinath Reddy Sadipiralla \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/CAD21AoDEB99VtNbQdDrNd=1gQupJNGMfW_5kdnxq03Q82EK3ag@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix races between deactivation of logical decoding and slot creation."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nNumerous callers have to manually check optval ownership (i.e. whether,\nand how, to release) via `is_callback_option`, `option_is_global_local`,\netc. This is fragile, hard to use correctly; and if we introduce another\noptval variant in the future, we'll have to redo all of these careful\nchecks and boilerplate again.\n\nSolution:\nProvide a unified system and use it everywhere:\n\n optval_free_owned\n optval_is_owned\n optval_own", "completion": "refactor(options): memory management"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSync fallback logic with other crypto algos to:\n\n- allow falling back to the next backend candidate when wolfSSL does not\n have ed25519 built in.\n\n- de-duplicate fallback code.\n\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\n\nCloses #22450", "completion": "curl_ed25519: tidy-up backend fallback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 6aba42c660c added quit() calls for two background psql sessions\nwhose slot creation is canceled by pg_cancel_backend(). Both sessions\nran with the default ON_ERROR_STOP=1 and ended their script with \\q,\nso psql exited as soon as the cancellation error arrived. quit() then\nwrote another \\q to the already-closed pipe, making the test die with\n\"ack Broken pipe\".\n\nRun both sessions with on_error_stop => 0 and drop the trailing \\q, so\nthat psql stays at the prompt after reporting the error and quit() can\nshut it down cleanly.\n\nDiscussion: https://postgr.es/m/CAD21AoCZY1fKYgfkvHGWGiXpatUKd23FSLnDCL4m9bWFjdXNZw@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix background psql session cleanup in 051_effective_wal_level.pl."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\n\nCloses #22451", "completion": "curl_ed25519: drop unused wolfSSL random generator"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis fixes some incorrect flattening of nested Result nodes during\ncreate_plan that was introduced by f2bae51df. That commit failed to\nmaintain the logic that checks for subplans and gating quals from the\nnested Result node before flattening, and that could result in the nested\ngating qual and subplan being lost, which could produce incorrect results.\n\nBug: #19579\nReported-by: Viktor Leis \nAuthor: Ayush Tiwari \nReviewed-by: David Rowley \nDiscussion: https://postgr.es/m/19579-e6296b6c9fc0591c@postgresql.org\nBackpatch-through: 19", "completion": "Fix incorrect Result node flattening logic"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- defer Vapor KeepAlive root-chain updates while async setup is pending, avoiding transient branch renders and matching VDOM behavior\n- preserve deferred updates across component-root wrappers, nested KeepAlive roots, and nested async roots in the same Suspense pending cycle\n- restore normal Vapor scheduler ordering and component update error handling when flushing deferred effects, with direct-owner hydration support", "completion": "fix(runtime-vapor): defer KeepAlive updates while async setup is pending"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe code paths patched in this commit fix some of remnants not addressed\nby 1b105f9472bd. We should have more holes in the tree that could\nbenefit from stronger type safety guarantees. These hypothetical holes\ncould be addressed later; this finishes the job in storage/file/ for the\nbackend code.\n\nAuthor: Tristan Partin \nReviewed-by: Daniel Gustafsson \nReviewed-by: Sami Imseih \nDiscussion: https://postgr.es/m/DKBAWPZ2QDOS.10Y3JDUNKFMXX@partin.io", "completion": "Use [re]palloc_array() in buffile.c and fd.c"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPartition pruning for RANGE-partitioned tables could mistakenly prune\nthe DEFAULT partition in some cases when it was not valid to do so,\nwhich could lead to rows missing from query results.\n\nThe only known cases where this could happen is when combining pruning\nsteps from an IS NOT NULL clause with other steps that matched to the\nDEFAULT partition. This could occur due to RANGE partitioned tables\nhaving two distinct internal representations for marking if the DEFAULT\npartition should be scanned. The IS NOT NULL steps would mark the\n\"scan_default\" boolean, but other steps created for different purposes\ncould mark a bound_offset Bitmapset, which would ultimately translate into\nalso scanning the default partition. This could all fail after multiple\nsteps were combined with a combine intersect operator, as that will\nintersect the bound_offset bits and only set scan_default if all pruning\nsteps have that flag set. When both input steps to the intersect operator\nhad different representations of whether to scan the DEFAULT partition,\nthe resulting intersect step result would contain neither representation.\n\nHere, we fix this by having the IS NOT NULL pruning result mark the\nbound_offsets so that it uses both representations to mark that the\nDEFAULT partition must be scanned.\n\nReported-by: Jacob Brazeal \nDiagnosed-by: Jacob Brazeal \nAuthor: David Rowley \nDiscussion: https://postgr.es/m/CA+COZaDXrfTaBjLE=Z79MTaH6Xun1V4PeKxLvCNv8mXS8wn0rw@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix issue with RANGE's DEFAULT partition pruning"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIn the long option error path, the code previously returned BADARG\nimmediately when optstring[0] == ':' for a missing required argument,\nwithout advancing \"optind\" or resetting \"place\". This error handling\nwas inconsistent with the short option path, where both updates are\nperformed before returning BADARG (and inconsistent with libc,\nadditionally..).\n\nThis affects platforms where our port version of getopt_long() is used,\na concept that should be limited to WIN32 these days. An argument could\nbe made in favor of a backpatch, but this could lead to a slight\ndifferent error handling, for a report that would only show up when\nusing incorrect option combinations.\n\nAuthor: Japin Li \nDiscussion: https://postgr.es/m/SY7PR01MB10921AF81F18A8BCFA06388BEB6C22@SY7PR01MB10921.ausprd01.prod.outlook.com", "completion": "Fix error handling in port's getopt_long() for missing argument"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ncheck_publications_origin_sequences() warns when a subscription with\norigin = NONE synchronizes sequence values that may have originated from\nanother subscription. The existing warning is phrased in terms of\ncopy_data and copying data, which is appropriate for table synchronization\nbut misleading for sequence synchronization.\n\nReword the warning, detail, and hint to describe sequence synchronization\nand the associated origin = NONE semantics more accurately.\n\nAlso fix a typo (\"rathen\" -> \"rather\") in a comment in sequencesync.c.\n\nReported-by: Noah Misch \nReported-by: Peter Smith \nAuthor: vignesh C \nReviewed-by: Amit Kapila \nBackpatch-through: 19, where it was introduced\nDiscussion: https://postgr.es/m/20260710045217.f0.noahmisch@microsoft.com", "completion": "Improve wording of sequence origin warning in logical replication."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency node to v22.23.2"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(Tree): support auto expand in scrollTo\n\n* refactor(Tree): simplify scrollTo demo\n\n* refactor(Tree): simplify scrollTo handling\n\n* refactor(Tree): simplify controlled scrollTo demo\n\n* test(Tree): skip scrollTo image demo\n\n* docs(Tree): show scrollTo target key\n\n* chore(deps): upgrade @rc-component/virtual-list to 1.5.1\n\n* fix(TreeSelect): use valid value in internal panel demo\n\n* Revert \"fix(TreeSelect): use valid value in internal panel demo\"\n\nThis reverts commit e9e989fb27229f327aa3e19e009e89c23b65519b.\n\n* test(TreeSelect): expect scrollTo retry warning", "completion": "feat(Tree): support auto expand in scrollTo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(Tree): add version to scrollTo demo\n\n* docs(Tree): add version to English scrollTo demo", "completion": "docs(Tree): add version to scrollTo demo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: There is no agreed way for plugins to provide extra information\n about themselves. Like required Neovim version, install/update/delete\n hooks, and dependencies.\n\nSolution: Introduce basic concept of plugin manifest file `pkg.json`\n based on https://packspec.org/.", "completion": "feat(pack): introduce plugin manifest support"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- sync KeepAlive state before interop deactivation\n- fully unmount max-pruned component types and VNodes", "completion": "fix(runtime-vapor): properly prune interop keep-alive entries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFor corps urls the promise is actually resolved but returns a `status:0`.\n\nfixes #70023", "completion": "fix(devtools): Extension name for non googlers."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSubstitute the remaining ``s with the Angie component.", "completion": "refactor(devtools): substitute remaining Angie images with ng-angie"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n'make update' doesn't quite agree with the ordering of error reasons\nfrom recent development / merge.\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Igor Ustinov \nMergeDate: Fri Jul 31 10:50:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32131)", "completion": "Error reason fixes - mostly a small reordering"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo test HTTPSIG with all supported OpenSSL forks.\n\nFollow-up to a55731050e8c3dbea0b96205cf916443118f6acb #22386 #21239\n\nCloses #22453", "completion": "GHA/http3-linux: enable HTTPSIG in jobs running tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nadf97c156 allowed expression evaluation to perform hashing, and\nsubsequently 9ca67658d fixed a memory stomping bug in that commit\nthat caused unrelated-to-hashing expression op steps to stomp on the\nintermediate hash value. The intermediate hash value needs to be\nmaintained when hashing multiple hash keys. 9ca67658d didn't quite get\nthings right when in \"strict\" mode when it aborted hashing early after\nencountering a NULL hash key. What was meant to happen was that the\nexpression returns NULL directly to indicate to the caller the value\nhashed to NULL. The problem was that any EEOP_HASHDATUM_FIRST_STRICT or\nEEOP_HASHDATUM_NEXT32_STRICT op step that didn't belong to the final\nkey to be hashed would have its op->resnull and op->resvalue pointing to\nthe location to store the intermediate hash value. That's correct for\nnon-NULLs since we bit-rotate the intermediate value and continue hashing,\nbut with the strict case, when we get a NULL key, we immediately jump to\nthe \"jumpdone\" step. The problem is the jumpdone step expects the\nExprState resnull and resvalue fields to be set (as they would be if we\ndidn't abort hashing early due to the NULL), but when we aborted early,\nthe ExprState fields never got set. This would result in inserting\nrecords into the hash table that would never match to any join partner,\nwhich is a waste of CPU and memory.\n\nHere we fix this by having EEOP_HASHDATUM_FIRST_STRICT and\nEEOP_HASHDATUM_NEXT32_STRICT populate the ExprState resnull and resvalue\nfields directly when the value to hash is NULL.\n\nAlthough Hash Agg and Hashed Subplans do use hashing from ExprStates,\nthose were unaffected by this bug, as neither of those uses the STRICT op\nsteps.\n\nThanks to Tomas Vondra for finding the offending commit.\n\nReported-by: Dan Stefura \nAuthor: David Rowley \nDiscussion: https://postgr.es/m/YQBPR0101MB89738FB972FBD02A3640C6D3D6C92@YQBPR0101MB8973.CANPRD01.PROD.OUTLOOK.COM\nBackpatch-through: 18", "completion": "Fix Hash Join performance issue when hashing NULL values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: No way for plugins to define hooks that would be executed\n during plugin lifecycle. Like after install/update or before\n update/delete.\n\nSolution: Automatically source scripts defined in plugin manifest file\n (if any) after triggering corresponding `PackChanged{,Pre}` events.\n During sourcing make some termporary adjustments:\n - Current directory is set to plugin's root to simplify execution of\n CLI calls like `make build`.\n - Plugin's path is ensured to be inside 'runtimepath' to allow using\n `require('plugin-module')` inside manifest scripts.\n\n The reason to execute after triggering event is so that there is a\n possibility for users to execute code both before the script (exactly\n on event) and after the script (more-or-less via `vim.schedule` called\n on the event).", "completion": "feat(pack): add support for sourcing manifest scripts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis isn't necessary anymore.\n\n(cherry picked from commit 1b13db7a1b6eb2451d28a66dde23a52fadf45ad6)", "completion": "refactor(animations): remove outdated comment"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis isn't necessary anymore.", "completion": "refactor(animations): remove outdated comment"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe `allowSignalWrites` option of `effect()` became a no-op and was\ndeprecated in v19, but the update guide never mentioned it. Applications\nupgrading from v18 or earlier still carry the option at their `effect()`\ncall sites, where it now only produces a dev-mode warning.\n\nAdd an entry to the v19 recommendations instructing those applications to\nremove it, mirroring the wording of the deprecation notice on\n`CreateEffectOptions`.\n\n(cherry picked from commit 690eecda6b3ec2a3f03410b5d0b244e9723d3fd5)", "completion": "docs: document deprecated allowSignalWrites option in v19 update guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe `allowSignalWrites` option of `effect()` became a no-op and was\ndeprecated in v19, but the update guide never mentioned it. Applications\nupgrading from v18 or earlier still carry the option at their `effect()`\ncall sites, where it now only produces a dev-mode warning.\n\nAdd an entry to the v19 recommendations instructing those applications to\nremove it, mirroring the wording of the deprecation notice on\n`CreateEffectOptions`.", "completion": "docs: document deprecated allowSignalWrites option in v19 update guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npoly1305-armv8 takes the address of poly1305_blocks_sve2 with a direct\nADRP/ADD sequence. Mark the SVE2 entry point hidden so ELF linkers bind\nit locally when building shared libraries.\n\nFixes #31670\n\nCLA: trivial\n\nReviewed-by: Milan Broz \nReviewed-by: Kurt Roeckx \nReviewed-by: Simo Sorce \nReviewed-by: Tom Cosgrove \nReviewed-by: Andrew Dinh \nMergeDate: Wed Aug 26 15:15:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32132)\n\n(cherry picked from commit 6bfa751d0e382a293a8572b7b05e4a65fb521ca6)", "completion": "Fix Poly1305 SVE2 symbol visibility"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npoly1305-armv8 takes the address of poly1305_blocks_sve2 with a direct\nADRP/ADD sequence. Mark the SVE2 entry point hidden so ELF linkers bind\nit locally when building shared libraries.\n\nFixes #31670\n\nCLA: trivial\n\nReviewed-by: Milan Broz \nReviewed-by: Kurt Roeckx \nReviewed-by: Simo Sorce \nReviewed-by: Tom Cosgrove \nReviewed-by: Andrew Dinh \nMergeDate: Wed Aug 26 15:15:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32132)", "completion": "Fix Poly1305 SVE2 symbol visibility"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWe recently removed support for upgrading from pre-v10 servers, so\nwe no longer need to handle older versions in this helper module.\n\nOversight in commit 14d8418083.\n\nDiscussion: https://postgr.es/m/ak7Ekv2-L-G55-YD%40nathan", "completion": "Remove code for pre-v10 servers from AdjustUpgrade.pm."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRepresent withRequestsMadeViaParent() with an internal delegating backend so the interceptor handler can distinguish delegated clients from independent child configurations.", "completion": "fix(http): run root interceptors in the terminal request chain"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRepresent withRequestsMadeViaParent() with an internal delegating backend so the interceptor handler can distinguish delegated clients from independent child configurations.\n\n(cherry picked from commit bb78286e5e729d1e1fcfd2733d88351a38083ef5)", "completion": "fix(http): run root interceptors in the terminal request chain"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen db_comparator() was updated to use pg_cmp_s32(), the arguments\nwere listed in the wrong order. This caused autovacuum to sort the\ndatabases by their scores in ascending order instead of descending\norder. To fix, swap the arguments to pg_cmp_s32().\n\nOversight in commit 3b42bdb471.\n\nReported-by: Хамидуллин Рустам \nAuthor: Хамидуллин Рустам \nDiscussion: https://postgr.es/m/5c5a7984-b149-b505-7ad9-2a7766c65b55%40postgrespro.ru\nBackpatch-through: 17", "completion": "Fix autovacuum's database sorting."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAs previously coded, walsummarizer only wants to read WAL from a file\nwhere the TimeLineID in the filename exactly matches the TimeLineID being\nsummarized. But in some cases, when a timeline switch occurs, the WAL file\nfrom the old timeline is not archived, because it's never completely\nfilled, so the only way to obtain the contents of that last partial\nsegment is to read from the first segment on the new timeline. Teach\nWAL summarizer to do that, and add a test case to make sure that it\nworks.\n\nReported-by: Nick Ivanov \nReviewed-by: Andrey Borodin \nTested-by: Amit Kapila \nReviewed-by: Srinath Reddy Sadipiralla \nReviewed-by: Zhijie Hou \nReviewed-by: Thom Brown \nDiscussion: http://postgr.es/m/CA+Tgmobr27GpKDZx3_ezW2+C5_g18i+jSK3sGF_cR-_ESv5N5A@mail.gmail.com\nBackpatch-through: 17", "completion": "Prevent walsummarizer from getting stuck at a timeline switch."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n(This is a late cherry-pick of 4e1e41733, now that the new suite has\nproven its stability, to ensure coverage for this code in PG18 as the\nlater branches diverge.)\n\nTo better record the internal behaviors of oauth-curl.c, add a unit test\nsuite for the socket and timer handling code. This is all based on TAP\nand driven by our existing Test::More infrastructure.\n\nThis commit is a replay of 1443b6c0e, which was reverted due to\nbuildfarm failures. Compared with that, this version protects the build\ntargets in the Makefile with a with_libcurl conditional, and it tweaks\nthe code style in 001_oauth.pl.\n\nReviewed-by: Dagfinn Ilmari Mannsåker \nReviewed-by: Andrew Dunstan \nDiscussion: https://postgr.es/m/CAOYmi+nDZxJHaWj9_jRSyf8uMToCADAmOfJEggsKW-kY7aUwHA@mail.gmail.com\nDiscussion: https://postgr.es/m/CAOYmi+m=xY0P_uAzAP_884uF-GhQ3wrineGwc9AEnb6fYxVqVQ@mail.gmail.com", "completion": "oauth: Add unit tests for multiplexer handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe slow_down interval parsing code checks explicitly for overflow, but\nsince it does that after the signed overflow has already occurred, we\nend up inviting undefined behavior from the compiler anyway.\n\nUse checked arithmetic instead. set_timer() takes a long int in order to\ninterface nicely with libcurl, so use an int32 as the interval counter\nand clamp to LONG_MAX during conversion to milliseconds.\n\nBackpatch to 18, where libpq-oauth was introduced.\n\nReported-by: Andres Freund \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/qtclihmrkq67ach3xjxyi4qcksstin5qxwsnkqefkmotxwh4g6%40ae2bj6jvcmry\nBackpatch-through: 18", "completion": "libpq-oauth: Avoid overflow for very large intervals"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCreateHardLinkA reports ERROR_INVALID_FUNCTION if the target file\nis on a filesystem that doesn't support hard links. _dosmaperr\nmaps that to EINVAL, which confuses zic.c into failure. zic.c is\nexpecting ENOTSUP if the filesystem lacks link support, and will\nproperly fall back to making a physical copy if it gets that.\nHence, add code to map ERROR_INVALID_FUNCTION to ENOTSUP.\n\n(We could instead teach _dosmaperr to do that, but it's far from clear\nthat this would be appropriate as a global behavior: intuitively\nit seems like EINVAL should be appropriate most of the time.)\n\nWe didn't need this before commit aeb07c55f, because the tzcode\nversion we were using before that didn't have this particular\nerror-handling logic. Hence, no back-patch for now; but if we\ndecide to back-patch tzcode 2026b or later, we'll need this too.\n\nAuthor: Vladlen Popolitov \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/e6122f9b2eef9096f1f11ecc058bcd91@postgrespro.ru", "completion": "On Windows, make link(2) report ENOTSUP when appropriate."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRecompute the checked state when a reused radio input receives a new value while the form model remains unchanged.\n\nHandle this case for both reactive forms and signal forms, and add regression tests covering reused radio elements.\n\n(cherry picked from commit 9e37a58e14bd7955d40255e42e20aa84fcde02f4)", "completion": "fix(forms): keep radio inputs in sync when values change"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRecompute the checked state when a reused radio input receives a new value while the form model remains unchanged.\n\nHandle this case for both reactive forms and signal forms, and add regression tests covering reused radio elements.", "completion": "fix(forms): keep radio inputs in sync when values change"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nReviewed-by: Michael Banck \nDiscussion: https://postgr.es/m/akWIxtcathhoUuCQ%40nathan\nBackpatch-through: 19 only", "completion": "Add list of major features to the v19 release notes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace synchronous detectChanges calls with zoneless-compatible scheduling and stability waits. Preserve NgComponentOutlet coverage for components declared by NgModules.\n\n(cherry picked from commit c9c4f2afc60f9d7d5c9f61c8b978691d9793d229)", "completion": "refactor(common): modernize directive tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace synchronous detectChanges calls with zoneless-compatible scheduling and stability waits. Preserve NgComponentOutlet coverage for components declared by NgModules.", "completion": "refactor(common): modernize directive tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSince 999dec9ec6a816680, pg_stat_io can show read time with zero reads\nfor an IO Context: a foreign IO is counted as a read only in the\ninitiating backend, while other waiters record only the wait time. That\nviolates pgstat_bktype_io_stats_valid(). Relax the check to allow time\nwithout a matching operation count, since we want to count read wait\ntime even in backends that did not initiate the read. This also enables\nfuture accounting of waits on IO resources (e.g., AIO handles) in\nbackends that didn't start the IO.\n\nAuthor: Andrey Rachitskiy \nReported-by: Justin Pryzby \nReviewed-by: Melanie Plageman \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/ak5lccE4qiQpOBHn@pryzbyj2023\nBackpatch-through: 19", "completion": "Allow IO time to be counted without a matching IO operation in pg_stat_io"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe necessary cryptography API is provided by nettle 3.1+, via its\n'hogweed' library. The minimum GnuTLS version required by curl is 3.6.5,\nwhich requires nettle 3.4.1+, so the API is always available.\n\nAlso:\n- autotools: detect and use nettle's hogweed library.\n- cmake/FindNettle: add support for the hogweed library.\n- GHA/http3-linux: enable in the autotools/cmake GnuTLS jobs.\n\nRef: https://github.com/gnutls/gnutls/commit/4353ea025ae032887f3e8cf5aadace25662c6b35\n\nCloses #22456", "completion": "curl_ed25519: add GnuTLS support (via nettle, hogweed)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Table): skip disabled rows across pages when selecting all data\n\n* test(Table): verify disabled row state across pages", "completion": "fix(Table): skip disabled rows across pages when selecting all data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* chore(ci): fix master ci/cd\n\n* chore: update", "completion": "chore(ci): fix master branch ci/cd"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nA Segmented item `icon` from a third-party library renders as a bare ``\ninside `.ant-segmented-item-icon`, which the `.anticon` reset never reaches.\nThe item label is a block with a tall line-height (not flex), so its inline\ncontent is baseline-aligned; an `` has no baseline, so it is aligned by\nits bottom margin edge (CSS 2.1 §10.8.1) and rides above the label — by an\namount that grows with icon size.\n\nCentre it with `vertical-align: middle` + `margin-block-end: 0.2em` (x-height\ncentre lifted onto the cap-height centre), which is size-independent. The\n`&-icon > svg` selector only matches a bare ``, never an `.anticon`, and\nleaves item height unchanged for 1em icons.", "completion": "fix(Segmented): center bare `` icons at any size"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix: apply disabled text color to AutoComplete input\n\n* test: assert AutoComplete disabled color on inner input node\n\n* test: add debug demo for AutoComplete disabled color in Form\n\n* test: add extend snapshot for AutoComplete disabled-in-form-debug demo\n\n---------", "completion": "fix: apply disabled text color to AutoComplete input"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRemoves unused code and exports that are no longer referenced anywhere\nin the compiler codebase.\n\n(cherry picked from commit 337053ef1ab6400c3641984511b45c341d306e87)", "completion": "refactor(compiler): remove unused code and exports"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRemoves unused code and exports that are no longer referenced anywhere\nin the compiler codebase.", "completion": "refactor(compiler): remove unused code and exports"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWindows searches the current directory before $PATH, so opening an archive\nin a directory that also contains an `unzip` executable runs that one. The\nlegacy plugin refused this; the port dropped the check.\n\nSolution:\nRefuse to run `unzip` when it resolves to the current directory.", "completion": "fix(zip): do not run unzip from the current directory"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`zipfile://{archive}::{entry}` is ambiguous: `::` is legal in both an\narchive path and an entry path, so the separator cannot be identified.\nSplitting at the last `::` reads archives correctly but breaks entries\nthat contain it, and the plugin then emits buffer names it cannot read\nback.\n\nSolution:\nAddress entries as `zip://{archive}/{entry}`, joining the two paths.\nResolve the split by walking components: the first one that is a regular\nfile is the archive, because a regular file cannot have children on disk.\nEntry paths may then contain any character, and no escaping is needed.\n\nzipPlugin.vim keeps its own scheme, so the Java ftplugin emits whichever\nform matches the active plugin until the legacy package is removed.", "completion": "refactor(zip)!: address entries with zip:// paths"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNote in EVP_CIPHER-SM4(7) that SM4 implementations may use\nsecret-dependent table lookups and are not guaranteed to be\nconstant-time. Mention the portable C path as a concrete example\nand point to CPU capability man pages for code-path selection.\n\nFixes: https://github.com/openssl/openssl/issues/31911\n\nAssisted-by: Cursor:composer\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Tue Aug 11 07:03:10 2026\n(Merged from https://github.com/openssl/openssl/pull/32136)", "completion": "Document SM4 table-lookup side-channel risk"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNote in EVP_CIPHER-SM4(7) that SM4 implementations may use\nsecret-dependent table lookups and are not guaranteed to be\nconstant-time. Mention the portable C path as a concrete example\nand point to CPU capability man pages for code-path selection.\n\nFixes: https://github.com/openssl/openssl/issues/31911\n\nAssisted-by: Cursor:composer\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Tue Aug 11 07:03:00 2026\n(Merged from https://github.com/openssl/openssl/pull/32136)", "completion": "Document SM4 table-lookup side-channel risk"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNote in EVP_CIPHER-SM4(7) that SM4 implementations may use\nsecret-dependent table lookups and are not guaranteed to be\nconstant-time. Mention the portable C path as a concrete example\nand point to CPU capability man pages for code-path selection.\n\nFixes: https://github.com/openssl/openssl/issues/31911\n\nAssisted-by: Cursor:composer\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Tue Aug 11 07:02:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32136)", "completion": "Document SM4 table-lookup side-channel risk"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNote in EVP_CIPHER-SM4(7) that SM4 implementations may use\nsecret-dependent table lookups and are not guaranteed to be\nconstant-time. Mention the portable C path as a concrete example\nand point to CPU capability man pages for code-path selection.\n\nFixes: https://github.com/openssl/openssl/issues/31911\n\nAssisted-by: Cursor:composer\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Tue Aug 11 07:02:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32136)", "completion": "Document SM4 table-lookup side-channel risk"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNote in EVP_CIPHER-SM4(7) that SM4 implementations may use\nsecret-dependent table lookups and are not guaranteed to be\nconstant-time. Mention the portable C path as a concrete example\nand point to CPU capability man pages for code-path selection.\n\nFixes: https://github.com/openssl/openssl/issues/31911\n\nAssisted-by: Cursor:composer\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Paul Yang \nMergeDate: Tue Aug 11 07:02:12 2026\n(Merged from https://github.com/openssl/openssl/pull/32136)", "completion": "Document SM4 table-lookup side-channel risk"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThree code paths checking the size, timeline ID and system identifier\nstored in a manifest now check for an empty value. Values are always\nexpected in these parts of a backup banifest. A couple of tests are\nadded to validate this behavior\n\nAdditionally, precheck_tar_backup_file() checked that \"endptr\" is NULL.\nBased on the C standard, strtoul() never sets an \"endptr\" to NULL when\ngiven a value (that is the case here), returning a pointer to the\noriginal value if there is nothing to convert. The pre-tar validation\ncode is adjusted to do so.\n\nAuthor: Tristan Partin \nDiscussion: https://postgr.es/m/DKBS2Z9CGARC.2T07O6TJYSE8B@partin.io", "completion": "pg_verifybackup: Improve some error handling around strtoul() calls"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: the ruler is not cleared in the following circumstances:\n- ui1 is running\n- 'rulerformat' is configured\n- the default ruler was not previously visible in the last line, for\n example because 'rulerformat' is configured in init.lua\n- 'ruler' is disabled without using the command-line, for example via\n key-binding (entering the command-line would clear the ruler)\n\nThe corresponding test case did not fail because 'rulerformat' was set\nwhile the default ruler was shown.\n\nSolution: use a dedicated variable for tracking whether the ui1 ruler\nwas previously shown in the last line. `did_ruler_col` is now only used\nfor setting `msg_col`, which is not implemented in the case where\n'rulerformat' is configured.\n\nReorder the test code to make the individual checks more independent\nfrom each other, and to reflect the future where 'rulerformat' will\nnever be empty. Note that the check where 'rulerformat' was configured\nrelied on the default ruler not being cleared and a stale \"0,\" still\nbeing shown in front of the new ruler - this is also fixed with ui2.", "completion": "fix(ruler): always clear ruler when disabled"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwo link issues on the roadmap page:\n\n- \"Introduce deferred loading\" linked next.angular.dev, the preview build of\n this same site, for a page that exists here at guide/templates/defer. Use the\n relative path so readers stay on the stable docs.\n- \"Local template variables\" linked \"`@let` docs\", putting a code chip and a\n plain word in one anchor. The anchor's underline crosses the chip and the two\n halves render in different colors. Link only the symbol, as the rest of adev\n does.\n\nAlso on the same page:\n\n- Drop a stray space before a period in the Components card.\n- Give the older completion labels the same \"Completed in \" wording the\n newer cards already use.\n\n(cherry picked from commit f2f12925bdea3a83fb49a4b6398b54ff63456202)", "completion": "docs: fix roadmap link text and preview-site link"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTwo link issues on the roadmap page:\n\n- \"Introduce deferred loading\" linked next.angular.dev, the preview build of\n this same site, for a page that exists here at guide/templates/defer. Use the\n relative path so readers stay on the stable docs.\n- \"Local template variables\" linked \"`@let` docs\", putting a code chip and a\n plain word in one anchor. The anchor's underline crosses the chip and the two\n halves render in different colors. Link only the symbol, as the rest of adev\n does.\n\nAlso on the same page:\n\n- Drop a stray space before a period in the Components card.\n- Give the older completion labels the same \"Completed in \" wording the\n newer cards already use.", "completion": "docs: fix roadmap link text and preview-site link"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIt comes as a transitive requirement by the minimum GnuTLS version.\nBecause libcurl uses nettle directly (in GnuTLS builds), I figure it is\nuseful to document explicitly.\n\nRefs:\nhttps://github.com/gnutls/gnutls/commit/4353ea025ae032887f3e8cf5aadace25662c6b35\nhttps://github.com/curl/curl/pull/22456#discussion_r3695417678\nhttps://github.com/gnutls/nettle/releases/tag/nettle_3.4.1_release_20181204\n\nCloses #22457", "completion": "DEPENDENCIES.md: document minimum nettle version: 3.4.1 (2018-12-04)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nA timer wrapper such as a browser extension, policy, or automation harness can block a call and return null instead of a handle. patchTimer then read `.refresh` on that null value and threw synchronously.\n\nTreat a nullish handle as non-refreshable so the patched timer keeps working.\n\nFixes #70044", "completion": "fix(zone.js): guard against null handle when detecting refreshable timers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- Remove code that is never executed because the ruler is never rendered\n separately for a window with visible statusline or when `ls=3`, in\n other words: the variables `part_of_status` and `in_status_line` were\n always false for the ruler and badly named for the statusline itself.\n- Leave `maxwidth` unchanged after calling `stl_alloc_click_defs`.\n- Don't reuse the window's click definitions for the ruler. Even though\n it doesn't seem to be a bug because statusline and ruler are never\n shown at the same time for the same window, the ruler currently\n doesn't support clicks anyway.\n- Disentangle the different cases, in particular statusline- from ruler-\n specific code. Another example: `wp->w_wincol`, `wp->w_winrow`, and\n `wp->w_width` are always used together, but this was hard to see.", "completion": "refactor(statusline): simplify and remove dead code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\n#17382", "completion": "fix(deps): remove duplicate version @fastify/static"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nTarget v8.2.0543\nThis can catch stray '#define' but they're most likely 'TTFLAG' for\nVim9 types. N/A.\nTTFLAG is used in 'static_types[]'.\nSee v9.0.0623.", "completion": "build(vim-patch): n/a vim9 struct from *.h"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nAdds optional parameters to `vim.fs.abspath`:\n1. `cwd` to specify directory akin to `--relative-from` in `realpath(1)`.\n2. `plain` disables expansion of tilde (~) in paths.", "completion": "feat(vim.fs): abspath({cwd, plain}) #40597"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`:set foo=` and `:set foo?` for func/expr options set to a Lua\nfunction, always displays \"v:lua\".\n\nThe existing \"\" form was avoided because the ref id\nN changes on every read of the same option.\n\nSolution:\n- Don't attempt to tab-complete Lua functions.\n- Show \"\" (or \"\" if source file is unknown).\n\nExample:\n\n :set operatorfunc?\n operatorfunc=", "completion": "fix(options): \":set foo?\" for Lua callbacks #41100"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Traditionally, the ruler in the last line is one cell shorter\nthan in the statusline, leaving the last cell of the screen blank.\nAccording to code comments, this is in order to prevent unwanted\nscrolling on \"some\" (unspecified, but presumably ancient) terminals.\nBerkeley vi is more specific in its `vs_modeline` function: dumb\nterminals with hardware scroll, SunOS 4.1.1 and Ultrix 4.2 curses.\n(n)curses still has a similar limitation in `(w)addstr`, but apparently\nonly for historical reasons.\n\nMaintaining the different widths leads to awkward inconsistencies when\nthe ruler is configured with 'rulerformat', except for the special case\nwhere it contains a top-level `%=`. Shifting the ruler in the last line\nto the left would be a solution, but the empty cell at the end doesn't\nseem to be relevant anymore.\n\nSolution: extend the ruler in the last line all the way to the right\nedge of the screen, just like in the statusline. The exact same amount\nof place will be available to the rest of the UI as before.\n\nBREAKING CHANGE:\n- the default ruler width is now 18 cells\n- the last cell of the screen is no longer empty\n\nCloses #41076", "completion": "fix(ruler)!: consistent width in last line and statusline"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nThe test uses the position col=5,row=5; but such a position\nis outside of the buffer.\n\nPresume that it was meant to be col=5,row=4...", "completion": "test(lsp-selection): of by one"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nCID 652079: (UNINIT)\n /src/nvim/bufwrite.c: 1413 in buf_write()\n 1407 // only makes sense at the start of the file.\n 1408 if (buf->b_p_bomb && !write_bin && (!append || perm < 0)) {\n 1409 write_info.bw_len = make_bom(buffer, fenc);\n 1410 if (write_info.bw_len > 0) {\n 1411 // don't convert\n 1412 write_info.bw_flags = FIO_NOCONVERT | wb_flags;\n >>> CID 652079: (UNINIT)\n >>> Using uninitialized value \"write_info.bw_first\" when calling \"buf_write_bytes\".\n 1413 if (buf_write_bytes(&write_info) == FAIL) {\n 1414 end = 0;\n 1415 } else {\n 1416 nchars += write_info.bw_len;\n 1417 }\n 1418 }\n /src/nvim/bufwrite.c: 1453 in buf_write()\n 1447 *s = c;\n 1448 }\n 1449 s++;\n 1450 if (++write_info.bw_len != bufsize) {\n 1451 continue;\n 1452 }\n >>> CID 652079: (UNINIT)\n >>> Using uninitialized value \"write_info.bw_first\" when calling \"buf_write_bytes\".\n 1453 if (buf_write_bytes(&write_info) == FAIL) {\n 1454 end = 0; // write error: break loop\n 1455 break;\n 1456 }\n 1457 nchars += bufsize - write_info.bw_len;\n 1458 s = buffer + write_info.bw_len;", "completion": "fix(bufwrite): coverity \"uninitialized member\" #41104"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nMeant for Vim job, terminal, cscope, etc.\nIncompatible with Nvim implementation.", "completion": "build(vim-patch): \"build_argv_from_\" api is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe glossary entry for data checksums workers incorrectly stated that\nthey were auxiliary processes, but they are implemented as background\nworkers. Fix, and while there, simplify the entry by combining the\nworker and launcher into a single glossary term. Backpatch down to\nv19 where online checksums were introduced.\n\nAuthor: Daniel Gustafsson \nReported-by: Fujii Masao \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwEv-C9ia+rBYyePzO8F=5FVvS412ZqcOupazuOb5RafNg@mail.gmail.com\nBackpatch-through: 19", "completion": "doc: Fix glossary entry for data checksums workers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe data checksums entries were seemingly auxiliary processes from\nreading the code, but they are in fact background workers. Add a\ncomment to clarify. Backpatch down to v19 where online checksums\nwere introduced.\n\nAuthor: Daniel Gustafsson \nReported-by: Fujii Masao \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwFsBjQs2fv7b72hxzGV_fJMh6LAg4E83pNfDOu1jVgWCA@mail.gmail.com\nBackpatch-through: 19", "completion": "Add a comment to distinguish backend types"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThere is no health check. Encrypted entries cannot be read at all, since\nInfo-ZIP takes a password only from a terminal and `-P` would expose it\nin the process arguments.\n\nSolution:\nAdd `:checkhealth nvim.zip`, reporting the backend and which\nimplementation is handling archives. Prompt for the password on a pty,\nextracting to a file so the entry's bytes stay off the terminal. Report\nInfo-ZIP's exit code rather than inferring a cause, so an archive using\nAES is not reported as a failed decryption.", "completion": "feat(zip): checkhealth and encrypted entries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nInline code inside a link renders as a chip with its own background. Text\ndecoration propagates from the anchor and cannot be cancelled by a descendant,\nso with the chip laid out as a regular inline box the link underline is drawn\nstraight across it.\n\nLay the chip out as an atomic inline box, which the propagated decoration is not\ndrawn across. This applies to the link rule only; code outside of links keeps\n`display: inline` for wrapping in multiline paragraphs, and the link rule\nalready sets `white-space: nowrap`.\n\n(cherry picked from commit efe1aae1cd31a6c107ec95d7d79114137d93e54d)", "completion": "fix(docs-infra): keep inline code in links as an atomic inline box"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nInline code inside a link renders as a chip with its own background. Text\ndecoration propagates from the anchor and cannot be cancelled by a descendant,\nso with the chip laid out as a regular inline box the link underline is drawn\nstraight across it.\n\nLay the chip out as an atomic inline box, which the propagated decoration is not\ndrawn across. This applies to the link rule only; code outside of links keeps\n`display: inline` for wrapping in multiline paragraphs, and the link rule\nalready sets `white-space: nowrap`.", "completion": "fix(docs-infra): keep inline code in links as an atomic inline box"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:44:55 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:44:05 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn its integrity-failure paths that primitive writes and cleanses up to inlen\nbytes of the output buffer. Size the buffer for that worst case so a failed\nunwrap cannot write past the allocation.\n\nFixes CVE-2026-63072\n\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 14:42:05 2026", "completion": "Fix heap buffer overflow (8-byte OOB write) in AES-WRAP-PAD unwrap"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDescribe the domain-wide consequences of interrupting QUIC API\nprocessing while synchronisation is held or notification state is\nregistered.\n\nClarify that SSL_poll() can leave stale registrations in multiple\nnotifier-enabled domains, and provide cooperative cancellation and\napplication-driven event-loop guidance.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:32:14 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document QUIC thread cancellation consequences"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that OpenSSL provides no general guarantee that an\nin-progress call can be abandoned safely through thread cancellation,\nforced termination, or another non-local exit.\n\nExplain indirect cancellation points, the limits of thread-local\ncleanup, POSIX cancellation masking, and cooperative cancellation.\nClarify in OPENSSL_init_crypto(3) that automatic thread cleanup does\nnot unwind an interrupted call.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:32:13 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document thread cancellation and non-local exits"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDescribe the domain-wide consequences of interrupting QUIC API\nprocessing while synchronisation is held or notification state is\nregistered.\n\nClarify that SSL_poll() can leave stale registrations in multiple\nnotifier-enabled domains, and provide cooperative cancellation and\napplication-driven event-loop guidance.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:31:46 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document QUIC thread cancellation consequences"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that OpenSSL provides no general guarantee that an\nin-progress call can be abandoned safely through thread cancellation,\nforced termination, or another non-local exit.\n\nExplain indirect cancellation points, the limits of thread-local\ncleanup, POSIX cancellation masking, and cooperative cancellation.\nClarify in OPENSSL_init_crypto(3) that automatic thread cleanup does\nnot unwind an interrupted call.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:31:45 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document thread cancellation and non-local exits"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDescribe the domain-wide consequences of interrupting QUIC API\nprocessing while synchronisation is held or notification state is\nregistered.\n\nClarify that SSL_poll() can leave stale registrations in multiple\nnotifier-enabled domains, and provide cooperative cancellation and\napplication-driven event-loop guidance.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:31:04 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document QUIC thread cancellation consequences"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that OpenSSL provides no general guarantee that an\nin-progress call can be abandoned safely through thread cancellation,\nforced termination, or another non-local exit.\n\nExplain indirect cancellation points, the limits of thread-local\ncleanup, POSIX cancellation masking, and cooperative cancellation.\nClarify in OPENSSL_init_crypto(3) that automatic thread cleanup does\nnot unwind an interrupted call.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:31:03 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document thread cancellation and non-local exits"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDescribe the domain-wide consequences of interrupting QUIC API\nprocessing while synchronisation is held or notification state is\nregistered.\n\nClarify that SSL_poll() can leave stale registrations in multiple\nnotifier-enabled domains, and provide cooperative cancellation and\napplication-driven event-loop guidance.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:28:50 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document QUIC thread cancellation consequences"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDocument that OpenSSL provides no general guarantee that an\nin-progress call can be abandoned safely through thread cancellation,\nforced termination, or another non-local exit.\n\nExplain indirect cancellation points, the limits of thread-local\ncleanup, POSIX cancellation masking, and cooperative cancellation.\nClarify in OPENSSL_init_crypto(3) that automatic thread cleanup does\nnot unwind an interrupted call.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Wed Aug 19 10:28:49 2026\nMerged-from: https://github.com/openssl/openssl/pull/32139", "completion": "doc: document thread cancellation and non-local exits"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\n- forward fragment move types to VDOM interop roots\n- apply current transition hooks during enter and leave moves", "completion": "fix(runtime-vapor): preserve move semantics for VDOM roots"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRef: https://github.com/openssh/openssh-portable/commit/ee9c0da8035b3168e8e57c1dedc2d1b0daf00eec\n\nCloses #22460", "completion": "sshserver.pl: bump an sshd config to use its modern name"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nTest fails if other \"build*/\" dirs exist with a \"nvim\" file, e.g.\n`build-asan/bin/nvim`.\n\nSolution:\nDo the test in an isolated dir.\nThis also fixes the test for the zig build.", "completion": "test(fs): \"fs.find() follows symlinks\" #41105"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAlberta (America/Edmonton) moved to permanent UTC-06 on\n2026-06-18, which will affect their clocks beginning on 2026-11-01.\nFor lack of any clarity on the point, assume their TZ abbreviation\nwill be CST from that time forward.\n\nMorocco (Africa/Casablanca) will move to permanent UTC+00,\nwithout daylight saving time transitions, on 2026-09-20.\n\nBackpatch-through: 14", "completion": "Update time zone data files to tzdata release 2026c."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAllocate CompoundAffix with room for its terminator, initialize the\nold-format flag buffer before NIAddAffix(), and reject incomplete or\nmissing Hunspell AF aliases. None of these errors would be likely to\ntrigger on real dictionary files, accounting for the lack of previous\nreports; but they're certainly bugs.\n\nBug: #19595\nReported-by: Michael Malis \nAuthor: Andrey Rachitskiy \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/19595-7dc18b4e212c4757@postgresql.org\nBackpatch-through: 14", "completion": "Fix memory-safety bugs in the ispell/hunspell dictionary loader."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFreeBSD and OpenBSD are Tier 2 supported platforms (:help\nsupported-platforms) but have had no CI coverage since Cirrus CI was\ndropped in #39321. Restore build coverage for both using vmactions,\nwhich boots the VM on a regular ubuntu-latest runner.", "completion": "ci: check FreeBSD, OpenBSD builds #41091"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nSimilar to #36123, the ui2 windows confuse `:$q`, which doesn't close\nthe last window on the tab, but targets a hidden ui2 window.\n\nThe problem seems to be a combination of using\n`FOR_ALL_WINDOWS_IN_TAB()`, which includes hidden windows, and then\ncounting the windows without factoring in `win_has_winnr()`.\n\nThere are examples of using `win_has_winnr()`, such as:\n- [`eval/buffer.c`'s `buf_win_common()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/eval/buffer.c#L474-L475)\n- [`eval/window.c`'s `f_getwininfo()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/eval/window.c#L130-L135)\n- [`window.c`'s `win_get_tabwin()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/window.c#L7860-L7869)\n\nBut possibly problematic ones:\n- `ex_docmd.c`'s:\n\t- [`invalid_range()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/ex_docmd.c#L3891-L3893)\n\t\t- ^ should this include hidden windows? Can a user address them by number? `win_has_winnr()` suggests not\n\t- [`ex_close()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/ex_docmd.c#L5233-L5244)\n\t- [`ex_hide()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/ex_docmd.c#L5478-L5484)\n- `eval/window.c`'s:\n\t- [`f_winrestcmd()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/eval/window.c#L797-L808)\n\t- [`find_win_by_nr()`](https://github.com/neovim/neovim/blob/4a5062cda69fa6cb59b7dc0c488dfb05accf99de/src/nvim/eval/window.c#L172-L180)", "completion": "fix(ui2): `:$q` should not target hidden windows #40992"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCalling vim.treesitter.start() a second time on a buffer that already\nhas an active TSHighlighter creates a brand new instance instead of\nreusing it, whether the parser tree is unchanged (e.g. calling start()\ntwice) or different (e.g. switching languages). Either way the old\ninstance is silently discarded without calling :destroy() on it, so\nits on_bytes/on_changedtree/on_detach callbacks stay registered and\nits buffer-local state (spelloptions, decoration namespace) is never\nrestored, both leaking indefinitely for an orphaned instance that\nnothing references anymore.\n\nSolution:\nReturn the existing instance when TSHighlighter.active[source] is\nalready set for the same parser tree, instead of unconditionally\nconstructing a new one. When the tree differs instead (e.g. a language\nswitch), destroy() the old instance first, matching stop() semantics,\nbefore constructing the new one.\n\n(cherry picked from commit 67839a72f7eba1454a1a3755a55bca5e6562e461)", "completion": "fix(treesitter): make TSHighlighter.new() idempotent for an active buffer #41090"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nCalling vim.treesitter.start() a second time on a buffer that already\nhas an active TSHighlighter creates a brand new instance instead of\nreusing it, whether the parser tree is unchanged (e.g. calling start()\ntwice) or different (e.g. switching languages). Either way the old\ninstance is silently discarded without calling :destroy() on it, so\nits on_bytes/on_changedtree/on_detach callbacks stay registered and\nits buffer-local state (spelloptions, decoration namespace) is never\nrestored, both leaking indefinitely for an orphaned instance that\nnothing references anymore.\n\nSolution:\nReturn the existing instance when TSHighlighter.active[source] is\nalready set for the same parser tree, instead of unconditionally\nconstructing a new one. When the tree differs instead (e.g. a language\nswitch), destroy() the old instance first, matching stop() semantics,\nbefore constructing the new one.", "completion": "fix(treesitter): make TSHighlighter.new() idempotent for an active buffer #41090"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nA breadcrumb item `title` from a third-party icon library (lucide, react-icons,\nphosphor) renders as a bare `` inside `.ant-breadcrumb-link`, which the\n`.anticon` reset never reaches. An `` has no baseline of its own, so it is\naligned by its bottom margin edge (CSS 2.1 §10.8.1) and rides above the link\ntext — by an amount that grows with the icon's size, so a constant nudge like\n`.anticon`'s `-0.125em` cannot fix it. The existing icon-to-text spacing rule\nwas also `.anticon`-only, so a bare `` sat flush against the label.\n\nCenter and space it like an `.anticon`: `.ant-breadcrumb-link > svg { display:\ninline-block; vertical-align: middle; margin-block-end: 0.2em }`, and extend the\nicon+text spacing selector to `> svg + span` / `> svg + a`. `display: inline-block`\nkeeps the svg an atomic inline box so `vertical-align` still applies even under a\nCSS reset that forces `svg { display: block }` (e.g. Tailwind Preflight), which\nwould otherwise drop the icon onto its own line. `middle` centres the margin box\non the x-height line; `margin-block-end` lifts it half its own value onto the\ncap-height centre (capHeight − xHeight ≈ 0.2em), keeping it centred at any size.\nThe `> svg` child selector never matches an `.anticon` (its `` is one level\ndeeper), so existing icons stay byte-identical. Mirrors the Tag fix (#58723).", "completion": "fix(Breadcrumb): align and space bare `` icons"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nA panel title `label` from a third-party icon library (lucide, react-icons,\nphosphor) renders as a bare `` inside `.ant-collapse-title`, which the\n`.anticon` reset never reaches. An `` has no baseline of its own, so it is\naligned by its bottom margin edge (CSS 2.1 §10.8.1) and rides above the title\ntext — by an amount that grows with the icon's size, so a constant nudge like\n`.anticon`'s `-0.125em` cannot fix it.\n\nCenter it instead: `.ant-collapse-title > svg { display: inline-block; vertical-\nalign: middle; margin-block-end: 0.2em }`. `display: inline-block` keeps the svg\nan atomic inline box so `vertical-align` still applies even under a CSS reset\nthat forces `svg { display: block }` (e.g. Tailwind Preflight), which would\notherwise drop the icon onto its own line. `middle` centres the margin box on the\nx-height line; `margin-block-end` then lifts it half its own value onto the\ncap-height centre (capHeight − xHeight ≈ 0.2em), keeping it centred at any size.\nThe `> svg` child selector never matches an `.anticon` (its `` is one level\ndeeper), and the expand arrow lives in a separate `.ant-collapse-expand-icon`,\nso both stay byte-identical.", "completion": "fix(Collapse): center bare `` icons at any size"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nThe bare-`` icon-alignment fixes shipped for Tag (#58723), Tabs (#58847)\nand Segmented (#58862) rely on the icon being an inline-level box so that\n`vertical-align: middle` applies. Under a CSS reset that forces\n`svg { display: block }` — most notably Tailwind Preflight, and the ant.design\ndocs site's own reset — the bare `` becomes block-level, which *ignores*\n`vertical-align` entirely and breaks the icon onto its own line. The icon then\nrides a full line-height above the label (measured -18 to -24px), which is why\nthe released Tag/Tabs icon demos look broken on ant.design even though the fix\nworks in a reset-free app.\n\nAdd `display: inline-block` to each `> svg` rule so the icon stays an atomic\ninline box: `vertical-align` applies again and the icon no longer wraps. The\nrule's specificity (`.ant-x > svg`) beats a bare `svg { display: block }`, and\n`@ant-design/icons` icons are unaffected (an `.anticon` keeps its `` one\nlevel deeper, so `> svg` never matches it). No behavior change without a reset.", "completion": "fix: keep bare `` icons aligned under a `display: block` reset"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIn the not-too-likely scenario where we successfully created a hash\ntable entry for a TS dictionary, but then failed to make a small\nmemory context for it, we left the hash entry in existence but with\na garbage value for dictCtx. This confused the code the next time\nthrough, leading to a crash. Rearrange things so that we leave\nthe hash entry in a well-defined state with dictCtx == NULL, and\nthen the next try knows it still needs to make a memory context.\n\nReported-by: Alexander Lakhin \nAuthor: Tom Lane \nDiscussion: https://postgr.es/m/0f3ddeb5-0dbd-479c-9d0e-ae254758e624@gmail.com\nBackpatch-through: 14", "completion": "Tighten up TS dictionary cache entry creation."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIt is now \"Curl_easy\"\n\nFollow-up to 434f8d0389 (June 2016)\n\nCloses #22463", "completion": "lib: update mentions of the legacy \"sessionhandle\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- drop redundant casts for `CURL_UNCONST()` pointers (Windows).\n- GHA/linux: delete redundant/dupe `-g` C flag in memory sanitizer job.\n Spotted-by: Daniel Stenberg\n- examples/http2-upload: drop local macro.\n- examples/http2-upload: drop leading underscore from union name.\n- examples/http2-upload: drop interim macro.\n- tests/server/util: reapply patch lost in a rebase.\n- sync `main()` declarations across the codebase.\n\nCloses #22559", "completion": "tidy-up: C and CI"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(site): avoid Markdown route conflicts in Surge previews\n\n* update", "completion": "fix(site): avoid Markdown route conflicts in Surge previews"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCompile component v-text and v-html directives as textContent and innerHTML\nprops so reactive updates and attribute fallthrough follow the normal\ncomponent prop flow.\n\nPreserve values that VDOM considers constant, escape literal v-text content\nembedded in native element templates, and remove the obsolete setBlockText\nand setBlockHtml runtime helpers.", "completion": "fix(vapor): align component v-text and v-html with vdom"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBefore: The View Source button tooltip in signal details static ('View source') even when disabled.\n\nAfter: The tooltip explains 'Source location is not available for this node' when disabled.", "completion": "fix(devtools): clarify disabled View Source tooltip and update demo app"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(App): remove css variable warning for component={false}\n\n* update\n\n* update", "completion": "fix(App): warn about ignored root props"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nGenerate built-in v-model operations after initial DOM prop operations and\nreactive effects. This ensures dynamic input types are applied before\napplyDynamicModel selects the text, checkbox, or radio implementation.\n\nAdd codegen coverage for constant and reactive input types, along with runtime\nregressions for initially dynamic checkbox and radio inputs.", "completion": "fix(compiler-vapor): generate v-model after prop effects"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen checking whether a sub-select's output columns can produce NULL,\nso as to decide whether a NOT IN can be converted to an anti-join,\nquery_outputs_are_not_nullable() falls back on find_nonnullable_vars()\nfor targetlist entries that are plain Vars: if the sub-select's own\nquals prove the Var non-null, the output is non-nullable. But that\ntest compared only varno and varattno, without checking varlevelsup.\nAn outer reference in the targetlist could thus be matched against a\nVar of the sub-select's own range table that happens to share the same\nvarno and varattno, wrongly proving the output non-nullable and\nallowing an invalid conversion to an anti-join, which yields wrong\nanswers when the outer reference is NULL.\n\nTo fix, restrict the fallback to Vars of the current query level.\n\nAuthor: Rui Zhao \nReviewed-by: Tender Wang \nReviewed-by: Richard Guo \nDiscussion: https://postgr.es/m/CAHWVJhGuaFFRpmq4j+mcMcm_HC5QOT7LZsC9bf9b7BCBmvbfMA@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix nullability check for a sub-select's upper-level Vars"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAlso, mark X448MLKEM1024 as FIPS non-approved (backport of #26220)\n\nReviewed-by: Tim Hudson \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 15:06:57 2026\n(Merged from https://github.com/openssl/openssl/pull/32167)", "completion": "Additional ML-KEM cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAlso, mark X448MLKEM1024 as FIPS non-approved (backport of #26220)\n\nReviewed-by: Milan Broz \nReviewed-by: Neil Horman \nReviewed-by: Tim Hudson \nMergeDate: Tue Aug 11 15:05:35 2026\n(Merged from https://github.com/openssl/openssl/pull/32152)", "completion": "Additional ML-KEM cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAlso, mark X448MLKEM1024 as FIPS non-approved (backport of #26220)\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 13:56:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32159)", "completion": "Additional ML-KEM cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAlso, mark X448MLKEM1024 key management as FIPS non-approved (completion of #26220)\n\nReviewed-by: Tim Hudson \nReviewed-by: Bob Beck \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 06:57:33 2026\n(Merged from https://github.com/openssl/openssl/pull/32148)", "completion": "Additional ML-KEM cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nget_graph_pattern_def() emitted the pattern-level WHERE keyword as\n\"WHERE \" with no leading space, so reverse-parsing produced output\nlike \"(o IS orders)WHERE (...)\". The element-level WHERE deparse in\nget_path_pattern_expr_def() already prepends a separating space; the\npattern-level branch was inconsistent with it. Emit \" WHERE \" to\nmatch.\n\nThe output still re-parses to the same tree, so this is cosmetic.\n\nFor test coverage, add a whole-pattern WHERE clause to the existing\ncustomers_us view, which is already reverse-parsed with\npg_get_viewdef().\n\nAuthor: Dhruv Chauhan \nReviewed-by: Ashutosh Bapat \nDiscussion: https://www.postgresql.org/message-id/flat/CANWwWcpHb0h7tg6otRnL-FV83jwQpAiyw1bhvv8T78kpwZ-0ow%40mail.gmail.com", "completion": "Fix missing space before WHERE in GRAPH_TABLE deparse"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22467", "completion": "multi: remove #if 0'ed code that uses old struct"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWhen 'linebreak' pushes a word entirely to the next screen row, the\nfiller cells left on the current row keep whatever highlight was set\nby the last real character before the break, even when that highlight\nshould not extend past it (e.g. an underline, which looks broken drawn\nover blank cells).\n\nSolution:\nReset decor_attr and area_attr at the filler when their attribute has\nan underline, undercurl, strikethrough, or overline; otherwise leave\nthem, since a plain background or reverse-video highlight looks\ncorrect extending through blank filler cells, regardless of where the\npushed-down word happens to end. search_attr keeps the same check,\nplus its pre-existing on_last_col case (its own match ending exactly\nhere).\n\n(cherry picked from commit 9ff302d0ca260ffb06b1f1815ac4db1c63d1a9b3)", "completion": "fix(ui): highlight bleeds into 'linebreak' filler #41072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWhen 'linebreak' pushes a word entirely to the next screen row, the\nfiller cells left on the current row keep whatever highlight was set\nby the last real character before the break, even when that highlight\nshould not extend past it (e.g. an underline, which looks broken drawn\nover blank cells).\n\nSolution:\nReset decor_attr and area_attr at the filler when their attribute has\nan underline, undercurl, strikethrough, or overline; otherwise leave\nthem, since a plain background or reverse-video highlight looks\ncorrect extending through blank filler cells, regardless of where the\npushed-down word happens to end. search_attr keeps the same check,\nplus its pre-existing on_last_col case (its own match ending exactly\nhere).", "completion": "fix(ui): highlight bleeds into 'linebreak' filler #41072"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15202", "completion": "fix(runtime-vapor): avoid tracking v-show transition hooks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Tim Hudson \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 15:06:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32167)", "completion": "Additional ML-DSA cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Milan Broz \nReviewed-by: Neil Horman \nReviewed-by: Tim Hudson \nMergeDate: Tue Aug 11 15:05:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32152)", "completion": "Additional ML-DSA cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 13:56:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32159)", "completion": "Additional ML-DSA cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Tim Hudson \nReviewed-by: Bob Beck \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 06:57:34 2026\n(Merged from https://github.com/openssl/openssl/pull/32148)", "completion": "Additional ML-DSA cleansing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat: add Listy virtual list component\n\n* update\n\n* Update components/listy/index.en-US.md\n\nCo-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>\nSigned-off-by: Koyomi <1844749591@qq.com>\n\n* add demo\n\n* test(Listy): skip big-data demos in snapshot tests\n\n* test: update antd exports snapshot with Listy\n\n* fix(Listy): include item padding and border in itemHeight estimation\n\n* chore(Listy): remove code comments\n\n* test: update exports, site and vitest snapshots for Listy\n\n* test(Listy): skip demo snapshot tests for virtual rendering\n\n* test: support boolean skip option in node ssr demo test\n\n* docs(Listy): add global config column to API table\n\n* remove deprecated api\n\n* update api docs\n\n* update\n\n* fix(Listy): improve virtual config, itemHeight token and type support\n\n* test(Listy): exclude jest.mock based token test from vitest\n\n* docs: add 6.6.0 version\n\n* fix: apply code review\n\n* fix: fix lint\n\n* test: update snap\n\n* update demo\n\n* test: update Listy Vitest snapshot\n\n* docs: update docs\n\n* docs(Listy): adjust demos for non-virtual default and enable demo snapshots\n\n* docs(Listy): mark scroll-to demo as debug\n\n* test(Listy): add image snapshot test\n\n* docs(Listy): complete API metadata\n\n* fix(Listy): adjust itemHeight calculation\n\n---------", "completion": "feat(Listy): add virtual list component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n* build(vim-patch): n/a func in version.c\n\ninit_longVersion() sets datetime for \":version\".\nNvim removed it for more deterministic builds.\n\n* build(vim-patch): n/a header from amiga\n\n* build(vim-patch): n/a vim9 err msg for declaring vars\n\n* build(vim-patch): nvim support.txt replaces *os-support*\n\n* build(vim-patch): vim xdg is n/a\n\n* build(vim-patch): n/a 1-line err msg\n\nVim error message can be 1-line (globals.h), not multi-line (errors.h).\nTarget v8.2.1032", "completion": "build(vim-patch): misc n/a funcs, headers, err msgs #41116"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nEnable the sixel feature when WezTerm is detected and clarify that the kitty terminal feature requires Unicode placeholder support rather than only the basic graphics protocol.", "completion": "Use sixel images for WezTerm"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nA resize may temporarily leave the terminal cell pixel dimensions unknown while tmux queries the terminal. Schedule another client redraw when the pixel geometry response arrives so the graphical backend replaces the temporary text fallback.", "completion": "Redraw images after pixel geometry changes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nANALYZE VERBOSE and VACUUM VERBOSE both print per-table information\nat INFO level, including the table currently being processed and\nvarious statistics. However, the documentation described ANALYZE\nVERBOSE only as displaying generic \"progress messages\", while VACUUM\nVERBOSE used different wording about a vacuum activity report.\n\nReword the VERBOSE option descriptions and Outputs sections to describe\nthe actual output more consistently.\n\nAuthor: Shinya Kato \nReviewed-by: Surya Poondla \nReviewed-by: solai v \nReviewed-by: Maciek Sakrejda \nReviewed-by: David G. Johnston \nReviewed-by: Yushu Chen \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAOzEurTpMTUEW8kHu-zKB0EBtuPfpvyoJ--8pxKe87p24BGrpg@mail.gmail.com", "completion": "doc: Clarify VERBOSE output for ANALYZE and VACUUM"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe expire timers\n- DNS_PER_NAME\n- DNS_PER_NAME2\n- HAPPY_EYEBALLS_DNS\n\nare unused since we changed our happy eyeballing and handling of partial\nresolve results.\n\nCloses #22468", "completion": "curl_trc: remove unused expire timers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: An error raised after the list handler ran (e.g. while\n rendering) unwinds through the pcall around provider.list()\n and is routed back into the now no-op handler: silently\n discarded.\nSolution: Re-raise the error when the handler has already run.", "completion": "fix(dir): do not swallow errors raised after the list callback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: A failed initial directory listing discards the listing state:\n the user is left in an empty modifiable non-listing buffer, and\n the BufEnter autocmd retries the failing open, repeating the\n error on every re-entry.\nSolution: Render the failure as an empty listing with state and handlers\n intact: the error is reported once and \"R\" or :edit retries the\n listing. Keep the error on the listing state so a failed\n listing is distinguishable from an empty one; the next list\n clears it.", "completion": "fix(dir): keep a listing buffer when the initial listing fails"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22469", "completion": "lib1560: add CURLU_NO_GUESS_SCHEME tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nReplace screen-coordinate image placements with immutable pixel images referenced by ordinary grid cells. Draw visible marker runs through the redraw scene using per-client sixel or text backends so images follow history, copy mode, clipping and overwrites.", "completion": "Make sixel images grid resident"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCode using GetNamedDSHash() to retrieve a dshash table may also want to\nlimit its size, but there is actually no easy way to do so because the\ndsa_area of a hash table is hidden within dshash.c.\n\nThis commit adds dshash_get_dsa_area() to close the gap, which returns\nthe dsa_area for a given dshash_table. The DSA area retrieved can then\nbe passed to dsa_set_size_limit(), to limit its size. This accessor\nroutine also opens the door for allocating additional objects in the\nsame DSA area as a hash table, which may be useful for some.\n\nAuthor: Sami Imseih \nDiscussion: https://postgr.es/m/CAA5RZ0tKfCVqFnMZtavM42H63ha2Haf_C4mbJNWqkaW30cPW1w@mail.gmail.com", "completion": "Add dshash_get_dsa_area(), able to retrieve the DSA area of a dshash table"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nUse the DEC hue origin and channel order, and round percentage and HLS conversions to the nearest byte value.", "completion": "Correct SIXEL HLS colour conversion"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nRetain the padded canonical pixel canvas separately from the image content. Scale only the populated portion of partial edge cells so an image keeps its exact raster size on the originating terminal while retaining its cell footprint.", "completion": "Preserve SIXEL pixel dimensions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nBuild an adaptive 256-colour palette with median cut instead of using a fixed colour cube. Apply Floyd-Steinberg error diffusion while mapping pixels to reduce banding and preserve image detail.", "completion": "Improve SIXEL colour quantization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThey were previously unit tests but used only public library functions.\n\nCloses #22471", "completion": "tests: convert unit test 1396 and 1398 into libtests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nErase the temporaries that hold secrets or data derived from them:\nWOTS+ chain secrets, Merkle tree nodes, the message digest and\ncandidate FORS keys in sign and verify, the MGF1 seed and PRF-msg\noutput buffers, the encoded message (which may contain confidential\ncontent), and the caller's signature buffer when signing fails part\nway through. Also cleanse a private key of unexpected length that\nossl_slh_dsa_key_fromdata() copied into the key before rejecting it.\n\nThe SHA2 hash functions kept the digest and the concatenated child\nnodes in local stack buffers, abandoned on every call. Erasing them\nper call measurably slows the innermost functions, so move them into\na scratch buffer in SLH_DSA_HASH_CTX that is erased when the context\nis freed. The SHAKE hash functions write straight to the caller's\nbuffer and need no scratch.\n\nThe key material copies built by slh_dsa_export() were freed with\nOSSL_PARAM_free(), which only wipes the secure-heap data block. This\nbranch has no OSSL_PARAM_clear_free(), so wipe the copies explicitly\nbefore freeing.\n\nThe FORS roots buffer in ossl_slh_fors_pk_from_sig() was sized as if\nit held k * a nodes, but only one root per tree is ever written.\nShrink it to k * n bytes maximum and erase only the used length.\n\nReviewed-by: Tim Hudson \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 15:07:00 2026\n(Merged from https://github.com/openssl/openssl/pull/32167)", "completion": "slh-dsa: cleanse temporary copies of sensitive data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe hash functions worked on stack copies of the prehashed PK.seed context.\nDuring signing these absorb SK.seed and WOTS+ chain secrets, and every call\nleft the final hash state on the stack. Erasing it per call would burden the\ninnermost functions, which dominate signing time.\n\nGive SLH_DSA_HASH_CTX a heap-allocated scratch context and use it in place of\nthe stack copies. The working state now sits in one reusable buffer, erased\nwhen the hash context is freed; the per-call copy is unchanged and stack use\ngoes down. For the SHA2 parameter sets the buffer is sized to double as the\nSHA-512 context of security categories 3 and 5. The prehashed contexts are now\nfreed with OPENSSL_clear_free().\n\nErase the remaining temporaries holding secrets or data derived from them:\nWOTS+ and FORS secret values, Merkle tree nodes, the message digest and\ncandidate FORS keys in sign and verify, the encoded message, and the caller's\nsignature buffer when signing fails part way. Cleanse a wrong-length private\nkey that ossl_slh_dsa_key_fromdata() copied in before rejecting it. The FORS\nroots buffer held one root per tree but was sized for k * a nodes; shrink it to\nk * n bytes and erase only the used length.\n\nPerformance is unchanged within noise; the SHAKE parameter sets measure a few\npercent faster, likely because the working Keccak state now stays at one fixed\naddress rather than a fresh stack copy at each recursion depth.\n\nReviewed-by: Milan Broz \nReviewed-by: Neil Horman \nReviewed-by: Tim Hudson \nMergeDate: Tue Aug 11 15:05:38 2026\n(Merged from https://github.com/openssl/openssl/pull/32152)", "completion": "slh-dsa: cleanse temporary copies of sensitive data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nErase the temporaries that hold secrets or data derived from them:\nWOTS+ chain secrets, Merkle tree nodes, the message digest and\ncandidate FORS keys in sign and verify, the MGF1 seed and PRF-msg\noutput buffers, the encoded message (which may contain confidential\ncontent), and the caller's signature buffer when signing fails part\nway through. Also cleanse a private key of unexpected length that\nossl_slh_dsa_key_fromdata() copied into the key before rejecting it.\n\nThe SHA2 hash functions kept the digest and the concatenated child\nnodes in local stack buffers, abandoned on every call. Erasing them\nper call measurably slows the innermost functions, so move them into\na scratch buffer in SLH_DSA_HASH_CTX that is erased when the context\nis freed. The SHAKE hash functions write straight to the caller's\nbuffer and need no scratch.\n\nThe key material copies built by slh_dsa_export() were freed with\nOSSL_PARAM_free(), which only wipes the secure-heap data block. This\nbranch has no OSSL_PARAM_clear_free(), so wipe the copies explicitly\nbefore freeing.\n\nThe FORS roots buffer in ossl_slh_fors_pk_from_sig() was sized as if\nit held k * a nodes, but only one root per tree is ever written.\nShrink it to k * n bytes maximum and erase only the used length.\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 13:56:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32159)", "completion": "slh-dsa: cleanse temporary copies of sensitive data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe hash functions worked on stack copies of the prehashed PK.seed context.\nDuring signing these absorb SK.seed and WOTS+ chain secrets, and every call\nleft the final hash state on the stack. Erasing it per call would burden the\ninnermost functions, which dominate signing time.\n\nGive SLH_DSA_HASH_CTX a heap-allocated scratch context and use it in place of\nthe stack copies. The working state now sits in one reusable buffer, erased\nwhen the hash context is freed; the per-call copy is unchanged and stack use\ngoes down. For the SHA2 parameter sets the buffer is sized to double as the\nSHA-512 context of security categories 3 and 5. The prehashed contexts are now\nfreed with OPENSSL_clear_free().\n\nErase the remaining temporaries holding secrets or data derived from them:\nWOTS+ and FORS secret values, Merkle tree nodes, the message digest and\ncandidate FORS keys in sign and verify, the encoded message, and the caller's\nsignature buffer when signing fails part way. Cleanse a wrong-length private\nkey that ossl_slh_dsa_key_fromdata() copied in before rejecting it. The FORS\nroots buffer held one root per tree but was sized for k * a nodes; shrink it to\nk * n bytes and erase only the used length.\n\nPerformance is unchanged within noise; the SHAKE parameter sets measure a few\npercent faster, likely because the working Keccak state now stays at one fixed\naddress rather than a fresh stack copy at each recursion depth.\n\nReviewed-by: Tim Hudson \nReviewed-by: Bob Beck \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 06:57:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32148)", "completion": "slh-dsa: cleanse temporary copies of sensitive data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe is_valid parameter was never referenced in the function body, and\nthe 'thisatt' local variable is set but never used. Remove both.\n\nOversight in a379061a22a8.\n\nAuthor: Sami Imseih \nBackpatch-through: 18\nDiscussion: https://postgr.es/m/CAA5RZ0tHnvSrfUy4jWJchjvkL_aJe0hCnZpMsFRdLrSxCne5qQ@mail.gmail.com", "completion": "Remove unused arg and dead code in set_attnotnull()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThese functions were previously untested in the test suite. This is just\na set of basic invokes to make sure they work. The core of these\nfunctions is identical and is tested already.\n\n - curl_mvfprintf\n - curl_mvprintf\n - curl_mvsnprintf\n - curl_mvsprintf\n - curl_mvaprintf\n\nCloses #22472", "completion": "test557: test curl_mv*printf() functions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Neil Horman \nMergeDate: Thu Sep 10 21:14:58 2026\n(Merged from https://github.com/openssl/openssl/pull/30431)", "completion": "fix: guard MD5-dependent X509_ALGOR test with OPENSSL_NO_MD5"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\nchore: add missing backticks to `no-duplicate-imports.js`", "completion": "docs: add missing backticks to `no-duplicate-imports.js`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit d137c9e4f722 \"Fix false success on zero BIO write\" introduced\na function-scope left variable while the app-buffer recovery block\nalready declared one. This breaks builds using -Werror=shadow.\n\nAssign the current buffer length to the existing function-scope variable\nin the recovery block. This preserves the previous re-read at that point\nwhile eliminating the shadowed declaration.\n\nFixes: d137c9e4f722 \"Fix false success on zero BIO write\"\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 15:46:22 2026\n(Merged from https://github.com/openssl/openssl/pull/32153)\n\n(cherry picked from commit a2eea872d0af948e5b889083f248e270d7326be7)", "completion": "ssl: Remove shadowed variable in write retry path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit 8d46334ee4ef \"Fix false success on zero BIO write\" introduced\na function-scope left variable while the app-buffer recovery block\nalready declared one. This breaks builds using -Werror=shadow.\n\nAssign the current buffer length to the existing function-scope variable\nin the recovery block. This preserves the previous re-read at that point\nwhile eliminating the shadowed declaration.\n\nFixes: 8d46334ee4ef \"Fix false success on zero BIO write\"\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 15:46:22 2026\n(Merged from https://github.com/openssl/openssl/pull/32153)\n\n(cherry picked from commit a2eea872d0af948e5b889083f248e270d7326be7)", "completion": "ssl: Remove shadowed variable in write retry path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit fae9fd3b6109 \"Fix false success on zero BIO write\" introduced\na function-scope left variable while the app-buffer recovery block\nalready declared one. This breaks builds using -Werror=shadow.\n\nAssign the current buffer length to the existing function-scope variable\nin the recovery block. This preserves the previous re-read at that point\nwhile eliminating the shadowed declaration.\n\nFixes: fae9fd3b6109 \"Fix false success on zero BIO write\"\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 15:46:22 2026\n(Merged from https://github.com/openssl/openssl/pull/32153)\n\n(cherry picked from commit a2eea872d0af948e5b889083f248e270d7326be7)", "completion": "ssl: Remove shadowed variable in write retry path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit ebfcd4cfd4b7 \"Fix false success on zero BIO write\" introduced\na function-scope left variable while the app-buffer recovery block\nalready declared one. This breaks builds using -Werror=shadow.\n\nAssign the current buffer length to the existing function-scope variable\nin the recovery block. This preserves the previous re-read at that point\nwhile eliminating the shadowed declaration.\n\nFixes: ebfcd4cfd4b7 \"Fix false success on zero BIO write\"\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 15:46:22 2026\n(Merged from https://github.com/openssl/openssl/pull/32153)\n\n(cherry picked from commit a2eea872d0af948e5b889083f248e270d7326be7)", "completion": "ssl: Remove shadowed variable in write retry path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit 5f3db0d81132 \"Fix false success on zero BIO write\" introduced\na function-scope left variable while the app-buffer recovery block\nalready declared one. This breaks builds using -Werror=shadow.\n\nAssign the current buffer length to the existing function-scope variable\nin the recovery block. This preserves the previous re-read at that point\nwhile eliminating the shadowed declaration.\n\nFixes: 5f3db0d81132 \"Fix false success on zero BIO write\"\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Jakub Zelenka \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 3 15:46:22 2026\n(Merged from https://github.com/openssl/openssl/pull/32153)", "completion": "ssl: Remove shadowed variable in write retry path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nui2 clears the substitute confirmation match when it updates its prompt buffer with hlsearch disabled.\n\nSolution:\nOnly invalidate the match highlight when the current buffer changes.", "completion": "fix(ui2): retain substitute confirmation highlight with nohlsearch #41067"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:23:43 2026\n(Merged from https://github.com/openssl/openssl/pull/31597)", "completion": "test: cover quoted property case variants"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Eugene Syromiatnikov \n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:00:52 2026\n(Merged from https://github.com/openssl/openssl/pull/32155)", "completion": "doc/internal/man7/deprecation.pod: document OSSL_DEPRECATEDIN_._._FOR macros"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReplace the `timeoutlist` and time nodes for expire timers with `struct\nexpire_timers` that keeps a time and next array.\n\nThere is only ever one timeout per timer id and a fully dynamic list is\nnot needed. Do the sorting by keeping an array of 'next' indiced and a\n'first' starting point.\n\nAdded tracking of splay tree status.\n\nFixed missing splay removal when last timeout was removed via\nCurl_expire_done().\n\nCloses #22473", "completion": "multi: use index list for expire timeouts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAnd correct some comments\n\nCloses #22474", "completion": "url: rename Curl_init_do => Curl_init_transfer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* chore: improve ecosystem test failure reporting\n\n* move ecosystem test inline scripts to tools\n\n* ignore ecosystem test scripts in knip\n\n* use process.cwd() and explicit issue state\n\n* update ecosystem-tests.yml\n\n* remove blank lines\n\n* refactor\n\n* move ecosystem test tools into `tools/test-ecosystem`\n\n* remove redundant async\n\n* Update .github/workflows/ecosystem-tests.yml\n\nCo-authored-by: Francesco Trotta \n\n---------", "completion": "chore: improve ecosystem test failure reporting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds a test to cover the case where an `@import` might have a URL with special characters that isn't quoted.", "completion": "test(compiler): add test for imports with unquoted URL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nVerify in test 2118\n\nCloses #22475", "completion": "mbedtls: enforce verifyhost when verifypeer is disabled"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n'breakindent' and 'showbreak' draw their own padding with no\nreference to whatever decoration or syntax highlight is currently\nactive, so it goes unhighlighted even mid-highlight, not just past a\nreal EOL. Gating this on the decoration's `hl_eol` flag (as an\nearlier version of this fix did) missed plain highlights with no\n`hl_eol` at all, which have the exact same problem.\n\nSolution:\nSnapshot decor_attr into decor_attr_save right before it can be\nreset by 'linebreak' filler handling, and pass it into\nhandle_breakindent()/handle_showbreak_and_filler() to extend into\ntheir padding: it is not a real end of the highlight, just screen\ncells with no buffer text. Like the 'linebreak' filler, an\nunderline/strikethrough/overline is excluded, since it looks like a\nbroken line drawn over the gap. This also fixes 'breakindent' losing\nthe highlight right after a real 'linebreak' word-push, since that\nreset otherwise leaked into the next row.\n\n(cherry picked from commit 866d61e91abaa73561f91ddd8f6e27bd50f9bc72)", "completion": "fix(decor): 'breakindent'/'showbreak' gap ignores active highlight #41073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n'breakindent' and 'showbreak' draw their own padding with no\nreference to whatever decoration or syntax highlight is currently\nactive, so it goes unhighlighted even mid-highlight, not just past a\nreal EOL. Gating this on the decoration's `hl_eol` flag (as an\nearlier version of this fix did) missed plain highlights with no\n`hl_eol` at all, which have the exact same problem.\n\nSolution:\nSnapshot decor_attr into decor_attr_save right before it can be\nreset by 'linebreak' filler handling, and pass it into\nhandle_breakindent()/handle_showbreak_and_filler() to extend into\ntheir padding: it is not a real end of the highlight, just screen\ncells with no buffer text. Like the 'linebreak' filler, an\nunderline/strikethrough/overline is excluded, since it looks like a\nbroken line drawn over the gap. This also fixes 'breakindent' losing\nthe highlight right after a real 'linebreak' word-push, since that\nreset otherwise leaked into the next row.", "completion": "fix(decor): 'breakindent'/'showbreak' gap ignores active highlight #41073"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit c8a350a439826267186c187dbfbf1f839f7521aa attempted to consolidate\ncode for identify possibly-compressed tar archives by suffix into a new\nfunction parse_tar_compress_algorithm(). Unfortunately, the refactoring\nwasn't perfect, and slightly changed the behavior at both existing call\nsites.\n\nIn CreateBackupStreamer(), the previous code required the filename to\nconsist of more than just a suffix, so the aforementioned commit had the\neffect of allowing pg_basebackup to accept a file from the server whose\nentire name was something like .tar.gz -- which should never happen, but\nlet's reject it as previous releases did.\n\nIn precheck_tar_backup_file(), the previous code required the suffix to\nbe immediately adjacent to the prefix already checked, so the commit\nin question allowed pg_verifybackup to accept not only filenames like\nbase.tar.gz but also filenames like baseFOOBARBAZ.tar.gz. While such\nfilenames are perhaps unlikely, rejecting them is correct, so let's go\nback to that behavior.\n\nDiscussion: http://postgr.es/m/CA+TgmoYJY8FkoeYKGF_YF1S6uOK7fd0Bd3zrw0XY_oZXbmVFpQ@mail.gmail.com\nReported-by: Sarath Kumar \nReviewed-by: Andrew Dunstan \nBackpatch-through: 19", "completion": "Undo inadvertent loosening of archive filename checking."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf the client attempted ECH, secrets are logged against the inner ClientHello\nrandom. CLIENT_EARLY_LABEL and EARLY_EXPORTER_SECRET_LABEL are special-cased\nbecause they are logged before the server's acceptance of ECH is known, but are\nalways derived from the inner ClientHello (see tls13_change_cipher_state()), so\nthey use the inner random regardless of ech.success.\n\nOn rejection the early secrets therefore carry the inner random while later ones\ncarry the outer: each line is tagged with the random of the ClientHello its\nsecret was derived from, and since a rejecting server never derives the early\nsecrets, both peers still log identical material for every label they both log.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Mounir Idrassi \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:36:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32149", "completion": "ECH: Fix keylog callback to use inner client hello random from ECH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf the client attempted ECH, secrets are logged against the inner ClientHello\nrandom. CLIENT_EARLY_LABEL and EARLY_EXPORTER_SECRET_LABEL are special-cased\nbecause they are logged before the server's acceptance of ECH is known, but are\nalways derived from the inner ClientHello (see tls13_change_cipher_state()), so\nthey use the inner random regardless of ech.success.\n\nOn rejection the early secrets therefore carry the inner random while later ones\ncarry the outer: each line is tagged with the random of the ClientHello its\nsecret was derived from, and since a rejecting server never derives the early\nsecrets, both peers still log identical material for every label they both log.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Mounir Idrassi \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:35:56 2026\nMerged-from: https://github.com/openssl/openssl/pull/32149", "completion": "ECH: Fix keylog callback to use inner client hello random from ECH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf the client attempted ECH, secrets are logged against the inner ClientHello\nrandom. CLIENT_EARLY_LABEL and EARLY_EXPORTER_SECRET_LABEL are special-cased\nbecause they are logged before the server's acceptance of ECH is known, but are\nalways derived from the inner ClientHello (see tls13_change_cipher_state()), so\nthey use the inner random regardless of ech.success.\n\nOn rejection the early secrets therefore carry the inner random while later ones\ncarry the outer: each line is tagged with the random of the ClientHello its\nsecret was derived from, and since a rejecting server never derives the early\nsecrets, both peers still log identical material for every label they both log.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Mounir Idrassi \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:35:44 2026\nMerged-from: https://github.com/openssl/openssl/pull/32149", "completion": "ECH: Fix keylog callback to use inner client hello random from ECH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(CheckboxGroup): add support for undefined value\n\n* test: null use case\n\n* fix: change key definition strategy to avoid key conflic with 'null' string\n\n* fix: add different prefixes\n\n* update\n\n---------", "completion": "fix(Checkbox): filter out Checkbox.Group options with nullish values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nLogging connection information, even at DEBUG1, creates unnecessary\nrisks. Remove the entire log message because it had no other useful\ncontent.\n\nAddresses finding 14 in report from linked discussion.\n\nReported-by: Noah Misch \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch@microsoft.com\nBackpatch-through: 14", "completion": "Do not log subscription conninfo."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen enabling checksums cannot process a database, the launcher uses\nDatabaseExists to tell a concurrent drop (benign) from a real failure.\nSince 1df361e3d82 that check also treats a present, but-invalid, data-\nbase as non-existent. An interrupted DROP DATABASE flush the invalid\nmarker before the row and files are removed, so a crash or ERROR can\nleave an invalid row whose files remain on disk.\n\nReport a database as existing whenever its catalog row is found to\nensure that checksums cannot be enabled if there are invalid databases.\nThe AccessShareLock in DatabaseExists already waits out an in-flight\ndrop, so an invalid-but-present row can only be an interrupted drop\nleftover whose files still need checksums; enabling then aborts until\nit is dropped.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Ayush Tiwari \nReviewed-by: Zsolt Parragi \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAN4CZFOGdqxtZ5-6gb4apqmvoH=Z+TNH8RKJ3mVtoR1HirKQWg@mail.gmail.com\nBackpatch-through: 19", "completion": "Don't skip invalid databases when enabling data checksums"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 6566133c5f5 added a case for AuthMemRelationId in\nAcquireDeletionLock(), but not ReleaseDeletionLock(). The fall-through\ncase would go to UnlockDatabaseObject(), which would raise a WARNING;\nand the lock would be retained until the end of the transaction.\n\nAdd the missing branch.\n\nDiscussion: https://postgr.es/m/2487ddcd737d4fc8e408e87aa9ad4365eed3bbb3.camel@j-davis.com\nBackpatch-through: 16", "completion": "Fix lock release for role membership grants in DROP OWNED BY."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace synchronous detectChanges calls with zoneless-compatible scheduling and stability waits in NgClass, NgStyle, and NgOptimizedImage tests.\n\n(cherry picked from commit 2f0be5bef83ce15668fd401a470b4a5abe9c7f88)", "completion": "refactor(common): modernize directive tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReplace synchronous detectChanges calls with zoneless-compatible scheduling and stability waits in NgClass, NgStyle, and NgOptimizedImage tests.", "completion": "refactor(common): modernize directive tests to rely on whenStable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWe do not allow a DROP SERVER ... CASCADE to implicitly drop a\nsubscription, because it's in a shared catalog and dropping a\nsubscription has side effects. Instead we throw an error and the user\nmust drop the subscription explicitly. Document this behavior and add\na HINT to the error message.\n\nGeneralize AcquireDeletionLock()/ReleaseDeletionLock() to use shared\nobject locks for all shared catalogs, which includes AuthMemRelationId\nand now SubscriptionRelationId.\n\nMove error message after AcquireDeletionLock() to avoid an unnecessary\nerror if there's a concurrent DROP SUBSCRIPTION.\n\nAddresses finding 10 & 15 in report from linked discussion.\n\nReported-by: Noah Misch \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Improve DROP SERVER handling of dependent subscriptions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe subscription is initiated from a logical replication worker, so\nSCRAM pass-through won't work.\n\nPartially addresses finding 3 in report from linked discussion.\n\nReported-by: Noah Misch \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "postgres_fdw: reject use_scram_passthrough for subscriptions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen VACUUM or ANALYZE is run without a table list, we scan\npg_class to build the list of relations to process, and we\ncheck the privileges on each relation we find. Since we don't\ntake any locks on the relations at this point, it's possible\nfor one to be concurrently dropped, in which case the privilege\ncheck fails with an ERROR such as the following:\n\n\tERROR: relation with OID 16388 does not exist\n\nThis unnecessarily aborts the entire command. To fix, use\npg_class_aclcheck_ext() for the privilege check so that we can\ndetect concurrently-dropped relations and silently skip them.\nThere's no need to emit a WARNING for such relations because\nthey weren't explicitly named, and a drop at this point is no\ndifferent than one that happened before our pg_class scan\nbegan. Note that concurrent drops that occur later on are\nalready handled gracefully by vacuum_open_relation().\n\nThe new missing_ok behavior is limited to get_all_vacuum_rels().\nAll other callers of vacuum_is_permitted_for_relation() should\nhold a lock on the relation that prevents it from being\nconcurrently dropped, so this commit also adds an assertion to\nthat effect.\n\nOversight in commit a556549d7e.\n\nThis is a bug fix and could be back-patched, but given the\npresumed rarity of the race condition and the lack of field\nreports, I'm not going to bother.\n\nReported-by: ChangAo Chen \nAuthor: ChangAo Chen \nCo-authored-by: Nathan Bossart \nReviewed-by: Kyotaro Horiguchi \nReviewed-by: Surya Poondla \nReviewed-by: Bharath Rupireddy \nReviewed-by: Michael Paquier \nDiscussion: https://postgr.es/m/tencent_F9D483523BB0D082C2EFDA80142F192DBC07%40qq.com", "completion": "Handle concurrently-dropped relations in database-wide VACUUM."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nExtract the charset parameter from the Content-Type response header in FetchBackend and pass it to TextDecoder when decoding text and json responses. When no valid charset is provided or supported, gracefully fall back to default utf-8 decoding.\n\nFixes #70061\n\n(cherry picked from commit 6a0789dc7f0ac9d1249c4d9f315e83424867169b)", "completion": "fix(http): respect content-type charset in fetch backend text decoder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nExtract the charset parameter from the Content-Type response header in FetchBackend and pass it to TextDecoder when decoding text and json responses. When no valid charset is provided or supported, gracefully fall back to default utf-8 decoding.\n\nFixes #70061", "completion": "fix(http): respect content-type charset in fetch backend text decoder"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nAlso fix up the evp tests to skip the 144 tests which allocate a DRBG\nwithout a derivation function when testing the fips provider\n\nReviewed-by: Neil Horman \nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:41 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)\n\n(cherry picked from commit 9ef31bc73697701219ff439b47f57de5cf61c1bf)", "completion": "Fix FIPS to require a derivation function with CTR-DRBG"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFIPS-140-3 requires that if a CTR-DRBG is allocated from the fips\nprovider that either:\n\na) The entropy source must be NIST validated and exist within the FIPS\nboundary\n\nor\n\nb) The CTR-DRBG must use a derivation function with an entropy source\noutside the FIPS boundary\n\nGiven that we have no approved noise source inside the FIPS boundary, we\nneed to enforce the fact that FIPS allocated CTR-DRBGS only allocate\ninstances in which a derivation function is requested (i.e. the USE_DF\nparameter is asserted and set to one)\n\nFollow path b, and ensure that FIPS CTR-DRBG allocations assert the use\nof USE_DF or fail if an allocation does not\n\nAlso fix up the evp tests to skip the 144 tests which allocate a DRBG\nwithout a derivation function when testing the fips provider\n\nReviewed-by: Neil Horman \nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:41 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)", "completion": "Fix FIPS to require a derivation function with CTR-DRBG"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n3592e0ff9 added caching logic to ExecFindPartition() to allow faster\npartition lookups for LIST and RANGE partitions when we hit the same\npartition multiple times in a row. The last_found_part_index field was\nadded, but it was never used, so remove it. Caching works by caching the\nlast matching index into the PartitionBoundInfo.datums, not by caching the\nlast found partition index.\n\nUpdate comments to reflect this, and perform other general improvements to\nthe comments in this area.\n\nAuthor: Aleksander Alekseev \nAuthor: David Rowley \nDiscussion: https://postgr.es/m/CAJ7c6TMRxO6vo1tNgLZs4nTNizpjCSWdUviB8Mf3nkYiNHNhzg@mail.gmail.com", "completion": "Remove unused field from PartitionDescData struct"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Carousel): keep current slide when children are added\n\nfix issue #24879\n\nCo-Authored-By: Claude \n\n* test(Carousel): add test case for children removal not overflow\n\n* test(Carousel): verify slide after children removal\n\n---------", "completion": "fix(Carousel): keep current slide when children are added"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWith -multi, a later certificate failure could return success after an\nearlier certificate succeeded because ret retained the earlier result\non reaching err:.\n\nSet ret = 1 at err: so every path reaching it reports failure. Paths\nbypassing err: remain unchanged, including the pre-existing\nX509_VERIFY_PARAM_new() failure under -checkend, which will be addressed\nseparately.\n\nAdd a regression test using -multi -checkhost with a two-certificate\nchain whose second certificate fails.\n\nFixes #32189\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Todd Short \nMerge-date: Mon Sep 7 14:01:00 2026\nMerged-from: https://github.com/openssl/openssl/pull/32190\n(cherry picked from commit 8da3880874acaac2e338665f216e430f78f976f1)", "completion": "apps/x509.c: failing exit status on every failure path reaching err:"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWith -multi, a later certificate failure could return success after an\nearlier certificate succeeded because ret retained the earlier result\non reaching err:.\n\nSet ret = 1 at err: so every path reaching it reports failure. Paths\nbypassing err: remain unchanged, including the pre-existing\nX509_VERIFY_PARAM_new() failure under -checkend, which will be addressed\nseparately.\n\nAdd a regression test using -multi -checkhost with a two-certificate\nchain whose second certificate fails.\n\nFixes #32189\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Todd Short \nMerge-date: Mon Sep 7 14:01:00 2026\nMerged-from: https://github.com/openssl/openssl/pull/32190", "completion": "apps/x509.c: failing exit status on every failure path reaching err:"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nEnabling retain_dead_tuples requires the publisher to run PostgreSQL 19 or\nlater and to not be in recovery. Previously this was checked only at DDL\ntime. That forced ALTER SUBSCRIPTION ... ENABLE to connect to the\npublisher, so pg_upgrade (which re-enables subscriptions during restore)\nfailed if the publisher was unreachable. It was also not authoritative,\nsince the publisher's version or recovery status can change afterwards,\nfor example after a failover.\n\nPerform the check authoritatively in the apply worker when it connects,\nand stop doing it when enabling a subscription. ENABLE is the only command\nissued during restore that triggered it, so this also fixes the pg_upgrade\nfailure. The DDL-time check is kept as a convenience for the other paths,\nnone of which are issued during restore.\n\nReported-by: Noah Misch \nAnalyzed-by: Jeff Davis \nAuthor: Amit Kapila \nReviewed-by: Jeff Davis \nReviewed-by: Hayato Kuroda \nBackpatch-through: 19, where it was introduced\nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch@microsoft.com", "completion": "Validate publisher for retain_dead_tuples in the apply worker."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nThe middle-wildcard branch used replaceAll('/*/', ...), which consumes the\nslash shared by two adjacent '/*/*/' segments, so only the first segment was\nconverted and the second was left as an unnamed '*' that path-to-regexp still\nrejects. Match '/*' with a lookahead for the following slash instead, so every\nwildcard segment is converted. Existing single-wildcard output is unchanged.", "completion": "fix(core): convert adjacent wildcard segments in legacy route converter"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nFix missing NULL check in MemoryContextAllocAligned(). The underlying\ncall to MemoryContextAllocExtended() could return NULL when\nflags contains MCXT_ALLOC_NO_OOM and the underlying malloc fails.\n\nThere are no current callers using MemoryContextAllocAligned() that pass\nthe MCXT_ALLOC_NO_OOM in core, so no live bug fix in core here. However,\nan extension might use this pattern, so we'd better fix.\n\nFix this so we correctly pass the NULL to the caller rather than trying\nto write to a NULL memory address.\n\nThis also fixes the same bug in AlignedAllocRealloc(), which is also\nunused in core.\n\nBackpatch to v16, where these functions first appeared.\n\nAuthor: Chao Li \nDiscussion: https://postgr.es/m/07DAC4C3-120D-4F3C-8FEE-BA236F7E9C1D@gmail.com\nBackpatch-through: 16", "completion": "Fix missing MCXT_ALLOC_NO_OOM handling in MemoryContextAllocAligned"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSimilar to what 1f7cb5c30 did for the INT types, protect against\noverflow when dividing the lowest possible money value by -1. This\ncannot be represented on a two's complement machine.\n\nWithout this check, the result depends on the machine, and in the worst\ncase, could result in a crash. With the fix installed, this will now\nresult in:\n\nERROR: money out of range\n\nBug: #19585\nAuthor: Andrey Rachitskiy \nReported-by: Michael Malis \nReviewed-by: Tristan Partin \nReviewed-by: Rafia Sabih \nDiscussion: https://postgr.es/m/19586-bb603bf5ad9934dd%40postgresql.org\nDiscussion: https://postgr.es/m/CAB8bMisnXJVXte6s3kUOpuuAY9%3D9kehG6MMX-%2BTQoFsSGan22Q%40mail.gmail.com\nBackpatch-through: 14", "completion": "Fix missing money overflow checks for INT64_MIN / -1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPer commit 8bf6ec3ba3a4, a column can be GENERATED only if it is such in\nthe whole inheritance tree.\n\nFor this reason, ATPrepDropExpression refuses to be called with ONLY on\na partitioned table. To detect this, the current implementation checks\nwhether recurse is set to false and the rel has direct children.\n\nRecursion is implemented with ATSimpleRecursion, which calls ATPrepCmd\nwith recurse = false for every node in the tree. Inner nodes (for\nexample a partition which itself has subpartitions) then fail the check,\naccidentally preventing the command from working on inheritance trees of\ndepth > 2.\n\nThis commit fixes it by also checking that we're at the top level of the\nrecursive calls using the recursing parameter, which is always true when\ncalled through ATSimpleRecursion, always false when invoked on the root\nrel.\n\nAlso, remove a comment claiming that DROP EXPRESSION could be\nimplemented with some effort. It cannot, as the commit message for\n8bf6ec3ba3a4 explains.\n\nAuthor: Alberto Piai \nBackpatch-through: 14\nDiscussion: https://postgr.es/m/DHMT78XOD8BK.341V3H87KZ7NO@gmail.com", "completion": "Fix ALTER COLUMN ... DROP EXPRESSION with subpartitions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15096", "completion": "fix(types): preserve defineModel inference with factory defaults"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nfix #15113", "completion": "fix(runtime-core): restore SSR setup state when handling async setup result"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15153", "completion": "fix(custom-element): preserve nested async mount order"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15142", "completion": "fix(scheduler): avoid stack overflow when flushing very large post cb arrays"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15126\nCloses #15128", "completion": "fix(compiler-sfc): handle transformed template AST after cache invalidation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nfix #11910", "completion": "fix(transition): support transition to teleport component child"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #5081", "completion": "dx(runtime-core): warn when innerHTML/textContent overrides children"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWe allowed GRANT ... ON TABLE on sequences for backward compatibility.\nWe don't need to consider backward compatibility in case of property\ngraphs since we will be prohibiting its usage on property graph from\nthe very release which introduced property graphs.\n\nChange regression tests that used GRANT ... ON [TABLE] on property\ngraphs to use GRANT ... ON PROPERTY GRAPH instead.\n\nWhile here, add the missing RELKIND_PROPGRAPH cases in\npg_class_aclmask_ext() and in the object-type switch in\nExecGrant_Relation() so that the default ACL and the objtype passed to\nrestrict_and_check_grant() are correct.\n\nAuthor: Ashutosh Bapat \nReviewed-by: Noah Misch \nReviewed-by: Tom Lane \nDiscussion: https://www.postgresql.org/message-id/20260630023308.c7.noahmisch@microsoft.com", "completion": "Prohibit GRANT ... ON TABLE on a property graph"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(table): support force rendering expanded rows\n\n* docs(table): add force render expanded rows demo\n\n* test(table): add force render demo extend snapshots\n\n* docs(Table): remove forceRender demo\n\n* build: increase bundle size limit\n\n---------", "completion": "feat(Table): support force rendering expanded rows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit f6f0542266f0 changed getNotify(),\ngetParameterStatus(), and related libpq message-processing paths to\nabandon the connection on out-of-memory errors.\n\nHowever, getCopyDataMessage() and pqFunctionCall3() did not handle\nthis new fatal-error state. Both can process asynchronous\nNotificationResponse and ParameterStatus messages while waiting for\nother responses. If one of those messages triggered a fatal error, these\nloops continued processing instead of reporting it immediately.\n\nFix this by checking for a saved fatal error after processing an\nasynchronous message. If the connection has been abandoned, return the\nappropriate error immediately instead of continuing to parse input.\n\nBackpatch to v18, where commit f6f0542266f0 introduced this issue.\n\nAuthor: Anthonin Bonnefoy \nReviewed-by: Ewan Young \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAO6_XqpGfm+XHE1OzS=_+jroeDOxhhGa11P3cbm9q2gT05yorA@mail.gmail.com\nBackpatch-through: 18", "completion": "Fix error handling in getCopyDataMessage() and pqFunctionCall3()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, CheckPointReplicationSlots() ran at the start of\nCheckPointGuts(), while WAL cleanup occurred much later in\nCreateCheckPoint() and CreateRestartPoint(), after the buffer write\nand ProcessSyncRequests() phases. During a spread checkpoint, this gap\ncould be several minutes.\n\nDuring that time, active replication slots could advance their\nrestart_lsn. However, replicationSlotMinLSN had already been\ncomputed from the older saved values. As a result, KeepLogSeg() could\nretain WAL segments that were no longer needed, causing unnecessary\npg_wal growth until the next checkpoint or restartpoint.\n\nFix this by moving CheckPointReplicationSlots(),\nCheckPointSnapBuild(), and CheckPointLogicalRewriteHeap() to just\nbefore CheckPointTwoPhase(), after the buffer write and\nProcessSyncRequests() phases. This makes WAL retention decisions use\nthe latest replication slot state. The logical snapshot and rewrite heap\ncleanup decisions also benefit from the updated saved restart_lsn.\n\nAuthor: Ants Aasma \nAuthor: Hüseyin Demir \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CANwKhkPCBcTQ_pk06MD5W5YYNnuYHp8dLNuOUz8-5pMBMPY1Bw%40mail.gmail.com", "completion": "Checkpoint replication slots later in the checkpoint cycle"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSee #22462\nCloses #22480", "completion": "TODO: do not consider APPDATA for netrc"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe SELECT privilege can be granted on a property graph, and its\nprivileges can be examined with psql's \\dp command, but property\ngraphs were missing from both summary tables in the \"Privileges\"\nsection: the applicable object types for SELECT in the privilege\nabbreviations table, and the per-object-type row in the summary of\naccess privileges table. Add the missing entries so the tables match\nthe actual behavior described for the SELECT privilege and in GRANT.\n\nWhile at it, also add a test for \\dp on a property graph.\n\nAuthor: Shinya Kato \nReviewed-by: Ashutosh Bapat \nDiscussion: https://www.postgresql.org/message-id/flat/CAOzEurScgwLDXQmNFnDZANGAMMiva9GnLH_kO8qGtGVHUvVk2A%40mail.gmail.com", "completion": "doc: Add PROPERTY GRAPH to the access privilege tables"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nIt's necessary to copy the global 'fileencoding' to the buffer-local\nvalue before entering the buffer, otherwise 'fileencoding' is changed\nwhen reading the file, which will mark the file as modified.", "completion": "fix(ctx): missing options copy when loading hidden buffer #41149"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\ntest: add location info to no-void tests", "completion": "test: add error locations info to `no-void`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nClient:_get_registrations() errors if a documentSelector pattern is not\na valid glob (e.g. \"**/**.dart\" from dartls). The error discards\nalready-matched registrations and propagates to supports_method() and\nthe client/registerCapability handler, disabling capabilities unrelated\nto the offending pattern.\n\nSolution:\nSkip invalid globs. Treat them as non-matching, and log once per client.\n\n(Similar approach was taken for filewatcher globs: 4d9e5acfb5ee081b5b0761205c8a8c36ed7e49e5)", "completion": "fix(lsp): ignore (and log once) invalid documentSelector globs #41055"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nheap_force_common() tracked the current position in the caller-supplied\ntid[] using OffsetNumber, which is only 16 bits wide, so when the array\nheld more than 65535 entries, the updated index wrapped around and the\nouter loop never reached the exit condition. A SQL call with a\nsufficiently large TID array would then run until interrupted.\n\nFix by tracking the tid[] position using int instead of OffsetNumber.\nA regress case based on the report is included.\n\nAuthor: Andrey Rachitskiy \nReviewed-by: Andrey Borodin \nReported-by: Yuelin Wang <1217816127@qq.com>\nBackpatch-through: 14\nBug: #19607\nDiscussion: https://postgr.es/m/19607-2f256a66481c514b@postgresql.org", "completion": "pg_surgery: Fix infinite loop on large TID arrays"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe run-name of a dispatched workflow is parsed by two services, not one: the CI\nbot correlates a run with its check-run, and the Actions statistics collector\nattributes CI load to the pull request that caused it. Neither validates the\nstring, so a mis-copied run-name is silent in both. The comment named only the\nfirst reader, which understates what editing that line costs.\n\nAssisted-by: Claude Opus 5 (1M context) \n\nReviewed-by: Dmitry Misharov \nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nReviewed-by: Andrew Dinh \nMergeDate: Sat Aug 8 15:34:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32174)", "completion": "ci: name the second reader of the dispatch run-name"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThese three only run after the fact: compiler-zoo and run-checker-merge on a\npush, avx512-sde on a nightly cron. Their coverage therefore lands once a pull\nrequest is already merged, which is when it is most expensive to act on.\n\nGive all three the dispatch entry point the daily workflows already have:\nvalidated pr/head_sha/check_run_id inputs, the run-name both services correlate\non, concurrency keyed on the pull request, and every checkout pinned to the\nrequested commit.\n\nExisting behaviour is untouched. A push or a cron carries no inputs, so the\nvalidator is skipped and each checkout falls back to github.sha -- the build jobs\nstill run on a push to a fork branch, the only pre-merge signal a contributor\ngets here. The jitter library stays pinned to its release tag: a dispatched run\nmay choose the OpenSSL tree, never its dependencies.\n\nRefs: openssl/project#2027\n\nAssisted-by: Claude Opus 5 (1M context) \n\nReviewed-by: Dmitry Misharov \nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nReviewed-by: Andrew Dinh \nMergeDate: Sat Aug 8 15:34:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32174)", "completion": "ci: let the CI bot dispatch the compiler, merge and AVX512 zoos"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nMove all DNS related source files from lib to lib/vdns. Fix\ninclude paths, no furher changes.\n\nCloses #22482", "completion": "vdns: directory for all DNS related sources"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThese five suites only run nightly, so a break in a platform, a cross-compiled\ntarget, a fuzzer or an interop peer is found the morning after it merged. Give\neach the dispatch entry point the daily workflows already have, and adapt the\nones that assumed they only ever see their own default branch.\n\nos-zoo's self-hosted legs (ppc64le, s390x, riscv64) are restricted to the\nnightly cron and plain manual runs, keeping pull-request code off them; the\nGitHub-hosted legs gain the repository guard the rest of the file already had.\nThe cross-compile suites' test steps, gated by event name, now also run on a\ndispatch instead of silently skipping. oss-fuzz checks out the requested tree\nso CIFuzz fuzzes it instead of the default branch. interop-tests skips\nopenssh_interop on a dispatch, since it never checks this repo out.\n\nRefs: openssl/project#2027\n\nAssisted-by: Claude Opus 5 (1M context) \n\nReviewed-by: Milan Broz \nReviewed-by: Norbert Pocs \nMergeDate: Fri Aug 7 13:31:12 2026\n(Merged from https://github.com/openssl/openssl/pull/32175)", "completion": "ci: let the CI bot dispatch the platform, cross-compile, fuzzing and interop suites"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nProcessSingleRelationByOid called RelationGetSmgr(rel), discarded the\nresult, and then read rel->rd_smgr directly when looping over forks.\nOnly RelationGetSmgr is authorized to read that field since a relcache\ninvalidation resets rd_smgr to NULL.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Mihail Nikalayeu \nReviewed-by: ChangAo Chen \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/CADzfLwXGvb4Y-mqy8T+O0f_tkXR1sTDBGzP5Z=V_qcGnZ46rWg@mail.gmail.com\nBackpatch-through: 19", "completion": "Do not reuse rd_smgr in fork loop when enabling data checksums"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nBy default, `nvim` does not survive if its host terminal dies. This is\ninconvenient if you want to use Nvim as a \"session manager\" (like tmux).\n\nSolution:\nLet users opt-in to the \"survive\" behavior via `:detach!` (bang \"!\").\nThis marks the current UI as \"detachable\", so the server will not\nself-exit if the UI channel closes.", "completion": "feat(detach): opt-in to \"server keeps running\" #41133"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n100 buffered next-epoch records is far more than a normal handshake\never needs. A peer that has already completed its side of the epoch\ntransition may send more than one record under the new epoch before\nwe catch up and bump our own receive epoch - for example, application\ndata sent immediately once the peer considers the handshake done -\nbut real-world bursts like that are still small. Now that each entry\nonly costs as much memory as the record actually received, the limit\nmainly serves as a ceiling on worst-case per-connection memory use, so\nlower it to 16 to keep that ceiling smaller while still leaving ample\nheadroom over legitimate usage.\n\ndtls1_buffer_record() serves three queues here, so take the limit as an\nargument rather than tightening all of them. Only unprocessed_rcds gets\nthe lower limit: processed_rcds is filled from unprocessed_rcds and so\ncannot exceed it in any case, and buffered_app_data holds application\ndata that arrived between ChangeCipherSpec and Finished, which is not\nthe queue this ceiling is aimed at.\n\nAssisted-by: Claude:claude-opus-5\nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 15:40:45 2026", "completion": "ssl/record: lower the DTLS unprocessed_rcds queue limit"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAssigning a Boolean or special value (v:true/v:false/v:null/v:none) to a TTY\noption aborts:\n\n Assertion failed: (curval.type == newval.type), function ex_let_option, file vars.c, line 1408.\n 3 libsystem_c.dylib __assert_rtn + 284\n 4 nvim ex_let_one + 3308\n 5 nvim ex_let_vars + 112\n 6 nvim ex_let + 2356\n 7 nvim execute_cmd0 + 252\n 8 nvim do_cmdline + 9076\n 9 nvim call_user_func + 3320\n 10 nvim call_func + 2076\n 11 nvim get_func_tv + 696\n 12 nvim eval_func + 380\n 20 nvim eval_to_string_eap + 276\n 21 nvim eval_map_expr + 444\n 22 nvim vgetorpeek + 3172\n 23 nvim vgetc + 764\n\nSolution:\nApply the string-type check to TTY options too, so a Boolean/special value\ngives \"E928: String required\" instead of aborting. Valid string/number\nassignments to `t_*` pseudo-options still silently no-op.", "completion": "fix(options): crash on \":let &t_Co = v:true\" #41152"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor the affected OpenSSL built-in provider AEAD implementations,\nEVP_Cipher(ctx, out, NULL, 0) reaches the ccipher callback as a\nNULL-input terminal call. OCB and ChaCha20-Poly1305 took an early exit\non an empty message, with or without AAD, and returned success without\ncomparing an explicitly supplied tag. Consequently a corrupted tag was\naccepted before this change.\n\nMake these built-in callbacks perform their terminal tag operation,\naligning their explicit-tag handling with the streaming Final path\nwithout defining NULL input as part of the generic EVP_Cipher()\ncontract.\n\nAES-GCM-SIV also failed to generate a tag when Final was its first\nempty-message operation. Generate the tag in that case and propagate\nfailures from the matching empty-message decrypt operation.\n\nThe stable ChaCha20-Poly1305 implementation aliases Update to the\none-shot cipher callback, so this backport introduces a dedicated Update\ncallback to preserve zero-length Update as a no-op.\n\nFollow-up to #31555\nFixes #32258\nFixes CVE-2026-75803\n\nAssisted-by: Claude:claude-opus-4-8\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 5741d29a5f356e05262cd0936a472a9961398d53)\n\nCo-authored-by: Mounir IDRASSI \nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 17:43:24 2026\nMerged-from: https://github.com/openssl/openssl/pull/32417", "completion": "Check the tag on EVP_Cipher() finalize: Poly1305 and OCB AEADs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor the affected OpenSSL built-in provider AEAD implementations,\nEVP_Cipher(ctx, out, NULL, 0) reaches the ccipher callback as a\nNULL-input terminal call. OCB and ChaCha20-Poly1305 took an early exit\non an empty message, with or without AAD, and returned success without\ncomparing an explicitly supplied tag. Consequently a corrupted tag was\naccepted before this change.\n\nMake these built-in callbacks perform their terminal tag operation,\naligning their explicit-tag handling with the streaming Final path\nwithout defining NULL input as part of the generic EVP_Cipher()\ncontract.\n\nAES-GCM-SIV also failed to generate a tag when Final was its first\nempty-message operation. Generate the tag in that case and propagate\nfailures from the matching empty-message decrypt operation.\n\nThe stable ChaCha20-Poly1305 implementation aliases Update to the\none-shot cipher callback, so this backport introduces a dedicated Update\ncallback to preserve zero-length Update as a no-op.\n\nFollow-up to #31555\nFixes #32258\nFixes CVE-2026-75803\n\nAssisted-by: Claude:claude-opus-4-8\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 5741d29a5f356e05262cd0936a472a9961398d53)\n\nCo-authored-by: Mounir IDRASSI \nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 17:41:16 2026\nMerged-from: https://github.com/openssl/openssl/pull/32416", "completion": "Check the tag on EVP_Cipher() finalize: Poly1305 and OCB AEADs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor the affected OpenSSL built-in provider AEAD implementations,\nEVP_Cipher(ctx, out, NULL, 0) reaches the ccipher callback as a\nNULL-input terminal call. OCB and ChaCha20-Poly1305 took an early exit\non an empty message, with or without AAD, and returned success without\ncomparing an explicitly supplied tag. Consequently a corrupted tag was\naccepted before this change.\n\nMake these built-in callbacks perform their terminal tag operation,\naligning their explicit-tag handling with the streaming Final path\nwithout defining NULL input as part of the generic EVP_Cipher()\ncontract.\n\nAES-GCM-SIV also failed to generate a tag when Final was its first\nempty-message operation. Generate the tag in that case and propagate\nfailures from the matching empty-message decrypt operation.\n\nThe stable ChaCha20-Poly1305 implementation aliases Update to the\none-shot cipher callback, so this backport introduces a dedicated Update\ncallback to preserve zero-length Update as a no-op.\n\nFollow-up to #31555\nFixes #32258\nFixes CVE-2026-75803\n\nAssisted-by: Claude:claude-opus-4-8\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 5741d29a5f356e05262cd0936a472a9961398d53)\n\nCo-authored-by: Mounir IDRASSI \nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 15:58:27 2026\nMerged-from: https://github.com/openssl/openssl/pull/32259", "completion": "Check the tag on EVP_Cipher() finalize: Poly1305 and OCB AEADs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor the affected OpenSSL built-in provider AEAD implementations,\nEVP_Cipher(ctx, out, NULL, 0) reaches the ccipher callback as a\nNULL-input terminal call. OCB and ChaCha20-Poly1305 took an early exit\non an empty message, with or without AAD, and returned success without\ncomparing an explicitly supplied tag. Consequently a corrupted tag was\naccepted before this change.\n\nMake these built-in callbacks perform their terminal tag operation,\naligning their explicit-tag handling with the streaming Final path\nwithout defining NULL input as part of the generic EVP_Cipher()\ncontract.\n\nAES-GCM-SIV also failed to generate a tag when Final was its first\nempty-message operation. Generate the tag in that case and propagate\nfailures from the matching empty-message decrypt operation.\n\nOpenSSL 4.0 already has a dedicated ChaCha20-Poly1305 Update callback,\nso keep zero-length Update as a no-op there while allowing the\nNULL-input ccipher call to perform the terminal tag operation.\n\nFollow-up to #31555\nFixes #32258\nFixes CVE-2026-75803\n\nAssisted-by: Claude:claude-opus-4-8\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 5741d29a5f356e05262cd0936a472a9961398d53)\n\nCo-authored-by: Mounir IDRASSI \nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 15:56:02 2026\nMerged-from: https://github.com/openssl/openssl/pull/32300", "completion": "Check the tag on EVP_Cipher() finalize: Poly1305 and OCB AEADs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAt the EVP level, for AEADs EVP_Cipher(ctx, out, NULL, 0) performs\nfinalization. For consistency across AEADs (GCM, etc.), on decrypt it\nmust check the tag. OCB and ChaCha20-Poly1305 took an early exit on the\nempty message (with or without AAD) and returned success without\nchecking, so a forged tag (with or without AAD) was accepted before this\nchange.\n\nFollow-up to #31555\n\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Fri Aug 7 13:34:35 2026\n(Merged from https://github.com/openssl/openssl/pull/32173)", "completion": "Check the tag on EVP_Cipher() finalize: Poly1305 and OCB AEADs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: The frame layout debug log uses the obsolete window ID field.\n\nSolution: Use the window handle field when printing window information.", "completion": "refactor(window): use window handle in frame layout log"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nExisting text (e.g., create_foreign_table.sgml) uses server_name, not\nservername.", "completion": "doc: Make synopsis placeholders consistent"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nOK tb@", "completion": "Switch from imsg_get to imsgbuf_get and switch type of n to int."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nX509V3_EXT_d2i() may return NULL on malformed input\nor on allocation failure. v2i_AUTHORITY_KEYID() passed\nthat NULL to ASN1_STRING_length_ex() causing NULL dereference.\n\nFound by x509v3 fuzzer. Example fuzzer input:\n```\n[default]\nsubjectKeyIdentifier = DER:05:00\nauthorityKeyIdentifier = keyid\n```\n\nReviewed-by: Milan Broz \nReviewed-by: Viktor Dukhovni \nMergeDate: Fri Aug 7 14:03:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32177)", "completion": "Fix NULL dereference in v2i_AUTHORITY_KEYID()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nX509V3_EXT_d2i() may return NULL on malformed input\nor on allocation failure. v2i_AUTHORITY_KEYID() passed\nthat NULL to ASN1_STRING_length_ex() causing NULL dereference.\n\nFound by x509v3 fuzzer. Example fuzzer input:\n```\n[default]\nsubjectKeyIdentifier = DER:05:00\nauthorityKeyIdentifier = keyid\n```\n\nReviewed-by: Milan Broz \nReviewed-by: Viktor Dukhovni \nMergeDate: Fri Aug 7 14:03:05 2026\n(Merged from https://github.com/openssl/openssl/pull/32177)", "completion": "Fix NULL dereference in v2i_AUTHORITY_KEYID()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nX509V3_EXT_d2i() may return NULL on malformed input\nor on allocation failure. v2i_AUTHORITY_KEYID() passed\nthat NULL to ASN1_STRING_length_ex() causing NULL dereference.\n\nFound by x509v3 fuzzer. Example fuzzer input:\n```\n[default]\nsubjectKeyIdentifier = DER:05:00\nauthorityKeyIdentifier = keyid\n```\n\nReviewed-by: Milan Broz \nReviewed-by: Viktor Dukhovni \nMergeDate: Fri Aug 7 13:59:14 2026\n(Merged from https://github.com/openssl/openssl/pull/32177)", "completion": "Fix NULL dereference in v2i_AUTHORITY_KEYID()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nX509V3_EXT_d2i() may return NULL on malformed input\nor on allocation failure. v2i_AUTHORITY_KEYID() passed\nthat NULL to ASN1_STRING_length_ex() causing NULL dereference.\n\nFound by x509v3 fuzzer. Example fuzzer input:\n```\n[default]\nsubjectKeyIdentifier = DER:05:00\nauthorityKeyIdentifier = keyid\n```\n\nReviewed-by: Milan Broz \nReviewed-by: Viktor Dukhovni \nMergeDate: Fri Aug 7 13:43:20 2026\n(Merged from https://github.com/openssl/openssl/pull/32177)", "completion": "Fix NULL dereference in v2i_AUTHORITY_KEYID()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nX509V3_EXT_d2i() may return NULL on malformed input\nor on allocation failure. v2i_AUTHORITY_KEYID() passed\nthat NULL to ASN1_STRING_length_ex() causing NULL dereference.\n\nFound by x509v3 fuzzer. Example fuzzer input:\n```\n[default]\nsubjectKeyIdentifier = DER:05:00\nauthorityKeyIdentifier = keyid\n```\n\nReviewed-by: Milan Broz \nReviewed-by: Viktor Dukhovni \nMergeDate: Fri Aug 7 13:42:59 2026\n(Merged from https://github.com/openssl/openssl/pull/32177)", "completion": "Fix NULL dereference in v2i_AUTHORITY_KEYID()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPrevent AbortController.abort() from executing during Observable teardown when a FetchBackend HTTP request has already completed successfully or errored.\nPreviously, FetchBackend unconditionally called abort() upon stream termination. When requests completed normally, calling abort() after delivery caused Chromium-based browsers to mark the resolved request as net::ERR_ABORTED in DevTools due to a race condition, leading to missing response body payloads (\"Failed to load response data\"). By tracking whether the request has already settled—similar to XhrBackend checking for xhr.readyState !== xhr.DONE—we ensure abort() is only called for unsettled, in-flight requests upon unsubscription.\n\nFixes #70071\n\n(cherry picked from commit ef4dfead83ea8b3843b98a17ac572f2a380b1c46)", "completion": "fix(http): avoid aborting completed requests in FetchBackend"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPrevent AbortController.abort() from executing during Observable teardown when a FetchBackend HTTP request has already completed successfully or errored.\nPreviously, FetchBackend unconditionally called abort() upon stream termination. When requests completed normally, calling abort() after delivery caused Chromium-based browsers to mark the resolved request as net::ERR_ABORTED in DevTools due to a race condition, leading to missing response body payloads (\"Failed to load response data\"). By tracking whether the request has already settled—similar to XhrBackend checking for xhr.readyState !== xhr.DONE—we ensure abort() is only called for unsettled, in-flight requests upon unsubscription.\n\nFixes #70071", "completion": "fix(http): avoid aborting completed requests in FetchBackend"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nFound via readability-misleading-indentation warning in clangd.\n\nAuthor: Tristan Partin \nDiscussion: https://postgr.es/m/DKFO99FP6SLY.2O6A6BUK6P3OQ@partin.io", "completion": "Reindent conditional to improve readability"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMade according to the recomimendation of @ZenithalHourlyRate\n\nFixes #32229\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Milan Broz \nMerge-date: Thu Aug 13 07:02:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32270\n(cherry picked from commit 5597d48bee6d7feb3b8c87fef7bcc52f3a3da91c)", "completion": "CI: specify RISC-V vector extension version in QEMU"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMade according to the recomimendation of @ZenithalHourlyRate\n\nFixes #32229\n\nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Milan Broz \nMerge-date: Thu Aug 13 07:02:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32270", "completion": "CI: specify RISC-V vector extension version in QEMU"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo prevent creating a curl-development (aka debug-enabled, aka\n`-DENABLE_DEBUG=ON`, `--enable-debug` or `DEBUGBUILD`) build without\n`assert()`s. Since it may break expectations by missing to catch error\ncases. Also to make it less likely to build an inherently insecure\ndevelopment build by accident.\n\n- in CMake, for non-Multi-Config builds, show this error unless Debug\n configuration is set at configure-time:\n ```\n CMake Error at CMakeLists.txt:263 (message):\n Debug-enabled (aka development mode) curl requires the Debug configuration\n ```\n Ref: https://github.com/curl/curl/actions/runs/31159065911/job/92805128331?pr=22513#step:6:56\n The other 3 predefined configs (`Release`, `RelWithDebInfo`,\n `MinSizeRel`) set `NDEBUG` automatically.\n\n- or this message in other cases, e.g. when using CMake Multi-Config\n with non-Debug, e.g. `--config Release`, or passed `NDEBUG` manually\n with either build tools:\n ```\n curl_setup.h(1062): fatal error C1189: #error:\n \"Debug-enabled builds cannot be combined with NDEBUG\"\n ```\n Ref: https://github.com/curl/curl/actions/runs/31159628749/job/92807878479#step:9:28\n\nAlso:\n- INSTALL-CMAKE.md: document.\n- GHA/windows: adjust CI jobs to meet the above requirement, where\n missing.\n\nReported-by Stefan Eissing\nBug: https://github.com/curl/curl/pull/22484#discussion_r3730045572\nRef: ea984456804ab3ff1656a668fabdf734a32e379e #13592\nFixes #22481\nFixes #22484\n\nCloses #22513", "completion": "build: require `!NDEBUG` for debug-enabled (aka development) builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nget_dp_url() returned the internal ASN1_STRING data of a DIST_POINT URI\ndirectly. That data has an explicit length and is not necessarily NUL\nterminated, yet load_crl() and the HTTP client it hands the URI to consume\nit as a C string, reading past the buffer for a certificate carrying a\nprimitive-form IA5String URI in its CRL distribution points.\n\nReturn an allocated NUL terminated copy of the URI and free it in\nload_crl_crldp().\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't treat a CRL distribution point URI as a NUL terminated string"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nBuffer-local CWD (:bcd) is \"sticky\", similar to window-local CWD (:lcd).\nBut this contradicts one of its main benefits: per-buffer \"project root\"\nfor LSP, OSC7.\n\nOther problems:\n- A buffer created with :edit/:enew/:new silently inherits b_localdir\n (and b_prevdir) from the previous buffer.\n- curbuf_reusable() refuses to recycle a scratch buffer that has\n `b_localdir`.\n- After :new/:vnew/:tabnew the CWD sticks to previous buffer's\n `b_localdir` even though the new curbuf has none, so :new is not\n equivalent to \":split | enew\", and getcwd() disagrees with\n haslocaldir().\n- Requires \"which buffer spawned this buffer\" semantics that no other\n buffer-local state has.\n\nSolution:\nDrop sticky/inherit behavior of buffer-local CWD (:bcd).\n\n- do_ecmd: always apply the new curbuf's dir (`fix_current_dir`), like\n `do_autochdir` already does. :tabnew from a :bcd buffer now reverts to\n global CWD (and fires DirChanged), same as :tabnew from a :lcd window.\n- curbuf_reusable(): recycling a scratch buffer frees its b_localdir.\n\nTo get sticky/inherit behavior of CWD, use `:lcd`.", "completion": "fix(:bcd): do not \"inherit\" buffer-local dir"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, `parseCookieValue` did not strip enclosing double quotes (`DQUOTE`) from quoted cookie values as specified in RFC 6265 Section 4.1.1. In addition, malformed percent-encoding in cookie values caused an unhandled `URIError` when calling `decodeURIComponent`.\n\n(cherry picked from commit 280d09b16011e4f53f9e696fd95964943c6dcbfa)", "completion": "fix(http): strip RFC 6265 DQUOTE characters and handle URIError in parseCookieValue"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, `parseCookieValue` did not strip enclosing double quotes (`DQUOTE`) from quoted cookie values as specified in RFC 6265 Section 4.1.1. In addition, malformed percent-encoding in cookie values caused an unhandled `URIError` when calling `decodeURIComponent`.", "completion": "fix(http): strip RFC 6265 DQUOTE characters and handle URIError in parseCookieValue"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npathed.cnf and nocache-and-default.cnf hardcoded \"p_test.so\", but\nprovider modules use the platform's DSO extension (e.g. .dylib on\nmacOS), so the file never existed there.\n\nConvert both configs to build-time templates to\nfill in the correct extension.\nUpdate prov_config_test.c's presence check to use DSO_EXTENSION, and\nhave 30-test_prov_config.t read the generated build-tree file.\n\nAssisted-by: Claude:claude-sonnet-5\n\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Bob Beck \nMergeDate: Fri Aug 7 01:45:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32192)", "completion": "fix module extension on non-.so platforms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_new_session_ticket() assumed ssl_session_dup() calls\nSSLfatal() on failure but it never does, unlike all its other call\nsites which call SSLfatal() themselves. An allocation failure there\nmade the construct function return CON_FUNC_ERROR without entering\nthe fatal state, tripping the check_fatal assertion in\nwrite_state_machine() on debug builds.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Tomas Mraz \nMergeDate: Mon Aug 10 13:55:51 2026\n(Merged from https://github.com/openssl/openssl/pull/32183)\n\n(cherry picked from commit d271efc353856df91d28c8f54ead56b298c852f0)", "completion": "statem: fix missing SSLfatal in TLSv1.3 ticket construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_new_session_ticket() assumed ssl_session_dup() calls\nSSLfatal() on failure but it never does, unlike all its other call\nsites which call SSLfatal() themselves. An allocation failure there\nmade the construct function return CON_FUNC_ERROR without entering\nthe fatal state, tripping the check_fatal assertion in\nwrite_state_machine() on debug builds.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Tomas Mraz \nMergeDate: Mon Aug 10 13:55:51 2026\n(Merged from https://github.com/openssl/openssl/pull/32183)", "completion": "statem: fix missing SSLfatal in TLSv1.3 ticket construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update domino digest to e0779df"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis version of pkcs11-provider has been fixed to work with\nOpenSSL ASN1 changes and the test passes again.\n\nSigned-off-by: Simo Sorce \n\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Milan Broz \nMergeDate: Thu Aug 6 12:16:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32180)", "completion": "Update pkcs11-provider and drop test disablement"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 96b80424c787f7a278b543c19f2c2364041761f4)", "completion": "docs: fix supported Node.js version in installation prerequisites"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAssigning to the local value of a global-local boolean option\n('autoread', 'autocomplete', 'fsync') aborts:\n\n Assertion failed: (curval.type == newval.type), function\n ex_let_option, file vars.c, line 1408.\n\n ex_let_one\n ex_let_vars\n ex_let\n execute_cmd0\n do_cmdline\n call_user_func\n ...\n eval_map_expr\n vgetorpeek\n vgetc\n state_enter\n main\n\nA global-local option may have local value `kObjectTypeUnset`, but\n`ex_let_option()` guards only `kObjectTypeNil`.\n\nSolution:\nWhen curval is Unset, resolve it to the inherited global value.", "completion": "fix(options): crash on \":let &l:autoread = v:true\" #41158"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nIgnore is linked to Normal by default, making the text visible instead\nof hidden.\n\nSolution:\nReplace the default link with an explicit highlight definition using\nctermfg=0 guifg=bg.", "completion": "fix(highlight): make Ignore hidden by default #41115"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDuplicate integer value fields in the policyConstraints,\nbasicConstraints and basicAttConstraints extensions overwrite\npreviously allocated ASN1_INTEGER values without freeing them.\n\nFound by : x509v3 fuzzer\n\nExample 1: (crypto/x509/v3_pcons.c)\n```\n[default]\npolicyConstraints = requireExplicitPolicy:1,requireExplicitPolicy:2\n```\n\nExample 2: (crypto/x509/v3_bcons.c)\n```\n[default]\nbasicConstraints = pathlen:1,pathlen:2\n```\n\nExample 3: (crypto/x509/v3_battcons.c)\n```\n[default]\nbasicAttConstraints = pathlen:1,pathlen:2\n```\nAssisted-by: ChatGPT:gpt-5.6\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Sun Aug 9 04:06:32 2026\n(Merged from https://github.com/openssl/openssl/pull/32181)", "completion": "Fix memory leaks in x509v3 config handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, uuid_extract_timestamp() returned NULL for UUIDv6 values,\neven though it already extracted timestamps from UUIDv1 and\nUUIDv7.\n\nThis commit adds a UUIDv6 branch that reassembles the timestamp from\nthat layout and then converts it exactly as the UUIDv1 branch does. We\nprovide no uuidv6() generator, but such values can be produced by\nclient applications and stored in the database, just as UUIDv1 values\nalready are.\n\nAuthor: Tristan Partin \nReviewed-by: Miłosz Bieniek \nReviewed-by: Masahiko Sawada \nDiscussion: https://postgr.es/m/DJHJW50YWKIT.XIOT4NOZRQ03@partin.io", "completion": "Support UUIDv6 in uuid_extract_timestamp()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n\n FAILED …/plugin/zip_spec.lua @ 442: nvim.zip reports an incorrect archive password\n Expected values to be equal.\n Expected:\n true\n Actual:\n false\n stack traceback:\n …/plugin/zip_spec.lua:453: in function <…/plugin/zip_spec.lua:442>\n\nSolution:\nThe message is scheduled, so poll for it.", "completion": "test: unreliable \"nvim.zip … incorrect password\" #41159"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSeveral subsystems need to derive a short, filesystem-safe identifier from an\narbitrary path, and each reinvents it ad-hoc:\n- `'undodir'` and `swapfiles` encode the full path into a single filename, which\n may exceed filesystem length-limits.\n- `:connect ssh://` needs the SSH ControlPath socket name to stay under the\n 104-byte `sun_path` limit on macOS; today the path overflows it.\n- the upcoming :terminal state dir.\n- arbitrary plugin purposes.\n\nSolution:\nProvide `vim.fs.slug()`, which generates a bounded, one-way filename from an\narbitrary string. The input is normalized so equivalent paths produce the\nsame result. An 8-char hash is appended for uniqueness", "completion": "feat(lua): vim.fs.slug() #41005"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSome assertions are erroneously skipped for `not is_os('win')`.\n\nSolution:\nUpdate tests. Deduplicate logic.", "completion": "test(chdir): cleanup #41161"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe timestamp-reassembly expressions in uuid_extract_timestamp() are\nchains of shifted octets whose shift counts encode the field layout of\neach UUID version, which is not otherwise recoverable from the code.\n\nThis commit documents, for UUIDv1, UUIDv6, and UUIDv7 alike, which\noctets carry which part of the timestamp and where each part lands in\nthe reassembled value, citing the RFC section that defines it.\n\nAuthor: Tristan Partin \nReviewed-by: Miłosz Bieniek \nReviewed-by: Masahiko Sawada \nDiscussion: https://postgr.es/m/DJHJW50YWKIT.XIOT4NOZRQ03@partin.io", "completion": "Add comments to uuid_extract_timestamp()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUpdating the CHANGES.md for all the changes added via the DTLS1.3\nfeature branch.\n\nFixes: openssl/project#2039\nAssisted-by: Claude:claude-opus-4-8\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 14:52:30 2026\n(Merged from https://github.com/openssl/openssl/pull/32182)", "completion": "DTLS 1.3 Update CHANGES.md"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nXLogRecordAssemble() refuses records larger than XLogRecordMaxSize when\ngenerating records, but the reader-side only checked a minimal number\nfor xl_tot_len.\n\nA crafted multi-page record with xl_tot_len near UINT32_MAX could bypass\nthe contrecord length checks, overflow allocate_recordbuf()'s size math,\nand corrupt memory during reassembly (or hit related asserts under\ncassert).\n\nxlogreader.c is updated to check that the received record is never\nlarger than XLogRecordMaxSize, when first receiving the first bytes of\nxl_tot_len, then again when validating the record header.\n\nWAL is a source of data trusted by the server, with CRC32 checksums\nproviding a level of protection before replaying the records if data is\ncorrupted. These limits could be internally reached only with crafted\nWAL records, which is something that analyzers (named as LLMs) like\ncomplaining about these days.\n\n039_end_of_wal.pl is adjusted according to the new maximum limit, a test\nfor XLogRecordMaxSize is added.\n\nAuthor: David Karapetyan \nAuthor: Matthias van de Meent \nDiscussion: https://postgr.es/m/CALmTjZBddzeGVU2o1JNZb3mPvV68PqDskWPAUQBVb-35yVkiwA@mail.gmail.com", "completion": "Improving handling of oversized records in xlogreader.c"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit c0d9864f5ce made all but one caller of visibilitymap_clear() check\nits return value, causing Coverity to flag the remaining unchecked call\nin heap_page_fix_vm_corruption().\n\nThis VM clear is not WAL-logged, so the caller doesn't need the return\nvalue of visibilitymap_clear(). Add an explicit void cast and comment to\ndocument that the return value is intentionally ignored.\n\nBackpatch to 19 when the number of callers discarding the return value\ndropped low enough to trigger Coverity's warning.\n\nDiscussion: https://postgr.es/m/1065814.1784514869%40sss.pgh.pa.us\nReported-by: Tom Lane \nBackpatch-through: 19", "completion": "Silence Coverity warning about unused visibilitymap_clear() result"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: A winbar-only window with zero text height still occupies one row,\n but win_update() returns early on w_view_height == 0 and skips the\n vertical separator.\n\nSolution: Also draw the vertical separator in the early return path.", "completion": "fix(ui): missing vertical separator for a winbar only window"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nport_default_packet_handler() may perform double free of qrx\nwhen channel creation fails. The port_default_packet_handler()\ntransfers ownership of qrx to channel/connection via call to\nport_bind_channel(). The port_bind_channel() however may\nrelease the qrx when channel can not be bound. The error is\nthen detected in port_default_packet_handler() which then agains\nreleases qrx for the second time.\n\nThe fix is to add a reference counter to QRX object so transfer\nof ownership between port_default_packet_handler() and QUIC_CHANNEL\ncan be handled safely.\n\nFixes CVE-2026-18798\n\nReviewed-by: Igor Ustinov \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 15:47:02 2026", "completion": "Avoid double free of qrx in port_default_packet_handler()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nport_default_packet_handler() may perform double free of qrx\nwhen channel creation fails. The port_default_packet_handler()\ntransfers ownership of qrx to channel/connection via call to\nport_bind_channel(). The port_bind_channel() however may\nrelease the qrx when channel can not be bound. The error is\nthen detected in port_default_packet_handler() which then agains\nreleases qrx for the second time.\n\nThe fix is to add a reference counter to QRX object so transfer\nof ownership between port_default_packet_handler() and QUIC_CHANNEL\ncan be handled safely.\n\nFixes CVE-2026-18798\n\nReviewed-by: Igor Ustinov \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 15:48:03 2026", "completion": "Avoid double free of qrx in port_default_packet_handler()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nport_default_packet_handler() may perform double free of qrx\nwhen channel creation fails. The port_default_packet_handler()\ntransfers ownership of qrx to channel/connection via call to\nport_bind_channel(). The port_bind_channel() however may\nrelease the qrx when channel can not be bound. The error is\nthen detected in port_default_packet_handler() which then agains\nreleases qrx for the second time.\n\nThe fix is to add a reference counter to QRX object so transfer\nof ownership between port_default_packet_handler() and QUIC_CHANNEL\ncan be handled safely.\n\nFixes CVE-2026-18798\n\nReviewed-by: Igor Ustinov \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 15:46:33 2026", "completion": "Avoid double free of qrx in port_default_packet_handler()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nport_default_packet_handler() may perform double free of qrx\nwhen channel creation fails. The port_default_packet_handler()\ntransfers ownership of qrx to channel/connection via call to\nport_bind_channel(). The port_bind_channel() however may\nrelease the qrx when channel can not be bound. The error is\nthen detected in port_default_packet_handler() which then agains\nreleases qrx for the second time.\n\nThe fix is to add a reference counter to QRX object so transfer\nof ownership between port_default_packet_handler() and QUIC_CHANNEL\ncan be handled safely.\n\nFixes CVE-2026-18798\n\nReviewed-by: Igor Ustinov \nReviewed-by: Andrew Dinh \nMerge-date: Mon Aug 24 15:46:13 2026", "completion": "Avoid double free of qrx in port_default_packet_handler()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #14403", "completion": "fix(v-model): preserve text input before hydration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nKeep the charset handling added in #70062 limited to text responses. JSON\nbytes must stay UTF-8 regardless of the Content-Type charset.\n\nFetch defines Body.json() using \"parse JSON from bytes\". Infra specifies that\nstep as: \"Let string be the result of running UTF-8 decode on bytes.\"\n\nhttps://fetch.spec.whatwg.org/#dom-body-json\nhttps://infra.spec.whatwg.org/#parse-json-bytes-to-a-javascript-value\n(cherry picked from commit 09bc90003ed6e9f6c166e885503728af49d1af67)", "completion": "fix(http): always decode JSON responses as UTF-8"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nKeep the charset handling added in #70062 limited to text responses. JSON\nbytes must stay UTF-8 regardless of the Content-Type charset.\n\nFetch defines Body.json() using \"parse JSON from bytes\". Infra specifies that\nstep as: \"Let string be the result of running UTF-8 decode on bytes.\"\n\nhttps://fetch.spec.whatwg.org/#dom-body-json\nhttps://infra.spec.whatwg.org/#parse-json-bytes-to-a-javascript-value", "completion": "fix(http): always decode JSON responses as UTF-8"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #9239\nclose #12569", "completion": "fix(compiler-core): preserve vnode lifecycle in stable v-for"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Viktor Dukhovni \nReviewed-by: Paul Dale \nMergeDate: Fri Aug 7 09:58:28 2026\n(Merged from https://github.com/openssl/openssl/pull/32191)", "completion": "FIPS: key gen PCT tests no longer cause FIPS provider to enter a unrecoverable error state."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Viktor Dukhovni \nReviewed-by: Paul Dale \nMergeDate: Fri Aug 7 09:57:46 2026\n(Merged from https://github.com/openssl/openssl/pull/32191)", "completion": "FIPS: key gen PCT tests no longer cause FIPS provider to enter a unrecoverable error state."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nClarify how special wal_sender_shutdown_timeout values affect shutdown\nwaiting. A value of -1 disables the shutdown timeout and lets the\nWAL sender wait for the receiver to catch up, while 0 causes immediate\ntermination without waiting for catch-up. Positive values bound how long\nshutdown waits, so document that they should be high enough for WAL data\nto be replicated under normal circumstances.\n\nUpdate the main documentation, the GUC long description, and\npostgresql.conf.sample consistently. While here, fix nearby paragraph\nindentation and spacing.\n\nBackpatch to v19, where wal_sender_shutdown_timeout was introduced.\n\nAuthor: Chao Li \nReviewed-by: Ian Barwick \nReviewed-by: Daniel Gustafsson \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/AF4FE756-A220-4DA7-87B7-A126F3F307FD@gmail.com\nBackpatch-through: 19", "completion": "doc: Clarify wal_sender_shutdown_timeout values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit e646450e609 added DETAIL messages for XID and MultiXactId\nwraparound warnings that described the reported percentage as the\npercentage of IDs available for use. However, the percentage is actually\ncalculated from the remaining distance to the wraparound limit, not the\nstop limit where new IDs are refused. As a result, the wording could be\nmisinterpreted as meaning that the reported percentage of IDs can still\nbe allocated.\n\nUpdate the wording to clarify that the reported percentage represents the\nremaining transaction ID space or MultiXactId space before wraparound.\n\nAlso update the related XID warning hints to use \"transaction ID\"\nterminology consistently.\n\nBackpatch to v19, where the DETAIL messages were added.\n\nAuthor: Fujii Masao \nReviewed-by: Bharath Rupireddy \nReviewed-by: Kyotaro Horiguchi \nReviewed-by: Nathan Bossart \nReviewed-by: Yugo Nagata \nDiscussion: https://postgr.es/m/CAHGQGwHWZTsR6bjdfpa+pOkBPjoXXm2LuJ+5nh+CvdyqEASHcQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Clarify wraparound warning percentage messages"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit edee0c621de, and the equivalent v17 commit f2353dd71724,\nchanged the runtime XID wraparound messages to use \"transaction IDs\"\nterminology, but one corresponding error example in maintenance.sgml\nstill used the older XID wording.\n\nUpdate that documentation example in line with the current runtime\nmessage.\n\nBackpatch to v17, where the runtime messages were changed.\n\nAuthor: Fujii Masao \nReviewed-by: Yugo Nagata \nDiscussion: https://postgr.es/m/CAHGQGwHTN-Xc5iDtbzNSjfxuab5Y9qAArw8cB4PrrDJpZ+1fgA@mail.gmail.com\nBackpatch-through: 17", "completion": "doc: Update XID wraparound error example"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #12124", "completion": "fix(custom-element): warn when props override native properties"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n\"here is your component/global tokens\" doesn't agree with the plural\n\"tokens\". This copy is rendered inside the Component Token / Global\nToken demo shown on every component's docs page via ComponentTokenTable.", "completion": "docs: subject-verb agreement in ComponentTokenTable locale"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nConfigure esbuild with supported 'async-await': false in esbuild-base.config.mts so esbuild downlevels async functions and async generators natively.\n\nThis allows removing the custom Babel plugin @babel/plugin-transform-async-generator-functions and downlevelAsyncGeneratorsIfPresent option.", "completion": "refactor(devtools): rely on esbuild to downlevel async generators"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRemove the supported 'async-await': false option in esbuild-base.config.mts as Angular DevTools is zoneless and does not require downleveling async/await syntax.", "completion": "refactor(devtools): remove async-await downleveling as devtools is zoneless"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis adds completion for CASCADE and RESTRICT, similar to what\ncompletion of other DROP commands provides.\n\nAuthor: Peter Smith \nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/CAHut+PuHsLupVWZ9SUeKm=jKR34wYP6qAZPoOHFhU3uDbx34wQ@mail.gmail.com", "completion": "More tab-completion for DROP PROPERTY GRAPH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nOn Windows, the init code calls `SetConsoleCtrlHandler()`, and before\nthis patch also set handlers for all Unixy signals. Of these, `SIGBREAK`\n(used on Windows-only), `SIGINT`, `SIGABRT` and `SIGTERM` were also\nsetting up a `SetConsoleCtrlHandler()`, in addition to the call made\ndirectly. (The rest, `SIGHUP`, `SIGPIPE`, `SIGALRM` are either missing\nthe macros, or ignored by `signal()` on Windows.)\n\nAs per WINE sources, `SetConsolCtrlHandler(, TRUE)` calls are\nadditive, which means the test server set up two console ctrl handlers.\n\nThen the ctrl handler set directly (`ctrl_event_handler()`), was\ntriggering the other signal handler via `raise()`, for the 'initiate\nexit' logic, which in turn triggered exiting a wait within `select_ws()`\nand other loops. The Windows window handler also made use of the\n`SIGTERM` event to initiate exit via `raise()` and the second signal\nhandler.\n\nTo simplify, de-duplicate the ctrl handlers by dropping `signal()` calls\nand keeping the direct Win32 call with `ctrl_event_handler()` doing all\nthe signal handling on Windows. Break out the 'initiate exit' logic into\na function and call it from both Unix and Windows signal/ctrl/window\nhandlers. Also drop calling `raise()` on exit, because it's a no-op\nwithout a `signal()` pair.\n\nAlso:\n- drop logging the actual ctrl type number, replace with just logging\n whether we handled the event, in `ctrl_event_handler()`. To avoid\n using non-signal-safe functions (e.g. `fprintf()`) from the handler.\n- also replace `logmsg()` with `WriteFile()` to prevent regressions.\n Ref: #22045\n- replace `logmsg()` with `WriteFile()` in `main_window_proc()`.\n- fix to forward ctrl handling to the OS in the rare case of failed\n `exit_event` initialization on startup. To swap a possible hang\n (within `WaitForMultipleObjectsEx()`) with an ungraceful shutdown.\n- add support for an 'exit message' string, set by signal/ctrl handlers,\n and log it on app exit. To avoid the need to deal with logging within\n the handlers,", "completion": "servers: drop duplicate (and interacting) ctrl handlers on Windows, add exit message"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nhashbulkdelete() fetched the relcache's cached hash metapage before\ncalling read_stream_begin_relation(). During the read stream\ninitialization, relation lookups may process pending relcache\ninvalidation messages, which could cause the cached metapage to be\ninvalidated before the read stream uses it, leading to the failure of a\nVACUUM bulk-deletion for a hash index.\n\nThis commit reworks the order of hashbulkdelete() so as its read stream\nis initialized before fetching the cached metapage, so as pending\ninvalidation messages do not interfere with the relation scan.\n\nIssue introduced by bfa3c4f106b1.\n\nAuthor: Mikhail Nikalayeu \nReviewed-by: Bertrand Drouvot \nReviewed-by: Nazir Bilal Yavuz \nReviewed-by: Xuneng Zhou \nDiscussion: https://postgr.es/m/CADzfLwVEJ2_7ioX3ZSB1P7qXW40ghUy_ZCzeFvhDLoa_3Muztg@mail.gmail.com\nBackpatch-through: 19", "completion": "Initialize read stream before fetching metapage in hash bulk-deletion"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nhttp2: make server push transfers inherit share from parent\n\nReported-by: Stephan Zeisberg\nCloses #22488", "completion": "CVE-2026-18924: HTTP/2 server push UAF"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from 90325ff0444cbdff368bda5d2\n\nhttp2: make server push transfers inherit share from parent\n\nReported-by: Stephan Zeisberg\nCloses #22488", "completion": "CVE-2026-18924: HTTP/2 server push UAF"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReported-by: Stephan Zeisberg\nCloses #22488", "completion": "http2: make server push transfers inherit share from parent"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Tour): remove unusable per-step indicatorsRender/actionsRender types\n\n* test(Tour): drop type-only assertion, already enforced by tsc", "completion": "fix(Tour): remove unusable per-step indicatorsRender/actionsRender types"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe COLUMNS list of a GRAPH_TABLE query is parsed as an ordinary select\ntarget list, which permits aggregate functions, window functions, and\nset-returning functions. GRAPH_TABLE has no machinery to evaluate them,\nthough: the rewriter copies the COLUMNS target list verbatim into a\nfreshly built subquery whose hasAggs/hasWindowFuncs/hasTargetSRFs flags\nare never set, so the planner builds no Agg/WindowAgg node (and no SRF\nexpansion) and the Aggref/WindowFunc/SRF reaches the executor. This\ntriggers an assertion failure (\"ecxt_aggvalues != NULL\"), or \"Aggref\nfound in non-Agg plan node\" on a non-assert build, for otherwise\nparser-accepted SQL such as\n\n SELECT max(c) FROM GRAPH_TABLE\n (g MATCH (x IS v) COLUMNS (count(*) AS c));\n\nReject these constructs in transformRangeGraphTable() the same way\nsubqueries are already handled: save and clear pstate->p_hasAggs,\np_hasWindowFuncs, and p_hasTargetSRFs around the transformation of the\nCOLUMNS list, and raise a \"not supported\" error if any of them got set.\n\nThis is deliberately a blanket prohibition for now. Once quantified\nelement patterns such as (a)->{1,5} are supported, aggregates over\nproperty references of higher degree (e.g. count(a) or sum(a.val)) can\nbe allowed; at that point the check will need to inspect the aggregate\narguments rather than reject all aggregates outright.\n\nAuthor: Ewan Young \nReviewed-by: Ashutosh Bapat \nDiscussion: https://www.postgresql.org/message-id/flat/CAON2xHOYAmYLkB2jGi6g77d6Fqv8YgOrfV-riQVf0K_7AdxD3w@mail.gmail.com", "completion": "Disallow aggregates, window functions, and SRFs in GRAPH_TABLE COLUMNS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n- Explicit `:bcd` (etc.) persists from `nvim_buf_call()` but not from an\n autocmd handler targeting a hidden buf (`LspAttach`, `TermRequest`, …),\n which needs a `vim.schedule()` workaround.\n- `vim._with()` is supposed to work as a \"sandbox\", discarding\n side-effects, but it leaks CWD changes: `:lcd` from a `win` context,\n any chdir from a visible-buffer context.\n\nSolution:\n- Explicit :cd/:tcd/:bcd during a temp context persists by default.\n - \"Ambient\" directory changes ('autochdir', existing win-local CWD,\n etc.) are still undone, as before.\n- Add `kCtxKeepDirs`: snapshot/restore the target's full CWD state\n (w/b/tp-local, global, cwd). Used by `vim._with()` and `'inccommand'`,\n which must not leak state.", "completion": "feat(cwd): support explicit chdir (:bcd/:tcd/…) in temp context"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRefactor the devtools optimization esbuild plugin to use JavaScriptTransformer from @angular/build/private.", "completion": "refactor(devtools): use JavaScriptTransformer for Angular optimization esbuild plugin"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nseq_search_localized() returns the length of the matching prefix in\n*len, but because it internally case-folds the inputs, it gets\nconfused on the length. The caller expects to get the length of the\nprefix in the original string, but what it actually returns is the\nlength of the prefix after case-folding, which can be different if the\ncase-folded characters have different byte-length than the original,\nor with ICU, if the case-folding changes the number of characters\n(e.g. \"ß\", the German double s).\n\nTo fix, once we have determined that we have a match, work harder to\nfind the match's length in the original string. This adds some\noverhead, but the strings are expected to be short.\n\nThe function does \"case-folding\" by converting a string to upper-case,\nthen to lower-case, which is a little ugly given that we have\ndedicated functions for case-folding nowadays. But switching to that\ndoesn't seem appropriate to backpatch in a security fix, and that's\nnot available in older stable versions, anyway.\n\nAuthor: Heikki Linnakangas ", "completion": "Fix calculating length of match to localized month/weekday names"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: An OSC 52 sequence from a :terminal job passes the decoded\npayload to the clipboard provider as a single list item. Command-line\nproviders (pbcopy, xclip, ...) receive it with channel semantics, where\na newline inside an item is sent as NUL (:h chansend()), so multiline\ncopies arrive with NUL bytes instead of newlines.\n\nSolution: Split the payload on newlines into a proper list of lines.\nA trailing newline yields a final empty item, which chansend() turns\nback into a newline, so payloads round-trip exactly.\n\n(cherry picked from commit e58f29ca3e6935af5b14879db1e8f2b959555c10)", "completion": "fix(terminal): OSC 52 multiline copy replaces newlines with NUL #41097"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: An OSC 52 sequence from a :terminal job passes the decoded\npayload to the clipboard provider as a single list item. Command-line\nproviders (pbcopy, xclip, ...) receive it with channel semantics, where\na newline inside an item is sent as NUL (:h chansend()), so multiline\ncopies arrive with NUL bytes instead of newlines.\n\nSolution: Split the payload on newlines into a proper list of lines.\nA trailing newline yields a final empty item, which chansend() turns\nback into a newline, so payloads round-trip exactly.", "completion": "fix(terminal): OSC 52 multiline copy replaces newlines with NUL #41097"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso: shorten code.\n\nReported by Copilot\nBug: https://github.com/curl/curl/pull/22487#pullrequestreview-4863399903\n\nCloses #22489", "completion": "servers: fix HANDLE leak in UWP builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nURL: https://curl.se/mail/lib-2026-08/0003.html\nCloses #22490", "completion": "DEPRECATE.md: HTTP/2 Server Push gets removed in March 2027"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n`strlen()` is only guaranteed to be signal-safe since POSIX.1-2008.\n\nRef: https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html#tag_02_04_03\n\nReported by Copilot\nBug: https://github.com/curl/curl/pull/22487#pullrequestreview-4863961494\nFollow-up to e95f509c66abdd88ae02e3243cdc217f19c4a330 #16852\n\nCloses #22491", "completion": "servers: fix to avoid a non-signal-safe call in signal handler"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- makes test names less complicated\n\n- makes them less likely to wrap lines when using narrow terminals\n\n- runtests now returns error for the test if the name is longer\n\n- replace the \"...\" with a singe space\n\nCloses #22492", "completion": "tests: keep test names shorter than 70 columns"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThese `SIG*` macro are provided by all supported Windows toolchains.\n\nCherry-picked from #22487\n\nCloses #22493", "completion": "servers: drop redundant guards on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSuggested-by: Marcel Jamin\nURL: https://curl.se/mail/lib-2026-08/0002.html\nURL: https://daniel.haxx.se/blog/2024/08/14/slow-tcp-connect-on-windows/\n\nCloses #22494", "completion": "cf-socket: disable TCP SYN retransmissions for localhost on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSuggested-by: Marcel Jamin\nURL: https://curl.se/mail/lib-2026-08/0002.html\n\nCloses #22494", "completion": "cf-socket: disable TCP SYN retransmissions for localhost on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA WPACKET failure in tls_construct_server_compressed_certificate()\nreturned CON_FUNC_ERROR without calling SSLfatal(), unlike the\nidentical failure handling in tls_construct_server_certificate().\nThis trips the check_fatal assertion in write_state_machine() on\ndebug builds and skips the alert and error state otherwise.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:34:32 2026\n(Merged from https://github.com/openssl/openssl/pull/32197)", "completion": "statem: add missing SSLfatal in compressed certificate construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA WPACKET failure in tls_construct_server_compressed_certificate()\nreturned CON_FUNC_ERROR without calling SSLfatal(), unlike the\nidentical failure handling in tls_construct_server_certificate().\nThis trips the check_fatal assertion in write_state_machine() on\ndebug builds and skips the alert and error state otherwise.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:34:19 2026\n(Merged from https://github.com/openssl/openssl/pull/32197)", "completion": "statem: add missing SSLfatal in compressed certificate construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA WPACKET failure in tls_construct_server_compressed_certificate()\nreturned CON_FUNC_ERROR without calling SSLfatal(), unlike the\nidentical failure handling in tls_construct_server_certificate().\nThis trips the check_fatal assertion in write_state_machine() on\ndebug builds and skips the alert and error state otherwise.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:34:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32197)", "completion": "statem: add missing SSLfatal in compressed certificate construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA WPACKET failure in tls_construct_server_compressed_certificate()\nreturned CON_FUNC_ERROR without calling SSLfatal(), unlike the\nidentical failure handling in tls_construct_server_certificate().\nThis trips the check_fatal assertion in write_state_machine() on\ndebug builds and skips the alert and error state otherwise.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:33:56 2026\n(Merged from https://github.com/openssl/openssl/pull/32197)", "completion": "statem: add missing SSLfatal in compressed certificate construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA WPACKET failure in tls_construct_server_compressed_certificate()\nreturned CON_FUNC_ERROR without calling SSLfatal(), unlike the\nidentical failure handling in tls_construct_server_certificate().\nThis trips the check_fatal assertion in write_state_machine() on\ndebug builds and skips the alert and error state otherwise.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:33:44 2026\n(Merged from https://github.com/openssl/openssl/pull/32197)", "completion": "statem: add missing SSLfatal in compressed certificate construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit e077455e9e dropped the SSLfatal() call together with the\nERR_R_MALLOC_FAILURE cleanup in nss_keylog_int(). Since then an\nallocation failure there propagates a plain zero return through\nssl_log_secret() and ssl_log_rsa_client_key_exchange() callers whose\n\"SSLfatal() already called\" comments no longer hold, tripping the\ncheck_fatal assertion in the state machine on debug builds when a\nkeylog callback is set.\n\nCommit 7d78cd722b papered over one symptom of this by calling SSLfatal()\ndirectly at the early exporter secret call site in\ntls13_change_cipher_state(). With the call restored at the source that\nwould now invoke SSLfatal() twice, pushing a duplicate entry on the\nerror queue, so revert that call site back to the\n\"SSLfatal() already called\" comment used by all the other callers.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMerge-date: Thu Aug 27 13:54:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32196\n(cherry picked from commit dde995f2913bf825bbd0e9c25af4c75caf917a10)", "completion": "ssl: restore missing SSLfatal in keylog output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit e077455e9e dropped the SSLfatal() call together with the\nERR_R_MALLOC_FAILURE cleanup in nss_keylog_int(). Since then an\nallocation failure there propagates a plain zero return through\nssl_log_secret() and ssl_log_rsa_client_key_exchange() callers whose\n\"SSLfatal() already called\" comments no longer hold, tripping the\ncheck_fatal assertion in the state machine on debug builds when a\nkeylog callback is set.\n\nCommit 7d78cd722b papered over one symptom of this by calling SSLfatal()\ndirectly at the early exporter secret call site in\ntls13_change_cipher_state(). With the call restored at the source that\nwould now invoke SSLfatal() twice, pushing a duplicate entry on the\nerror queue, so revert that call site back to the\n\"SSLfatal() already called\" comment used by all the other callers.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMerge-date: Thu Aug 27 13:54:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32196", "completion": "ssl: restore missing SSLfatal in keylog output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:29:11 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:28:59 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:28:48 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:28:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:28:26 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAn allocation failure for the PSK premaster secret buffer in\nssl_generate_master_secret() returned failure without calling\nSSLfatal(), while its callers on both the client key exchange\nconstruction and processing paths assume the fatal state was\nalready set. Also cover the unreachable no-PSK fallback branch.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMergeDate: Tue Aug 11 07:28:05 2026\n(Merged from https://github.com/openssl/openssl/pull/32195)", "completion": "ssl: add missing SSLfatal in PSK premaster secret generation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe first CRYPTO_THREAD_read_lock() failure in\nssl_generate_session_id() returned failure without calling SSLfatal()\nwhile the second lock right below does, and callers such as\ntls_construct_new_session_ticket() assume the fatal state was\nalready set. This should currently not happen as the read lock does\nnot realistically fail, so this is just future proofing of the error\nhandling.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:31:08 2026\n(Merged from https://github.com/openssl/openssl/pull/32200)", "completion": "ssl: add missing SSLfatal on session ID lock failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls13_final_finish_mac() returned failure on a NULL handshake digest\nwithout calling SSLfatal() or raising any error, while its callers on\nthe Finished construction and processing paths assume the fatal state\nwas already set. This should currently not happen as the handshake\ndigest must have been fetched successfully earlier in the handshake,\nso this is just future proofing of the error handling.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 07:49:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32198)", "completion": "ssl: add missing SSLfatal in TLSv1.3 finished MAC computation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_ctos_padding() returned EXT_RETURN_FAIL on a\nnon-positive digest size without calling SSLfatal(), propagating to\nCON_FUNC_ERROR in the ClientHello construction without the fatal\nstate set. This should currently not happen as ssl_md() only returns\ndigests with a positive size, so this is just future proofing of the\nerror handling.\n\nAssisted-by: Claude:claude-fable-5\n\nReviewed-by: Matt Caswell \nReviewed-by: Frederik Wedel-Heinen \nMergeDate: Tue Aug 11 08:45:51 2026\n(Merged from https://github.com/openssl/openssl/pull/32199)", "completion": "statem: add missing SSLfatal in padding extension construction"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTorture jobs are arguably the most flaky nowadays. Make a blind try to\nsee if re-enabling taskkill makes an observable improvement for torture.\n\nFollow-up to 208b87744e8ce326e2569c2efd735da43ce74a0b #21039\nFollow-up to f450f3801b6b9dff0ea280f5fb4bf28203f7b313 #19897\nFollow-up to 2701ac6a4d16a62130dad05be1c484903b8545c7 #19421\n\nCloses #22495", "completion": "GHA/windows: re-enable taskkill in torture jobs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_ctos_ech() called SSLfatal() on an ECH GREASE\nconstruction failure but returned EXT_RETURN_NOT_SENT, so extension\nconstruction reported success while the connection was already in the\nfatal error state. The ClientHello would still be sent together with\nthe fatal alert and the state machine kept running until it tripped\nover the error state later. Return EXT_RETURN_FAIL to fail the\nconstruction immediately.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:32:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32201", "completion": "statem: fail ClientHello construction on ECH GREASE failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_ctos_ech() called SSLfatal() on an ECH GREASE\nconstruction failure but returned EXT_RETURN_NOT_SENT, so extension\nconstruction reported success while the connection was already in the\nfatal error state. The ClientHello would still be sent together with\nthe fatal alert and the state machine kept running until it tripped\nover the error state later. Return EXT_RETURN_FAIL to fail the\nconstruction immediately.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:32:01 2026\nMerged-from: https://github.com/openssl/openssl/pull/32201", "completion": "statem: fail ClientHello construction on ECH GREASE failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls_construct_ctos_ech() called SSLfatal() on an ECH GREASE\nconstruction failure but returned EXT_RETURN_NOT_SENT, so extension\nconstruction reported success while the connection was already in the\nfatal error state. The ClientHello would still be sent together with\nthe fatal alert and the state machine kept running until it tripped\nover the error state later. Return EXT_RETURN_FAIL to fail the\nconstruction immediately.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Wed Sep 16 09:31:48 2026\nMerged-from: https://github.com/openssl/openssl/pull/32201", "completion": "statem: fail ClientHello construction on ECH GREASE failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nOptional chaining was generating expressions with included an extra pair of parenthesis which changed the semantics of the expression and threw an unexpected error from the optional chain non nullable extended diagnostic.\n\nfixes #70085\n\n(cherry picked from commit d7b03f5523d220c7935426d23ff5f103c96b00d9)", "completion": "fix(compiler): Generate correct expression for optional chaning."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nOptional chaining was generating expressions with included an extra pair of parenthesis which changed the semantics of the expression and threw an unexpected error from the optional chain non nullable extended diagnostic.\n\nfixes #70085", "completion": "fix(compiler): Generate correct expression for optional chaning."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nMigrate fixtures to standalone components and await zoneless updates\n\n(cherry picked from commit ec372d60294ff9b6137bf253201ce8341bd80f42)", "completion": "refactor(platform-browser): modernize DOM renderer tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nMigrate fixtures to standalone components and await zoneless updates", "completion": "refactor(platform-browser): modernize DOM renderer tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFix latent app bug in policy error diagnostics.\n\nFixes: #32176\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't read an ASN1_STRING data raw and assume it's 0 byte terminated"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nGetLocalPinLimit() and GetAdditionalLocalPinLimit(), currently in use\nonly by the read stream, previously allowed a backend to pin all\nnum_temp_buffers local buffers. This meant that the read stream could\nuse every available local buffer for read-ahead, leaving none for other\nconcurrent pin-holders.\n\nIn 18, this was reported as a sequential scan of a temporary table\nfailing with \"no empty local buffer available\": with\neffective_io_concurrency >= 64 and default io_combine_limit and\ntemp_buffers, the scan's read stream budget,\n(effective_io_concurrency + 1) * io_combine_limit, meets or exceeds\nnum_temp_buffers, so look-ahead could pin the entire local buffer pool.\nAny additional pin request made while returning tuples -- such as\nfetching TOASTed values from the table's (also temporary) TOAST table --\nthen found no unpinned buffer to evict.\n\nCap the local pin limit to num_temp_buffers / 4, providing some\nheadroom. This doesn't guarantee that all needed pins will be available\n-- for example, a backend can still open more cursors than there are\nbuffers -- but it makes it less likely that read-ahead will exhaust the\npool.\n\nThis is a backpatch of commit da6874635db, which was applied to master\nonly during the 19 development cycle, where the issue surfaced as a\nregression test failure after on-access pruning began setting the\nvisibility map. Reports of the failure above on 18 prompted\nbackpatching it now.\n\nNo backpatch to 17, even though its read stream also allows a single\nstream to pin the whole pool in principle. There, sequential scans pass\nREAD_STREAM_SEQUENTIAL, which disables fadvise-based look-ahead, so the\nlook-ahead distance cannot grow past io_combine_limit (at most 32\nbuffers, versus a minimum temp_buffers of 100) and the reported failure\nis unreachable. The remaining theoretical paths require adversarial\nsettings and have never been reported. Moreover, 17 predates these\nfunctions; the fix would have to be reimplemented in\nLimitAdditionalLocalPins(), making the", "completion": "Make local buffers pin limit more conservative"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAgain, ASN1_STRING_get0_data has never been guaranteed to be nul terminated.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't call strlcpy on a non-string."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Fix the tests to not pretend ASN1_STRING's are nul terminated."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhile it's really pretty foolish to do so (since it can\ncontain legitimate 0 bytes in the output) Some callers were\ntreating the returned buffer as a C string, in spite of the fact\nthat the documentation does not say that it is and a length\nis returned.\n\nUnfortunately, this probably stems from the bad habit in\nOpenSSL of trying to make things C strings anyway, - The conversion\npath already allocated the extra byte and terminated it as if it\nis a usable C string. The same-format path stored exact-length data\nfrom an ASN1_STRING with no NUL, so termination depended on the input\ntype and how it was constructed.\n\nSo be consistent, and NUL terminate the returned buffer in both cases.\n\nWe then document that the retured buffer *IS* nul terminated, add\nunit tests because of the Beyonce rule, and document in the\nwarnings that in spite of the output buffer being nul terminated\nit is potentially a bad idea to use C string functions on it as\nit can contain internal NUL bytes.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:42 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Make ASN1_STRING_to_UTF8() return a NUL terminated buffer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nBefore this patch modern systems used `sigaction()` and `SA_RESTART` to\ninstall signal handlers, but the signal handler function itself still\nmade a call to the legacy `signal()` function to re-register itself\nbefore returning.\n\nRe-registering the handler is not necessary with `sigaction()`. It's\nalso undesired to use the legacy API when the modern one is available.\n\nFix by guarding off this call in builds that support the modern API.\n\nFollow-up to 3fb6e5a01001b8c7dfdc33a89041178aac381a27 #6529\nFollow-up to 18cbb4d7d645016d1a9c0ee772c724d8c41db3bd\n\nCloses #22497", "completion": "servers: drop re-registering the signal handler on modern systems"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis function assumed there was one byte more than the\nlength of the string to add NUL byte termination. Don't\ndo that.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:43 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Fix one byte overrun in UNIVERSALSTRING_to_string"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe new timezone code from commit aeb07c55fab introduced a few new\ncompiler warnings from MSVC:\n\n ../src/timezone/zic.c(353): warning C5287: operands are different enum types '' and ''; use an explicit cast to silence this warning\n ../src/timezone/zic.c(353): warning C5287: operands are different enum types '' and ''; use an explicit cast to silence this warning\n ../src/timezone/zic.c(1654): warning C4146: unary minus operator applied to unsigned type, result still unsigned\n\nSilence these warnings with pragmas.\n\nIn order not to make future code merges more complicated, the pragmas\napply to the entire file, not only to the specific code sections where\nthey are needed. This also prevents further warnings of the same\nkinds creeping in.\n\nReviewed-by: Tom Lane \nDiscussion: https://www.postgresql.org/message-id/flat/2294297.1780270682%40sss.pgh.pa.us", "completion": "Fix MSVC warnings from new timezone code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWith `laststatus=3`, a pager float shares the main grid's statusline\nrow. Setting a diagnostic fires `DiagnosticChanged`, whose handler calls\n`nvim__redraw({ statusline = true })`.\n\nAnalysis:\nInside the autocmd, `curwin` is temporarily switched to the tiled window\nshowing that buffer, so `win_redr_status()` paints its statusline over\nthe pager's `[Pager]` statusline on the shared row. After the autocmd,\n`curwin` is restored but the pager statusline is never repainted.\n\nSolution:\nUse `ctx_saved_curwin()` decide whether to draw the global statusline,\nmatching `win_redr_stl_expr()` and `update_screen()`. No behavior change\nif no buffer-context switch is active.", "completion": "fix(statusline): don't clobber global statusline during autocmd #41169"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe element data is counted, not a C string, so strncpy() was wrong two\nways: an empty element yields strncpy(p, NULL, 0), which is undefined, and a\nvalue containing an embedded NUL was truncated and zero padded instead of\ncopied verbatim.\n\nUse memcpy() bounded by the element length, skipping empty elements. The\nseparator copy becomes a plain memcpy() as well, dropping the \"+ 1 to\nsilence gcc\" strncpy() hack. The computed buffer length and terminator are\nunchanged.\n\nNote in the documentation that using utf8 values in C strings is a\nfootgun if they contain NUL bytes internally\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:44 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't strncpy() counted ASN1_STRING data in ossl_sk_ASN1_UTF8STRING2text()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nreplace change detection calls with whenStable for async tests\n\n(cherry picked from commit 4631a6e47923dc72cba4fe5e6075873ccefe8012)", "completion": "refactor(forms): modernize Signal Forms tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nreplace change detection calls with whenStable for async tests", "completion": "refactor(forms): modernize Signal Forms tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nDuring insert-mode / replace-mode, `autowrite` may trigger. If it does, the\ncursor position can shift due to the automatic removal of trailing spaces on the\ncurrent line. When I resume typing, the space between the last word and the new\nword is suddenly gone.\n\nSolution:\nDisable the \"remove trailing spaces\" handler during Insert (or a similar) mode.\nAutosave logic is not affected.", "completion": "fix(editorconfig): avoid trim_trailing_whitespace in insert-mode #41175"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: A message emitted while a previous expanded message is still\n visible opens the pager and enters it, moving focus away from\n the buffer window without an explicit request (#41061).\nSolution: Only enter the pager when it was explicitly requested (\"g<\",\n :messages, or entered from the expanded cmdline). An unfocused\n pager is dismissed by the cmdline key handler, which stays armed\n across the cmdline and no longer dismisses on non-typed keys\n (#39221).", "completion": "fix(ui2): do not steal focus when consecutive cmds emit messages #41062"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAfter server-based subscriptions, conninfo became more than just a\ncatalog field. It has its own error paths, and it's important that\ncallers that don't need conninfo don't encounter errors related to it.\n\nReviewed-by: Amit Kapila \nReviewed-by: Hayato Kuroda (Fujitsu) \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nBackpatch-through: 19", "completion": "Remove Subscription conninfo field; generate in caller."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIf a subscription is disabled, don't try to build conninfo because\nthat may generate a confusing error and try to disable an\nalready-disabled subscription.\n\nPartially addresses finding 5 in report from linked discussion.\n\nReported-by: Noah Misch \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nBackpatch-through: 19", "completion": "Build subscription conninfo after checking that it's enabled."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:45 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Fix unguarded memcpy's asn1_type_get_int_oct()and X509_NAME_get_text_by_OBJ()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- Avoid shared state. Pass `focus` to set_pos()/expand_msg() instead of\n a shared `pager_focus` flag: the flag is only cleared when set_pos()\n actually enters the pager, so \":messages\" from inside the pager left\n it set.\n- pager_shown(): the pager window is invalid after leaving it with \"q\".\n- Reuse pager_shown() in expand_msg().", "completion": "fix(ui2): pager handling #41179"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOPENSSL_NONSTRING expands to __attribute__((nonstring)) where the compiler\nsupports it and to nothing otherwise. ASN1_STRING data has an explicit\nlength and is not necessarily NUL terminated, so marking the field lets GCC\ndiagnose direct use of it with C string functions such as strlen(), strcpy()\nor \"%s\".\n\nThe diagnostic fires only on GCC under an optimised build; other compilers,\nincluding current Clang, accept the attribute but do not warn.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:51 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Add OPENSSL_NONSTRING and apply it to ASN1_STRING's data field"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis flag is set by default in TS 6.0\n\n(cherry picked from commit f1c0c405c9d191fc42beec843c43d54392e53498)", "completion": "refactor(compiler): remove explicit `strict: true`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis flag is set by default in TS 6.0", "completion": "refactor(compiler): remove explicit `strict: true`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nDecide early whether the original conninfo is needed so that errors\nhappen consistently.\n\nAddresses finding 12 in report from linked discussion.\n\nCo-authored-by: Shlok Kyal \nReported-by: Noah Misch \nReviewed-by: Hayato Kuroda (Fujitsu) \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nBackpatch-through: 19", "completion": "Be precise about when ALTER SUBSCRIPTION needs conninfo."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n`opts.plain=true` does not expand tildes in addition to environment\nvariables, unlike `opts.expand_env=false`.\n\n`opts.expand_env=false` is soft-deprecated.", "completion": "feat(fs): vim.fs.normalize{plain:boolean} #41127"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, this was skipped in some cases to avoid raising errors\nwhen conninfo wasn't even needed. That was wrong in cases where\nconninfo was needed.\n\nNow that we only build conninfo when needed, always perform the USAGE\ncheck.\n\nAddresses finding 7 in report from linked discussion.\n\nCo-authored-by: Shlok Kyal \nReported-by: Noah Misch \nReviewed-by: Shlok Kyal \nReviewed-by: Hayato Kuroda (Fujitsu) \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nBackpatch-through: 19", "completion": "Always check foreign-server USAGE when resolving subscription conninfo."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe checks are useful to report to the user, but there's no reason to\nraise an error. If needed while constructing conninfo, fdwconnection\nwill raise an error then.\n\nPartially addresses finding 1, and addresses finding 13 in report from\nthe linked discussion.\n\nReported-by: Noah Misch \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nDiscussion: https://postgr.es/m/e103ae8daf74485e0c0ebde297fae735d38f54d1.camel@j-davis.com\nBackpatch-through: 19", "completion": "For subscription DDL, demote user mapping checks to WARNING."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nStill check that the creating user has USAGE privileges on the server,\nand that the FDW supports subscription connections.\n\nAddresses finding 1 in the report from the linked discussion.\n\nReported-by: Noah Misch \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nDiscussion: https://postgr.es/m/e103ae8daf74485e0c0ebde297fae735d38f54d1.camel@j-davis.com\nBackpatch-through: 19", "completion": "CREATE SUBSCRIPTION: do not construct conninfo unnecessarily."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nErrors will be caught when the connection is actually used.\n\nRestore uses multiple DDL commands to restore a subscription, so\nchecks of the intermediate state risk restore errors. In the future we\ncould address this with a more careful restoration order, but the\nDDL-time errors are merely for convenience.\n\nAddresses finding 2 in the report from the linked discussion.\n\nReported-by: Noah Misch \nReviewed-by: Shlok Kyal \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/20260710195902.4f.noahmisch%40microsoft.com\nDiscussion: https://postgr.es/m/e103ae8daf74485e0c0ebde297fae735d38f54d1.camel@j-davis.com\nBackpatch-through: 19", "completion": "When changing owner of a subscription, do not throw an error."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nViktor's proposals", "completion": "Apply suggestions from code review"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:46 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't assume an ASN1_STRING is nul byte terminated in the test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis should avoid the warning for calling strlen() on data in gcc\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:47 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't hit the legacy strlen case in ASN1_STRING_copy"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nTarget v8.2.1091.\nFrom v8.0.1000 for 'terminal'.", "completion": "build(vim-patch): mch_create_pty_channel() is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- convert the method switch() to a simple table\n\n- avoid converting the methods from external to internal numbers, they were\n the same anyway so keep the external ones, just use the old defines.\n\n- fix range check. It wrongly used the method numbers as bitmask, which made\n the check not work previously. Also error on OOM.\n\n- Dropped the session-id check. It too wrongly did a bitmask check which was\n wrong and never worked. When fixed, it broke test cases so I dropped the\n entire check.\n\n- split out rtsp_setup_request() from rtsp_do()\n\n- replace the httpversion variable with a define\n\nCloses #22505", "completion": "rtsp: refactor method handling and improve error checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nTarget v8.2.1120 .\nRemoved since https://github.com/neovim/neovim/pull/3074.\nNvim removed EOL versions in\nhttps://github.com/neovim/neovim/pull/17222 .", "completion": "build(vim-patch): python2 test is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAs an asn1_string of length 0 will have NULL data, don't\nprintf %s NULL.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:48 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Sweep for printf UB - don't printf %s NULL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhen the client installs early write keys, negotiated_version is not\nyet set to DTLS1_3_VERSION, so the RFC 9147 §5.2 stripping of\nmsg_seq, fragment_offset, and fragment_length was skipped in\ntls13_change_cipher_state. Fix by conditioning on\nSSL_CONNECTION_IS_DTLS() alone.\n\nFixes: openssl/project#2043\nReviewed-by: Frederik Wedel-Heinen \nReviewed-by: Matt Caswell \nMerge-date: Mon Aug 17 08:34:23 2026\nMerged-from: https://github.com/openssl/openssl/pull/32276", "completion": "Fix DTLS 1.3 early data transcript hash stripping"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMake the patch we use here length safe.\n\n(the original kerb code is not)\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:49 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Fix the kerberos external test patch"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\n- Parse Kitty graphics commands wrapped in tmux passthrough sequences.\n - Accept unpadded base64 payloads emitted by icat.\n - Handle chunked transfers whose final chunk omits m.\n - Track virtual image placements.\n - Convert Unicode placeholders into shared image cells for Kitty and SIXEL clients.\n - Add regression coverage for wrapped, chunked, unpadded input.", "completion": "Support Kitty Unicode placeholder image transmission"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThose options are enabled by default, they don't need to be explicit.\n\n(cherry picked from commit 9cf7b44f7c08082eaade725edf05cabe51f1a0b4)", "completion": "build: remove explicit strict options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThose options are enabled by default, they don't need to be explicit.", "completion": "build: remove explicit strict options"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\n- Layout corruption: C=1 is respected.\n - Lingering remnants: tmux now tracks Kitty’s (image ID, placement ID) identity, replaces moved placements, and honors\n placement-specific d=i,...,p=... deletion.", "completion": "The two Chawan symptoms now have matching fixes:"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nKeepFileRestoredFromArchive() called unlink() on an existing WAL segment\nbefore durable_rename() replaced it. rename(2) atomically replaces a\ntarget on POSIX systems, and the extra unlink() created a small window\nwhere it would be possible for a concurrent WAL sender to see a segment\nas missing.\n\nNote that the window still exists on WIN32, as we lack a safe concurrent\nalternative. Perhaps something like ReplaceFile() could be looked at\nfor this purpose.\n\nThis problem is hard to reach in practice, so no backpatch is done. I\nalso tend to be conservative regarding recovery changes, even small, in\nstable branches.\n\nAuthor: Stepan Neretin \nReviewed-by: Andrey Borodin \nReviewed-by: Neil Chen \nDiscussion: https://postgr.es/m/CA+Yyo5S0C25jS_pRWQiGgoiy+X=GyJS7ZJkEq=_SW1WWpkL3Sg@mail.gmail.com", "completion": "Remove redundant unlink() in KeepFileRestoredFromArchive() for non-WIN32"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 10:29:08 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 10:25:35 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 10:15:34 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 09:54:19 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 09:48:00 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn asn1_gen.c `asn1_multi()` function variable allocated as\n`ASN1_TYPE *typ = generate_v3()` is not freed if\n`if (!sk_ASN1_TYPE_push(sk, typ))` branch fails.\n\nBug found by x509v3 fuzzer MFAIL test.\nExample input:\n```\n[default]\n1.2.3.4 = ASN1:SEQUENCE:items\n\n[items]\nvalue = INTEGER:1\n```\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 14 09:42:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/32206", "completion": "Fix ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nUse ev.key directly to preserve Caps Lock casing, implement clipboard\npaste, and prevent :q/:qa from leaving the runtime in a loop.", "completion": "fix(wasm): fix browser input and runtime exit handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(utils): centralize guards function\n\n* update\n\n* update", "completion": "refactor(utils): centralize guards function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nPropagate exposed validity changes from forwarded root slot outlets so\nparent slot boundaries can re-resolve content and fallback correctly.", "completion": "fix(vapor): mark forwarded root slot outlets"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(Tooltip): support global mouseEnterDelay/mouseLeaveDelay via ConfigProvider\n\n- Add mouseEnterDelay and mouseLeaveDelay to TooltipConfig type\n- Consume global config in Tooltip component with component props override\n- Add unit tests for global delay config\n- Update documentation for ConfigProvider tooltip config\n\nCo-Authored-By: Claude \n\n* docs: update sharedProps global config version\n\nCo-Authored-By: Claude \n\n* docs: revert ConfigProvider tooltip section title\n\nCo-Authored-By: Claude \n\n* fix: use merged delay values in mergedProps\n\n* fix: use merged delay values in mergedProps for Tooltip and Popconfirm\n\nCo-Authored-By: Claude \n\n---------", "completion": "feat(Tooltip/Popover/Popconfirm): support global mouseEnterDelay/mouseLeaveDelay via ConfigProvider"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe code added in c456e3911 added populate_isnull_array() to bulk\npopulate the slot's tts_isnull array 8 elements at a time. When tuples\ndon't have an exact multiple-of-eight number of attributes, this will\nlead to populating the tts_isnull elements for attributes that don't\nexist in the tuple. This is ok as the array is large enough. However,\nif we perform tuple deforming in two passes, and on the first pass\ndeform *some* of the attributes with slot_getmissingattrs() then later\nwhen we deform the remaining missing attributes, the subsequent call to\npopulate_isnull_array() would overwrite the tts_isnull values previously\nset by slot_getmissingattrs(), and since that function only continues\nwhere it left off, it wouldn't reapply the previously set values and those\nwould be left as NULLs, as populate_isnull_array() would have set them.\n\nHere, we fix by passing the tuple's natts to slot_getmissingattrs()\nrather than the attnum we're deforming from. This means we apply all\nthe missing attribute values each deform pass, so slightly more work,\nbut deforming several missing values in different deform passes is\nlikely exceedingly rare. Doing that seems much better than adding\noverhead in the happy path to check for this and skip the subsequent call\nto populate_isnull_array().\n\nAuthor: David Rowley \nReported-by: Peter Geoghegan \nDiscussion: https://postgr.es/m/CAH2-WznHo4b+6AmAj0GZ0jXqDSK69MfHe8fAQwuY_01y7cVNdw@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix unlikely incremental tuple deform bug with missing attrs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo share more common code between servers, and to log the same set of\ninformation for all of them.\n\nAlso:\n- move server unix socket to global variable.\n\nFollow-up to d1eca3861c9cf8f3cd03274ce0db3c500bd246ae #22501\nFollow-up to 1637bbc9ced4213b902703b9223273ab2dcd2c6e #22498\n\nCloses #22503", "completion": "servers: de-duplicate shutdown signal/logging code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReplace `ipv_inuse` and `use_ipv6` with `socket_type` and\n`socket_domain` (where missing) to avoid dupliicate globals with\noverlapping purposes. The replacement variables also support Unix\nsockets.\n\nAlso:\n- simplify/reduce IPv6 guards.\n- socksd: fix to reset `socket_domain` for `--ipv4` option.\n\nCloses #22498", "completion": "servers: sync socket type global variables"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBuildfarm member olingo intermittently failed this test, timing out while\nwaiting for the subscriber log to report an ERROR because\nmax_prepared_transactions is zero there. The test captured the log offset\nonly after issuing the publisher's\nBEGIN/INSERT/PREPARE TRANSACTION/COMMIT PREPARED sequence.\n\nSince streaming is enabled, the subscriber can receive and apply the\ntransaction, and log the expected ERROR, before that publisher SQL command\neven returns, i.e. before the test captures the offset. The subsequent\nwait_for_log() calls then searched only from a point after the message had\nalready been written, and timed out waiting for it.\n\nFix by moving the offset capture to before the publisher's transaction is\nissued, ensuring it always precedes the point where the ERROR can appear\nin the subscriber log.\n\nReported-by: Alexander Lakhin \nAuthor: Zhijie Hou \nReviewed-by: Amit Kapila \nBackpatch-through: 16, where test was introduced\nDiscussion: https://postgr.es/m/c43753d8-5265-4f77-83ff-9b1167276ec5@gmail.com", "completion": "Fix race condition in subscription TAP test 023_twophase_stream."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nstrtoul() informs that in the case of no conversion, \"endptr\" is set\nequal to the location of the input pointer, which is something that\ntidin() has never checked.\n\nThis allowed inputs like \"(,)\", \"(1,)\" or \"(,1)\" to be accepted on some\nplatforms, like Linux where \"(1,)\" implied \"(1,0)\", but rejected on\nothers like macos where \"(1,)\" is rejected, due to the fact that errno\nmay not be set.\n\nThis change may cause some issues as some tid values will now be\nrejected, but at least we get the consistent strtoul() experience.\nIf it proves to be a pain for some, it could always be reverted.\nAnother point of this change is that we get one step closer to a\npossible common strtoul() where the error handling could be unified in\ncore, with all the errors handled the same way for errno and no input\nparsed, at least.\n\nReported-by: Michael Malis \nAuthor: Tristan Partin \nDiscussion: https://postgr.es/m/19584-e60c446ba6f57c9c@postgresql.org\nDiscussion: https://postgr.es/m/DKBS2Z9CGARC.2T07O6TJYSE8B@partin.io", "completion": "Tighten tid input parsing with strtoul() to reject empty fields"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo sync with the rest of code which already handled `got_exit_signal`\nand did the restoration on exit. Also syncing with rest of servers.\n\nAlso: turn off `keep_sigalrm` to sync with most servers.\n\nCloses #22499", "completion": "tests/server/dnsd: fix to install signal handlers on startup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nVerified by test 409\n\nReported-by: 1rhino2 on hackerone\n\nCloses #22500", "completion": "cookie: refuse to load cookies set against a PSL domain"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 1637bbc9ced4213b902703b9223273ab2dcd2c6e #22498\n\nCloses #22501", "completion": "servers: sync server port global variable across servers, make port variables `uint16_t`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis is similar to 58ff4a0a0867, but this time for the parameter\n\"proto_version\", when given as a parameter to pgoutput for logical\nreplication. strtoul() lacked a check for an empty string, leading to\nan inconsistent behavior depending on the platform.\n\nThe author has originally proposed a TAP test to check this empty value\npattern. I have added a cheaper SQL query, instead, test_decoding\nincluding a test area where this is possible.\n\nAuthor: Tristan Partin \nDiscussion: https://postgr.es/m/DKBS2Z9CGARC.2T07O6TJYSE8B@partin.io", "completion": "Tighten proto_version parsing in pgoutput"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22502", "completion": "psl: update a comment to understandable English"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAdding a property with the same name multiple times to a label on an\nelement, either within a single PROPERTIES clause or across statements\nvia ALTER PROPERTY GRAPH ... ADD PROPERTIES, previously failed with a\nunique-index violation on pg_propgraph_label_property. The same class\nof bug existed for labels: listing the same label multiple times on\none element in CREATE PROPERTY GRAPH, or adding a label to an element\nthat already has it via ALTER PROPERTY GRAPH ... ADD LABEL, failed\nwith a unique-index violation on pg_propgraph_element_label. Detect\nthe duplicates up front and raise a friendlier error in both cases.\n\nFor properties, the cross-statement duplicate is caught by a syscache\nprobe before insertion. The in-clause duplicate could have been\ncaught by the same probe if we issued a CommandCounterIncrement()\nbetween property inserts, but that forces a catalog invalidation per\nproperty purely to detect a condition we can check for free on the\nin-memory target list. The list-based check is only needed when the\nproperties are listed explicitly; when they are derived from the\ntable's attributes, names are already unique.\n\nFor labels, a single syscache probe on pg_propgraph_element_label\nsuffices for both the in-clause and cross-statement cases because\ninsert_element_record() already issues CommandCounterIncrement()\nbetween successive label inserts.\n\nAuthor: Ashutosh Bapat \nReported-by: Noah Misch \nDiscussion: https://www.postgresql.org/message-id/flat/20260630173053.51.noahmisch%40microsoft.com", "completion": "Report duplicate property and label names with a proper error"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* test: fix failing ecosystem test for `eslint-plugin-unicorn`\n\n* test: don't use `--save-dev` for `core-js-compat` and unpin `eslint-plugin-eslint-plugin` in ecosystem test config", "completion": "test: fix failing ecosystem test for `eslint-plugin-unicorn`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAnd drop:\n\n- Consider OCSP stapling by default\n\nIt is a practice that is going out-of-style, so doing this by default now\nseems wrong.\n\n- Provide callback for cert verification\n\nWe have lots of options already. Let's not do this.\n\nCloses #22504", "completion": "TODO: ECH for QUIC"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIn year 2020 the Unixy signal handler received a `logmsg()` call to log\nthe signal number, but at the same time it already saved it to a global\nvariable and logged it on exit, meaning this extra `logmsg()` was\nredundant. Because `logmsg()` is not signal-safe, this call was replaced\nin 2025 with signal-safe logging, but without the signal number, while\nalso adding complexity, spent on trying to open the log file and handle\nerrors. All for nothing, because the signal number was logged all along.\n\nThis patch removes all this, and simplifies it to a single, signal-safe\n`write()` to STDERR to say that the signal handler triggered. This is\nalso non-critical, but may help debugging.\n\nAlso: point the POSIX documentation to the 2004 revision, which has a\nshorter list of safe functions. (was: 2018)\n\nFollow-up to e95f509c66abdd88ae02e3243cdc217f19c4a330 #16852\nFollow-up to 9869f6dc5af85caf2e0fd4c56713a7f2049ecfff #5218\n\nCloses #22507", "completion": "servers: drop complex and redundant signal handler output"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\ndnsd now opens UDP+TCP sockets and accepts http: DoH requests to obtain\nthe same, configured answers (records, delays, error codes) as over UDP.\n\nDoH: use `async->queries_ongoing` like all other resolvers instead of\nthe internal `pending` counter. Fixes waiting for results.\n\nTests: in pytest, parameterize dnsd tests to use both DNS and DoH.\n\nCloses #22506", "completion": "dnsd: add support for DoH"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\ncurl already built like this in UWP mode; add a macro to allow building\nregular Win32 targets too, meaning without the hidden GUI window, window\nhandler, and thus without support for shutting down `servers.exe`\ngracefully. To test the server in CI as a plain console app and remove\none component/variable from the system, in an effort chasing flaky runs.\n\nThe graceful option was used by `taskkill` (without `-f`) in runtests,\nand it has been disabled (in favor of always `-f` (forced) kill), in an\nattempt to avoid taskkill hanging. Those resolved, but general CI\nflakiness remained. We see `taskkill` invoked seldom per job, and in\nmost of these cases it doesn't find the PID requested. It means the\ngraceful option is not actually used since 2025-04, and rather rarely\nbefore that. Also just today, the callback and main loop received a few\nupdates to avoid potentially unsafe calls and interaction with the ctrl\nhandler.\n\nNot expecting anything breakthrough here. Also graceful shutdown\nis a useful feature to cleanup properly and to be in sync with other\nplatforms.\n\nAlso: GHA/windows: enable in Windows CI jobs.\n\nRef: https://learn.microsoft.com/windows/console/registering-a-control-handler-function#listen-with-hidden-window-example\n\nFollow-up to 7db9947fcf5d3deebe98e7992ebedc9a2f624bf5 #22045\nFollow-up to 9ea48811fed455d4a869eb100b2216f039f8677a #22487\nFollow-up to b11e0026f71aa33b47d3b31f7c6a2aee4f929b12 #22495\nFollow-up to 208b87744e8ce326e2569c2efd735da43ce74a0b #21039\nFollow-up to f450f3801b6b9dff0ea280f5fb4bf28203f7b313 #19897\nFollow-up to 2701ac6a4d16a62130dad05be1c484903b8545c7 #19421\nFollow-up to 4e203f65a1e5e448daf1da2b8c3aaa33654dd080 #17054\n\nCloses #22496", "completion": "servers: add option to build without window handler (Windows)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nXID is defined as an acronym in the documentation but MXID (Multixact\nID) was missing from the acronym list. This adds MXID as an acronym\nand links it to the \"Multixacts and Wraparound\" section.\n\nAuthor: Koshino Taiki \nDiscussion: https://postgr.es/m/OS9PR01MB17364A940ACFCADBB7593498A94D32@OS9PR01MB17364.jpnprd01.prod.outlook.com", "completion": "doc: Define MXID as an acronym"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNow this was a cargo cult anti-pattern to write home about.\nDoing painful save-and-restore bookkeeping around a separate\n`magic_overruled` decoy global is just as messy as doing painful\nsave-and-restore logic around `p_magic` itself. only that now you need\nto wrap every access to the effective value in a function call.\n\nThis replaces this with a marvellous new Clean Code technique™:\npassing in the intended behavior as a function parameter to functions\nwhere either the option or an explicit value might be used.", "completion": "refactor(ex_cmds): use function arguments for magic behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nGiving a window a status line when `'laststatus'` starts requiring one\ntakes the row from a resizable frame found by walking up the frame\ntree, but only the window's own leaf frame is grown back. Every frame\nbetween the leaf and the donor keeps its old height, so a later resize\nhands out a row that does not exist and a window's status line ends up\non the command line.\n\nSolution:\nGrow the window's frame with `frame_setheight()`, which takes the row\nfrom a neighbouring frame and keeps every enclosing frame consistent.", "completion": "fix(window): 'laststatus' change pushes win past last row #41189"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReject repeated fields in policyConstraints, basicConstraints\nand basicAttConstraints instead of silently accepting the last value.\n\nAssisted-by: ChatGPT:gpt-5.6\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Sun Aug 9 04:06:37 2026\n(Merged from https://github.com/openssl/openssl/pull/32181)", "completion": "Reject duplicate fields in X509v3 config"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Sun Aug 9 04:06:42 2026\n(Merged from https://github.com/openssl/openssl/pull/32181)", "completion": "Add x509v3 duplicate field config tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nForks are just wasting CI cycles spinning actions which are probably not\nlooked at. Also avoid locking issues and PRs on any forks with\nupstream's policies.", "completion": "ci: only run `lock` and `regress` workflows on the main repo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Sun Aug 9 04:06:46 2026\n(Merged from https://github.com/openssl/openssl/pull/32181)", "completion": "Run clang-format - chore"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis fixes a regression introduced by #69309 where the format of `serializedId` from a coma separated string, to a JSON representation of an array.\n\nfixes #70104\n\n(cherry picked from commit 03f1758e2ae7e033c14360a72583d51825993217)", "completion": "fix(devtools): fix regression for node serialization."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis fixes a regression introduced by #69309 where the format of `serializedId` from a coma separated string, to a JSON representation of an array.\n\nfixes #70104", "completion": "fix(devtools): fix regression for node serialization."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nv8.2.1300", "completion": "build(vim-patch): vim9 skip_type() is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRe-document that ASN1_STRINGs are not NUL byte terminated, and\nhave been documented as such for over 20 years.\n\nASN1_STRING data has never been guaranteed to be NUL byte terminated.\nASN1_STRING_set() added one anyway; its replacements do not, so code\nrelying on UB, and treating it as a C string is more likely to break.\n\nReviewed-by: Neil Horman \nReviewed-by: Mounir Idrassi \nReviewed-by: Norbert Pocs \nReviewed-by: Tomas Mraz \nMerge-date: Fri Sep 4 17:35:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32233", "completion": "Add a migration entry for ASN1_STRINGs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nv8.2.1341", "completion": "build(vim-patch): vim9 error 1103 is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThese functions date back to commit 461ef73f09, which predates the\n64-bit byte-swapping routines in pg_bswap.h (added in commit\n510b8cbff1). Commit 0ba99c84e8 converted them to use pg_hton32()\nand pg_ntoh32() but stopped short of removing them, so let's do\nthat now.\n\nDiscussion: https://postgr.es/m/ahXE28klgxIJXBLq%40nathan", "completion": "Remove lo_hton64() and lo_ntoh64()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe \"state\" variable is dead, nothing ever reads it. We will\nbe repurposing it for something else.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 13:56:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/32242", "completion": "Remove dead code from pkcs7"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhether the content octet string was created locally (to be filled in)\nor read in via d2i is CMS's own state; it was being kept in the\nASN1_STRING via ASN1_STRING_FLAG_CONT, of which the only user was\nCMS. Track it in a CMS_ContentInfo field instead of using ASN1_STRING\nas a convenient internal state toilet. No change in behaviour.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 13:56:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32242", "completion": "Store the CMS created-content state in CMS_ContentInfo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhether the content is an indefinite-length (NDEF) streaming placeholder\nis PKCS7's own state, but it was read back from ASN1_STRING_FLAG_NDEF on\nthe content octet string. Record it in a spare bit of the PKCS7 state\nfield instead, set in PKCS7_stream and read where the content BIO is set\nup and finalized. PKCS7_stream still sets the NDEF flag for the ASN.1\nencoder; that move follows separately. No change in behaviour.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 13:56:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32242", "completion": "Track the PKCS7 streaming state in the state field, not the ASN1_STRING"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCMS_stream() and PKCS7_stream() marked the content octet string with\nASN1_STRING_FLAG_NDEF and handed BIO_new_NDEF() the address of its data\nfield, where the encoder records the position of the content. Add an\nASN1_OP_STREAM_CONTENT callback operation through which BIO_new_NDEF()\nobtains that string, sets the flag, and reads the position back out, so\nboth are manipulated only by the ASN.1 code that uses them. What is left\nof the two functions becomes ossl_cms_stream() and ossl_pkcs7_stream();\nthe public ones remain as wrappers but are unused.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 13:56:42 2026\nMerged-from: https://github.com/openssl/openssl/pull/32242", "completion": "Do the NDEF streaming setup in the ASN.1 layer, not in CMS and PKCS7"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe filter only leaves comments and strings in all files using .c or .h\nextensions.\n\nIt is important that the filter runs after all the other checks are done\non these files as this process destroys the files.\n\nFixes #22508\nCloses #22509", "completion": "CI: filter all .[ch] files before doing typo checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe filter only leaves comments and strings in all files using .c or .h\nextensions.\n\nIt is important that the filter runs after all the other checks are done\non these files as this process destroys the files.", "completion": "CI: filter all .[ch] files before doing typo checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- (much) less code repetition\n\n- simplifies ldap_do somewhat\n\nCloses #22510", "completion": "ldap_do: refactor error handling and simplify show_vals function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nVACUUM's wraparound failsafe mode exists to reclaim transaction IDs as\nquickly as possible. 4830f1024325 made the failsafe stop using the\nBAS_VACUUM buffer access strategy so that the rest of the vacuum could\nmake use of all of shared buffers rather than being confined to the\nsmall strategy ring.\n\nHowever, when 9256822608f3 made vacuum's first heap pass use the read\nstream, this was accidentally disabled. The read stream keeps its own\nreferences to the buffer access strategy, so clearing vacrel->bstrategy\nin lazy_check_wraparound_failsafe() no longer had any effect on the\nreads issued by the first pass.\n\nFix this by adding clearing the BufferAccessStrategy reference actually\nbeing used by the ongoing scan -- those in the ReadBuffersOperations\nstructs themselves.\n\nTwo things we accept rather than fix, as neither is worth the added\ncomplexity given how rarely failsafe mode is reached:\n\n- A small amount of read time for IOs that were already in progress when\n the strategy was cleared may be attributed to IOCONTEXT_NORMAL instead\n of IOCONTEXT_VACUUM. WaitReadBuffers() derives the IOContext from the\n (now cleared) strategy, so the wait time of these in-flight IOs is\n misattributed. This is bounded by the stream's look-ahead window and\n happens at most once per vacuum, when the strategy is first cleared.\n\n- The stream's buffer pin limit stays lower than it would have been had\n no strategy been used at all. max_pinned_buffers is capped by the\n strategy's pin limit when the stream is created and is not recomputed\n when the strategy is cleared. Raising it would mean building a new,\n larger ring, which would require first waiting for all in-progress IOs\n to complete. That didn't seem worth it.\n\nReported-by: Jingtang Zhang \nDiscussion: https://postgr.es/m/CAPsk3_APRYVLhAJ5TMwdmpSx8W_%3DPHMm%3DPmKAvnC3gBrfNommQ%40mail.gmail.com\nBackpatch-to: 18", "completion": "Restore vacuum failsafe abandonment of buffer access strategy"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 761c79508e7 added scram_client_key_len and scram_server_key_len\nto PGconn, but no consumer read the fields and there were no accessor\nfunctions defined. Code which need the length use SCRAM_MAX_KEY_LEN\nwhich the new fields were also verified to match, so remove the fields\nas they are not used.\n\nAuthor: Aleksander Alekseev \nReviewed-by: Matheus Alcantara \nDiscussion: https://postgr.es/m/CAJ7c6TMx3pyuW86zEjGs4kua0vQPzZEg2sCUe+NnP08fBKuVoQ@mail.gmail.com", "completion": "Remove scram_client_key_len and scram_server_key_len from PGconn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTreat MathML-namespaced script elements as scripts during template preprocessing. This prevents scripts nested in MathML HTML integration points from surviving template compilation.\n\n(cherry picked from commit 107f6fa49d00ec250b94a8d5f484bae2fc3d71c9)", "completion": "fix(compiler): remove namespaced MathML script elements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTreat MathML-namespaced script elements as scripts during template preprocessing. This prevents scripts nested in MathML HTML integration points from surviving template compilation.", "completion": "fix(compiler): remove namespaced MathML script elements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nPrior patches for it are marked n/a.\nTarget v8.2.2630 .", "completion": "build(vim-patch): runnvim should make redir_test_to_null n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nImplements persistent breakpoints for Angular signal consumers (computeds and effects) in Angular DevTools using Chrome DevTools Protocol (CDP).\n\n- Adds debugger permission to Chrome and Firefox extension manifests.\n- Implements CDP breakpoint orchestration in background script.\n- Updates SignalDetailsComponent and SignalGraphPaneComponent with label icon toggle and persistent state sync across reloads.", "completion": "feat(devtools): implement persistent breakpoints on signal consumers using CDP"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nFixes #17428", "completion": "fix(core): share existing singleton providers with lazily loaded modules"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`DeferredSymbolTracker.lookupIdentifiersInSourceFile` prunes `ts.isTypeNode`\nsubtrees so that references appearing exclusively inside type annotations\ndo not keep static import declarations in the emitted JavaScript.\n\nHowever, `ts.isTypeNode` returns `true` for `ts.ExpressionWithTypeArguments`,\nwhich TypeScript uses to represent both `extends` and `implements` heritage\nclauses. An `extends` clause on a class declaration or class expression is a\nvalue position that survives in the emitted JavaScript output.\n\nBecause `isTypeNode` returned `true`, references to base classes imported\nalongside deferred dependencies were ignored. As a result, the compiler\nerroneously marked the static import statement as deferrable and deleted it\nfrom the emitted JavaScript, leaving the `extends ` clause referencing\nan undeclared identifier and causing a runtime `ReferenceError`.\n\nThis commit ensures that `ExpressionWithTypeArguments` under a class `extends`\nclause is not treated as an erasable type node, preserving the static import\nwhenever a base class is referenced.\n\n(cherry picked from commit 8d6c925392c7230fbe6b39abdad05381672631b1)", "completion": "fix(compiler-cli): record class extends clause references in DeferredSymbolTracker"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`DeferredSymbolTracker.lookupIdentifiersInSourceFile` prunes `ts.isTypeNode`\nsubtrees so that references appearing exclusively inside type annotations\ndo not keep static import declarations in the emitted JavaScript.\n\nHowever, `ts.isTypeNode` returns `true` for `ts.ExpressionWithTypeArguments`,\nwhich TypeScript uses to represent both `extends` and `implements` heritage\nclauses. An `extends` clause on a class declaration or class expression is a\nvalue position that survives in the emitted JavaScript output.\n\nBecause `isTypeNode` returned `true`, references to base classes imported\nalongside deferred dependencies were ignored. As a result, the compiler\nerroneously marked the static import statement as deferrable and deleted it\nfrom the emitted JavaScript, leaving the `extends ` clause referencing\nan undeclared identifier and causing a runtime `ReferenceError`.\n\nThis commit ensures that `ExpressionWithTypeArguments` under a class `extends`\nclause is not treated as an erasable type node, preserving the static import\nwhenever a base class is referenced.", "completion": "fix(compiler-cli): record class extends clause references in DeferredSymbolTracker"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nGive each anchored dynamic block its own template placeholder so\nCSR element indexes align with SSR logical units. This removes the\nseparate hydration index bookkeeping and unifies compiler and runtime\ninsertion behavior.\n\nReuse eligible placeholders as fragment anchors, remove the\nprepend-specific runtime paths, and fix invalid-nesting insertion\ncodegen.\n\nThis changes the internal Vapor compiler/runtime codegen contract and\nthe CSR DOM anchor shape. Output from older Vapor compiler versions is\nnot compatible.", "completion": "refactor(vapor): replace logicalIndex with block placeholders"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- Use %hu for unsigned short instead of %u.\n\nPrior to this change some compilers could warn of an argument type\nmismatch. C argument promotion rules promote the unsigned short argument\nto an int, which does not match %u (unsigned int) but does match %hu\n(unsigned short).\n\nAssisted-by: Viktor Szakats\n\nCloses https://github.com/curl/curl/pull/22511", "completion": "api: fix printf format specifier"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFollowing remain relevant:\n\n- src/testdir/Makefile (default setup in Unix-like OS)\n- src/testdir/Make_all.mak (define old/new style Vim tests)\n\nRest are n/a because Nvim runs Vim's tests on GHA Windows runner.", "completion": "build(vim-patch): os makefile for tests are n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe reconnection test assumed that a restarted walsender would always\nhave a different PID from the previous one. On some platforms, however,\nPIDs can be reused quickly, causing the test to time out even though\npg_recvlogical has successfully reconnected.\n\nThis issue was reported by buildfarm member fairywren:\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2026-07-30%2009%3A58%3A12\n\nFix this by waiting for the server log message indicating that the\nlogical replication slot has been acquired again, rather than relying on\na PID change.\n\nBackpatch to v19, where the affected reconnection test was introduced by\ncommit d89b1d817513.\n\nAuthor: Hayato Kuroda \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/OS9PR01MB121497CF10DFF54F745E37204F5C92@OS9PR01MB12149.jpnprd01.prod.outlook.com\nBackpatch-through: 19", "completion": "Make 030_pg_recvlogical robust against PID reuse"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- Change --enable-debug help text to say it is for developing curl.\n\n- Warn when --enable-debug is used.\n\nThis change copies the help text and warning from cmake ENABLE_DEBUG.\nAlso, it shortens the \"for debugging curl itself\" to just say \"for\ndebugging curl\".\n\nNow it looks like this:\n\n --enable-debug Enable curl debug features (for developing\n curl)\n --disable-debug Disable curl debug features\n\nRef: https://github.com/curl/curl/issues/22481#issuecomment-5207220359\n\nReported-by: Viktor Szakats\n\nCloses https://github.com/curl/curl/pull/22512", "completion": "configure: clarify --enable-debug option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nEvaluating 'statuscolumn' overwrites transchar_charbuf[], which breaks\nthe drawing of an unprintable char if p_extra points there.\n\nSolution:\nMake a copy in wlv.extra so that it won't be overwritten.", "completion": "fix(drawline): 'statuscolumn' breaks unprintable char wrapping"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen pgstat_init_entry() fails due to an OOM in the DSA allocation,\npgstat_get_entry_ref() cleaned up the shared hashtable but forgot to\nremove the local reference that pgstat_get_entry_ref_cached() had\nalready inserted into pgStatEntryRefHash.\n\nMissing this cleanup would leave a backend with a stale local cache\nentry whose entry_ref points to a NULL shared_stats. If\npgstat_gc_entry_refs() runs with this reference still around, it would\ncrash due to a pointer dereference.\n\nThe local reference is now removed before removing the shared entry,\nthe order being sensitive to pending interrupts.\n\nOversight in 8191e0c16a03.\n\nAuthor: Niall Newman \nDiscussion: https://postgr.es/m/2FDAA194-9CF3-4FD7-A450-F1A4BEB125F6@turacolabs.com\nBackpatch-through: 15", "completion": "Fix local pgstat entry leak on OOM during entry creation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npgstat_acquire_entry_ref() does an entry acquisition with the following\nactions:\n- Increment of a shared ebtr's refcount.\n- Release dshash partition lock.\n- Update local entry_ref fields.\n\nWith a pending interrupt, the LWLock acquired by dshash_release_lock()\nin the second step could fail, leaving around a local entry_ref with\nshared_stats set to NULL and the refcount permanently inflated as\npgstat_release_entry_ref() skips the refcount decrement is shared_stats\nis not set.\n\nThe actions are now reordered so as the lock is released after the local\nentry_ref fields are populated.\n\nThe consequence of this problem is a minor leak. It can only happen if\nan interrupt is processed when a dshash lock is released, which is a\nvery narrow window (very unlikely), so no backpatch is done.\n\nAuthor: Niall Newman \nDiscussion: https://postgr.es/m/2FDAA194-9CF3-4FD7-A450-F1A4BEB125F6@turacolabs.com", "completion": "Fix shared refcount leak in pgstat entry acquisition"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe note claiming ri_FastPathCheck() is only used by the ALTER TABLE\nvalidation path is no longer accurate. Rather than reword it, remove\nit; the block comment above RI_FKey_check()'s call to the function\nalready documents when each path is taken, and a duplicated\ncross-reference here would only drift out of date again.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Remove stale comment on ri_FastPathCheck()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(Pagination): support custom size changer render\n\n* refactor(Pagination): use components for custom size changer\n\n* refactor(Pagination): refine custom size changer API", "completion": "feat: support custom components in Pagination"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe RI fast-path check probes the referenced index directly and, for\nsingle-column keys, uses SK_SEARCHARRAY. Both assume the index is a\nbtree. A comment claimed \"PK indexes are always btree\", but a foreign\nkey's referenced index need not be a primary key:\ntransformFkeyCheckAttrs() accepts any unique (or, for temporal keys,\nexclusion) index, so an out-of-tree access method advertising\namcanunique could supply a non-btree index reachable by the fast path.\n\nAdd pk_index_is_btree to RI_ConstraintInfo, set from the referenced\nindex's access method when the constraint is loaded, and make\nri_fastpath_is_applicable() return false for non-btree indexes so such\nconstraints fall back to the SPI path.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Restrict RI fast-path FK check to btree referenced indexes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nri_FastPathCheck() called index_beginscan() before switching to the\nreferenced relation's owner for the permission check and probe. For\nbtree this has no consequence, but starting the scan before the user id\nswitch sets a poor example for code dealing with out-of-tree access\nmethods, whose beginscan could observe the wrong user id. Move\nindex_beginscan() after the SetUserIdAndSecContext() call.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Begin RI fast-path index scan under the switched user id"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFixes that we were running a `for in` loop on an array and silently doing the wrong thing.\n\nFixes #70113.\n\n(cherry picked from commit 565dbb2fe5406f2a86d43a5b3c6993434b7124a7)", "completion": "fix(core): incorrect loop in defer blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nFixes that we were running a `for in` loop on an array and silently doing the wrong thing.\n\nFixes #70113.", "completion": "fix(core): incorrect loop in defer blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAfterTriggerFireDeferred() drained its queued events in a loop, then\ncalled FireAfterTriggerBatchCallbacks() once after the loop to flush\nthe RI fast-path FK-check batches the fired triggers accumulated.\n\nA batch callback runs user-supplied cast or equality functions, whose\nDML can queue further deferred trigger events. Because the flush ran\nafter the loop had exited, such an event was left in\nafterTriggers.events with nothing to fire it, since\nAfterTriggerFireDeferred() is the last drainer at commit. The deferred\ncheck was skipped and a row violating the constraint committed.\n\nMove the flush inside the loop, after afterTriggerInvokeEvents(), and\ndrop the \"all fired\" break, so afterTriggerMarkEvents() re-checks after\neach flush and fires events a flush queued at the correct time. The\nother FireAfterTriggerBatchCallbacks() callers leave any queued event\nfor the eventual commit-time AfterTriggerFireDeferred(), so only the\ncommit-time firing, which has no later drainer, lost events.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Fire fast-path FK batches inside the deferred trigger loop"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe logic for asynchronous Append assumes that pending requests made for\nsubplans of an Append are drained during ExecReScanAppend. To ensure\nthat, commit 9e283fc85 modified postgresReScanForeignScan to drain such\na request if any, but failed to take into account that if such a request\nwas made for a subplan that is re-scanned with parameter changes or\npruned in the next round by runtime pruning, the postgres_fdw callback\nfunction is called after ExecReScanAppend or never called, respectively.\nThis would cause such a request to remain even after ExecReScanAppend,\nleading to incorrect results, an infinite loop, or an assertion failure.\n\nTo fix, modify ExecReScanAppend to, for each of the pending requests,\ngive the FDW a chance to drain that request using the existing\nForeignAsyncConfigureWait/ForeignAsyncNotify callback functions. This\nmakes the change made to postgresReScanForeignScan useless, so remove it\nas well.\n\nBack-patch to v14 where asynchronous Append was added.\n\nReported-by: Alexander Korotkov \nCo-authored-by: Alexander Korotkov \nCo-authored-by: Gleb Kashkin \nCo-authored-by: Etsuro Fujita \nReviewed-by: Alexander Pyhalov \nReviewed-by: Gleb Kashkin \nDiscussion: https://postgr.es/m/CAPpHfduMOTnV5Zj2KGJ7zanL_10QvccZHtPUaDfJvBhsh9axnQ%40mail.gmail.com\nBackpatch-through: 14", "completion": "Drain pending asynchronous requests during ExecReScanAppend."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nThe lazy-load short-circuit in scanner.ts relies on the inserted flag\nto skip re-scanning already-loaded modules. NestContainer.replaceModule()\nwas incorrectly returning inserted: false, causing overridden lazy\nmodules (via testing module builder) to be skipped entirely and their\nproviders never scanned. replaceModule() always creates a new module\nreference that must be scanned, so it now correctly returns\ninserted: true.", "completion": "fix(core): correctly scan providers when overriding a lazy-loaded module"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nNoticed before the commit reached koel.", "completion": "Fix indentation issue introduced by commit 291a4bd2ca"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe RI fast-path FK check asserted that the referenced key is never\nNULL, in ri_FastPathFlushArray() and in recheck_matched_pk_tuple().\nThat holds for a primary key, but a foreign key may reference any\nunique column, and a UNIQUE column is nullable.\n\nThe assertion is reachable under READ COMMITTED. ri_LockPKTuple()\nlocks the matched PK tuple with TUPLE_LOCK_FLAG_FIND_LAST_VERSION, so\nwhen a concurrent transaction commits a key-changing UPDATE while the\ncheck waits, the lock follows the update chain to the latest version.\nIf that version now has NULL in the referenced column, the fast path\nreaches the assert; in a non-assert build it would compare against the\nNULL and treat it as a match.\n\nA NULL referenced key cannot equal any (non-null) FK value, so treat it\nas no match and let the ordinary foreign-key violation be raised. This\nmatches the SPI path, whose requalifying \"pkatt = $n\" evaluates to NULL\nfor such a row, so the row is not returned and the check reports a\nviolation.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Handle nullable referenced key in RI fast-path check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n- buf-local CWD scope is lower priority than :lcd, which is weird.\n ```\n win > buf > tab > global\n ```\n- No way to clear current CWD at a given scope.\n\nSolution:\n- Rerrange scope precedence to:\n ```\n buf > win > tab > global\n ```\n- Introduce \"bang\" variants (`:bcd!`/`:lcd!`/`:tcd!`) which clears the\n local CWD for the given scope.", "completion": "feat(cwd)!: :lcd! (bang), rearrange :bcd/:lcd/… scope precedence #41194"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n'linebreak' filler and 'breakindent'/'showbreak' padding are screen\ncells with no buffer character behind them, yet a decoration draws over\nthem whether or not it asked to cover such cells. A highlight bounded to\nits text then paints a tail out to the edge of the row, most visible on\ninline code spans from plugins. That same highlight already leaves the\ncells past the end of a line alone, so it treats identical cells two\ndifferent ways.\n\nSolution:\nOnly a decoration with 'hl_eol' draws the gaps, which is what the flag\nalready means at the end of a line. A full-width background such as a\nfenced code block sets it and still covers them. Classic :syntax has no\nsuch flag and is unchanged.", "completion": "fix(decor): highlight without 'hl_eol' bleeds into wrap gaps #41160"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nfix #15217", "completion": "chore(playground): default to TypeScript 6"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* fix: prevent ASI hazard in `no-unused-labels` autofix\n\nWhen removing an unused label whose body starts with `(`, `[`, `` ` ``,\n`/`, `+`, or `-`, the autofix could silently change program semantics by\nmerging the body with the preceding statement via ASI.\n\ne.g. `foo()\\nLABEL: [1,2,3].forEach(x => x)` was incorrectly fixed to\n`foo()\\n[1,2,3].forEach(x => x)`, which parses as `foo()[1,2,3].forEach(...)`.\n\nThe fix skips autofixing in those cases when the token before the\nLabeledStatement is not a safe ASI boundary (`;`, `{`, `}`, `:`).\n\n* fix: remove } from safe ASI boundary tokens in no-unused-labels\n\n} is not always a safe ASI boundary — e.g. a function expression ending with } can still be continued by [ on the next line:\n\n const foo = function() {}\n LABEL: [1, 2, 3].forEach(x => x)\n\nRemoving LABEL: here would produce `function() {}[1, 2, 3]` which is a member access, not two separate statements.\n\n* Apply suggestion from @mdjermanovic\n\ngetFirstToken(node.body) always returns a token.\n\nCo-authored-by: Milos Djermanovic \n\n* Update tests/lib/rules/no-unused-labels.js\r\n\r\nThis test was already being caught by the isStaticTemplateLiteral check above\n\nCo-authored-by: Milos Djermanovic \n\n* Update tests/lib/rules/no-unused-labels.js\n\nCo-authored-by: Milos Djermanovic \n\n---------", "completion": "fix: prevent ASI hazard in `no-unused-labels` autofix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat: add BackTop progress ring\n\n* fix(BackTop): sync progress ring with target scroll state\n\n* test(BackTop): cover null progress target\n\n* fix(BackTop): handle document targets in isolated environments\n\n* fix(FloatButton): correct BackTop progress ring rendering\n\n* test(FloatButton): update progress ring demo snapshot\n\n* fix lint error\n\n* test(utils): remove obsolete getScroll regression test\n\n* fix(utils): guard missing document constructor\n\n* docs(FloatButton): improve progress ring demo\n\n* docs(FloatButton): show progress ring immediately in demo\n\n* demo: update demo\n\n* add useScroll hook\n\n* fix(FloatButton): render progress ring on button border\n\n* refactor: address BackTop progress review feedback\n\n* fix(utils): guard missing document constructor\n\n* test(FloatButton): ignore progress ring demo snapshots\n\n---------", "completion": "feat: support progress ring for FloatButton.BackTop"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit 9044e5f42556 (\"Convert internal use of ASN1_STRING_set and\nASN1_STRING_length\") replaced ASN1_STRING_set() with the new\nASN1_STRING_set1_data() in X509_ATTRIBUTE_set1_data(). The new setter\nintentionally rejects strings of type V_ASN1_BIT_STRING, so creating an\nattribute value of type BIT STRING from raw bytes with an explicit\nlength now fails with ASN1_R_ILLEGAL_BITSTRING_FORMAT.\n\nThis broke PKCS8_add_keyusage() and therefore PKCS#12 creation with a\nnon-zero keytype (e.g. 'openssl pkcs12 -export -keyex' or '-keysig'),\nas well as the public X509_ATTRIBUTE_create_by_*() and\nX509at_add1_attr_by_*() APIs when used with BIT STRING values supplied\nas bytes plus an explicit length.\n\nRestore the previous behaviour by dispatching to ASN1_BIT_STRING_set1()\nwith zero unused bits when attrtype is V_ASN1_BIT_STRING, keeping\nASN1_STRING_set1_data() for the other types: the signature of this\nexplicit-length raw-data API provides no way to specify another\nunused-bit count, so the data is taken as complete octets, which\npreserves the previous encoding for supplied raw-byte values. Document\nthis in the X509_ATTRIBUTE manual page.\n\nFixes #32234\n\nAssisted-by: Cline:Qwen3.8 Max\nReviewed-by: Richard Levitte \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 15:44:48 2026\nMerged-from: https://github.com/openssl/openssl/pull/32238", "completion": "Fix X509_ATTRIBUTE_set1_data() for BIT STRING attribute values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nTest that X509_ATTRIBUTE_create_by_NID() accepts a BIT STRING value\nsupplied as raw bytes with an explicit length, as done for the keyUsage\nattribute by openssl pkcs12 -export -keyex and -keysig via\nPKCS8_add_keyusage(). Both KEY_EX (0x10) and KEY_SIG (0x80) are exercised\nat this common boundary, and the resulting attribute is checked for the\nexpected type, value, length, and zero unused bits.\n\nAlso pass -keyex to an existing PKCS12 export test so the reported CLI\npath is covered end to end.\n\nRegression test for https://github.com/openssl/openssl/issues/32234\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Richard Levitte \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 15:44:50 2026\nMerged-from: https://github.com/openssl/openssl/pull/32238", "completion": "Add regression tests for BIT STRING X509 attributes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22515", "completion": "curl_url_set.md: expand the CURLU_NO_AUTHORITY description"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15226", "completion": "fix(compiler-vapor): preserve optional chaining in cached member expressions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nShow the missing nav arrows when you select a deeply nested component where\nthe breadcrumbs path is longer than the container. The nav arrows used to\nappear only when the split is resized. Add some other minor improvements.", "completion": "fix(devtools): breadcrumbs missing nav arrows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`:terminal` does not respect the invocation-time CWD.\nThis wasn't noticeable with `:lcd` because the window-local CWD gets\napplied to the new terminal buffer. But it is noticeable with `:bcd`.\n\nSolution:\nSpecify `cwd` in the job spec.", "completion": "fix(terminal): spawn in effective CWD #41211"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCollapse the section since it takes a significant portion of the vertical space,\nwhereas most of the times users are exploring the properties leading them to scroll.\n\nAddiotionally, introduce some other minor UI improvements.", "completion": "refactor(devtools): collapse injected services section in the side pane by default"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: `TabLineSel` by default is defined with only bold attribute.\n This makes selected tabpage stand out relatively well, but when used\n in custom tabline it will be combined with `TabLineFill` (which is\n reserved for the \"non tabpage\" part of the tabline).\n Plus the behavior is not consistent with the default 'tabline' which\n combines it with `Normal`.\n\nSolution: Explicitly define background and foreground colors to come\n from `Normal` to ensure the current default 'tabline' behavior even in\n custom tabline.\n The more semantically driven solution here is to link `TabLineSel` to\n `StatusLine`. This makes it more aligned with how `TabLine` is linked\n to `StatusLineNC`. But the current \"bold text with `Normal` colors\" is\n argued to look better as a default.\n\n Also make sure that 'notermguicolors' highlighting in default and\n custom tablines is the same: the current tabpage does not have\n underline and is not bold.", "completion": "fix(highlight): explicitly define `TabLineSel` bg/fg #41196"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n112c2683807b4d690 restored failsafe vacuum's abandonment of a buffer\naccess strategy by clearing the ReadBuffersOperations' strategy\nreferences. But it did so in lazy_scan_heap()'s main loop, meaning it\nlooped through all the ReadBuffersOperations once per block after\nfailsafe was engaged. Track it with a local flag and clear the strategy\nonly once.\n\nReported-by: Melanie Plageman \nDiscussion: https://postgr.es/m/CAAKRu_Zse14nSNeCgtnE1LUAH8Of7OmYR%2BCc3O_DAzxt3m6T-g%40mail.gmail.com\nBackpatch-through: 18", "completion": "Only clear VACUUM's read stream strategy once in failsafe mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nRe-editing a buffer (`:edit!`, re-reading a dir.lua buffer, etc.) drops\nits `:bcd` directory, so the CWD falls back to the global one. Whereas\nother buffer-local state (`b:` vars, local options) survives a reload.\n\nSolution:\nDon't clear buf dir in `buf_freeall()`; `do_ecmd()` calls that when\nreloading/re-editing. `free_buffer_stuff()` still clears them when\na buffer is freed or reused for another file.", "completion": "fix(cwd): keep buffer-local dir when re-editing #41215"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit b53b88109f9 made the postmaster maintain reachedConsistency in\naddition to the startup process. Since the startup process is forked\nfrom the postmaster, it begins life holding whatever value the\npostmaster last set.\n\nOn a crash reset the postmaster re-forks the startup process while its\nown copy still says true: it clears that copy only on receipt of\nPMSIGNAL_RECOVERY_STARTED, which the replacement process cannot send\nbefore it exists. The replacement therefore starts out believing the\ndatabase is already consistent.\n\nCheckRecoveryConsistency() then skips the minRecoveryPoint comparison\naltogether, so hot standby is announced at redo start while replay may\nbe arbitrarily far behind minRecoveryPoint. Read-only connections are\naccepted and answer from heap pages that were flushed ahead of the\nreplay position, returning wrong results with no error raised. The\nsame branch also runs XLogCheckInvalidPages() and\nCheckTablespaceDirectory(), which are skipped as well, and\nlog_invalid_page() treats page references that are normal before\nconsistency as a PANIC.\n\nFix by clearing reachedConsistency in InitWalRecovery(), so that a\nstartup process never depends on the value it inherited. The\npostmaster's own copy is deliberately left alone: forked backends read\nit to choose the \"not yet accepting connections\" errdetail, and it\nconverges once the new startup process sends PMSIGNAL_RECOVERY_STARTED\nand, on reaching minRecoveryPoint, PMSIGNAL_RECOVERY_CONSISTENT.\n\nSuccessive crash resets alternate. A startup process that skips the\nbranch never sends PMSIGNAL_RECOVERY_CONSISTENT, so the postmaster's\ncopy stays false and the next reset forks a process holding the correct\nvalue; that pass reaches consistency properly, which sets the\npostmaster's copy back to true and re-arms the problem for the reset\nafter it. Roughly every other crash reset is therefore affected, not\njust the first one. EXEC_BACKEND builds are unaffected, as\nreachedConsistency is not carried in BackendPa", "completion": "Fix hot standby accepting connections too early after a crash reset"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nFixed:\n - Preserves image metadata while updating the text underlay in the collected ASCII path: grid.c:779\n - Handles the single-cell/non-ASCII path and schedules an image redraw: screen-write.c:2631\n - Uses the requested if/else for new_id.\n - Adds a deterministic regression reproducing point (2): regress/image-support.sh:240\n\n This matches Kitty’s requirement that normal text operations must not affect graphics; graphics require\n explicit deletion. Kitty graphics protocol", "completion": "Ordinary text writes replaced the entire grid cell, dropping GRID_FLAG_IMAGE and releasing the mage reference. Deferred pane redraws explain the intermittent “image never appears” behavior."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 7f6a75664f9fb45390193e492ee3361fb795d098 #22506\n\nCloses #22517", "completion": "tests/server/tftpd: replace duplicate code with `open_udp_sock()` call"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe listener's notifier was signalled when the demux routed a datagram into a\nconnection's receive queue, but not when dtls_listener_drive_pending() moved\na completed connection onto the accept queue - even though the latter is\nprecisely the readiness event a thread waiting in SSL_poll() for\nSSL_POLL_EVENT_IC is waiting for.\n\nUsually the injection signal covers for this. Every connection reaching the\naccept queue got there because a datagram was demuxed into its receive queue,\nso the waiter is woken by that, ticks the listener during its own readout,\nand finds the connection. The exception is the window in which the injection\nand the queue push straddle a waiter registering, since signalling only\nhappens if there is a waiter at the time:\n\n 1. Accept thread A polls the listener for SSL_POLL_EVENT_IC. Its readout\n ticks the listener, finds nothing, and it decides to block. It is not a\n registered waiter yet.\n 2. Worker thread B polls one of its own connections, which also ticks the\n listener. The pump reads a client's final ClientHello and injects it into\n that pending connection's queue. There are no waiters, so nothing is\n signalled.\n 3. A enters the blocking section. Its re-check runs without ticking, so it\n sees only the accept queue, still empty, and blocks.\n 4. B's tick reaches dtls_listener_drive_pending(), which completes the\n connection against the buffered ClientHello and pushes it onto the accept\n queue.\n\nWith no signal at step 4, A sleeps on while a validated connection sits ready\nto be accepted, until an unrelated datagram makes the socket readable again.\nB consumed the only one in flight and the client is now waiting on the server,\nso on a quiet listener that means waiting for the client to retransmit its\nhandshake.\n\nFactor the signalling out of dtls_listener_packet_handler() into a helper and\ncall it from both places. Both call sites already hold the listener mutex,\nwhich the helper requires.\n\nAssisted-by: Claude Code", "completion": "DTLS 1.3 Signal the listener notifier on accept queue push"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhen SSL_poll() decides to block it computes a wakeup deadline from the\nper-object event timeout, so that timer driven work is not delayed by the\nwait. This was done for QUIC objects but not for DTLS connections, whose\ntimeout is the handshake retransmission timer.\n\nThe consequence was that a poll with no user timeout would sleep until a\ndatagram arrived, straight through the point at which the connection should\nhave retransmitted. If the peer had itself lost the message we were waiting\nfor, neither side would make progress.\n\nFold SSL_get_event_timeout() into the deadline for DTLS connections as the\nQUIC branch already does. It reports the DTLS timer already, so no new\nplumbing is needed there.\n\nWaking at the deadline is only useful if something then services the timer.\nUnlike the QUIC case, where the readout ticks the reactor and that handles\ntimeouts, the DTLS readout only pumped the listener's demux. Nothing\nretransmitted, and because an expired timer reports zero time remaining the\nrecomputed deadline would be \"now\" on every subsequent wait, turning the\nsleep into a spin. Call SSL_handle_events() from the readout as well, which\nis what a caller polling without SSL_POLL_FLAG_NO_HANDLE_EVENTS is asking\nfor, and which for a DTLS connection services that timer.\n\nBoth of those are the calls the documentation asks new code to use:\nDTLSv1_get_timeout(3) and DTLSv1_handle_timeout(3) each record that\nSSL_get_event_timeout(3) and SSL_handle_events(3) respectively supersede all\nof their use cases. The test asserts its precondition through\nSSL_get_event_timeout() for the same reason, which has the side benefit of\nusing the same call SSL_poll() uses to compute the deadline being tested.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 14 15:45:37 2026\nMerged-from: https://github.com/openssl/openssl/pull/32239", "completion": "DTLS 1.3 Honour the DTLS retransmit timer in SSL_poll"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA DTLS listener added only the network socket to the poll set. Three things\nfollowed from that. The notifier was not in the poll set, so a thread blocked\nin SSL_poll() on the listener could not be woken by it. The thread never\ncalled ossl_dtls_listener_enter_blocking_section(), so cur_blocking_waiters\nstayed at zero - and since signalling is conditional on there being a waiter,\nno other thread even attempted to signal. And there was no re-check after\nregistering, so readiness arising between the readout deciding nothing was\nready and the wait actually starting was lost.\n\nPolling the socket alone is not sufficient, though not because a wakeup can\nbe missed outright. poll() reports whatever is currently sitting in the\nsocket buffer and returns immediately if there is any, so a thread cannot\nmiss a datagram just by being outside poll() when it arrives. What it can\nmiss is a datagram another thread has already taken. With several threads\npolling the one shared socket that happens constantly: an arriving datagram\nwakes all of them, only one gets it, and the rest find nothing. Any of them\ncan be the one that takes it, because SSL_read() on a connection pumps the\ndemux and SSL_poll() on a connection ticks the whole listener.\n\n 1. Accept thread A polls the listener for SSL_POLL_EVENT_IC. Its readout\n ticks the listener, finds nothing, and it decides to block.\n 2. A client's final ClientHello lands on the shared socket.\n 3. Worker thread B, polling one of its own connections, ticks the listener\n and is the one that takes the datagram. Its tick completes the pending\n connection and pushes it onto the accept queue. Signalling is attempted,\n but A never registered as a waiter, so nothing is signalled.\n 4. A reaches its poll, watching the socket alone. B drained it, so it is\n empty. A sleeps with a validated connection sitting on the accept queue,\n and nothing can wake it until an unrelated datagram arrives or its\n deadline expires.\n\nA's readout,", "completion": "DTLS 1.3 Enter a blocking section when polling a DTLS listener"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: The reuse_client predicate does not pass the target buffer,\npreventing decisions from being truly made per buffer.\n\nSolution: Pass the target buffer.", "completion": "feat(lsp): pass target buffer to `reuse_client` predicate #41163"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n:bcd (buffer-local directory) is not preserved after\n`nvim_open_win` or `nvim_win_set_buf`\n\nAnalysis:\nset_curbuf() ends with update_cwd(), which falls back to\nos_chdir(globaldir) when the target buffer has no b_localdir.\n\nSolution:\nPass kCtxKeepCwd to ctx_switch().", "completion": "fix(cwd): :bcd lost by nvim_win_set_buf, nvim_open_win #41218"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 144b90c907b69f88ce869b8929af0a81aba13b01)", "completion": "docs: add code style in Antigravity file reference"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThese set up the indefinite length streaming used by BIO_new_NDEF(), which\nnow obtains the content octet string through the ASN.1 callback, so they\nno longer return a streaming boundary and have no use outside the library.\nNeither has ever been documented, so there is no manual page to update.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 13:56:43 2026\nMerged-from: https://github.com/openssl/openssl/pull/32242", "completion": "Deprecate CMS_stream() and PKCS7_stream()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nfilemess() treats an empty suffix as \"a buffer write is starting\", but\nreadfile() calls it that way too. So \":read\" (and \":edit\", …) opens a\n`nvim.bufwrite \"\"` progress that is never completed.\n\nUsers of e.g. ghostty will see a stuck \"progress\" spinner.\n\nSolution:\nOnly `buf_write()` starts the progress, via `filemess_progress()`.", "completion": "fix(messages): :read starts a \"bufwrite\" progress #41219"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdate the roadmap to reflect that Angular Aria became stable in Angular v22 while development of new patterns continues.\n\n(cherry picked from commit 8e41e97dfea09ceba52eca2b7ce4c06196b09b04)", "completion": "docs: update Angular Aria roadmap status"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUpdate the roadmap to reflect that Angular Aria became stable in Angular v22 while development of new patterns continues.", "completion": "docs: update Angular Aria roadmap status"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nState in fips_module(7) that a FIPS provider built from a validated\nversion can be used with libcrypto and libssl from any supported\nrelease from OpenSSL 3.0 onwards, backward and forward, including\nfuture major release series, replacing the narrower wording that\nlimited this to the same major release series.\n\nThe downloads page reference in the same paragraph now points at\nhttps://openssl-library.org/source/, which www.openssl.org/source/\nredirects to.\n\nAligns the documentation with the OpenSSL Library FIPS Module\nSupport Policy.\n\nAssisted-by: Claude Code:claude-fable-5\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nMerge-date: Tue Aug 18 07:21:22 2026\nMerged-from: https://github.com/openssl/openssl/pull/32105\n(cherry picked from commit 090868518bbff01f8e9590444aed3c06a254a3b2)", "completion": "doc: FIPS provider is compatible with releases from 3.0 onwards"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nState in fips_module(7) that a FIPS provider built from a validated\nversion can be used with libcrypto and libssl from any supported\nrelease from OpenSSL 3.0 onwards, backward and forward, including\nfuture major release series, replacing the narrower wording that\nlimited this to the same major release series.\n\nThe downloads page reference in the same paragraph now points at\nhttps://openssl-library.org/source/, which www.openssl.org/source/\nredirects to.\n\nAligns the documentation with the OpenSSL Library FIPS Module\nSupport Policy.\n\nAssisted-by: Claude Code:claude-fable-5\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nMerge-date: Tue Aug 18 07:21:22 2026\nMerged-from: https://github.com/openssl/openssl/pull/32105", "completion": "doc: FIPS provider is compatible with releases from 3.0 onwards"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nState that a FIPS provider built from any validated version may be\nused together with an OpenSSL library built from any supported release\nfrom OpenSSL 3.0 onwards, backward and forward, including future major\nrelease series.\n\nThe downloads page references in the updated paragraph now point at\nhttps://openssl-library.org/source/, which www.openssl.org/source/\nredirects to.\n\nAligns the documentation with the OpenSSL Library FIPS Module\nSupport Policy.\n\nAssisted-by: Claude Code:claude-fable-5\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nMerge-date: Tue Aug 18 07:21:24 2026\nMerged-from: https://github.com/openssl/openssl/pull/32105\n(cherry picked from commit 93a175f15adfad7f469f98cd2455cd65551e4eb6)", "completion": "README-FIPS: clarify provider and library cross-version compatibility"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nState that a FIPS provider built from any validated version may be\nused together with an OpenSSL library built from any supported release\nfrom OpenSSL 3.0 onwards, backward and forward, including future major\nrelease series.\n\nThe downloads page references in the updated paragraph now point at\nhttps://openssl-library.org/source/, which www.openssl.org/source/\nredirects to.\n\nAligns the documentation with the OpenSSL Library FIPS Module\nSupport Policy.\n\nAssisted-by: Claude Code:claude-fable-5\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nMerge-date: Tue Aug 18 07:21:24 2026\nMerged-from: https://github.com/openssl/openssl/pull/32105", "completion": "README-FIPS: clarify provider and library cross-version compatibility"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nv8.2.1551", "completion": "build(vim-patch): vim9 check_typval_type() is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSome builtin features emit progress-messages which never \"complete\".\n- On failure, `:write` does not complete the progress-msg it started.\n- ins-completion never ends its \"Scanning...\" message.\n\nSolution:\n- `buf_write()` emits \"failed\" status on failure.\n- `ins_compl_stop()` ends the completion one.", "completion": "fix(messages): dangling progress-messages #41222"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFAILED …/terminal/ex_terminal_spec.lua @ 270: :terminal (fake shell) spawns in CWD effective at time of invocation\n Expected values to differ.\n Value:\n \"~/work/neovim/neovim/build/Xtest_xdg_terminal\"\n stack traceback:\n …/terminal/ex_terminal_spec.lua:276: in function <…/terminal/ex_terminal_spec.lua:270>", "completion": "test(terminal): unreliable \"spawns in CWD effective at time of invocation\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nCID 652778: Uninitialized variables (UNINIT)\n /src/nvim/context.c: 353 in ctx_dirs_save()\n 347 if (curbuf->b_sfname != NULL && curbuf->b_fname == curbuf->b_sfname) {\n 348 cs->cs_save_sfname = xstrdup(curbuf->b_sfname);\n 349 }\n 350 do_autochdir();\n 351 char autocwd[MAXPATHL];\n 352 if (os_dirname(autocwd, MAXPATHL) == OK) {\n >>> CID 652778: Uninitialized variables (UNINIT)\n >>> Using uninitialized value \"*cwd\" when calling \"strcmp\".\n 353 cs->cs_apply_acd = strcmp(cwd, autocwd) == 0;\n 354 }\n 355 }\n 356 }\n 357\n 358 /// Restores the dir state saved by ctx_dirs_save(), undoing any chdir made while switched. The\n\n CID 652777: Null pointer dereferences (FORWARD_NULL)\n /src/nvim/context.c: 556 in ctx_switch()\n 550 cs->cs_target_win = wp->handle;\n 551 cs->cs_target_old_pos = wp->w_cursor;\n 552 }\n 553 // The CWD-state snapshot is only for a real window target; hidden-buffer target is handled by the\n 554 // ctx_win machinery (ctx_win_prep).\n 555 if (buf == NULL || wp != NULL) {\n >>> CID 652777: Null pointer dereferences (FORWARD_NULL)\n >>> Passing null pointer \"wp\" to \"ctx_dirs_save\", which dereferences it.\n 556 ctx_dirs_save(cs, wp, tp == NULL ? curtab : tp, buf);\n 557 }\n 558\n 559 // Save the current state.\n 560 cs->cs_curwin = curwin->handle;\n 561 cs->cs_prevwin = prevwin == NULL ? 0 : prevwin->handle;", "completion": "fix(coverity): UNINIT, FORWARD_NULL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: The reuse_client predicate does not pass the target buffer,\npreventing decisions from being truly made per buffer.\n\nSolution: Pass the target buffer.", "completion": "backport: feat(lsp): pass target buffer to `reuse_client` predicate #…"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nMergeDate: Sun Aug 9 04:06:52 2026\n(Merged from https://github.com/openssl/openssl/pull/32181)", "completion": "Add valid single field tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe insert-mode completion progress-message is in \"running\" state while\nthe user is selecting an item. That is noisy and unwanted UX; it was\nonly intended for the \"Scanning...\" task.\n\nSolution:\nEnd the progress-msg just after `ins_compl_show_statusmsg`.", "completion": "fix(progress): ins-compl progress-msg during pum #41226"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:00 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Replace generated crypto/objects files only when their content changes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:02:59 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Skip error and ordinal regeneration when nothing has changed"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:02:58 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "copyright.pm: cope with files that git does not know"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGuard the generate_apps, generate_crypto_bn, generate_crypto_conf,\ngenerate_crypto_asn1 and generate_fuzz_oids recipes with test -nt\nchecks against their inputs, so \"make update\" no longer reruns them\nwhen nothing they consume has changed.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:01 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Skip the small generator scripts when their output is current"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUse the host element's namespace-aware local name when checking for script\nelements. A prefixed SVG script can expose a qualified tag name such as\n\"x:script\" while its local name remains \"script\".\n\n(cherry picked from commit 9f8e32616b79892785051fab1c3120a770f5f682)", "completion": "fix(core): reject prefixed SVG script hosts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nUse the host element's namespace-aware local name when checking for script\nelements. A prefixed SVG script can expose a qualified tag name such as\n\"x:script\" while its local name remains \"script\".", "completion": "fix(core): reject prefixed SVG script hosts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nMove charmap.h, bn_prime.h, conf_def.h, obj_mac.h, obj_dat.h and\nobj_xref.h from committed generator output to GENERATE rules with\nDEPENDs on their consumers; obj_mac.h joins the mandatory generated\nheaders built before everything else. objects.pl learns -a to append\nthe obj_compat.h aliases itself, replacing the sed step, and\nobj_dat.pl reads only the guarded body of obj_mac.h so the appended\naliases cannot pollute its tables. obj_mac.num remains the curated NID\nregistry in git; the generate_crypto_objects developer target shrinks\nto maintaining it, generate_fuzz_oids now depends on the\nbuild-generated obj_dat.h, and the other generate_* developer targets\nfor these files are retired.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:02 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Generate the committed generator-output headers at build time"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nTeach util/mkerr.pl two new modes. -emit FILE writes one generated\nerror file to standard output as a pure function of openssl.ec and\nopenssl.txt, with no source scan and no state update; every file in\nthe openssl.ec L table becomes a GENERATE rule driven by it, and the\ngenerated error headers join the mandatory generated headers.\n-state scans the sources and maintains openssl.txt but writes no\nother files; \"make errors\" now uses it, so the developer flow only\ncurates the state and the build emits everything else.\n\nReason-code assignment moves out of the header emission into its own\npass, the three emitters become subroutines writing to a filehandle,\nand the up-to-date stamp moves from the statefile's own timestamp to\na separate gitignored stamp file, since the statefile is now a build\ninput whose timestamp must track its content.\n\nRemoving the committed copies also retires 15 that had silently\ndrifted from the generator's output, among them crypto/bio/bio_err.c,\nwhich was missing the reason strings for three BIO error codes that\nexist in the state file.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:03 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Generate the error headers and tables at build time"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nRedudant code\n\nSolution:\nAdd `path_fold_char()` to normalize path sep.\nRefactor `pathcmp()` and `path_fnamencmp()` into `path_cmp`.\n\n| feature | pathcmp | path_fnamencmp | path_cmp(now) |\n| ------------------------ | -------------- | -------------- | ------------- |\n| case folding | `mb_toupper()` | `utf_fold()` | `utf_fold()` |\n| consults fileignorecase | ✅ | ✅ | `ic` param |\n| `maxlen` | ✅ | ✅ | ✅ |\n| `/` == `\\` | ✅ | ✅ | ✅ |\n| MSWIN drive letter | ❌ | ✅ | ✅ |\n| sep affects sorting | ✅ | ❌ | ✅ |\n| ignores a trailing slash | ✅ | ❌ | ✅ |\n\nRefactor `path_fnamecmp` and `path_full_compare` into `path_equal`,\nwith flags controlling \"no filesystem\" comparison (i.e. `path_cmp`), env\nvariables expansion, absolute path resolution and filesystem access.", "completion": "refactor(path): pathcmp() #41035"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReplace util/write-man-symlinks with util/install-man-pages.pl,\nwhich installs or uninstalls an entire man section in one process:\ncopy, chmod and the NAME-alias symlinks that previously cost a\nbasename, cp, chmod and a full perl interpreter for every one of\nthe ~900 installed pages.\n\nStale alias links are removed before being recreated, with one\nconstraint carried over from the old script's silent symlink\nfailures: on a case-insensitive file system an alias can collide\nwith an installed page (OSSL_TRACE_ENABLED alongside\nOSSL_trace_enabled), so nothing that is not a symlink is ever\nremoved, and an occupied alias name is skipped.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:04 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Install man pages a section at a time, not a process per page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nInstall the public headers and the pkg-config and cmake exporters\nthrough a new util/install-files.pl, which handles a whole file set\nin one process and replaces a file only when its content differs; an\nunchanged file keeps its timestamp, so builds against the installed\ntree no longer see every header change after each install.\n\nThe static and shared library installs keep their staged copies --\nthe mv is what makes replacing a mapped library safe -- but now\ncompare the staged copy against what is installed and discard it\nwhen identical, and only report an install when one happens.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:05 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Install only changed development and runtime files"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd INCLUDE directives for the objects whose sources include a\ngenerated header by its bare name; in-tree builds masked the missing\nbuild-directory include paths. Make mkerr.pl's config and state\nparsing tolerate CRLF line endings, since it now runs at build time\non Windows checkouts.\n\nAlso repair the error state itself: openssl.txt disagreed with the\npublished bioerr.h on BIO_R_PEER_ADDR_NOT_AVAILABLE (151, not 114)\nand had lost BIO_R_NULL_PARAMETER entirely -- the shipped header is\nthe ABI, so the state now matches it. The out-of-order defines at\nthe bottom of the old header show it had been edited by hand without\nregenerating, which is exactly the failure mode that generating\nthese files at build time removes.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:06 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Fix the emitted error files for out-of-tree and Windows builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nno-http removes the HTTP client but still builds http_lib.c for URL\nparsing, and it raises HTTP reason codes; mkerr must not wrap\nhttperr.h in OPENSSL_NO_HTTP, so HTTP joins SSL, ASYNC and DSO on\nthe list of libraries whose error codes survive disabling.\n\nThe committed httperr.h never had the guard -- it predates HTTP\nbecoming disablable and was never regenerated -- so no-http builds\nhave been quietly relying on the committed copy being stale. The\nemitted header now matches the published one.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Keep the HTTP reason codes visible in no-http builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nLong reason strings in openssl.txt are stored on a continuation\nline, which was read without stripping its line ending; the greedy\nwhitespace trim kept the carriage return on a CRLF checkout, and\nthe emitted string then carried a bare CR, which compilers treat\nas a line ending inside the literal.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:08 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Strip the line ending from continuation lines in the mkerr state"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(site): exclude bot accounts from contributors\n\n* update\n\n* Potential fix for pull request finding\n\nCo-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>\nSigned-off-by: lijianan <574980606@qq.com>\n\n* update\n\n* update\n\n---------", "completion": "fix(site): exclude bot accounts from contributors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPrevent arbitrary MetaDefinition properties from writing on* handlers directly to meta elements. Browser events can execute these handlers, including on meta elements rendered in the document body.\n\nReject handler attributes case-insensitively before matching or mutating tags.\n\nFixes #70126", "completion": "fix(platform-browser): disallow event handler attributes in Meta"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nLink.ABI is a feature of pkgconf 3.0 and indicates the ABI against which\na consumer must link the package. For libcurl, this is hard-coded as C.\nSource is a URL from which to download the package tarball.\n\nCloses #22519", "completion": "libcurl.pc: add the Link.ABI and Source tags"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nVapor effects can continue tracking parent-owned reactive sources after a\ncached branch is moved into storage. This allows render and watcher jobs to\nconsume transient values while the branch is inactive.\n\nCollect the detached component scopes within each KeepAlive boundary and\npause them on deactivation, then resume dirty effects on activation. Ensure\neffects and child scopes created under an already-paused scope inherit its\nstate, and prevent jobs queued before deactivation from running.\n\nAllow unresolved async wrappers to finish resolving while ensuring their\nresolved component effects start paused when the branch is cached.\n\nCloses #15228", "completion": "fix(runtime-vapor): pause KeepAlive scopes when deactivated"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFound by pyrefly.", "completion": "tests: fix typo in assert message in http test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- decode results when individual requests are done\n- makes happy eyeballing start asap\n- remove doh_resp structures as no longer needed\n- remove CURL_DNS_TYPE_NS, CURL_DNS_TYPE_CNAME and\n CURL_DNS_TYPE_DNAME from DoH\n- DoH: do not set PIPEWAIT and SSL OPTS when url starts with http:\n- mark Doh master handle as dirty after every sub-request, not only the last\n- Doh: start probe on AAAA before A (was the other way).\n\ncf-dns: set EXPIRE_HAPPY_EYEBALLS timer when waiting 50ms on AAAA\nresult or progress will not be triggered in time.\n\nAdd debug env var CURL_DBG_HE_AAAA_AWAIT_MS to override the\ndefault 50ms on waiting for the AAAA result to arrive.\n\ntest2100: set CURL_DBG_HE_AAAA_AWAIT_MS to 60 seconds to\nprovide enough time for slow CI runs to sent all DoH requests.\n\ncloses #22514", "completion": "DoH: improvements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe per-page copy loops become one process per section that\nreplaces only a page whose content changed, matching the man page\nand header installs; an unchanged page keeps its timestamp and a\nreinstall is quiet. The image documents get the same treatment.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:09 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Install the HTML manual pages through install-files.pl"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* test(Form): replace compiler assertion with dist regression test\n\n* update", "completion": "test(Form): replace compiler assertion with dist regression test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nAdd a dedicated nvim.wasm build workflow and\ninclude the resulting WASM artifact in nightly releases.", "completion": "ci: add nvim.wasm build and nightly release"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\n`String#match` coerces a string argument into a RegExp, so a `fileType` such as\n`image/svg+xml` or `application/ld+json` was compiled into a pattern that cannot\nmatch the MIME type it was written as, and files were rejected with a message\nnaming the expected type as the type they already had.\n\nCompare a string `fileType` literally before falling back to the existing regex\nmatch, which partial values like `jpeg` still rely on.", "completion": "fix(common): match string file types containing regex metacharacters"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Neil Horman \nReviewed-by: Nikola Pajkovsky \nMergeDate: Tue Aug 11 05:09:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32250)\n\n(cherry picked from commit 72f063b8403210c876372ab1941c9e8c1b4c5dda)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Neil Horman \nReviewed-by: Nikola Pajkovsky \nMergeDate: Tue Aug 11 05:09:36 2026\n(Merged from https://github.com/openssl/openssl/pull/32250)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Mon Aug 10 14:00:08 2026\n(Merged from https://github.com/openssl/openssl/pull/32249)\n\n(cherry picked from commit e12d71f09a4cd41ca45920fe589b99df3b85532a)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Andrew Dinh \nReviewed-by: Neil Horman \nMergeDate: Mon Aug 10 14:00:08 2026\n(Merged from https://github.com/openssl/openssl/pull/32249)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Neil Horman \nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:44 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)\n\n(cherry picked from commit 5b4df6eac1a7d228ad2a8f08d45c7d0a13992026)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nNewer versions require the use of the derivation function and non-use is\nan error. This means a number of tests must be inhibited in such situations.\n\nReviewed-by: Neil Horman \nReviewed-by: Viktor Dukhovni \nReviewed-by: Milan Broz \nReviewed-by: Andrew Dinh \nMergeDate: Mon Aug 10 12:01:44 2026\n(Merged from https://github.com/openssl/openssl/pull/32235)", "completion": "evp_test: condition CTR-DRBG tests on FIPS version when the df is not used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* docs: update moved JSX specification links\n\nThe JSX specification moved from the `facebook` GitHub organization to\n`react`, so https://facebook.github.io/jsx/ now returns a 404. GitHub\nPages does not redirect across organization renames, so the old URL is\npermanently dead.\n\nPoints the three remaining references at https://react.github.io/jsx/.\n\nThe nearby link to github.com/facebook/jsx/issues/25 is left unchanged\nbecause GitHub does redirect renamed repositories, so it still resolves.\n\n* Update lib/rules/no-useless-escape.js\n\nCo-authored-by: Milos Djermanovic \n\n---------", "completion": "docs: update moved JSX specification links"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 9a2663322c330ff11275abafd612e9c99407a94a #17572\nFollow-up to c96f982166fbc671b77f84a1730e9b6d11357e8f #10451\n\nCloses #22521", "completion": "build: replace `assert()` with `DEBUGASSERT()`, where missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 493a46c61983195c2b49bfde75ffba0321e5e69d)\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 10:04:26 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 493a46c61983195c2b49bfde75ffba0321e5e69d)\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 10:00:11 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 493a46c61983195c2b49bfde75ffba0321e5e69d)\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:57:46 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 493a46c61983195c2b49bfde75ffba0321e5e69d)\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:54:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\n\n(cherry picked from commit 493a46c61983195c2b49bfde75ffba0321e5e69d)\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:37:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCCM Final was routed through an update helper whose pointer-based\ndispatch treats a NULL-input call as a no-op or a length declaration.\nIf an empty message skips payload Update, decryption can therefore skip\ntag verification and encryption does not generate a tag.\n\nProcess an empty payload during Final only when the existing state flags\nshow that no payload operation took place. Route the NULL-input\nEVP_Cipher() form through the same Final path.\n\nEnable CCM in the generic zero-length AEAD test. Declare the zero payload\nlength and supply AAD while deliberately omitting payload Update.\n\nFixes #32253\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Tomas Mraz \nReviewed-by: Bob Beck \nMerge-date: Fri Aug 21 08:51:03 2026\nMerged-from: https://github.com/openssl/openssl/pull/32256", "completion": "CCM: authenticate empty Final when payload Update is skipped"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nvim-patch.sh fails to detect n/a patches\nbecause of ifdef FEAT_ guards and reserved Vim9script error codes.\n\nIgnore all conditional directives for Vim's \"FEAT_\" guards.\nhttps://cppreference.com/c/preprocessor/conditional", "completion": "build(vim-patch): n/a patches from comments, ifdefs #41247"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSuggested by @bbbrumley in review of #31617.\n\nReferences #15076 (add constant time coverage everywhere).\n\nAssisted-by: Claude:claude-sonnet-5\nReviewed-by: Jakub Zelenka \nReviewed-by: Shane Lontis \nMerge-date: Tue Sep 1 14:06:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/32255", "completion": "Test the constant-time validation helpers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe VAES CBC decryptor uses volatile stores to clear its source-level\nround-key array. With GCC 13.3 at -O3, scalar replacement separates\nthat object from the stack slots holding broadcast round keys. The\nstores remain, but the actual key spills survive return.\n\nRoute cleanup through a dedicated perlasm helper. Passing rk across\nthis opaque assembly boundary forces optimized callers to materialize\nthe consumed key array. The helper erases exactly 11, 13, or 15\n64-byte entries and scrubs caller-clobbered vector and general-purpose\nregister state within the System V and Win64 ABI constraints. Gate\nVAES-CBC eligibility on assembler support and include the helper in\nregular and FIPS builds.\n\nThis is a pragmatic boundary rather than a guarantee against every\ncompiler-created spill or abnormal exit. In particular, the Win64 ABI\nrequires the low 128 bits of XMM6-XMM15 to remain intact until the\ncaller restores them. A complete guarantee would require moving the\ndecryptor behind an assembly or custom-ABI boundary.\n\nFixes #32254\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Shane Lontis \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:00:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32257", "completion": "Fix VAES CBC round-key stack cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn particular, clarify that they focus on the Lightweight CMP Profile\nand that the server is single-threaded.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Thu Aug 27 07:24:59 2026\n(Merged from https://github.com/openssl/openssl/pull/28988)\n\n(cherry picked from commit 44635ff58b34e677b1bcf4bd87be07c4698d414c)", "completion": "OSSL_CMP_{exec_certreq,SRV_CTX}_new.pod: enrich doc of CMP client and server"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn particular, clarify that they focus on the Lightweight CMP Profile\nand that the server is single-threaded.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Thu Aug 27 07:24:59 2026\n(Merged from https://github.com/openssl/openssl/pull/28988)", "completion": "OSSL_CMP_{exec_certreq,SRV_CTX}_new.pod: enrich doc of CMP client and server"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\n`useBodyParser()` never checked its options argument.\n`Options` occurs only inside `Omit`, a non-inferrable position, so it always\nfell back to its default, and that default carries a `[key: string]: unknown` index signature.\n`keyof` on it is `string | number`, `Exclude` removes nothing, and the\nresulting `Pick` collapses to bare index signatures. Every call therefore\naccepted any key, any value type, and even `verify` (the single option the signature claims to\nremove, and the one Nest reserves to capture `rawBody`).\n\nKey the options off the `parser` argument instead. `NestExpressBodyParserOptionsMap` maps each\nparser to the options object its Express factory accepts, derived from `express` itself so the two\ncannot drift, and `NestExpressBodyParserType` is now `keyof` that map. The type parameter is\ninferred from `parser`, a real inference site, so `useBodyParser('json', ...)` accepts only\n`express.json` options and now rejects typos, wrong value types, options belonging to a different\nparser, and `verify`.\n\nThis is a types-only change; no emitted JavaScript differs.\n\n`NestExpressBodyParserOptions` is\ndeprecated rather than removed, and calls that pass no explicit type argument are unaffected.\n\nBREAKING CHANGE: `useBodyParser` now takes the parser type as its first type argument.\nCalls that\npass an explicit options type, such as `app.useBodyParser('urlencoded', {...})`, no longer compile.\nDrop the type argument and let it be inferred from the parser argument.", "completion": "feat: narrow body parser options to the selected parser"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n\":call nvim_get_mode()\" logs a nonsense channel-id:\n\n RPC: ch 9223372036854775808: invoke nvim_get_mode\n\nSolution:\nCheck `is_internal_call`.\nAlso, skip this logging for RPC calls, because it's redundant with\n`log_request`/`log_notify`.\n\n API: vim -> nvim_get_mode", "completion": "fix(logging): vimscript API calls #41253"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nEleven arguments are named one way in the header and another in the\ndefinition. the compiler only checks types so nothing is broken, but the\nheader is what people read first, and then the name changes under them\nin the source:\n\n```\ncurl_dbg_malloc size -> wantedsize\ncurl_dbg_calloc n, size -> wanted_elements, wanted_size\ncurl_dbg_realloc size -> wantedsize\ncurl_dbg_strdup src -> source\nr_freeaddrinfo res -> cahead\nmy_get_line fp, db -> input, buf\ncurl_slist_append_ccsid l -> list\ncurl_version_info_ccsid cid -> ccsid\ncurl_easy_setopt_ccsid curl -> easy\n```\n\nFollow-up to df6014894b789768b139fff27e8aed9dbc46ed79 #20794\n\nCloses #22550", "completion": "headers: name the arguments the way the definitions name them"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npgstat_get_entry_ref() called dshash_find_or_insert() to insert a new\nentry into the shared pgstats hashtable. If the allocation required for\nthe new entry fails, a local cache entry would be left in\npgStatEntryRefHash with a NULL shared_entry. This code is switched to\nuse dshash_find_or_insert_extended(), so as local hash entries can be\ncleaned up before failuring. This change makes pgstat_get_entry_ref()\nmore robust on re-entry.\n\nTaken in isolation within a single backend, local entries are handled\nfine on HEAD as pgstat_get_entry_ref() is able to handle the case of a\nNULL shared_entry on re-entry. However it is possible to finish with\nsome NULL pointer dereference in more complex scenarios, like:\n- First backend fails insert into the shared hashtable on OOM.\n- Second backend bumps the same entry's refcount (due to\nreinitialization of the same entry, for example).\n- First backend calls pgstat_gc_entry_refs(), uses its local entry\nreference with the NULL shared_entry, crashes when checking if the\nshared entry has been dropped.\n\n6f0738ddec85 has introduced dshash_find_or_insert_extended() for the\nsame reason as what we are dealing with here: the backend could be left\nin an inconsistent stat, and clean up actions need to be taken before\nissuing an error. The failure is unlikely going to show up in practice,\nso no backpatch is done. This hash insert extended routine is new as of\nv19.\n\nAuthor: Michael Paquier \nDiscussion: https://postgr.es/m/anV8ftNMW3xyKSMG@paquier.xyz", "completion": "Use OOM-safe routine for pgstats shared hashtable insert"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ncryptohash_openssl.c initialized the EVP_MD_CTX with the implicit static\ndigest objects (EVP_sha256() and friends). These do not dispatch\nthrough a loaded provider. OpenSSL 3.0 and newer versions recommend to\nswitch to an explicit fetch, using EVP_MD_fetch(), the older routines\nbeing deprecated, available for backward-compatibility purposes.\n\nNow, when building with OpenSSL 3.0 or a newer bersion, we fetch the\ndigest by name with EVP_MD_fetch(), cache it in the context, and free it\non teardown. This has as consequence to feed the hash from a provider.\nThe implicit path is kept for older OpenSSL, 1.1.1 being the oldest\nversion still supported on HEAD, and for LibreSSL.\n\nThis is a slight change in the hashing logic. No backpatch is done as\nthat looks safer, and the code in the back-branches is also able to\nwork. This has been locally tested across OpenSSL 1.1.1 up to 3.5, so\nhopefully nothing is broken.\n\nNote: The submitted code was clearly AI-generated. I have spend a bit\nof time cleaning it up, making it more consistent with the project style\nin terms of coding, adjusting a few more things on the way.\n\nAuthor: Mark Atwood \nCo-authored-by: Michael Paquier \nDiscussion: https://postgr.es/m/178596055358.1584287.8485463954311014881@reviewcommit.com", "completion": "Use explicit fetching for digests in cryptohash (OpenSSL >= 3.0)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15236", "completion": "fix(runtime-vapor): clean up teleport targets on scope disposal"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22524", "completion": "ldap: reject control characters in URL-decoded filter values"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15227", "completion": "fix(runtime-vapor): normalize class prop passed to components"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerate an empty-message tag with the streaming path, then check that\nEVP_Cipher() decryption accepts the correct tag and rejects a corrupted\none. Also verify that EVP_Cipher() encryption produces the same tag.\n\nCover AES-OCB and ChaCha20-Poly1305, with and without AAD.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 17:43:25 2026\nMerged-from: https://github.com/openssl/openssl/pull/32417", "completion": "Add tests for empty AEAD EVP_Cipher() finalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerate an empty-message tag with the streaming path, then check that\nEVP_Cipher() decryption accepts the correct tag and rejects a corrupted\none. Also verify that EVP_Cipher() encryption produces the same tag.\n\nCover AES-OCB, ChaCha20-Poly1305, and AES-GCM-SIV, with and without AAD.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 17:41:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32416\n(cherry picked from commit e9fb43aee8654b492ed8a239d3f2bacf13bb9081)", "completion": "Add tests for empty AEAD EVP_Cipher() finalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerate an empty-message tag with the streaming path, then check that\nEVP_Cipher() decryption accepts the correct tag and rejects a corrupted\none. Also verify that EVP_Cipher() encryption produces the same tag.\n\nCover AES-OCB, ChaCha20-Poly1305, and AES-GCM-SIV, with and without AAD.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 17:41:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32416", "completion": "Add tests for empty AEAD EVP_Cipher() finalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerate an empty-message tag with the streaming path, then check that\nEVP_Cipher() decryption accepts the correct tag and rejects a corrupted\none. Also verify that EVP_Cipher() encryption produces the same tag.\n\nCover AES-OCB, ChaCha20-Poly1305, and AES-GCM-SIV, with and without AAD.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 15:58:28 2026\nMerged-from: https://github.com/openssl/openssl/pull/32259", "completion": "Add tests for empty AEAD EVP_Cipher() finalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerate an empty-message tag with the streaming path, then check that\nEVP_Cipher() decryption accepts the correct tag and rejects a corrupted\none. Also verify that EVP_Cipher() encryption produces the same tag.\n\nCover AES-OCB, ChaCha20-Poly1305, and AES-GCM-SIV, with and without AAD.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 15:56:03 2026\nMerged-from: https://github.com/openssl/openssl/pull/32300", "completion": "Add tests for empty AEAD EVP_Cipher() finalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim core did not leverage it to override/customize bell/beep.\nIt wasn't used for custom sounds for system/user (autocmd) events.\nIt should be in-scope for GUI, unlike terminal, even as a plugin\nby leveraging some internal option similar to `set guioptions+=!`.\n\nNo progress as of Vim 9.2 so I quit.", "completion": "build(vim-patch): sound feature is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe legacy HMAC_CTX interface (HMAC_CTX_new(), HMAC_Init_ex(), etc.) has\nbeen deprecated since OpenSSL 3.0. The legacy routines do not dispatch\nthrough the provider framework, so a loaded provider's HMAC\nimplementation could be bypassed.\n\nThis commit updates hmac_openssl.c to use EVP_MAC when building with\nOpenSSL 3.0 or newer versions. OpenSSL 1.1.1 is the oldest version\nsupported on HEAD, so the legacy routines need to be kept. Note that\nLibreSSL uses the legacy routines.\n\nLike b91f79cd08ab, no backpatch is done.\n\nAuthor: Mark Atwood \nCo-authored-by: Michael Paquier \nDiscussion: https://postgr.es/m/178596055149.1584250.13974609482797470185@reviewcommit.com", "completion": "Use EVP_MAC for HMAC (OpenSSL >= 3.0)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 791b6883edc1c02c4b253e8b47237ec13ac66d06 #22521\n\nCloses #22527", "completion": "checksrc: check for `assert`, replace in tests where missing, drop from examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Select): reset clear button background\n\n* test(Select): remove redundant style test", "completion": "fix(Select): remove native clear button background"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nUsing \"a member of\" instead of \"member of\" is consistent with other\nsimilar error messages.\n\nAuthor: Peter Smith \nReviewed-by: Ewan Young \nReviewed-by: Amit Kapila \nDiscussion: https://postgr.es/m/CAHut+Pvyj3ad7g-Sb98LDsf1i4c+92rqr+OVG9Lb3fikc_POLg@mail.gmail.com", "completion": "Fix errmsg grammar for publication membership"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe intended sequence:\n 1. Convert the PR to draft.\n 2. Update branch labels.\n 3. Mark it ready for review.\n 4. Backports CI runs with the updated labels.\n\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:08:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32260\n(cherry picked from commit 0eb3b1575caed6c622f63bb380b5257618a1fa3b)", "completion": "ci: trigger backports on ready_for_review"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe intended sequence:\n 1. Convert the PR to draft.\n 2. Update branch labels.\n 3. Mark it ready for review.\n 4. Backports CI runs with the updated labels.\n\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:08:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32260", "completion": "ci: trigger backports on ready_for_review"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ndtls1_handle_timeout() fails the connection with SSLfatal() once\ndtls1_check_timeout_num() reports that DTLS1_TMO_ALERT_COUNT unanswered\nretransmissions have been sent. It returns at that point without reaching\ndtls1_start_timer(), so next_timeout is left holding a time in the past.\n\nNothing re-arms or clears it afterwards, the connection being finished, so\nevery later dtls1_get_timeout() computes a negative remaining time, clamps it\nto zero and reports the timeout as due immediately. A caller which waits on\nthat timeout therefore never waits at all. The documented\nDTLSv1_get_timeout() plus select() loop turns into a busy loop on any\nconnection which has given up retransmitting, consuming a core until the\napplication gives up on the connection itself.\n\nStop the timer instead. dtls1_stop_timer() zeroes next_timeout, which\ndtls1_get_timeout() already reports as \"no timer running\", so callers see no\npending timeout and wait on whatever other deadline they have.\n\nThe test drives this without waiting by forcing a retransmission timeout of\n1ms, which is below the 15ms floor at which dtls1_get_timeout() treats a\ntimer as already expired. The server therefore retransmits on every read\nattempt and exhausts its budget inside SSL_accept().\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 14 15:45:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32239", "completion": "Stop the DTLS timer when the retransmit budget is exhausted"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npoll_translate_ssl_dtls_conn() adds no file descriptor to the poll set when\nthe connection's BIO cannot supply one, which is the case for the memory and\ndatagram-pair BIOs the test suite is built on. Unlike the QUIC and DTLS\nlistener paths it does not report that as an error, and rightly so: a DTLS\nconnection with no pollable BIO has no readiness to wait for, but it still\nhas a retransmission deadline to wake for, so a wait with nothing to watch is\nmeaningful.\n\nThe resulting empty descriptor set was then handed to the operating system,\nwhere the behaviour differs. poll() treats it as a plain sleep, so this\nworked on Unix. Windows' select() rejects a call with no descriptors, so\nossl_rio_poll_builder_poll() returned failure and SSL_poll() failed with it.\n\nSleep out the deadline explicitly rather than relying on the platform. With\nno descriptors and no deadline nothing could ever provide a wakeup, so that\ncombination is reported as a failure instead of sleeping for ever.\n\nThis has no test of its own: on any platform whose poll() already sleeps, the\nbehaviour before and after is identical, so only the Windows CI builds\ndistinguish them.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 14 15:45:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32239", "completion": "Wait consistently across platforms when there is nothing to poll"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nduring the test backportg, the test was accidentally placed into\nifdef\n\nFixes: 69de45cd12e5 (\"Reject clearly degenerate RSASVE parameters.\")\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tomas Mraz \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 10 10:34:32 2026\n(Merged from https://github.com/openssl/openssl/pull/32261)\n\n(cherry picked from commit 190a56c010a306d8e03216a1db5c4d495f52cb94)", "completion": "move the test code outside of the #ifdef"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nduring the test backportg, the test was accidentally placed into\nifdef\n\nFixes: 69de45cd12e5 (\"Reject clearly degenerate RSASVE parameters.\")\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Tomas Mraz \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Mon Aug 10 10:34:32 2026\n(Merged from https://github.com/openssl/openssl/pull/32261)", "completion": "move the test code outside of the #ifdef"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 4b8c4dfc680fe0b6c6883ff0e641c1ee7f835711)", "completion": "fix(channel): handle socket accept failure #41240"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReorder logic when looking for matching connections. Check candidate\nNegotiate/NTLM state first. Require same \"input\" parameters when\nconnection is already authenticated. Same for proxy.\n\nDeny connection reuse for empty usernames for NTLM/Negotiate using\nconnections.\n\nReported-by: Martin Dukek\nCloses #22528", "completion": "url: fix negotiate/ntlm connection reuse"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAfter #40270, events are no longer emitted from the automatic background\ndetection. This applies not just during startup, but also if the user\nmanually changes the background of their terminal.\n\nSolution:\nSet the background as normal, assuming that a normal terminal will\nrespond within 100 ms. Change test to match expected behavior:\n- BG set during startup won't trigger user autocmds since it runs before\n any user config\n- If the terminal takes longer than 100 ms to respond to initial OSC 11,\n it does trigger the OptionSet, but it is triggered through the normal\n path to ensure values like v:option_new are set #38551\n- BG change after startup still triggers autocmds #41146", "completion": "fix(defaults): emit events on automatic background change #41242"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nA mark moved by nvim_buf_set_extmark() during an edit is misplaced by\nundo and redo. Only splices (\"edits\") are recorded, and replaying them\nreproduces the shifts they caused, never the explicit set: the mark ends\nup wherever the text pushed it.\n\nSolution:\nWhen an open undo block moves an existing mark, record both positions.\nUndo restores the pre-set position, redo re-applies the set.\n\nPartially reverts 18334a4a0cd9 ; ExtmarkSavePos.row/col were unused\nbecause nothing recorded an explicit move, but now `extmark_set()` does.", "completion": "fix(extmarks): undo-redo of a mark explicitly moved during an edit #41252"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* docs: update architecture documentation\n\n* include `js` language\n\n* clarify terminology\n\n* apply review suggestions\n\n* remove mention of directory traversal and file reading", "completion": "docs: update architecture documentation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- CMAKE_INSTALL.md: sync up option desc with `CMakeLists.txt`.\n- sync `--enable-debug` configure text with help description.\n- say `--disable-debug` is the default in help description.\n\nFollow-up to a15cf1ea07963ab9d92803e23a96ac5541c6ba0f #22512\n\nCloses #22532", "completion": "build: minor debug option message fixes/improvements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 51cd5d6f0 used ssup_datum_unsigned_cmp for the OID comparator,\nwhich compares entire Datums. That gave wrong results, since the upper\nhalf of a Datum containing a 32-bit type is not reliably zero-extended:\nvalues fetched from tuples are sign-extended, while values returned\nby e.g. oidin() are zero-extended. An OID with the high bit set could\ntherefore compare as larger or smaller depending on its source.\n\nFix by adding a sort support comparator that only looks at the low 32\nbits. Also teach radix sort to normalize Datums the same way. This keeps\nOID eligible for radix sort. Add a regression test that sorts OIDs above\n2^31 from both kinds of source, taken from Peter Geoghegan's report.\n\nReported-by: Zsolt Parragi \nReported-by: Peter Geoghegan \nSuggested-by: David Rowley \nReviewed-by: David Rowley \nReviewed-by: Zsolt Parragi \nDiscussion: https://postgr.es/m/CAN4CZFM2afRzSLJJiWKnRjqPwL7Scm2Wd1xXu140diJGuJtzGg@mail.gmail.com\nDiscussion: https://postgr.es/m/CAH2-WznvXyKRah=MQ3ONGHiN8ahJcqpmtyikxCOO96A4usDPpg@mail.gmail.com", "completion": "Add ssup_datum_uint32_cmp for comparing OIDs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe previous names used \"unsigned\" for Datum-width abbreviated keys\nand \"signed\" for 64-bit signed integers. This may have made more\nsense when Datum width was platform-dependent, but commit 805c64f84\nadded a 32-bit unsigned variant for OIDs, so it makes even less sense\nnow. Rename all to be explicit about signedness and width.\n\nSuggested-by: David Rowley \nDiscussion: https://postgr.es/m/CAApHDvrNMz5ahN1x=uK9yscTogmLupfLBy-_qMW9Z+k=HE5u_A@mail.gmail.com", "completion": "Rename sort support integer comparators for clarity"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nReplace the per-cell image marker with sparse placement spans attached to\ngrid lines. A placement owns all of its spans and records the input\nprotocol, application image and placement IDs, z-index, and creation order.\n\nThis retains overlapping image layers without storing a list in every grid\ncell. Grid operations move, split, clip, and remove only the affected spans.\n\nUse the input protocol to determine image/text interaction: later text\ndamages SIXEL spans, while Kitty placements remain and are ordered by their\nz-index. Rendering then adapts that one logical scene for each client,\nrather than changing its semantics according to whether the outer terminal\nuses Kitty or SIXEL.", "completion": "image: retain ordered placements in the grid"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAdd API guards for curl_easy_header and curl_easy_nextheader.\n\nurldata.h: remove prevhead member as not used\n\nCloses #22530", "completion": "header api: add guards"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRegister the missing RSA signature OID mappings for SHA-512/224 and SHA-512/256.\n\nThis lets certificate request and X.509 verification resolve the digest and key type.\n\nFixes #32252\n\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 12 10:07:33 2026\nMerged-from: https://github.com/openssl/openssl/pull/32269", "completion": "Fix RSA SHA-512 truncated digest signature mappings"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSince commit 62d712ecfd94, pg_stat_statements has been underestimating\nthe size of the result buffer possible for a normalized query, in cases\nwhere the query includes many squashable lists, causing the normalized\nquery to write past the allocated area.\n\nThe allocated buffer size forgot to account for the comment appended in\na squashable list, \"/*, ... */\". Instead of trying to track down\nprecisely how much space we need, fix by switch to using an expansible\nStringInfo. This not only fixes the bug, but it also makes the code\nsimpler to follow.\n\nAuthor: Álvaro Herrera \nReported-by: Sajeeb Lohani with TrendAI Zero Day Initiative\nReported-by: Yuelin Wang <3020001251@tju.edu.cn>\nDiagnosed-by: Michaël Paquier \nBackpatch-through: 18\nSecurity: CVE-2026-14676\nDiscussion: https://postgr.es/m/19528-7290dd7e6f7dcc22@postgresql.org", "completion": "pg_stat_statements: Fix buffer overflow with query normalization"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nstatatt_get_type() unconditionally converted multirange types to their\nunderlying range type. This choice affected all the type information,\nlike atttypid, atttyptype and operators.\n\nThis made the bounds histogram work correctly (range type is required),\nbut it was wrong for all the other stat kinds. MCV values for a\nmultirange column should be parsed as multirange arrays, not range\narrays. It also made the TYPTYPE_MULTIRANGE check for the range stats\nvalidation as dead code, since atttyptype was always TYPTYPE_RANGE\nafter the conversion due to the centralized statatt_get_type().\n\npg_restore_extended_stats() handles the same case correctly: it keeps\nthe original type and explicitly converts to the range type only at the\npoint where range_histogram_bounds is built.\n\nThe fix of this issue is simple: the multirange-to-range conversion\nneeds to be moved from the centralized statatt_get_type() up to where\nattribute stats build their range_histogram_bounds, matching what is\ndone for extended statistics restore.\n\nThe regression tests for multiranges with attribute stats are extended\nto cover this case.\n\nAuthor: OpenAI Security Research Team\nBackpatch-through: 18\nSecurity: CVE-2026-16238", "completion": "Fix multirange type handling in pg_restore_attribute_stats()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit adds a test for pg_restore_attribute_stats() with the\ninjection of statistics related to a multirange type. This case is\nsupported in statatt_get_type() since its introduction in ce207d2a7901,\nbut there was no test in the main regression test suite to check for the\ncase where attribute stats is restored for a multirange type, as done by\nmultirange_typanalyze().\n\nNote that this has been originally applied as d4504d6f60e0 in v19 and\nnewer branches. This will be used for the test of a follow-up commit.\n\nAuthor: Corey Huinker \nDiscussion: https://postgr.es/m/CADkLM=c3JivzHNXLt-X_JicYknRYwLTiOCHOPiKagm2_vdrFUg@mail.gmail.com\nSecurity: CVE-2026-16238\nBackpatch-through: 18", "completion": "Add test with multirange type for pg_restore_attribute_stats()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhile typical abbreviations are only a few bytes long, a user-supplied\ntime_zone setting could specify a much longer abbreviation, enough to\noverflow to_char's allocation of 12 bytes per format character. If so,\nthrow an error in the same style as commit 9241c84cb (CVE-2015-0241).\n\nReported-by: Hcamael \nReported-by: Amjad Shahzad \nReported-by: Tan Zhen of AntAISecurityLab \nReported-by: Tomer Fichman \nReported-by: Zheng Yu \nReported-by: Amy Burnett (OpenAI Codex Security)\nReported-by: Rick de Jager \nReported-by: Heewon Song \nReported-by: Sylvie Mayer \nReported-by: Aleksander Alekseev \nReported-by: Hillai Ben Sasson \nAuthor: Tom Lane \nBackpatch-through: 14\nSecurity: CVE-2026-14669", "completion": "Guard against overlength time zone abbreviations in to_char()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis is needed so that all versions of pg_upgrade that migrate logical\nreplication slots can parse the new output_plugin_libraries GUC.\n\nBackpatch-through: 17\nSecurity: CVE-2026-6471", "completion": "Move SplitGUCList() to fe_utils"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen a direct SSL connection was established, ProcessStartupPacket()\nstill accepted GSSEncRequest messages. The GSSAPI negotiation would\nthen use raw writes and reads, bypassing the TLS encryption layer.\nAfter the GSS encryption was established, the connection continued to\nuse TLS. This could betray the HBA rules so as the backend does\nprotocol exchanges inconsistent with the connection policies in place,\nwith TLS taking priority over GSS in the backend.\n\nThe SSL negotiation path already guarded against attempts to request\nSSL after a direct SSL request has been processed. The GSS path is now\nguarded the same way when receiving a startup packet.\n\nReported-by: p4p3r \nAuthor: Michael Paquier \nReviewed-by: Jacob Champion \nBackpatch-through: 17\nSecurity: CVE-2026-14681", "completion": "Reject GSSEncRequest after direct SSL connection"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPresently, mock_scram_secret() always uses\nSCRAM_SHA_256_DEFAULT_ITERATIONS, which poses an observable\nresponse discrepancy hazard when scram_iterations is set to\nsomething else. To fix, use the value of the configuration\nparameter instead, and document that unauthenticated users can\ndiscover the existence of roles with passwords created with\ndifferent iteration counts.\n\nReported-by: Radim Marek \nAuthor: Nathan Bossart \nReviewed-by: Michael Paquier \nReviewed-by: Heikki Linnakangas \nReviewed-by: Jacob Champion \nSecurity: CVE-2026-14672\nBackpatch-through: 16", "completion": "Use value of scram_iterations in mock_scram_secret()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe only overflow hazards I could find in tsquery construction\nare in QTN2QT(), which builds a flat tsquery datum from the\nQTNode tree representation used by tsquery_or, tsquery_rewrite,\nand allied functions. There are two:\n\n1. It seems theoretically possible for the outputs of cntsize() to\noverflow an int, so I widened them to size_t. There's no hazard\ncertainly in tsquery_or and friends, but tsquery_rewrite could expand\nthe query tree by large multiples (by replacing many identical\nsubtrees with a large replacement tree), so in a 64-bit machine\nwith plenty of available memory it should be possible to build a\nQTNode tree large enough to cause that. If these counters did\noverflow then we'd under-allocate the output tsquery and have a heap\noverwrite problem. size_t is sufficient, since it's counting the size\nof a subset of an in-memory data structure. We also have to fix the\nTSQUERY_TOO_BIG() macro to not get confused if sumlen exceeds\nMaxAllocSize.\n\n2. fillQT() neglects to check that the new \"distance\" value for a\nQI_VAL item fits into the available 20-bit field. It's quite easy\nto reach this, for example by tsquery_or'ing two near-megabyte-sized\ntsquerys. However, the result is only a corrupt tsquery that does\nnot represent the expected query, so perhaps this doesn't rise to\nthe level of a security bug. Nonetheless it should be fixed.\n\nNote: I followed the practice used in other tsquery code of checking\neach distance value as it's assigned, which means that the last\noperand string could extend past the MAXSTRPOS boundary. This is a\nbit different from the pattern used for tsvectors, which insist that\nthe total data length not exceed MAXSTRPOS and thereby avoid making\nper-item checks. Perhaps that should be harmonized sometime, but for\nnow it's okay for the two types to do this differently as long as\neach one is self-consistent.\n\nAuthor: Tom Lane \nReviewed-by: Amit Langote \nBackpatch-through: 14\nSecurity: CVE-2026", "completion": "Harden tsquery code against overflows."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe core of this patch is to prevent array_to_tsvector() from\ngenerating invalid tsvectors. It did not check for overly-long\nlexemes (so that WordEntry.len fields could overflow), nor did it\ncheck that the total \"datalen\" fits within MAXSTRPOS (so that\nWordEntry.pos fields could overflow, and the number of entries\nin the tsvector could be much more than the normal limit).\nWhile the field overflows couldn't do anything much worse than\nproduce a corrupted tsvector value, a sufficiently large number\nof tsvector entries could cause integer overflows in later\nprocessing, such as tsvectorout.\n\nAnother important fix is to prevent tsvectorrecv() from accepting\ninvalid tsvectors. The main problem there is that it did not\nreject empty-string lexemes. Hence, even though it did (mostly)\nenforce the MAXSTRPOS limit, it could still produce a result\nwith an unreasonable number of tsvector entries, if they were\nprimarily empty strings.\n\nAlso, fix tsvectorout's calculation of its required output\nbuffer size: it was multiplying the string lengths by\npg_database_encoding_max_length() for no reason. That contributed\nto the risk of integer overflow there. With valid tsvector input,\nthere's no risk, but there's still no reason to make the output\nbuffer several times bigger than needed.\n\nI also tried to make a couple of related routines more robust,\nand spent some effort on improving the comments in ts_type.h.\nAlso, standardize on a single spelling of the \"string is too long\nfor tsvector\" message, using %zu instead of an assortment of formats.\nThese changes aren't security per se but came out of inspecting the\ncode for problems.\n\nReported-by: Yuhang Wu and Zhenpeng Lin\nReported-by: Zheng Yu \nReported-by: Hcamael \nAuthor: Tom Lane \nReviewed-by: Amit Langote \nBackpatch-through: 14\nSecurity: CVE-2026-14662", "completion": "Harden tsvector code against overflows."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe parser accepts any string as an EXTRACT() field name, but\ndeparsing does not quote and escape it accordingly. To fix, quote\nand escape the field name during deparsing as needed. It might be\na good idea to validate the field name during parsing and\ndeparsing, too, but that is left as a future exercise.\n\nReported-by: Ben Morris in collaboration with Claude and Anthropic Research\nAuthor: Nathan Bossart \nReviewed-by: Tom Lane \nReviewed-by: Etsuro Fujita \nSecurity: CVE-2026-15741\nBackpatch-through: 14", "completion": "Obstruct EXTRACT() field name deparse injection."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nECPG assumes that any bytea data it receives from a backend starts with\n'\\x' as its first two bytes, but a check was missed to enforce that. A\nrogue server sending some garbage bytea data would be able to crash a\nclient, resulting in a client-side DoS, in the most common cases.\n\nReported-by: ylwangtju \nBackpatch-through: 14\nSecurity: CVE-2026-16241", "completion": "ecpg: Fix out-of-bound writes due to processing of invalid bytea data"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSome of these could overflow on 32-bit systems with the right input.\nConvert all cases where we called palloc() with multiplication to fix\nthem. Not all of them were bugs, but it's better to be safe than\nsorry.\n\nReported-by: Tulya Project, Team Dhiutsa, Bitecope Technologies Private Ltd\nBackpatch-through: 14\nSecurity: CVE-2026-14677", "completion": "Use palloc_array() in pltcl and plperl to avoid overflow"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe CACHESIGN.sign field is a BITVECP, not a TRGM, so you should not\nuse GETSIGN() on it. You don't get a compiler warning because the\nGETSIGN() macro includes a cast. It resulted in a bogus read beyond\nend of buffer, which would cause bad split decisions or a crash if\nyou're very unlucky.\n\nReported-by: Mehmet D. INCE \nBackpatch-through: 14\nSecurity: CVE-2026-14678", "completion": "Fix pg_trgm's picksplit function with all-true datums"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen ALTER TABLE ... ALTER COLUMN TYPE (or any subcommand that rebuilds\nthem) drops and re-creates the extended statistics objects depending on\nthe altered column, the re-created objects were owned by the role running\nALTER TABLE rather than by the original owner of the statistics.\n\nRemember each object's owner before dropping it, and restore it on\nre-creation.\n\nCreateStatistics()'s signature changes and CreateStatsStmt gains a field,\nbut no known third-party code calls the former or constructs the latter.\n\nAuthor: Masahiko Sawada \nReviewed-by: Noah Misch \nBackpatch-through: 14\nSecurity: CVE-2026-6469", "completion": "Preserve the owner of extended statistics rebuilt by ALTER TABLE."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nnumeric_combine() and several other state-combining functions for\naggregates cheated for the case of both inputs being NULL: they\nreturned a null pointer without bothering to mark it as a SQL NULL.\nThis was harmless in the expected usage where the result would be\npassed to the same combine function or a related aggregate final\nfunction. But it's bad news from a security standpoint, because\nnow that value can be passed to an internal-accepting function\neven if said function is strict. While a previous patch prevented\nsuch queries from being issued, it seems like good defense-in-depth\nto expend the few additional lines of code needed to do this properly.\nComparable functions such as array_agg_combine() already do so.\n\nReported-by: Amy Burnett (OpenAI Codex Security)\nAuthor: Tom Lane \nBackpatch-through: 14\nSecurity: CVE-2026-14680", "completion": "Return nulls honestly in aggregate \"combine\" functions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAllowing that is a security hole, since there are many different\nfunctions with different ideas of what their \"internal\" argument or\nresult is. We already had a defense against the easy case of\n\"'foo'::internal\", but that turns out to be insufficient. Lock down\nboth function and operator syntax. Also disallow attempts to cast to\nor from type internal; those would mostly fail anyway, but we have\ncreated some holes with features such as CoerceViaIO.\n\nReported-by: Amy Burnett (OpenAI Codex Security)\nAuthor: Tom Lane \nReviewed-by: Robert Haas \nBackpatch-through: 14\nSecurity: CVE-2026-14680", "completion": "Reject calls from SQL to functions that take or return type internal."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe maximum number of arguments allowed for an aggregate function\nis FUNC_MAX_ARGS-1 (since the underlying transfn and/or finalfn\nwill be called with one more argument). parse_func.c failed to\nenforce this, allowing construction of calls that would try to\npass FUNC_MAX_ARGS+1 to the underlying functions, resulting in\na memory stomp in the executor. Add correct checking there.\n\nSince it's possible that a bad call has been stored in a view or\nSQL function, also add checks in various aggregate-related and\nwindow-function-related code that there are not more than\nFUNC_MAX_ARGS arguments. These will also protect us against the\npossibility that we're trying to run a stored view that was made\nby a server executable with different FUNC_MAX_ARGS. (Arguably,\nthat scenario does not qualify as a security problem. But let's\njust tighten up all of this while we're here, rather than split\nhairs over whether an overrun is reachable.)\n\nLikewise check in compute_function_hashkey. Here the hazard is\ndirectly from a pg_proc row, but the scenario is the same.\n\nPL/Tcl has a similar issue with a fixed-size string buffer.\nLet's just replace that buffer with a Tcl_DString, removing the\nwhole issue and making the code look more like what's around it.\n\nThere are a lot of other FUNC_MAX_ARGS-sized arrays, but the rest\nhave nearby guards already, some with comments explicitly pointing\nout the hazard of FUNC_MAX_ARGS changing.\n\nI also used palloc_array() in a few related places in funcapi.c.\nThose aren't live hazards AFAICS, but nearby code has been\npalloc_array-ified already, so it seemed inconsistent to not use\nit here.\n\nReported-by: Masahiko Sawada \nAuthor: Tom Lane \nReviewed-by: Masahiko Sawada \nBackpatch-through: 14\nSecurity: CVE-2026-14679", "completion": "Protect some fixed-size arrays that have FUNC_MAX_ARGS elements."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe backend doesn't impose any particular limit on the length of this\narray, and since there could be entries for both input and output\narguments, it's feasible for the length to exceed FUNC_MAX_ARGS\neven without funny business. This could lead to crashes or worse.\n\nMoreover, pg_dump shouldn't rely on hard-coding FUNC_MAX_ARGS in the\nfirst place: it has no business assuming that the backend it's dumping\nfrom was compiled with the same value of FUNC_MAX_ARGS that it is.\nSo the stanza in dumpFunc() that allocates exactly FUNC_MAX_ARGS space\nfor the parsed OID array is fundamentally misguided. And it's broken\nin another way too: if there are exactly FUNC_MAX_ARGS OIDs, then\nparseOidArray won't zero-fill any entries, allowing the subsequent\nloop to run off the end of the array. A crash seems unlikely in\nthis variant, but garbage output is certain.\n\nTo fix, redesign parseOidArray's API so that it does the\narray-mallocing, which simplifies the callers anyway. While we're\nhere, tighten and modernize it a bit; in particular, split it into\nseparate functions for OIDs and integers, as was foreseen long ago.\nThis lets us get rid of the confusing type-punning involved in\nhaving IndxInfo.indkeys be declared as \"Oid *\" when it's really\npotentially-signed ints. Also, most of the callers expect an exact\nnumber of array entries, so make it verify that not just check for\n\"too many\".\n\nI noted while testing that this dumpFunc() stanza isn't even reached\nduring check-world. Add a function with transform to the regression\ntests to rectify that.\n\nReported-by: Masahiko Sawada \nAuthor: Tom Lane \nReviewed-by: Masahiko Sawada \nBackpatch-through: 14\nSecurity: CVE-2026-19385", "completion": "pg_dump: avoid assuming how long pg_proc.protrftypes can be."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nMatchNamedCall's arggiven array was declared FUNC_MAX_ARGS long,\nbut we may actually use up to pronallargs elements, and that can\nbe more than FUNC_MAX_ARGS if the function has OUT arguments\n(cf. ProcedureCreate). Convert it to a palloc'd array.\n\nReported-by: Zheng Yu \nReported-by: ylwangtju \nAuthor: Tom Lane \nReviewed-by: Michael Paquier \nReviewed-by: Masahiko Sawada \nBackpatch-through: 14\nSecurity: CVE-2026-14679", "completion": "Replace fixed-size, too-short array with a palloc'd one."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe special case here for estimating conditions involving a ctid\ncolumn failed to check that the RHS constant is of type tid.\nWhile that'd always be true for the built-in operators that\nreference this selectivity estimator, a maliciously constructed\noperator could provide a user-controlled Datum value that would\nget interpreted as an ItemPointer pointer. That at least risks\nSIGSEGV, and perhaps with a bit of sweat it could be used for\nserver memory disclosure.\n\nReported-by: Hcamael \nAuthor: Tom Lane \nReviewed-by: Noah Misch \nBackpatch-through: 14\nSecurity: CVE-2026-14668", "completion": "Be more wary about constant's datatype in scalarineqsel()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nTied arrays might report different sizes each time they are inspected.\nTo avoid generating a corrupt result array, fix plperl_array_to_datum()\nto read av_len() of each input array only once. If the input does\nappear to get shorter, we'll fill nulls for the now-missing entries,\nwhich seems fine. Conversely, if it gets longer, we'll ignore the new\nentries.\n\nplperl_to_hstore() assumed that Perl's hv_iterinit() returns the\nnumber of entries in the given Perl hash. Usually that's true,\nbut per the Perl docs, \"the return value is currently only meaningful\nfor hashes without tie magic\". That could potentially end in a memory\nstomp. We don't depend on that result value anywhere else, so don't\ndo so here either.\n\nReported-by: Hcamael \nAuthor: Tom Lane \nReviewed-by: Andrew Dunstan \nBackpatch-through: 14\nSecurity: CVE-2026-14670", "completion": "Harden PL/Perl code against \"tied\" Perl arrays and hashes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nsetup_regexp_matches() sizes the buffer used to convert matched\nsubstrings back from pg_wchar form at the smaller of maxlen*eml and\nthe original string's byte length, on the assumption that such a\nconversion cannot produce more bytes than the string it came\nfrom. That assumption holds only for validly encoded input. But\npg_mb2wchar_with_len() silently accepts bytes that are invalid in the\ndatabase encoding, turning each such byte into one pg_wchar, and\nconverting that back can take more bytes than the input did. A string\nmade of such bytes therefore overruns the conversion buffer by up to\nits own length, corrupting the following memory. regexp_match(),\nregexp_matches(), regexp_split_to_table() and regexp_split_to_array()\nare all affected.\n\nFix by dropping the tighter bound and always allocating maxlen*eml + 1\nbytes.\n\nReported-by: Francesco Verardi \nAuthor: Masahiko Sawada \nReviewed-by: Tom Lane \nBackpatch-through: 14\nSecurity: CVE-2026-14664", "completion": "Fix potential buffer overrun in regexp match/split functions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit addresses two defects in this SQL function, the code\nassuming that:\n- The user-supplied string was long enough to contain a character of the\nlength implied by the first byte. It is possible to provide in input\ndata that was able to disclose a few bytes of server memory, allowing\nout-of-bound reads.\n- Specific bytes had values within the expected range, using a set of\nassertions to validate them. The assertions could be triggered on\ninvalid input. These are replaced by tests and error reports.\n\nReported-by: Hcamael \nAuthor: Michael Paquier \nReviewed-by: Robert Haas \nBackpatch-through: 14\nSecurity: CVE-2026-18024", "completion": "Fix out-of-bound reads with ascii() for invalid multibyte characters"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIf the COPY command fails before sending PGRES_COPY_IN, psql did\nnot realize that it ought to consume any in-line data following\nthe command. Failing to do so leads to trying to execute that\ndata as SQL commands, which in the best case is wrong and in the\nworst case is a SQL-injection hazard.\n\nTo fix:\n\n1. Extend psqlscan.l to recognize COPY ... FROM STDIN. This can\nbe done with a pretty simple extension to the logic that already\nrecognizes nested BEGIN blocks within CREATE FUNCTION et al.\nBut unlike that case, we need to consider and count multiple COPY\ncommands within a single query string (separated by \"\\;\"). The\nfallout from that is that psql_scan_reset must now always be called\nbefore starting a new query string. (The comment for it that claimed\nwe didn't need that because \"the scan state must be INITIAL\" was\nreally obsolete already, since it has long reset more state besides\nstart_state.)\n\n2. Teach handleCopyIn() to read and discard data when passed\nNULL for \"conn\".\n\n3. Add logic to SendQuery() to call handleCopyIn() that way\nif the query string contained COPY ... FROM STDIN command(s)\nthat remain unaccounted-for at the end.\n\nNow that we have this counting logic, we can also detect\nif the backend sends an unexpected PGRES_COPY_IN message.\nThat should never happen, but perhaps a malicious server\ncould try to extract data that way.\n\nA side-effect of doing this is that we have to adjust a number of test\nscripts that thought they needn't write \"\\.\" after a COPY FROM STDIN\nthat they expect to fail. On the whole this is an improvement, since\nthere's now a uniform rule \"write \\. after COPY FROM STDIN, whether\nyou expect it to work or not\". But it is an annoying amount of test\nchurn.\n\nA loose end in this patch is that if it has to skip data, it assumes\nthat that data is text not binary. It seems unduly difficult to\ndetect whether the COPY command requested binary (we could handle the\nold-style COPY BINARY ... syntax, but not the new style with format\noptions).", "completion": "Teach psql to skip in-line COPY ... FROM STDIN data after a failure."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen we implemented \\if ... \\endif in psql, we arranged to\nsave/restore the lexer's parenthesis depth counter across any chunk\nof input that we're ignoring. At the time, that was sufficient,\nbecause no other part of PsqlScanState could need to be restored to\nits prior value. However, commit e717a9a18 and follow-ons added\nmore state fields that ought to be restored to their prior values.\nA problem would only be observed if someone tries to \\if out a\nportion of a CREATE FUNCTION/PROCEDURE command that is relevant to\nBEGIN/END matching, which seems like a pretty unusual usage, so the\nlack of field reports isn't surprising. Nonetheless it's a bug.\n\nTo fix, replace the simple counter field in ConditionalStack\nentries with a pointer to a struct defined by psqlscan_int.h.\n(In the back branches, keep the old field and associated functions\nto minimize the risk of API/ABI breakage, even though it seems\nunlikely that any third-party code is using this. Making the\nnew struct private to psqlscan-related code should prevent API/ABI\nissues for future additions of this type.)\n\nIn itself this is only a minor bug fix, but it's prerequisite\ninfrastructure for the fix for CVE-2026-6464, which will add\nanother such field.\n\nAuthor: Tom Lane \nReviewed-by: Noah Misch \nBackpatch-through: 14\nSecurity: CVE-2026-6464", "completion": "Save/restore more lexer state when skipping text due to \\if."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nRole membership, role attribute, and database ownership changes may\nimpact the expected behavior of row-level security policies, but\ncurrently the plan cache doesn't take notice. To fix, register\nsyscache callbacks on pg_auth_members, pg_authid, and pg_database\nthat invalidate the role-dependent plans. Changes to other\ndatabases' pg_database rows are ignored.\n\nReported-by: Ilya Staroverov \nReported-by: Shinya Kato \nAuthor: Ilya Staroverov \nAuthor: Shinya Kato \nCo-authored-by: Nathan Bossart \nReviewed-by: Tom Lane \nSecurity: CVE-2026-14666\nBackpatch-through: 14", "completion": "Invalidate plan cache after role changes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis omission allowed roles without USAGE on a type to create\ntables that depend on it, which could prevent the owner from\nchanging the type later.\n\nReported-by: Nathan Bossart \nAuthor: Nathan Bossart \nReviewed-by: Robert Haas \nSecurity: CVE-2026-6470\nBackpatch-through: 14", "completion": "Check for USAGE privilege on the composite type in ALTER TABLE OF."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis omission allowed roles without USAGE on a type to create\nstored expressions that depend on it, which could prevent the owner\nfrom changing the type later.\n\nThe checks deliberately live in the command paths rather than the\ndependency-recording routines. Those routines also run whenever\nthe server re-derives an existing expression, and re-checking there\nwould break routine maintenance for an owner who has since lost\nUSAGE on a type its objects already reference. (Checking in the\ndependency-recording routines would also require additional\nCommandCounterIncrement() calls to avoid spurious errors.)\n\nThe addition of a parameter to AlterDomainAddConstraint() breaks\nABI compatibility, but we are unaware of any impacted third-party\ncode.\n\nReported-by: Noah Misch \nAuthor: Nathan Bossart \nReviewed-by: Noah Misch \nReviewed-by: Tom Lane \nReviewed-by: Robert Haas \nSecurity: CVE-2026-6470\nBackpatch-through: 14", "completion": "Check for USAGE privilege on types used by stored expressions."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis omission allowed roles without USAGE on a type to create range\ntypes that depend on it, which could prevent the owner from\nchanging the type later.\n\nReported-by: Jingzhou Fu \nAuthor: Nathan Bossart \nReviewed-by: Noah Misch \nReviewed-by: Robert Haas \nSecurity: CVE-2026-6470\nBackpatch-through: 14", "completion": "Check for USAGE privilege on the subtype in CREATE TYPE AS RANGE."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nlevenshtein() and levenshtein_less_equal() let the caller specify\nthe insertion, deletion, and substitution costs, and\nfuzzystrmatch's corresponding SQL functions accept any 32-bit\ninteger for each. Since the distances are calculated with 32-bit\narithmetic, large costs can cause overflows, thereby producing\nnonsensical results. Certain inputs to levenshtein_less_equal()\ncan even cause out-of-bounds writes. To fix, use 64-bit arithmetic\ninstead, and error whenever the final result won't fit in the\nreturned 32-bit integer.\n\nWe may want to teach these functions to reject negative costs, too,\nbut that didn't seem appropriate for a security fix, and therefore\nit is left as a future exercise.\n\nReported-by: Ben Morris in collaboration with Claude and Anthropic Research\nAuthor: Nathan Bossart \nReviewed-by: Dean Rasheed \nSecurity: CVE-2026-15742\nBackpatch-through: 14", "completion": "Avoid overflow in Levenshtein distance calculations."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen an EXECUTE or FETCH statement is executed, there are two portals:\nan outer portal that is created for the EXECUTE or FETCH statement itself,\nand an inner portal for the statement being executed on its behalf.\nBefore this commit, nothing checked that these two portals agreed on\nthe tuple descriptor of the rows being returned. This can be leveraged\nto disclose server memory contents and achieve arbitrary code execution.\n\nTo prevent that, we can make use of an existing safety mechanism,\nadded by Tom Lane in commit 2f48ede080f42b97b594fb14102c82ca1001b80c,\nwhich allows a tuplestore DestReceiver to be informed of the tupleDesc\nrequired by the caller, and which will cause an ERROR to occur if\nthat doesn't match the tupleDesc of what emerges from the executor\n(modulo dropped columns, which aren't an issue in the case at hand).\n\nReported-by: Ben Morris in collaboration with Claude and Anthropic Research\nReported-by: Peter Geoghegan \nReviewed-by: Michael Paquier \nSecurity: CVE-2026-16239", "completion": "Cross-check the type of a portal running EXECUTE or FETCH."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nREPLICATION users were not previously subject to restrictions on output\nplugin paths, so they were able to bypass LOAD-time protections during\nlogical decoding. Unfortunately, adding the standard LOAD restrictions\nnow would retroactively require all third-party output plugins to be\ninstalled under the $libdir/plugins directory. This would prevent the\nuse of dynamic_library_path, introduce a wire incompatibility for\nclients, and require all plugin authors to check that their libraries\nare safe for use by any unprivileged user; we want to avoid that.\n\nInstead, introduce an output_plugin_libraries GUC so that DBAs can\nspecify the output plugins that are trusted for use in logical decoding.\nFor simplicity, superusers are subject to the restriction as well\n(though they're free to modify the GUC at will during a session, so no\npower is actually lost).\n\nThe default setting is 'pgoutput, test_decoding'. If other third-party\nplugins are in use, DBAs will need to modify this parameter after they\nupdate. Some pointers have been added to the documentation to assist\nwith this.\n\nAuthor: Jacob Champion \nReported-by: Vladimir Tokarev \nReported-by: Yu Kunpeng \nReviewed-by: Álvaro Herrera \nReviewed-by: Noah Misch \nReviewed-by: Robert Haas \nReviewed-by: Tom Lane \nBackpatch-through: 14\nSecurity: CVE-2026-6471", "completion": "Add an output_plugin_libraries GUC to bless trusted output plugins"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA grantee of amcheck function EXECUTE privilege could execute arbitrary\nfunctions as the owners of expression indexes that depend on the search\npath. An expression like (lower(col)) was not vulnerable, because\nlower() is resolved at CREATE INDEX time. However, an expression\ncalling an sql-language or plpgsql-language function often was\nvulnerable, even if it used search_path only to find objects in\npg_catalog. The amcheck documentation has been warning about data\ndisclosure after such a GRANT, not about function execution.\n\nThis might cause new amcheck errors when index expressions rely on a\nbroader search_path. Such indexes have seen errors during auto-analyze\nsince CVE-2018-1058 commit 582edc369cdbd348d68441fc50fa26a84afd0c1a, and\nv17 amcheck always worked this way. Hence, the risk is low.\n\nLeave a comment on the one other sandbox entrance that doesn't empty\nsearch_path. In its case, the choice was valid.\n\nBack-patch to v14 (all supported versions), but v17 was safe already.\nCommit 2af07e2f749a9208ca1ed84fa1d8fe0e75833288 (v17) unintentionally\nblocked the attack, and commit d70b17636ddf1ea2c71d1c7bc477372b36ccb66b\n(v18) unintentionally removed that protection. Hence, this adds to v17\njust a test and a comment. While emptying search_path became more\nwidespread in commit 2af07e2f749a9208ca1ed84fa1d8fe0e75833288 (v17),\nnone of its other changes blocked an attack available in v16, even when\nconsidering GRANT. For example, brin_summarize_range() has had an owner\ncheck that GRANT does not override.\n\nReported-by: 王跃林 \nReported-by: Jacob Brazeal \nBackpatch-through: 14\nSecurity: CVE-2026-14673", "completion": "Empty search_path in amcheck."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis oversight in commit 71ea0d6795 allows a malicious server to\ninject shell commands into plain-text dump output that are run at\nrestore time on the machine running psql. To fix, interpret all\ntext after \\unrestrict until the end of the line as its argument.\n\nReported-by: Lucas Velgus \nReported-by: Filip Janus \nReported-by: Daniel Bakker \nAuthor: Nathan Bossart \nReviewed-by: Robert Haas \nReviewed-by: Noah Misch \nSecurity: CVE-2026-18408\nBackpatch-through: 14", "completion": "psql: Don't do backquote expansion in \\unrestrict."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe previous commit raises an ERROR during PGP operations if OpenSSL\ndoes not support the cipher in use. However, any existing messages\ncreated with faulty encryption will no longer be accessible via\npgp_[sym|pub]_decrypt().\n\nTo help users out of this situation, add a new ignore-cipher-failure\noption which reverts to the broken behavior during decryption only. A\nfaulty encryption wrapper, created by an OpenSSL configuration that does\nnot support the cipher, can then be stripped back off by that same\nOpenSSL in order to safely reencrypt it. (Note that when OpenSSL does\nsupport the cipher, corrupted messages will not be decrypted regardless\nof the ignore-cipher-failure setting; this is unchanged.)\n\nThe new tests add a corrupted Blowfish message for both public- and\nsymmetric-key decryption, resulting in the following test matrix:\n\n- Blowfish supported, default behavior: fails to decrypt\n- Blowfish supported, ignore-cipher-failure: fails to decrypt\n- Blowfish unsupported, default behavior: fails to load cipher\n- Blowfish unsupported, ignore-cipher-failure: strips faulty encryption\n\nThe previous commit's change to the pubkey tests is expanded similarly:\ncorrectly encrypted messages cannot be decrypted by an OpenSSL that does\nnot support the cipher, regardless of the option's setting, though the\nfailure mode will change.\n\nSuggested-by: Noah Misch \nReviewed-by: Daniel Gustafsson \nReviewed-by: Noah Misch \nSecurity: CVE-2026-14663\nBackpatch-through: 14", "completion": "pgcrypto: Add option to revert to prior decryption behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPGP encryption was using px_cipher_encrypt without checking if any\nerror was returned. When OpenSSL is running in FIPS mode, or when\nthe legacy provider hasn't been loaded, not all ciphers which are\nsupported by the PGP code are available and fail the init step in\npx_cipher_encrypt. Since the PGP encryption failed to notice this\nit XORed the non-encrypted block with the plaintext, effectively\ndisabling the encryption.\n\nThis was found due to a report of PGP encryption not respecting\nthe pgcrypto.builtin_crypto_enabled flag and allowing Blowfish\nand DES. This however turned out to be a false positive, since\nthe PGP code only use ciphers from OpenSSL and not the built in\nciphers.\n\nBug: #19457\nReported-by: Shishir Sharma \nReviewed-by: Jacob Champion \nDiscussion: https://postgr.es/m/19457-4bab15c17aea36c7@postgresql.org\nSecurity: CVE-2026-14663\nBackpatch-through: 14", "completion": "Fix errorhandling for PGP encryption"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nScrolling to the top or bottom of the version picker's dropdown list\nlet the scroll event chain into the page behind it, causing the whole\napp to scroll. The search dialog and search history dropdowns already\nguard against this with overscroll-behavior: contain; apply the same\nfix to the version picker.\n\n(cherry picked from commit 768c8c29dc3388017bcef37ce5eb01c15e13533f)", "completion": "fix(docs-infra): contain scroll within version picker dropdown"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nScrolling to the top or bottom of the version picker's dropdown list\nlet the scroll event chain into the page behind it, causing the whole\napp to scroll. The search dialog and search history dropdowns already\nguard against this with overscroll-behavior: contain; apply the same\nfix to the version picker.", "completion": "fix(docs-infra): contain scroll within version picker dropdown"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSSL_accept_connection() looped calling ossl_dtls_tick() with nothing in\nbetween, so it only avoided spinning if the application supplied a\nblocking network BIO and each tick slept inside BIO_recvmmsg().\n\nA listener cannot require that. It demultiplexes one socket to many\nconnections and ossl_dgram_demux_pump() holds the demux lock across the\nreceive, so a thread blocked in accept stalls reads on every established\nconnection until a datagram for any peer arrives. QUIC takes the\nopposite approach, keeping the socket non-blocking and waiting for\nreadiness instead.\n\nDo the same: set the listener's network BIO non-blocking and wait\nbetween ticks via ossl_dtls_block_until_ready(), which reuses\nSSL_poll()'s blocking machinery. It reads nothing out, so the caller\nre-tests its own condition and waits again if the wakeup was not for it.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug 17 08:29:51 2026\nMerged-from: https://github.com/openssl/openssl/pull/32324", "completion": "DTLS 1.3 Wait rather than spin in the blocking accept path"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth tests describe themselves in terms of \"blocking mode\" and\n\"non-blocking behaviour\", when what they actually vary is the\nSSL_ACCEPT_CONNECTION_NO_BLOCK flag. That reads as though they concern a\nmode on the object, which invites confusion with\nSSL_set_blocking_mode(). Name the flag, and say what each case is really\nasserting.\n\nComment only, no functional change.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug 17 08:29:53 2026\nMerged-from: https://github.com/openssl/openssl/pull/32324", "completion": "DTLS 1.3 Name the accept flag in the no-BIO test comments"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency @types/jsdom to v30"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSecurity: CVE-2026-6470, CVE-2026-6471, CVE-2026-6469", "completion": "Update .abi-compliance-history for security fixes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`getTIcu` and `setTIcu` performed `hasOwnProperty` checks with string\nliterals (`'currentCaseLViewIndex'` and `'tView'`). Under Closure Compiler\nproperty renaming optimizations, these properties are minified but the\nstring literals are not, causing property lookups and type discriminations\nto fail.\n\nThis commit defines closure-safe property constants using\n`getClosureSafeProperty` so the property names are renamed consistently.\n\n(cherry picked from commit 8925a4ee491aebaf6a1a74880c73dfb20e0a4ba1)", "completion": "fix(core): ensure i18n_util hasOwnProperty checks are safe for property renaming"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`getTIcu` and `setTIcu` performed `hasOwnProperty` checks with string\nliterals (`'currentCaseLViewIndex'` and `'tView'`). Under Closure Compiler\nproperty renaming optimizations, these properties are minified but the\nstring literals are not, causing property lookups and type discriminations\nto fail.\n\nThis commit defines closure-safe property constants using\n`getClosureSafeProperty` so the property names are renamed consistently.", "completion": "fix(core): ensure i18n_util hasOwnProperty checks are safe for property renaming"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRef: #22533\nFollow-up to 2a46df31fdb91851895bc46d81f0065e6cafc80b #18274\n\nCloses #22534", "completion": "GHA/linux: replace raw C option with `CMAKE_BUILD_TYPE=Debug` in tsan job"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso drop `!DEBUGBUILD` from job names, it's redundant now.\n\nFollow-up to 5050196dcc74b8369bcfad35d3b0926d0ff96180 #22513\n\nCloses #22535", "completion": "appveyor: sync Debug options in two jobs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUpdate the FFC parameter validation to explicitly reject DSA configurations\nwhere the N parameter is greater than 512. Previously, the logic accepted any\nN >= 256 if L >= 3072. This change enforces the maximum supported limit for N\nand raises an error to prevent the use of invalid or unsupported parameter\ncombinations.\n\nThis is needed because generate_q_fips186_4() allocates a `md` buffer that is\nat most `EVP_MAX_MD_SIZE` long (64 bytes). If N is greater than 512 then the\nqsize parameter passed in input to generate_q_fips186_4() will be greater\nthan 64 causing internal operations on the buffer to overflow.\n\nThis was found by Red Hat with AISLE, but deemed not a security issue\nbecause there is no reasonable way to cause an attacket to set the qbits\nvalues directly, if this ever happen it is just misuse of an API by an\napplication.\n\nSigned-off-by: Simo Sorce \n\nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Tue Aug 18 12:41:55 2026\n(Merged from https://github.com/openssl/openssl/pull/32271)\n\n(cherry picked from commit 1bf213943b0f422ced4b0c2db51f626f488f89c7)", "completion": "Reject DSA parameters where N exceeds 512"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUpdate the FFC parameter validation to explicitly reject DSA configurations\nwhere the N parameter is greater than 512. Previously, the logic accepted any\nN >= 256 if L >= 3072. This change enforces the maximum supported limit for N\nand raises an error to prevent the use of invalid or unsupported parameter\ncombinations.\n\nThis is needed because generate_q_fips186_4() allocates a `md` buffer that is\nat most `EVP_MAX_MD_SIZE` long (64 bytes). If N is greater than 512 then the\nqsize parameter passed in input to generate_q_fips186_4() will be greater\nthan 64 causing internal operations on the buffer to overflow.\n\nThis was found by Red Hat with AISLE, but deemed not a security issue\nbecause there is no reasonable way to cause an attacket to set the qbits\nvalues directly, if this ever happen it is just misuse of an API by an\napplication.\n\nSigned-off-by: Simo Sorce \n\nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMergeDate: Tue Aug 18 12:41:55 2026\n(Merged from https://github.com/openssl/openssl/pull/32271)", "completion": "Reject DSA parameters where N exceeds 512"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe test added to catch invalid input will fail on older providers\nthat will ignore the \"1x\" in the test and treat it as \"1\".\n\nGate this test on 4.1.0\n\nReviewed-by: Neil Horman \nReviewed-by: Milan Broz \nMergeDate: Tue Aug 11 05:03:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32272)", "completion": "Fix provider compat test."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 3f1c033afe008123680306663cc01279e831ac2d #22519", "completion": "libcurl.pc: Add Copyright tag to the pkgconf file"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFixing:\n```\n$ pccritic libcurl.pc\n[...]\n [info ] file has trailing whitespace on one or more lines (style/PC062)\n```\n\nCloses #22536", "completion": "build: strip trailing spaces from `libcurl.pc`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nHTTP Negotiate can create and send a Kerberos token before receiving a\nserver challenge. The SSPI backend only supplied Schannel endpoint\nbindings when a challenge token was present, causing IIS with EPA\nenabled to reject preemptive Kerberos authentication with\nSTATUS_BAD_BINDINGS.\n\nBuild the SSPI input descriptor independently of the challenge token so\nSchannel endpoint bindings are included on both initial and subsequent\nInitializeSecurityContext calls.\n\nAssisted-by: martin-fzi@users.noreply.github.com\n\nFixes https://github.com/curl/curl/issues/22466\nCloses https://github.com/curl/curl/pull/22537", "completion": "spnego_sspi: pass channel bindings on initial context"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nScrolling to the top or bottom of a dropdown let the scroll event chain into\nthe page behind it, causing the whole app to scroll. #70137 fixed this for the\nversion picker, but the same containment was missing on every other menu.\n\nThe API reference filter, the tutorial step list and the update guide's version\ndropdowns already had a scroll container, so they only needed\noverscroll-behavior.\n\nThe social and theme mini-menus had neither a height cap nor overflow, so\noverscroll-behavior alone would have been inert on them. They now share the\nversion picker's max-height/overflow-y/overscroll-behavior, hoisted onto\n.adev-mini-menu, which also keeps their items reachable when the viewport is\ntoo short to fit the whole menu.\n\n(cherry picked from commit dd2971382887feaf123204dc484d76f920bf0a0b)", "completion": "fix(docs-infra): contain scroll within adev dropdown menus"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nScrolling to the top or bottom of a dropdown let the scroll event chain into\nthe page behind it, causing the whole app to scroll. #70137 fixed this for the\nversion picker, but the same containment was missing on every other menu.\n\nThe API reference filter, the tutorial step list and the update guide's version\ndropdowns already had a scroll container, so they only needed\noverscroll-behavior.\n\nThe social and theme mini-menus had neither a height cap nor overflow, so\noverscroll-behavior alone would have been inert on them. They now share the\nversion picker's max-height/overflow-y/overscroll-behavior, hoisted onto\n.adev-mini-menu, which also keeps their items reachable when the viewport is\ntoo short to fit the whole menu.", "completion": "fix(docs-infra): contain scroll within adev dropdown menus"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is a partial backport of patch\n60c15b2aff (\"Remove support for SSLv3\") to fix CI run.\n\nReviewed-by: Neil Horman \nReviewed-by: Nikola Pajkovsky \nMergeDate: Tue Aug 11 05:21:41 2026\n(Merged from https://github.com/openssl/openssl/pull/32278)", "completion": "ci: remove enable-ssl3 from prov-compat-label tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ninstall_dev, install_modules and install_runtime each reach the build\nthrough a recursive make of their own, and the sets they build overlap:\napps/libapps.a is one of the libraries and is also needed to link the\ninstallable programs. Under \"make -j\" the three run concurrently, so the\narchive gets built twice at the same time and one job removes it while\nthe other is indexing it, failing the install with a ranlib error.\n\nBuild the installable software in a single make before the install\ntargets run, so they find everything current.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:02:57 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Build the software once before installing it"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22538", "completion": "tests: verify AWS SigV4 redirect auth scope"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npod2man is a perl program that compiles Pod::Man before it reads a\nsingle pod, and there are over nine hundred pages, so formatting the\nmanual spent most of its effort compiling the same module again and\nagain -- 24 seconds of user time and 6 of system time to produce\nabout two and a half seconds of formatting.\n\nFormat the manual in one invocation that loads the module once and\ndivides the pages between a few forked workers. No target depends on\nan individual page, since the install recipes take them as arguments,\nso a stamp is enough to order the work. The per-page rules stay,\ncalling the same script with a single pod, so one page can still be\nbuilt by name, and that path is quicker than pod2man was too.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:10 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Stop reloading Pod::Man for every manual page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nPod::Html is compiled before the first pod is read, so converting the\nmanual to HTML started nine hundred perl processes to do about a\nsecond of work.\n\nConvert the whole set in one invocation that loads the module once and\ndivides the pages between a few forked workers. Nothing depends on an\nindividual page, since the install recipe takes them as arguments, so\na stamp is enough to order the work, and the per-page rules stay for\nbuilding one page by name. The single page option the VMS and Windows\nbuild files use is unchanged, and both paths convert through the same\ncode.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:11 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Stop reloading Pod::Html for every manual page"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15228\n\nVapor component props can retain lazy subscriptions to live parent sources. When the same parent value controls a v-if branch and is passed as a prop, a cached component can observe a transient value before the branch is deactivated. This can run render effects and flush: 'sync' watchers with invalid props, unlike VDOM where a cached vnode retains its last patched inputs.\n\nCommit dynamic raw prop sources through an effect owned by the KeepAlive branch scope. Cached components read the committed shallow values instead of subscribing directly to the parent sources. When the branch is removed, its scope is paused before queued commit jobs run, so the cached component continues to observe its last committed props. Activation resumes the scope and synchronizes the latest values.\n\nKeep component scopes and their local effects active, preserve raw source ordering and key spelling, reconcile dynamic key additions and removals, and skip the commit bridge for v-once components that already snapshot their raw props.\n\nApply the same commit boundary to dynamic slot descriptors so cached components using useSlots() retain their last committed slot table while deactivated. Static slot entries and slot function closure semantics remain unchanged.", "completion": "fix(runtime-vapor): isolate cached component props and dynamic slots"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15253", "completion": "fix(compiler-vapor): wrap custom directive value in parens"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15257", "completion": "fix(compiler-vapor): keep the space after a quoted attribute value"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15254", "completion": "fix(runtime-vapor): preserve vdom props normalization in interop"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* demo(FloatButton): demo update\n\n* demo(FloatButton): demo update\n\n---------", "completion": "demo(FloatButton): demo update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGenerated files were left writable, so a hand edit looked like it had\nworked and was silently lost at the next build. Only the pods and the\ngenerated scripts were protected, by a chmod either side of the\nrecipe, which cost a shell and two processes for each file.\n\nRoute the generators that write to standard output through a helper\nthat collects the output, sets the mode and renames the result into\nplace. Renaming needs no permission on the file it replaces, so there\nis no unlocking step, and a generator that fails part way now leaves\nthe previous file rather than a truncated one with a fresh timestamp\nthat make would believe.\n\nThe perlasm modules name their own output rather than writing to\nstandard output, so they are unchanged and their output stays\nwritable.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:03:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32243", "completion": "Make most generated files read-only, and write them atomically"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIncremental Sort's costs heavily depend on the estimated number of input\ngroups with equal presorted key values. Overestimations can cause the\nplanner to choose Incremental Sort over Sort when Sort would have\nbeen a better choice.\n\nHere, we add the planner's estimate to EXPLAIN to allow easier\nunderstanding of why Incremental Sort has been chosen.\n\nAuthor: Ilia Evdokimov \nReviewed-by: Enrique Sánchez \nReviewed-by: David Rowley \nReviewed-by: solai v \nDiscussion: https://postgr.es/m/10682fef-3748-43f5-a932-7adcdd9bd2b8%40tantorlabs.com", "completion": "Show estimated number of groups for Incremental Sort in EXPLAIN"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* refactor(BorderBeam): optimize border style handling\n\n* update\n\n* update\n\n* update\n\n* update\n\n* update FAQ\n\n* update FAQ\n\n* update snap\n\n* update\n\n* add test case\n\n* update test case\n\n---------", "completion": "refactor(BorderBeam): optimize border style handling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15234", "completion": "fix(runtime-vapor): align app unmount lifecycle with vdom"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* feat: add checkConditionalExpressions to `no-unmodified-loop-condition`\n\n* apply suggestions", "completion": "feat: add checkConditionalExpressions to `no-unmodified-loop-condition`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- Reuse a buffer for schannel_send instead of allocating and freeing a\n buffer for every send.\n\nCloses https://github.com/curl/curl/pull/22540", "completion": "schannel: reuse the send buffer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* fix: Prevent no-var autofix when var is shadowed by catch parameter\n\nA `var` declaration may reuse the name of a simple catch clause parameter,\nbut the equivalent `let` declaration may not. Directly inside the catch\nblock, `let` is a syntax error. In a nested block, `let` is valid but\nassigns a separate binding and leaves the catch parameter untouched.\n\nThe catch parameter and the `var` are distinct variables in distinct\nscopes, so neither has more than one definition and `isRedeclared` does\nnot detect the conflict.\n\nFixes #21194\n\n* fix: Simplify catch parameter check with getVariableByName\n\nResolve the declared name from the scope of the declaration instead of\nwalking the scope chain looking for a catch scope. A simple catch parameter\nis the only binding a `var` is allowed to shadow, so a name that does not\nresolve to the variable being declared is shadowed by one.", "completion": "fix: Prevent no-var autofix when var is shadowed by catch parameter"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nVerified by test 2119\n\nCloses #22541", "completion": "content_encoding: exact-match the identity transfer-coding token"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15264", "completion": "fix(compiler-vapor): preserve modifiers on merged event handlers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis simplifies error message printing a bit.\n\nAuthor: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org", "completion": "Use frontend logging API in fe_utils/string_utils.c"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThese functions would sometimes overwrite the string argument they are\npassed, namely via mbvalidate(), which removes invalid UTF-8\ncharacters (or potentially analogously in other encodings, but that is\nnot implemented). However, many callers are not expecting that. In\nmany callers, the input value comes directly from libpq structures,\nsuch as from PQgetvalue() or PQsslAttribute(). The latter actually\nhas a const char * return type, and that was cast away. But even the\nformer is not expecting its return value to be modified.\n\nFix that by making these arguments const. Internally, we add a\nseparate function that does only the checking part of mbvalidate().\nOnly if the validation returns a negative result, we make a copy and\nrun mbvalidate() on the copy. printTableAddCell() already had\ninternal infrastructure for keeping track of what values needed to be\nfreed. We add the same for printTableAddHeader().\n\nIn passing, also simplify the code a bit. There were essentially\nduplicate mechanisms for keeping track of the most recently added\ncell (fields .cell and .cellsadded). Make that consistent by using an\ninteger counter for everything. That makes the code arguably easier\nto read than with the \"current pointer\" approaches.\n\nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org", "completion": "Make printTableAddCell/printTableAddHeader string argument const"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis simplifies error message printing a bit. Also adjust the error\nmessages a bit for style, while we're here.\n\nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org", "completion": "Use frontend logging API in fe_utils/print.c"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis already works even without those conditionals, since _() expands\nto a no-op if NLS is disabled.\n\nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org", "completion": "Remove useless ENABLE_NLS conditionals"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe const qualifiers removed here did not qualify what is being\npointed to, which is the normal use in function prototypes. Instead,\nthey qualify the variable itself, so that it cannot be changed inside\nthe function. That is itself not wrong, but it's not a normal style,\nand it seems distracting here.\n\nReviewed-by: Chao Li \nDiscussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org", "completion": "Remove useless/confusing const qualifiers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nUse explicit fragment role flags and separate the internal bridge interfaces\nwithout changing the unified interop plugin.", "completion": "refactor(runtime-vapor): formalize fragment and interop boundaries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`1-` does nothing from a directory buffer, because we are already in the\nbuffer-local CWD. It's also unintuitive that this mapping behaves\ndifferently based on the resolved CWD.\n\nSolution:\nHave `1-` open the global CWD.", "completion": "refactor(defaults): edit global cwd on \"1-\" #41254"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n`pccritic` is available on the latest macOS runner revision (not every\njob runs get it yet), Cygwin, MSYS2/mingw-w64 (one job, others will\nfollow on the next msys2/setup-msys2 Action bump). It will be\nautomatically used on BSDs, once they start offering it. Missing from\nLinux jobs.\n\nAlso:\n- GHA/windows: convert `libcurl.pc` to Unix newlines to bump score\n 96 to 100 in mingw-w64 jobs.\n CMake-specific fix pending in: #22556\n- GHA: verify with minimum `pccritic` score 94 to 100 (depending on CI\n job).\n- build: fill `Maintainer:` `libcurl.pc` property when run curl CI.\n\nIssues remaining:\n\nmacOS:\n```\n[info ] Cflags adds an include path already on the default search path (pkgconf strips it): -I/usr/local/include (cflags/PC031)\n[info ] Libs adds a library path already on the default search path (pkgconf strips it): -L/usr/local/lib (libs/PC040)\n[minor ] Libs.private contains an unexpected flag: /Applications/Xcode_26.6.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX26.5.sdk/System/Library/Frameworks/GSS.framework (libs/PC041)\n```\n\nWindows:\n```\n[minor ] file uses CRLF line endings (style/PC061)\n```\n\nRef: #22556\nFollow-up to b9254da6175360102176303ecf9dbb5519b0ffcf #22548\nFollow-up to 852f5d34da772de65d057897278aa1e75dd060d1 #22553\nFollow-up to 4d9ba9fef48e43903815e0c0e96f917eaf9f185c #22545\nFollow-up to 6c7993d4d9f8722a869207f86a31f20fa9e8780d #22536\nFollow-up to 3f1c033afe008123680306663cc01279e831ac2d #22519\n\nCloses #22543", "completion": "CI: dump `libcurl.pc` (and `curl-config`) to log, verify `.pc` with `pccritic` tool"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIn addition report the maximum of the sampple RSS values. Increase the\nsampling frequency for accuracy.\n\nCloses #22542", "completion": "scorecard: report 'rss-max'"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso to improve `pccritic` score.\n\nIdea-by: Dan Fandrich\n\nFollow-up to 3f1c033afe008123680306663cc01279e831ac2d #22519\nCherry-picked from #22543\n\nCloses #22545", "completion": "libcurl.pc: add `License` tag"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen `LIBCURL_PC_LDFLAGS_PRIVATE` is empty and `LIBCURL_PC_LIBS_PRIVATE`\nis not.\n\nTo keep it tidy.\n\nCloses #22544", "completion": "build: strip duplicate spaces after `Libs.private:` in `libcurl.pc`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nBump `@rc-component/tree` to `~1.5.0` and `@rc-component/tree-select` to\n`~1.17.0` to pick up react-component/tree#1066, which adds a\n`treenode-unselectable` class when a non-checkable Tree node has\n`selectable={false}`.\n\nIn non-checkable mode such a node can neither be selected nor checked, so\nalign its visual with `disabled` (disabled text color + not-allowed cursor,\nno hover highlight). Checkable mode keeps the existing behavior — a\n`selectable={false}` node stays checkable and no longer shows the\ndisabled look.", "completion": "feat(Tree): align `selectable={false}` with disabled style in non-checkable mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCall tls_construct_client_key_exchange() directly for each key exchange\nthe dispatcher can select, priming the connection with the state the\nreal state machine would have set up: a minimal session, the negotiated\ncipher and the server key material. The kRSA test decrypts the emitted\npremaster secret and checks it against the saved one, kECDHE/kDHE check\nthe encoded public key and the derived secret, and kPSK checks the\nemitted identity plus the PSK stashed for the secret derivation. Add\ndeterministic tests for the error branches: a missing server\ncertificate or ephemeral key, the PSK callback failures, a WPACKET\noverflow and a cipher matching no key exchange. Out-of-memory branches\nare exercised with the mfail tests.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Mon Sep 7 13:26:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32299", "completion": "statem: test tls_construct_client_key_exchange"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe Perl 5.10 makefile can run multiple configpm recipes concurrently\nduring a parallel build. They update Config.pm and Config_heavy.pl in\nplace, so one process may read a partially written Config.pm and fail.\n\nBuild this old Perl release serially. Other workflow builds continue\nto use all available CPUs.\n\nReviewed-by: Richard Levitte \nReviewed-by: Eugene Syromiatnikov \nMergeDate: Thu Aug 13 11:37:13 2026\n(Merged from https://github.com/openssl/openssl/pull/32302)", "completion": "ci: fix race condition in parallel Perl 5.10 build"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe test_rsasve_degenerate_ciphertext calls EVP_PKEY_get_size and uses\nthat returned value as an array index (offset by -1), but fails to check\nif the returned size is greater than zero (which can be returned in an\nerror case), leading to an array index underflow.\n\nEnsure that the returned value is greater than zero\n\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1699973\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Paul Dale \nMergeDate: Thu Aug 13 11:54:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32309)\n\n(cherry picked from commit 05103ee62c17dfe7de61af2ec91130527643678a)", "completion": "Test EVP_PKEY_get_size for zero return"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe test_rsasve_degenerate_ciphertext calls EVP_PKEY_get_size and uses\nthat returned value as an array index (offset by -1), but fails to check\nif the returned size is greater than zero (which can be returned in an\nerror case), leading to an array index underflow.\n\nEnsure that the returned value is greater than zero\n\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1699973\n\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Paul Dale \nMergeDate: Thu Aug 13 11:54:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32309)", "completion": "Test EVP_PKEY_get_size for zero return"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_clear_free() with the original allocation length on the\nKARI, KEKRI, and PWRI failure paths. This is defense-in-depth\nhardening at the CMS/provider boundary.\n\nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 14 06:38:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32303\n(cherry picked from commit 57b84ed1cf9b6c6fe8230be85869351ce2e8e839)", "completion": "cms: clear temporary key buffers on failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_clear_free() with the original allocation length on the\nKARI, KEKRI, and PWRI failure paths. This is defense-in-depth\nhardening at the CMS/provider boundary.\n\nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 14 06:38:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32303\n(cherry picked from commit de80bb12501c32bd92cfd02b56da778925da992c)", "completion": "cms: clear temporary key buffers on failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_clear_free() with the original allocation length on the\nKARI, KEKRI, and PWRI failure paths. This is defense-in-depth\nhardening at the CMS/provider boundary.\n\nReviewed-by: Tomas Mraz \nReviewed-by: Dmitry Belyavskiy \nMerge-date: Fri Aug 14 06:38:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32303", "completion": "cms: clear temporary key buffers on failure"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStateValue and AnimationTransitionNamespace.trigger detect the {value,\nparams} object form of a trigger binding by calling hasOwnProperty on the\nbound value. When that value is an object from untrusted data (for example\na parsed JSON payload) carrying an own hasOwnProperty key, the shadowed\nproperty is called as a method and throws, breaking the animation flush.\nUse Object.hasOwn for the check so a shadowing key no longer matters.\n\n(cherry picked from commit c73a001fbf766b350fab4e64244cfaee23fdc8bc)", "completion": "fix(animations): detect object trigger values with Object.hasOwn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStateValue and AnimationTransitionNamespace.trigger detect the {value,\nparams} object form of a trigger binding by calling hasOwnProperty on the\nbound value. When that value is an object from untrusted data (for example\na parsed JSON payload) carrying an own hasOwnProperty key, the shadowed\nproperty is called as a method and throws, breaking the animation flush.\nUse Object.hasOwn for the check so a shadowing key no longer matters.", "completion": "fix(animations): detect object trigger values with Object.hasOwn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ndtlsv1listentest uses DTLSv1_listen(), a DTLS 1.2-only API that crashes\nwhen DTLS 1.2 is disabled. Guard the test in build.info under\n!$disabled{dtls1_2} and add a matching recipe skip so the test is neither\ncompiled nor run when DTLS 1.2 is unavailable.\n\nThe dtls_ccs_reorder test file is specific to DTLS 1.0/1.2 CCS reordering,\nwhich does not apply to DTLS 1.3. The recipe only skipped when all DTLS was\ndisabled, so when both DTLS 1.0 and 1.2 were disabled while DTLS 1.3\nremained, the test still ran. Add a recipe skip for when both DTLS 1.0 and\nDTLS 1.2 are disabled, matching the build.info condition.\n\nssl_ctx_test had two test table entries that set DTLS1_2_VERSION as a max\nprotocol version and expected success. When DTLS 1.2 is disabled that\nversion is not valid for any protocol, so SSL_CTX_set_max_proto_version()\nreturns 0. Guard both entries with #ifndef OPENSSL_NO_DTLS1_2.\n\ndtlstest contained a dead #ifdef OPENSSL_NO_DTLS1_2 block inside\ntest_listen(), which is itself wrapped in #ifndef OPENSSL_NO_DTLS1_2.\nThe inner ifdef could never be true; remove it.\n\nAssisted-by: Claude:claude-sonnet-4-6\nReviewed-by: Tomas Mraz \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:55:38 2026\nMerged-from: https://github.com/openssl/openssl/pull/32340", "completion": "DTLS 1.3 CI nightly NO DTLS 1.2 Failures Fix"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nBefore this patch static-only libcurl builds stored the list of module\ndependencies in both `Require` and `Require.private`. The new `pccritic`\ntool flagged this as an issue. Having (or not) a duplicate in\n`Require.private` does not change the output created by `pkgconf` and\n`pkg-config`, as tested with both with and without `--static` option.\nThus, fix by deleting the private copy.\n\nFixing:\n```\n$ pccritic libcurl.pc\nbld/libcurl.pc\n score: 63/100 grade: D (0 critical, 0 major, 9 minor, 1 info)\n [minor ] 'libssh2' appears in both Requires and Requires.private (requires/PC051)\n [minor ] 'libidn2' appears in both Requires and Requires.private (requires/PC051)\n [minor ] 'openssl' appears in both Requires and Requires.private (requires/PC051)\n[...]\n```\nRef: https://github.com/curl/curl/actions/runs/31495008715/job/93790403026#step:10:210 (macOS, CM clang OpenSSL torture)\nRef: https://github.com/curl/curl/actions/runs/31495008825/job/93790433646#step:9:216 (mingw, AM ucrt-x86_64 wolfssl c-ares U)\n\nFollow-up to f057de5a1a950a90d1920021db152a4b695f1a8a #13911\nFollow-up to 98e5904165859679cd78825bcccb52306ee3bb66 #5373\nCherry-picked from #22543\n\nCloses #22548", "completion": "build: clear `Require.private` for static-only builds in `libcurl.pc`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA DTLS listener cannot take its blocking behaviour from its network BIO\nthe way an ordinary DTLS object does. It demultiplexes one socket to\nmany connections, so a read for one of them must not be allowed to\nblock and stall the others, and the connections it hands out have no BIO\nof their own to configure - they read from a queue the listener fills.\nBlocking was therefore unavailable to them, SSL_set_blocking_mode()\nbeing QUIC only.\n\nExtend it to a DTLS listener and to the connections created from one,\nwith the same semantics QUIC has. Blocking is the default, a connection\nfollows its listener unless given a setting of its own, and asking for\nblocking fails where it cannot be delivered, which for a listener means\na network BIO with no poll descriptor to wait on.\nSSL_accept_connection() waits only where the caller did not pass\nSSL_ACCEPT_CONNECTION_NO_BLOCK and the listener is in blocking mode,\nmatching what QUIC does with the same flag.\n\nOnly the accept path acts on the mode so far; reads and writes follow.\n\nNote that this does not extend to a DTLS object which did not come from\na listener. Such an object has its own BIO and already offers both modes\nthrough it, so unlike QUIC - where the socket is always nonblocking and\nnothing works without emulation - there is nothing missing to provide.\n\nWhile documenting the above, correct the existing description of which\nQUIC objects these functions apply to. It said connection objects only,\nbut they have always been accepted for QUIC stream and listener objects\ntoo.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug 17 08:29:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32324", "completion": "DTLS 1.3 Support SSL_set_blocking_mode() on a DTLS listener"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nKeep only a single `start` time and calculate the rest in delta\nmicroseconds since then. Separate timestamps and durations into separate\nsub-structures for clarity.\n\nremove progress.t_acceptdata\nIt was recorded in FTP accept but never used anywhere.\n\nCloses #22547", "completion": "progress: cleanup, less memory"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTrigger routed viewport hydration so its cached observer is removed before later randomized specs run.\n\n(cherry picked from commit 870a525bd3c9eaf98d79e426d8ddf2625afe474d)", "completion": "test(platform-server): clean up viewport hydration observer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTrigger routed viewport hydration so its cached observer is removed before later randomized specs run.", "completion": "test(platform-server): clean up viewport hydration observer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency node to v24"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nanimate.leave waits for the longest-running animation before removing an element. When multiple animations use the same keyframe name, their animationend events have the same animationName, so a shorter animation can be mistaken for the longest one and remove the element too early.\n\nTrack the longest animation duration returned by getAnimations() and compare it with the duration from event.animation when available. Keep the existing name/property checks as a fallback for older browsers and computed-style detection.\n\nAllow a 1ms tolerance for rounding differences between CSSOM and Web Animations and add a regression test using values equivalent to fractional calc() durations.\n\n(cherry picked from commit a26fbfa641b965ad581a3919c06d2c51d8b16125)", "completion": "refactor(core): distinguish animations that share a name"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nanimate.leave waits for the longest-running animation before removing an element. When multiple animations use the same keyframe name, their animationend events have the same animationName, so a shorter animation can be mistaken for the longest one and remove the element too early.\n\nTrack the longest animation duration returned by getAnimations() and compare it with the duration from event.animation when available. Keep the existing name/property checks as a fallback for older browsers and computed-style detection.\n\nAllow a 1ms tolerance for rounding differences between CSSOM and Web Animations and add a regression test using values equivalent to fractional calc() durations.", "completion": "refactor(core): distinguish animations that share a name"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n- Add info tooltips that describe the visualizations and other\nparts of the UI\n- Improve the frame selector by adding axes labels and a\nhorizontal line for frames exceeding 60 fps\n- Use a precise frame rate calculations instead of approximations\n- Introduce improvements to the details panel\n- Improve the bar chart visualization\n- And more", "completion": "refactor(devtools): improve profiler ux"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't do pointer arithmetic on a NULL pointer in OPENSSL_uni2asc"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:50 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Don't hit the legacy strlen case in ASN1_PRINTABLE_type"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDTLS_get_data_mtu() included the explicit IV overhead from\nssl_cipher_get_overhead() for AES-GCM and CCM ciphers, but DTLS 1.3 uses\nimplicit IVs so no IV bytes appear on the wire. Fix by subtracting\nEVP_GCM_TLS_EXPLICIT_IV_LEN or EVP_CCM_TLS_EXPLICIT_IV_LEN.\n\nRestructure the MTU test to pin DTLS 1.2 in the PSK cipher loop (previously\nDTLS 1.3 was silently negotiated instead) and add a DTLS 1.3 loop using\ncertificate-based auth. Guard TLS_CHACHA20_POLY1305_SHA256 with both\nOPENSSL_NO_CHACHA and OPENSSL_NO_POLY1305.\n\nAssisted-by: Claude:claude-sonnet-4-6\nReviewed-by: Tomas Mraz \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:55:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/32340", "completion": "DTLS 1.3 Fix DTLS_get_data_mtu() and extend MTU test to cover DTLS 1.3"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nStarting with commit 011384ba45, calling to_date() or to_timestamp()\nwith \"TMMonth\" or other TM-prefixed format keyword, with the C locale,\nwould crash.\n\nIn REL_19_STABLE and above, pg_strupper(), pg_strlower(),\npg_strtitle(), and pg_strfold() functions have a special case for the\nC locale, but that was missing in REL_18_STABLE. On REL_18_STABLE,\nthe functions call the libc function even in C locale, even though the\nnative locale object is NULL. On Linux, the underlying libc functions\nwill crash when called with NULL locale. (On macOS, they reportedly\ndo not, but even then it's not clear if they will do what you'd\nexpect.)\n\nThis went unnoticed because until commit 011384ba45, we never called\nthese functions in C locale, all the callers had a special codepath\nfor C locale. We could add a special path in the new callers too, but\nit's an accident waiting to happen, so let's backport the C\nlocale-specific handling from REL_19_STABLE to REL_18_STABLE. Older\nversions did not have these functions at all, hence no problem.\n\nThis applies to REL_18_STABLE only.\n\nReported-by: Masashi Kamura \nReviewed-by: Álvaro Herrera \nDiscussion: https://www.postgresql.org/message-id/OS9PR01MB1317436E07D06281AD1A0452F94DD2%40OS9PR01MB13174.jpnprd01.prod.outlook.com", "completion": "Fix pg_strupper/lower/title/fold() functions to work with C locale"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAnd as a result in this loop. I changed this to a size_t\nwhich was needed where the variable was used later on and\nmissed this case at the start.\n\nWhile harmless, coverity notices. so let's do it right\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nMerge-date: Fri Aug 14 06:29:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32310", "completion": "Use an int for the return value of i2a_ASN1_OBJECT"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nFarewell, 18.5; we hardly knew ye.", "completion": "Release notes for 18.6."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe ssl_handshake_started field was added by d39a49c1e45 to allow\nconnection_failed() skip retrying with a different SSL negotiation\nmethod, once the server had reported an error after the TLS handshake\nhad already started. That logic was dropped by fb5718f35ff, which\nremoved the ability to fall back from direct to negotiated SSL, and\nwith it the only consumer of the data in this field. Fix by removing\nthe field.\n\nAuthor: Aleksander Alekseev \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAJ7c6TPkHjVFERp1Fd-idMe=iRJnDX2Nzy_ZOkV=y4OLLgf89Q@mail.gmail.com", "completion": "libpq: remove unused field ssl_handshake_started from PGconn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen resolving template symbols for SafePropertyRead in TCBs emitted with optional chaining (strictSafeNavigationTypes: true), SymbolBuilder falls back to finding a TS node matching the AST expression's nameSpan. It then traverses up through parent nodes to find the enclosing expression.\n\nPreviously, the traversal loop checked isAccessExpression(node.parent) without verifying whether node was the accessed member name or the expression receiver. When multiple optional navigation expressions are chained (e.g. route?.data?.['icon']), the parent of ((route)?.data) is an access expression where ((route)?.data) is the receiver. Because isAccessExpression was true, the loop continued ascending into the outer access expression, causing symbol resolution for data to erroneously return the symbol and TCB location of icon.\n\nThis commit refines the parent traversal condition so that it only climbs into a parent PropertyAccessExpression if node is the accessed name (node.parent.name === node), preventing escape into outer receiver expressions.\n\n(cherry picked from commit e8aa222e7d98d2e54c5604107a929a11cb1ef62d)", "completion": "fix(compiler-cli): correctly resolve symbol for SafePropertyRead in chained optional navigation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWhen resolving template symbols for SafePropertyRead in TCBs emitted with optional chaining (strictSafeNavigationTypes: true), SymbolBuilder falls back to finding a TS node matching the AST expression's nameSpan. It then traverses up through parent nodes to find the enclosing expression.\n\nPreviously, the traversal loop checked isAccessExpression(node.parent) without verifying whether node was the accessed member name or the expression receiver. When multiple optional navigation expressions are chained (e.g. route?.data?.['icon']), the parent of ((route)?.data) is an access expression where ((route)?.data) is the receiver. Because isAccessExpression was true, the loop continued ascending into the outer access expression, causing symbol resolution for data to erroneously return the symbol and TCB location of icon.\n\nThis commit refines the parent traversal condition so that it only climbs into a parent PropertyAccessExpression if node is the accessed name (node.parent.name === node), preventing escape into outer receiver expressions.", "completion": "fix(compiler-cli): correctly resolve symbol for SafePropertyRead in chained optional navigation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGuard the DTLS1_3_VERSION entry in dtls_version_table with\nOPENSSL_NO_DTLS1_3 (NULL fallback), matching the pattern used by\ntls_version_table for TLS1_3. Add a min_version clamp for DTLS1_3 in\nssl_check_allowed_versions() to fix SSL_CTX_set_min_proto_version()\nincorrectly returning failure under no-dtls1_3, caused by DTLS inverted\nwire-number ordering making the range check fire after max was clamped to\nDTLS1_2. Guard _dtls13 test functions and their ADD_TEST calls in\ndtlstest.c. Guard DTLS 1.3-only helpers and tests in\ndtlsssllistenertest.c, and move SSL_poll tests outside the DTLS 1.3\nguard so they run for any DTLS version. Add no-dtls1_3 to the daily CI\nchecker matrix.\n\nAssisted-by: Claude:claude-sonnet-4-6\nReviewed-by: Tomas Mraz \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:55:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32340", "completion": "DTLS 1.3 Fix no-dtls1_3 build configuration CI failures"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFor DTLS, TLSProxy picked a random port for s_client to -bind to,\nprobing it for availability first. This was racy in two ways: the\nprobe socket was TCP while s_client binds UDP (the two port spaces\nare independent, so a UDP socket held by a parallel test job was\ninvisible to the probe), and even a UDP probe would leave a window\nbetween closing the probe socket and s_client binding the port.\nWith many tests now running under the DTLS proxy in parallel CI\njobs this caused intermittent BIO_bind EADDRINUSE failures.\n\nInstead, drop -bind and the port probing entirely. The kernel\nassigns s_client's source port atomically on first send, and the\nproxy, whose UDP socket is now left unconnected, learns the\nclient's address from the datagrams it receives, in the same way\nany regular UDP server does.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Tomas Mraz \nReviewed-by: Frederik Wedel-Heinen \nMerge-date: Thu Aug 13 13:42:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/32312", "completion": "test: let the kernel pick the DTLS client port in TLSProxy"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBy default, allocate this via malloc, as we've been doing since commit\n62c8421e8. Commit aeb07c55f adopted upstream tzdb's default of\nallocating it on the stack, but that still doesn't seem like a good\nidea for the reasons given in 62c8421e8 (and now memorialized in a\ncomment, in hopes that we don't make the same mistake again).\n\nHowever, under USE_VALGRIND, put it on the stack as upstream does.\nThis accidentally prevents a crash when Python 3.14 is used under\nValgrind. The reasons for that are obscure, and it's most likely\nnot our bug, and even if we figured it out it'd be nice to have a fix\nfor buildfarm member skink now rather than after persuading the guilty\nparty to fix it.\n\nIn the normal non-USE_VALGRIND case, this has no effect on the logic\nin released branches, and it reverts master to match them.\n\nReported-by: Alexander Lakhin \nAuthor: Tom Lane \nDiscussion: https://postgr.es/m/f071e691-5930-4738-9dbd-43ed2da367fe@gmail.com\nBackpatch-through: 14", "completion": "Tweak allocation rule for tzload()'s \"union local_storage\" variable."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFuzz CMS_verify() with CMS_NO_SIGNER_CERT_VERIFY\nto exercise signature verification without requiring\ntrusted certificate store.\n\nMotivated by : CVE-2026-45447 which affects PKCS7_verify(),\nand add coverage for similar CMS_verify().\n\nAssisted-by: ChatGPT:gpt-5.6\nReviewed-by: Jakub Zelenka \nReviewed-by: Milan Broz \nMerge-date: Tue Sep 15 15:00:01 2026\nMerged-from: https://github.com/openssl/openssl/pull/32342", "completion": "Add cms_verify fuzzer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis updates the docs to be explicit about `animate.leave` and nested element removal order. It clearly specifies that `animate.leave` will only fire nested animations within the same component template.\n\ncloses: #70131\n(cherry picked from commit 3d32db6a493e24c09da9bff6f01c7a73ae804f44)", "completion": "docs: clarify animate.leave child animation behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis updates the docs to be explicit about `animate.leave` and nested element removal order. It clearly specifies that `animate.leave` will only fire nested animations within the same component template.", "completion": "docs: clarify animate.leave child animation behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPreviously, wal_compression=on was an alias for pglz, with the\nassumption that users could make an informed choice to pick a better\noption. But in practice, users rarely got to that second step.\n\nMany users don't want to be choosing algorithms - they just want WAL\ncompression, and expect that to work well. The configuration parameter\nis set by administrators, who do not control the workload, and so are\nnot in a position to evaluate the options anyway. Some users may not\neven realize there are other options, as previously \"on\" was the only\nchoice available.\n\nThis change maps \"on\" to non-pglz options, supported by the build. Both\nlz4 and zstd are faster, with a comparable (or better) compression\nratio. We prefer zstd over lz4 - per our testing the better compression\nratio pays for the lower (de)compression speed.\n\nLike for TOAST compression, the value depends on algorithms supported by\nthe PostgreSQL build, with lz4 and zstd being optional. But most builds\nwill have at least one of these external libraries. If neither zstd or\nlz4 is supported, we fallback to pglz.\n\nThis only affects what \"on\" means. Users can still make the informed\nchoice and explicitly select a compression algorithm if it works better\nfor their system. The default value for \"wal_compression\" remains \"off.\"\n\nInitial proposal and patch by wenhui qiu, reviews and patch adjustments\nby Christoph Berg. A number of other people participated in the\ndiscussion. Benchmarks by me.\n\nBackpatch to 19.\n\nAuthor: wenhui qiu \nReviewed-by: Christoph Berg \nReviewed-by: Michael Paquier \nDiscussion: https://postgr.es/m/CAGjGUAL1b=Mwd1SCvLbo+fivEr9KDpFcu4jmqKCZXwT=6CiiGQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Change wal_compression=on to the first of zstd, lz4, pglz"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAdd an MFAIL regression test for X509V3_EXT_add_nconf().\n\nTargeting bug : (https://github.com/openssl/openssl/pull/32206)\nIn asn1_gen.c asn1_multi() function variable allocated as\nASN1_TYPE *typ = generate_v3() is not freed if\nif (!sk_ASN1_TYPE_push(sk, typ)) branch fails.\n\nThe issue was found by the x509v3 fuzzer MFAIL test.\n\nReviewed-by: Milan Broz \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Sep 7 14:08:11 2026\nMerged-from: https://github.com/openssl/openssl/pull/32330", "completion": "Add test for ASN1_TYPE memory leak in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOn the first LockAcquire for a lock tag, LockAcquireExtended() creates\na LOCALLOCK entry in the hash table LockMethodLocalHash, with lockOwners\nset to NULL. lockOwners is then allocated in TopMemoryContext.\n\nIf the allocation fails, the hash entry would persist with lockOwners\nstill NULL and maxLockOwners already set to 8. A follow-up\nLockAcquire() on the same entry would crash on a NULL pointer\ndereference.\n\nThis commit adds an extra layer of safety for such a case, by\nre-attempting MemoryContextAlloc() if a LOCALLOCK entry exists but its\nlockOwners is still NULL due to a previous in-flight allocation failure.\n\nThis problem is unlikely going to show up in practice, so no backpatch\nis done.\n\nAuthor: Bryan Green \nAuthor: Mark Dilger \nDiscussion: https://postgr.es/m/c9a5eeb1-4d31-46e1-bb9e-33448a23a5d3@gmail.com", "completion": "Improve GrantLockLocal() handling on out-of-memory errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nKeepFileRestoredFromArchive() has been using an incorrect WAL segment\nname in the error report for an unlink() failure.\n\nEven without 1200dfd60c36, this was of consequence only on WIN32, where\nwe would miss to report a segment name suffixed by \".deleted%u\".\n\nOversight in 60df192aea0e, for what looks like a copy-pasto to me.\n\nReported-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwHSbJnUmWCuF-QNUsGYF=iSSuzLRx1z_dLfYFwfbTu4Cw@mail.gmail.com", "completion": "Fix unlink() error report in KeepFileRestoredFromArchive()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe pkcs12 documentation incorrectly says that -passin is used to\nencrypt output private keys. The implementation uses -passin for input\nand -passout for output, with direction-specific roles depending on\n-export.\n\nDescribe both options explicitly and link -passout to the shared\npassphrase-options documentation.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Richard Levitte \nReviewed-by: Jakub Zelenka \nMerge-date: Tue Sep 1 14:10:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32315\n(cherry picked from commit 2c5f67b894e4f0703ab23262800897b81586651a)", "completion": "doc: correct pkcs12 passin and passout descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe pkcs12 documentation incorrectly says that -passin is used to\nencrypt output private keys. The implementation uses -passin for input\nand -passout for output, with direction-specific roles depending on\n-export.\n\nDescribe both options explicitly and link -passout to the shared\npassphrase-options documentation.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Richard Levitte \nReviewed-by: Jakub Zelenka \nMerge-date: Tue Sep 1 14:10:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32315", "completion": "doc: correct pkcs12 passin and passout descriptions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nClose #15274\n\nTreat a root Transition as transparent when determining its single-root\nchild so fallthrough class and style bindings use root merging.", "completion": "fix(compiler-vapor): propagate component root through Transition"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit splits the relation and index stats data, where the index\ndata is now moved to a new kind called PGSTAT_KIND_INDEX. A benefit of\nthis refactoring is a reduction of the shared memory required for each\nindex, the new PgStat_StatIdxEntry including only the fields required\nfor indexes. This leads to less data flushed to disk on shutdown.\nAnother benefit is that the addition of new fields for relation-level\nstats is easier to think about. Note that indexes have no need for most\nof the xact-level fields that relations care about, clarifying the role\nof each counter for each relkind.\n\nSystem views are updated to use the index-level functions. Note this\nsplit means a possible break for tools that had the idea to call the\nSQL functions for relation stats (not documented), as now these would\nreturn 0 when queried for an index. These tools can use the new index\nfunctions to achieve the same result.\n\nAs of this change, the pending statistics are still controlled by\nPgStat_TableStatus for both relation and index kinds. This is left as a\nfollow-up piece, this one being good enough on its own. This commit is\nfocused on the changes required for the SQL interface, shared memory\nmanagement and the on-disk format.\n\nBump catalog version.\nBump PGSTAT_FILE_FORMAT_ID.\n\nAuthor: Bertrand Drouvot \nAuthor: Michael Paquier \nDiscussion: https://postgr.es/m/f572abe7-a1bb-e13b-48c7-2ca150546822@gmail.com", "completion": "Move index statistics into their own stats kind"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe additional ciphertext check is now applied in rsasve_recover() where it\nbelongs, and not in the underlying RSA primitives, where it remains conditional\ndefined(FIPS_MODULE).\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Aug 17 14:02:44 2026\n(Merged from https://github.com/openssl/openssl/pull/32314)", "completion": "Revised RSASVE degenerate ciphertext check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe additional ciphertext check is now applied in rsasve_recover() where it\nbelongs, and not in the underlying RSA primitives, where it remains conditional\ndefined(FIPS_MODULE).\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Aug 17 14:01:18 2026\n(Merged from https://github.com/openssl/openssl/pull/32314)", "completion": "Revised RSASVE degenerate ciphertext check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe additional ciphertext check is now applied in rsasve_recover() where it\nbelongs, and not in the underlying RSA primitives, where it remains conditional\ndefined(FIPS_MODULE).\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Aug 17 14:00:11 2026\n(Merged from https://github.com/openssl/openssl/pull/32314)", "completion": "Revised RSASVE degenerate ciphertext check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe additional ciphertext check is now applied in rsasve_recover() where it\nbelongs, and not in the underlying RSA primitives, where it remains conditional\ndefined(FIPS_MODULE).\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Aug 17 13:58:56 2026\n(Merged from https://github.com/openssl/openssl/pull/32314)", "completion": "Revised RSASVE degenerate ciphertext check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe additional ciphertext check is now applied in rsasve_recover() where it\nbelongs, and not in the underlying RSA primitives, where it remains conditional\ndefined(FIPS_MODULE).\n\nReviewed-by: Milan Broz \nReviewed-by: Nikola Pajkovsky \nMergeDate: Mon Aug 17 13:56:53 2026\n(Merged from https://github.com/openssl/openssl/pull/32314)", "completion": "Revised RSASVE degenerate ciphertext check."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* chore: update ecosystem plugins\n\n* unpin `core-js-compat`\n\n---------", "completion": "chore: update ecosystem plugins"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15277", "completion": "fix(runtime-vapor): respect inheritAttrs ownership for component roots"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nREFRESH MATERIALIZED VIEW currently calls SetMatViewPopulatedState()\neven when the materialized view's relispopulated value already matches\nthe state requested by the command. That performs a catalog update of\npg_class without changing the visible state of the materialized view.\n\nThe extra update creates a dead pg_class tuple and causes the usual\ncatalog-update side effects, including relcache invalidation and WAL,\nfor no semantic benefit. The effect is especially visible for\nREFRESH MATERIALIZED VIEW CONCURRENTLY, where the refresh updates the\nmaterialized view contents with DML and otherwise need not change\npg_class just to keep relispopulated set to true.\n\nCheck the current populated state before calling SetMatViewPopulatedState(),\nand update pg_class only when the value would actually change. This\npreserves the required state transitions for WITH DATA and WITH NO DATA\nwhile avoiding catalog churn for repeated refreshes that leave the\npopulated state unchanged.\n\nAuthor: ChangAo Chen \nReviewed-by: Zizhuan Liu <44973863@qq.com>\nReviewed-by: Adam Brusselback \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/tencent_DF2D8533B5412908326F7806075B7637A108@qq.com", "completion": "Avoid unnecessary matview populated-state updates"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOpenTableList() is invoked at most once per DDL statement, from\nCreatePublication() and AlterPublicationTables(), and everything it\nbuilds (relids, relids_with_rf, and relids_with_collist) is allocated\nin the command's own memory context. That context is reclaimed as\nsoon as the command finishes, so explicitly freeing relids and\nrelids_with_rf here served no purpose.\n\nReported-by: Peter Smith \nSuggested-by: Tom Lane \nAuthor: Peter Smith \nReviewed-by: shveta malik \nReviewed-by: shihao zhong \nReviewed-by: surya poondla \nDiscussion: https://postgr.es/m/CAHut+Pt3bgyt==d6GCj=p9qu4sVSH_KQWLN7cMaH0RdJCO-K_Q@mail.gmail.com", "completion": "Remove unnecessary list_free() calls in OpenTableList()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* demo: add drag-sorting demo\n\n* Refine Listy drag sorting handle UI in demo\n\n---------", "completion": "demo: add drag-sorting demo"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOn timeout, poll_query_until() would fail to print its report when\n\"$query\" was undefined. Instead of the expected report, this prevented\nthe contents of stdout and stderr from being shown.\n\nNote that some of the in-core tests use an undefined query for\nconnection-only polls.\n\nAuthor: Bryan Green \nReviewed-by: Jonathan Gonzalez V. \nDiscussion: https://postgr.es/m/0f515c6d-6032-4c5f-80ac-5c78faae9522@gmail.com\nBackpatch-through: 14", "completion": "Fix poll_query_until() timeout handling with an undefined query in Cluster.pm"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA buildfarm failure in subscription/038_walsnd_shutdown_timeout was\ndiagnosed to the background psql session timing out due to a backup\ntaking a long time. The session was using a single timeout for all\nqueries, so switch to resetting the timer for each query to make it\nsurvive slow backups due to constrained buildfarm machines.\n\nBackpatch to v19 where the test was introduced.\n\nAuthor: Hayato Kuroda \nDiscussion: https://postgr.es/m/OS9PR01MB12149AA18EEA475D2AA22FD3BF5D12@OS9PR01MB12149.jpnprd01.prod.outlook.com\nBackpatch-through: 19", "completion": "Use per-query timeout in subscription test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npg_waldump (--start/--end), pg_recvlogical (--startpos/--endpos), and\npg_receivewal (--endpos) parsed user-supplied WAL locations with\nsscanf(\"%X/%08X\"). That accepts several forms rejected by pg_lsn input\nand can proceed with a different location than the user specified:\noverlong components, trailing characters, leading whitespace, signs, and\n0x prefixes.\n\nAdd pg_parse_lsn() to src/common and use it for those command-line\noptions. The helper accepts the pg_lsn text syntax only: one to eight\nhexadecimal digits, a slash, one to eight hexadecimal digits, and no\ntrailing characters. Each frontend tool keeps its existing error\nmessage.\n\nUse the same helper from pg_lsn_in_safe(), leaving only backend-specific\nsoft error reporting there. This keeps frontend command-line validation\nand backend pg_lsn input tied to one parser.\n\nBug: #19598\nReported-by: Michael Malis \nAuthor: Zexin Li \nReviewed-by: Ayush Tiwari \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/19598-aa67c8f4331611b4@postgresql.org", "completion": "Add common LSN parser for user-supplied locations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIt can never be true elsewhere.\n\nReported-by: Max Dymond\nCloses #22552", "completion": "tool_operate: only check for schannel if on windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Select): keep customize input aligned on clear hover\n\n* test(AutoComplete): cover both customize inputs on clear hover\n\n---------", "completion": "fix(Select): keep customize input aligned on clear hover"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo keep it tidy and to support properties in the template that only\nappear in the generated `libcurl.pc` when filled.\n\nE.g. `Required.private` may remain empty after #22548.\n\nAlso:\n- GHA/windows: dump `libcurl.pc` to log in every job\n- tidy up a pre-existing regex in the updated command.\n 2c22d3069aef507d6a6876a6d20616fe5e50c6a3 #22544\n\nRef: b9254da6175360102176303ecf9dbb5519b0ffcf #22548\nCherry-picked from #22543\n\nCloses #22553", "completion": "build: strip empty properties from `libcurl.pc`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 7cc2e8b349df28d55d5f40bfae323485df9f0cf2\nFollow-up to bfaab6ed6bb3e8865cd8dd60375fbdc39203a862\nCherry-picked from #22543\n\nCloses #22554", "completion": "configure: replace stray raw `grep` with `$GREP`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA DTLS listener drives the handshakes of connections which have not been\naccepted yet from inside its own tick: dtls_listener_drive_pending()\ncalls SSL_accept() on each of them. Those connections inherit the\nlistener's blocking mode, so once a listener connection is able to block\nwaiting for a datagram, that SSL_accept() can block too - and it must\nnot, because the listener is the only thing which will ever deliver the\ndatagram it is waiting for. Nothing else runs while the tick is inside\nthat call, so the wait cannot end.\n\nAdd force_nonblocking to DTLS1_STATE, set around the SSL_accept() that\ndtls_listener_drive_pending() performs, and consulted by\nossl_dtls_desires_blocking(). Ownership of a connection passes to the\napplication when SSL_accept_connection() returns it, and by then the\nflag is clear, so an application which asked for blocking still gets it.\n\nThe flag has to survive SSL_clear(), which memsets d1. SSL_clear() can\nrun inside the very SSL_accept() the listener is driving:\ndrive_single_connection() sets TLS1_FLAGS_STATELESS to suppress it, but\nonly where cookie validation is enabled. Losing the flag there is not\nmerely a missed optimisation - the connection blocks inside the tick,\npoll_translate_ssl_dtls_conn() ticks the listener again from another\nthread, drive_pending re-enters and collects the same connection twice,\nand registering it a second time trips the old == NULL assertion in the\nconnection lookup. In a release build that appears later as a\nuse-after-free rather than as anything to do with blocking mode.\n\nNothing blocks in a read yet, so this commit changes no behaviour on its\nown. It lands first so that the commit which adds blocking reads cannot\ndeadlock at any point in the series.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug 17 08:29:56 2026\nMerged-from: https://github.com/openssl/openssl/pull/32324", "completion": "DTLS 1.3 Keep listener driven connections out of blocking mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA connection created by a DTLS listener has no BIO of its own. The\nlistener owns the socket and demultiplexes datagrams into a per\nconnection queue, so there is nothing for a read to block in, and every\nread on an empty queue reported WANT_READ however the connection was\nconfigured. SSL_set_blocking_mode() therefore had no effect on reads.\n\nWait in the record layer instead, where a blocking BIO would have. When\nrlayer_dtls_get_urxe_packet() finds the queue empty and the connection is\nin blocking mode, ossl_dtls_conn_wait_for_datagram() waits for one to\narrive. The state machine above is untouched, so SSL_read(), SSL_peek(),\nSSL_do_handshake() and SSL_accept() all become blocking together, which\nis what an application moving from a plain DTLS object expects.\n\nThe wait loops, because the socket is shared: a wakeup may be for a\ndatagram belonging to a different connection, in which case our queue is\nstill empty and there is nothing to return. It also handles events after\neach wakeup, since while a thread is in here nothing else services the\nconnection, and the retransmission timer has to keep running - the poll\ntranslation folds the event timeout into the deadline so the wait ends in\ntime for it.\n\nExisting tests drive both ends of a connection from a single thread,\nwhich cannot work if the server side blocks, so create_dtls_listener() in\ndtlsssllistenertest.c now turns blocking mode off for its callers, with\ncreate_dtls_listener_unconfigured() for the one test which has to observe\nthe default. test_dtls_multithread opts out for the same reason.\n\nThe new test_dtls_blocking_read has the client stay silent for a while\nafter its handshake, so the server thread is already parked in\nSSL_read_ex() when the write finally comes. Its second iteration\nhandshakes in non-blocking mode and switches to blocking only for the\nread, which pins the read path on its own: in the first iteration the\nhandshake is what fails without this change, and the read is never\nreached.\n\nAssisted-by: Cl", "completion": "DTLS 1.3 Support blocking reads on listener connections"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nclose #15276\n\nMake createForSlots retain slot records across source updates. Reconcile keyed slots by their template key and unkeyed slots by their resolved slot name, updating loop alias refs without recreating slot functions.\n\nPass a stable record identity to slot fragments so unchanged slots retain their mounted content and local state. Reuse the resolved records array when slot resolution is unchanged to avoid unnecessary outlet updates.\n\nUpdate compiler-vapor to emit separate source, slot factory, name, and key callbacks, and add regression coverage for keyed and unkeyed dynamic slots.", "completion": "fix(vapor): preserve dynamic v-for slot state"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe only usage of the thread queue and pool is for \"DNS\" which is a\nstatic string. No point in strdup'ing it (twice). Future users are\n*likely* to also used fixed strings, otherwise we revert this change\nwhen dynamic names are introduced.\n\nReported-by: Max Dymond\nCloses #22555", "completion": "thrdqueue: drop name strdups from Curl_thrdq_create"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit db89a47115f0 added an 'options' argument to table_tuple_update()\nand table_tuple_delete(), correctly documenting it as recognizing no\nvalues. It also (correctly) added pg_attribute_unused() to the\ncorresponding heap_update() argument. Commit 28d534e2ae0a then added\nTABLE_UPDATE_NO_LOGICAL and TABLE_DELETE_NO_LOGICAL, but failed to\n(correctly) update the comment and heap_update()'s signature.\n\nIn table_tuple_update(), move the correct explanation of 'options' to\nthe right place, remove the bogus one.\n\nIn table_tuple_delete(), add the missing TABLE_DELETE_NO_LOGICAL doc.\n\nIn heap_update(), remove the pg_attribute_unused() marker.\n\nAuthor: Nikhil Sontakke \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/CA+UBoq21SzkjThYMSwSpVU-jwzpuEsf22Hq1FPbcKcDc43C29g@mail.gmail.com", "completion": "Fix stale comments/signature after commit 28d534e2ae0a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe dedotdotify() function that removes ./ and ../ sequences from paths\njuggles memory and is slow. Now needs_dedotdot() is called first to\ndetermine if the removal process is necessary and otherwise avoids doing\nit. Avoids unnecessary memory operations.\n\nAdjusted unit test 1395 accordingly because now a lot of input strings\nreturn NULL for \"no change necessary\".\n\nSuggested-by: Max Dymond\n\nCloses #22557", "completion": "urlapi: avoid dedotdotify() if possible"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe dedotdotify() function that removes ./ and ../ sequences from paths\njuggles memory and is slow. Now needs_dedotdot() is called first to\ndetermine if the removal process is necessary and otherwise avoids doing\nit. Avoids unnecessary memory operations.\n\nAdjusted unit test 1395 accordingly because now a lot of input strings\nreturn NULL for \"no change necessary\".", "completion": "urlapi: avoid dedotdotify() if possible"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA listener connection writes through the listener's socket, which is\nshared with every other connection and is always non-blocking. When a\nsend cannot be completed the DTLS record layer discards the datagram and\nreports that the write should be retried - a fair default for an\nunreliable transport, but not what an application which asked for\nblocking writes expects, since it gets neither the data sent nor a call\nwhich waited.\n\nAdd an rlayer callback, OSSL_FUNC_RLAYER_BLOCK_FOR_WRITE, which the\nrecord layer calls instead of reporting a retry. For a listener\nconnection in blocking mode it waits for the socket to become writable\nand returns 1, and tls_retry_write_records() goes round its loop again to\nrepeat the same send: nothing has been consumed at that point, so the\nretry is a genuine second attempt rather than a resend.\n\nOnly the BIO_sendmmsg() branch is hooked. That is the one listener\nconnections take, because their peer address is set, and the BIO_write()\nbranch below it belongs to connections which have a BIO of their own to\nblock in. A NULL callback leaves both paths exactly as they were, so TLS\nand standalone DTLS are untouched.\n\nThe wait itself is one wait per call, not a loop: the caller retries the\nsend and comes back here if it still cannot proceed, so a wakeup which\nturns out not to have left room in the socket buffer costs another\nattempt rather than a lost datagram.\n\nA loopback socket's send buffer does not fill, so the test supplies the\ntransient failure with a filter BIO in front of the listener's write BIO\nwhich rejects one send with a non-fatal error. Its ctrl forwards\neverything to the socket underneath, the poll descriptors included, since\nthose are what the wait itself needs. The client is then read to confirm\nthe datagram really was sent rather than merely reported as sent.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug", "completion": "DTLS 1.3 Support blocking writes on listener connections"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nFree the partially constructed ASN1_TYPE and return NULL when\nASN1_STRING_type_new() fails. Previously asn1_multi() returned an\nincomplete object.\n\nFound by x509v3 mfail regression test.\n\nReviewed-by: Milan Broz \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Sep 7 14:08:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32330", "completion": "Fix error handling in asn1_multi()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs: refine AI-assisted maintenance guide\n\n* docs: fix Markdown parsing in AI maintenance guide", "completion": "docs: refine AI-assisted maintenance guide"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nsetup_tests() read its two positional arguments without first calling\ntest_skip_common_options(), so the option cursor was never advanced from\nthe test's point of view and test_get_argument(0) returned the option\nitself. Passing -test or -iter therefore left the certificate path set to\nthe literal string \"-test\", and the run failed on that:\n\n error:80000002:system library:file_ctrl:No such file or directory:\n ...:calling fopen(-test, r)\n\nThe option was not being ignored: the framework parses it in\nprocess_shared_options() and the selected sub-test really does run. Only\nthe positional arguments were shifted, which is what made the failure\nlook unrelated to the option.\n\nAlso declare the usage string, so -help describes the two arguments the\ntest needs rather than showing none.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Jakub Zelenka \nMerge-date: Mon Aug 17 08:36:26 2026\nMerged-from: https://github.com/openssl/openssl/pull/32331", "completion": "Skip the common test options in dtls_multithread_test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo allow the function to verify that the buffer is large enough. Avoids\npossible future internal mishaps.\n\nCloses #22560", "completion": "keylog: add a random size argument to Curl_tls_keylog_write()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n- enums\n- macros\n- struct members\n- popup_.*()\n\n8.1.1523\n\n* build(vim-patch): 8.1.0863 is almost auto n/a\n\nCan't ignore os_unix.c hunk for \"failed:\" .", "completion": "build(vim-patch): n/a popup_ api #41270"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAdd a fixed slot0 member for uint32_bset to have no allocations for\nsizes < 64. This is a common use case for curl_easy_perform().\n\nCloses #22561", "completion": "uint-bset: add slot0 member"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe value is already stored in a local variable a few lines above.\nThis is just a cosmetic change.\n\nAuthor: Shinya Kato \nReviewed-by: Chao Li \nReviewed-by: solai v \nReviewed-by: Pierre Forstmann \nDiscussion: https://postgr.es/m/CAOzEurTJO2aqd9ewQmo9vjCrFUAD8Lk+raujCfK5oWoLGUP_3w@mail.gmail.com", "completion": "Avoid recalculating pgprocno in ProcArrayAdd()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22562", "completion": "progress: fix progress meter update to run every second again"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 649828769 improved this code to keep Sxx, Syy, and Sxy\nexactly zero so long as we see only a single value of the input(s).\nHowever, if any values of the other input are Inf or NaN, we'd\nbetter set Sxy to NaN instead. Otherwise we risk reporting zero\nvariance when the result is really undefined. The old coding handled\nthis implicitly, but in the short-circuit path we have to take care\nof it explicitly.\n\nBug: #19615\nReported-by: Junwen An \nAuthor: Andrey Rachitskiy \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/19615-c7e390593416f6b6@postgresql.org\nBackpatch-through: 19", "completion": "Fix float8_regr_accum() for Inf/NaN with constant other input."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nALTER TABLE ... REPLICA IDENTITY USING INDEX verified key columns by\nreading pg_attribute.attnotnull, but commit a379061a22a8 made\nattnotnull true also for unvalidated (NOT VALID) not-null constraints,\nwhich do not prove the column null-free. An index over such a column\ncould thus be marked as replica identity even though the column might\ncontain NULLs, causing apply-side divergence for UPDATE/DELETE on the\nnullable rows.\n\nFix by additionally requiring convalidated for the underlying\nconstraint, mirroring the fix d9ffc27291f applied to ATExecAddIdentity\nfor the analogous identity-column case.\n\nAuthor: Ante Krešić \nReviewed-by: Aleksander Alekseev \nReviewed-by: solai v \nBackpatch-through: 18\nDiscussion: https://postgr.es/m/CABXQ4dJUibZzN91qvWmsfA7MUDn9YRCNyu3CcukdyokbH1=41Q@mail.gmail.com", "completion": "Reject REPLICA IDENTITY USING INDEX on column with invalid NOT NULL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_FUNC instead of __func__ so the helper compiles in strict\nANSI/C90 builds.\n\nFixes: 0461a5636dec (\"test/quicapitest.c: add test for pending connections limit enforcement\")\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Viktor Dukhovni \nReviewed-by: Saša Nedvědický \nReviewed-by: Milan Broz \nMerge-date: Thu Aug 13 07:18:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32337\n(cherry picked from commit 0b9dacf5ef252775a9fab0e876a05415b23651ab)\n(cherry picked from commit 7df38b8e2a11ce14e2c2b8257c290ae7647fd5bd)", "completion": "test: use portable function-name macro in QUIC test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_FUNC instead of __func__ so the helper compiles in strict\nANSI/C90 builds.\n\nFixes: 0461a5636dec (\"test/quicapitest.c: add test for pending connections limit enforcement\")\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Viktor Dukhovni \nReviewed-by: Saša Nedvědický \nReviewed-by: Milan Broz \nMerge-date: Thu Aug 13 07:18:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32337\n(cherry picked from commit 0b9dacf5ef252775a9fab0e876a05415b23651ab)", "completion": "test: use portable function-name macro in QUIC test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse OPENSSL_FUNC instead of __func__ so the helper compiles in strict\nANSI/C90 builds.\n\nFixes: 0461a5636dec (\"test/quicapitest.c: add test for pending connections limit enforcement\")\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Viktor Dukhovni \nReviewed-by: Saša Nedvědický \nReviewed-by: Milan Broz \nMerge-date: Thu Aug 13 07:18:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32337", "completion": "test: use portable function-name macro in QUIC test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nValgrind slows execution down, causing DTLS retransmission timers to fire\nduring otherwise normal handshakes. The client retransmits its ClientHello\nbefore the server responds, and TLSProxy recorded the duplicate into\nmessage_list unconditionally. This shifted every subsequent message index\nby one, breaking three DTLS 1.3 subtests:\n\n70-test_tls13alerts.t: alert_filter corrupted message_list[1] expecting\nthe ServerHello, but found the retransmitted ClientHello instead. The\nreal ServerHello passed through uncorrupted, the handshake succeeded,\nand Message->fail() returned false.\n\n70-test_tls13messages.t / 70-test_tls13kexmodes.t: checkhandshake.pm\nwalks message_list sequentially comparing each .mt to an expected\nsequence. The extra ClientHello at position 0 shifted all five\nsubsequent checks.\n\nFix by deduplicating message_list in DTLS mode using (sender, msgseq) as\nthe key. Retransmitted DTLS handshake messages always carry the same\nmessage sequence number as the original, so duplicates are naturally\ndiscarded. HelloRetryRequest is unaffected becasue the retried ClientHello\ngets an incremented msgseq. The seen_msgseq hash is reset by clearClient\nso there is no state leakage between subtests.\n\nAssisted-by: Claude:claude-sonnet-4-6\nReviewed-by: Tomas Mraz \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:55:42 2026\nMerged-from: https://github.com/openssl/openssl/pull/32340", "completion": "DTLS 1.3 Fix TLSProxy DTLS retransmission in valgrind CI"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nRecent backport applied cleanly to 3.6, but 3.6 includes an extra call\nto evp_mac_fetch_from_prov, which uses a no longer in existance\nparameter.\n\nFix that up.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Paul Dale \nReviewed-by: Viktor Dukhovni \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 13 08:57:03 2026\nMerged-from: https://github.com/openssl/openssl/pull/32341", "completion": "Fix build break on evp_mac_fetch_from_prov"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSince this code needs to work (identically) on systems with 32 bit longs\nanyway, this might just as well always use 32 bit to save space and make\nthe code work the same everywhere.\n\nCloses #22564", "completion": "multi: hold timeout values in 'int' instead of 'long'"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo avoid holes on 64-bit architectures.\n\nCloses #22565", "completion": "multihandle: move two struct fields"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.2.0-next.1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.1.2"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTheir output is nearly identical to curl's implementations. Minor\ndifferences: it goes to stdout (curl: stderr), marks cache variables,\nbut doesn't mark 'advanced' ones.\n\nAlso:\n- indent curl's output to match CMake's.\n- replace single quotes with double to match CMake output.\n- alpha-sort target properties to match CMake.\n- alpha-sort config types to match CMake.\n- tested OK with cmake-4.4.20260811-g567ed0e and 4.4.20260812-g760e4fb.\n\nRefs:\nhttps://gitlab.kitware.com/cmake/cmake/-/commit/f723293c7f625b14bd48627042fc04e67b76c513\nhttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/11834\nhttps://gitlab.kitware.com/cmake/cmake/-/work_items/27513\nhttps://cmake.org/cmake/help/git-master/command/cmake_language.html#command:cmake_language\n\nFollow-up to 855acb3bb07e0dd06b5722218eb5fded333f7ce0 #17701\nFollow-up to f58342ae21fe4a04edddd98f255d8b0c3d66ae3a #15562\nFollow-up to cd51bb503ae1779a45c90898b89da6e19c616521 #14439\n\nCloses #22566", "completion": "cmake: use built-in variable and target property dump functions with CMake 4.5+"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis commit adds an implementation of a router resource (not currently exposed for public use) which\ndefines the behavior of a resource dependent on the Router navigation lifecycle.\n\n(cherry picked from commit c111f3fb0c2ee03ea9d96ea31306faddd519e575)", "completion": "refactor(router): Create transactional router resource"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis commit adds an implementation of a router resource (not currently exposed for public use) which\ndefines the behavior of a resource dependent on the Router navigation lifecycle.", "completion": "refactor(router): Create transactional router resource"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, the release script hardcoded the upstream repository URL as an unauthenticated HTTPS URL (https://github.com/angular/angular.git). Although the script verified that a GITHUB_TOKEN environment variable was present, it only used that token for REST API calls (such as creating the GitHub release) and did not provide it to Git commands. As a result, users who authenticate to GitHub via SSH (and do not have an HTTPS Git credential helper configured) were prompted interactively for GitHub login credentials when pushing the release tag.\n\nThis change dynamically resolves the upstream remote name from the user's configured remotes by checking for any remote pointing to angular/angular. When pushing over SSH, Git uses the user's existing SSH credentials. When pushing over HTTPS (or falling back), the script injects GITHUB_TOKEN into the push URL to prevent interactive authentication prompts.\n\n(cherry picked from commit 6f848db435ed7b675f0d8955f93c40da69904a20)", "completion": "build(vscode-extension): dynamically resolve upstream remote and use token for https pushes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, the release script hardcoded the upstream repository URL as an unauthenticated HTTPS URL (https://github.com/angular/angular.git). Although the script verified that a GITHUB_TOKEN environment variable was present, it only used that token for REST API calls (such as creating the GitHub release) and did not provide it to Git commands. As a result, users who authenticate to GitHub via SSH (and do not have an HTTPS Git credential helper configured) were prompted interactively for GitHub login credentials when pushing the release tag.\n\nThis change dynamically resolves the upstream remote name from the user's configured remotes by checking for any remote pointing to angular/angular. When pushing over SSH, Git uses the user's existing SSH credentials. When pushing over HTTPS (or falling back), the script injects GITHUB_TOKEN into the push URL to prevent interactive authentication prompts.", "completion": "build(vscode-extension): dynamically resolve upstream remote and use token for https pushes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nEvery GENERATE target must be absent from the index and covered by a\ncommitted .gitignore. The deliberately committed generated files, such\nas util/libcrypto.num and doc/build.info, come from \"make update\" rather\nthan GENERATE, and are not checked. Skips without git or a checkout.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMergeDate: Tue Aug 18 15:27:39 2026\n(Merged from https://github.com/openssl/openssl/pull/32343)", "completion": "Add a test that generated files are gitignored and untracked"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nVS Code parses notification text for links and permits `command:` URIs. Interpolating the workspace-controlled TSDK path can therefore let a malicious path add a command link to the approval prompt.\n\nRemove the path from the notification instead of attempting to sanitize or escape it. This keeps the prompt static and matches VS Code's TypeScript extension workspace-version approval flow.\n\nFixes #70176\n\n(cherry picked from commit ba13a3ce22fdf875b14c1cbbe200dcfa23717bf4)", "completion": "fix(vscode-extension): prevent command URI injection in TSDK approval"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nVS Code parses notification text for links and permits `command:` URIs. Interpolating the workspace-controlled TSDK path can therefore let a malicious path add a command link to the approval prompt.\n\nRemove the path from the notification instead of attempting to sanitize or escape it. This keeps the prompt static and matches VS Code's TypeScript extension workspace-version approval flow.\n\nFixes #70176", "completion": "fix(vscode-extension): prevent command URI injection in TSDK approval"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nClarify that transactions failed under --continue-on-error are reported\nseparately and are not counted as transactions actually processed, while\ntime spent on them can lower reported TPS. Also adjust the latency\ndescription to avoid implying that failed transactions are generally included\nin latency measurements.\n\nBackpatch to v19, where pgbench's --continue-on-error option was introduced.\n\nAuthor: Chao Li \nReviewed-by: Yugo Nagata \nReviewed-by: Xuneng Zhou \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/597C9755-4386-488D-A289-16D50AD81FBF@gmail.com\nBackpatch-through: 19", "completion": "doc: Clarify pgbench reporting with --continue-on-error"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe note used a confusing \"tables/except tables/schemas\" slash-list,\nomitted DROP from the operations requiring a subscriber refresh, and\ncalled out \"unset ALL SEQUENCES\" without its symmetric \"unset ALL TABLES\"\ncase. Reword for clarity and consistency.\n\nAuthor: Peter Smith \nReviewed-by: Amit Kapila \nBackpatch-through: 19\nDiscussion: https://postgr.es/m/CAHut+PuGKrWhVMvuFyf-wSdF-Tai_jPTz2UCSCqsYM-82ATY5w@mail.gmail.com", "completion": "Doc: Clarify ALTER PUBLICATION's REFRESH PUBLICATION wording."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen vacuumdb --analyze-only or --analyze-in-stages enumerates\ntables itself, it can select both a partitioned table and its\npartitions as separate work items. Previously, it generated plain\nANALYZE for the partitioned table, which recursively analyzed its\npartitions as well.\n\nThis caused duplicate work when the partitions were already selected by\nvacuumdb. With --analyze-in-stages, the redundant work could be\nrepeated at every stage.\n\nFix this by generating ANALYZE ONLY for automatically selected\npartitioned tables when connected to servers that support it. This\nupdates inherited statistics for the partitioned table while leaving\nper-partition statistics to the separately selected partition entries.\nFor older servers that do not support ANALYZE ONLY, vacuumdb falls back\nto the previous plain ANALYZE command.\n\nThis also applies when partitioned tables are selected by schema\nfilters. In that case, partitions matching the filters are analyzed as\nseparate targets, while per-partition statistics for partitions outside\nthe filters are not updated via the partitioned parent.\n\nThis commit does not change the behavior for partitioned tables\nspecified explicitly with --table, i.e., in that case, vacuumdb\ncontinues to generate plain ANALYZE, recursively analyzing the specified\npartitioned table and its partitions.\n\nSuggested-by: Justin Pryzby \nAuthor: Fujii Masao \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/aKZ7lMYGnnIo35c0@pryzbyj2023\nBackpatch-through: 19", "completion": "vacuumdb: Use ANALYZE ONLY for partitioned tables"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhen the RISCV vector extensions version is not explicitly\nspecified, qemu issues warnings to stderr when running each\nprogram. This broke some CI jobs.\n\nPin the version to the (current) \"v1.0\" default.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Saša Nedvědický \nReviewed-by: Igor Ustinov \nMergeDate: Thu Aug 13 06:32:59 2026\n(Merged from https://github.com/openssl/openssl/pull/32345)\n\n(cherry picked from commit 31e93626b5f24b84947a954929106b4cfd5a03e7)", "completion": "Deal with riscv64 qemu-user stderr noise"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nWhen the RISCV vector extensions version is not explicitly\nspecified, qemu issues warnings to stderr when running each\nprogram. This broke some CI jobs.\n\nPin the version to the (current) \"v1.0\" default.\n\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Saša Nedvědický \nReviewed-by: Igor Ustinov \nMergeDate: Thu Aug 13 06:32:59 2026\n(Merged from https://github.com/openssl/openssl/pull/32345)", "completion": "Deal with riscv64 qemu-user stderr noise"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nA lazily loaded `DynamicModule` whose dynamic metadata carries `imports`\nnever had those imports scanned, so their providers could not resolve.\n\n`NestContainer#setModule` pre-registers a dynamic module's `imports` via\n`addDynamicMetadata` -> `addDynamicModules` -> `addModule` before the\nscanner recurses into them. Those modules therefore report\n`inserted: false`, and the lazy skip condition treated them as already\nloaded, leaving them registered but never scanned or instantiated.\n\nSkip only modules that were actually instantiated, and bind global\nproviders on every lazy pass: a rescanned module reports\n`inserted: false`, so `lazy && moduleInserted` skipped binding `@Global`\nproviders into it.\n\nCloses #17462", "completion": "fix(core): scan pre-registered dynamic imports of lazy modules"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCapture cleanup callbacks registered while rendering component v-for items\nand transfer them from the owner scope to the corresponding ForBlock.\n\nRun the captured callbacks after structural removal so removed component\ninstances and their DOM can be released immediately. This preserves the\ncomponent v-for optimization by avoiding an additional EffectScope for every\nitem.", "completion": "fix(runtime-vapor): clean up removed v-for components"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse the configuration filename that was actually added. Set the random\nconfiguration property to fips=yes so the existing RSA checks use a DRBG\nfrom the renamed FIPS provider, rather than one from the default\nprovider.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Nikola Pajkovsky \nReviewed-by: Norbert Pocs \nMerge-date: Fri Aug 21 11:51:15 2026\nMerged-from: https://github.com/openssl/openssl/pull/32357", "completion": "test: fix FIPS identity DRBG regression coverage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse the configuration filename that was actually added. Set the random\nconfiguration property to fips=yes so the existing RSA checks use a DRBG\nfrom the renamed FIPS provider, rather than one from the default\nprovider.\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Simo Sorce \nReviewed-by: Andrew Dinh \nMergeDate: Tue Aug 18 16:22:41 2026\n(Merged from https://github.com/openssl/openssl/pull/32355)", "completion": "test: fix FIPS identity DRBG regression coverage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse the configuration filename that was actually added. Set the random\nconfiguration property to fips=yes so the existing RSA checks use a DRBG\nfrom the renamed FIPS provider, rather than one from the default\nprovider.\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Richard Levitte \nReviewed-by: Paul Dale \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Neil Horman \nMergeDate: Fri Aug 14 12:41:55 2026\n(Merged from https://github.com/openssl/openssl/pull/32346)\n\n(cherry picked from commit fd2e2860a415c6febbb180ab4133dfa0e9d8d6a6)", "completion": "test: fix FIPS identity DRBG regression coverage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUse the configuration filename that was actually added. Set the random\nconfiguration property to fips=yes so the existing RSA checks use a DRBG\nfrom the renamed FIPS provider, rather than one from the default\nprovider.\n\nAssisted-by: Codex:gpt-5.6-sol\n\nReviewed-by: Richard Levitte \nReviewed-by: Paul Dale \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Neil Horman \nMergeDate: Fri Aug 14 12:41:55 2026\n(Merged from https://github.com/openssl/openssl/pull/32346)", "completion": "test: fix FIPS identity DRBG regression coverage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency tar.bzl to v0.10.8"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nCloses #15285", "completion": "fix(runtime-vapor): normalize declared style props (fix #15285)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to cd238bb7addf5b1f174df47ccc61651a545c4876 #22552\n\nCloses #22568", "completion": "tool_operate: limit `is_using_schannel()` call to Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nExport containsTree from @angular/router to enable direct UrlTree subset matching.", "completion": "feat(router): add containsTree as public API"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe OPENSSL_armcap(3) man page does not exist on the 3.4 branch,\nwhich makes 'make doc-nits' (check_docs CI job) fail with:\n\n doc/man7/EVP_CIPHER-SM4.pod:1: reference to non-existing OPENSSL_armcap(3)\n\nRemove the references, keeping the existing OPENSSL_ia32cap(3) and\nOPENSSL_riscvcap(3) ones.\n\nFixes: d0aa08287cae \"Document SM4 table-lookup side-channel risk\"\nAssisted-by: Pi:moonshotai/kimi-k3\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 13 13:24:24 2026\nMerged-from: https://github.com/openssl/openssl/pull/32350", "completion": "doc: drop OPENSSL_armcap(3) references in EVP_CIPHER-SM4"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSigned-off-by: Nikola Pajkovsky \n\nReviewed-by: Saša Nedvědický \nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Viktor Dukhovni \nMergeDate: Thu Aug 13 12:15:34 2026\n(Merged from https://github.com/openssl/openssl/pull/32349)", "completion": "test: use portable function-name macro in QUIC test helper"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIn the totally unlikely event that next_easy_id would ever wrap, avoid\nundefined behavior. It is a signed type.\n\nAlso: update the related comment in urldata.h that mentioned LONG_MAX\nbut is nowadays CURL_OFF_T_MAX\n\nCloses #22569", "completion": "conncache: don't assume curl_off_t increment wrap-around"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 9d034539ece1e\n\nCloses #22570", "completion": "tool_operate: refactor schannel checks and move win32 cert checks to function"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to 9d034539ece1e", "completion": "tool_operate: reduce ifdefs for the is_using_schannel check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nmdc_finish used to set this field once it had successfully verified\nthe MDC packet, with its only reader in the same function. This was\nremoved by a59ee881978 when mdc_finish stopped being called through\nthe pullf_read API, the field has been unused since.\n\nNote that MDC verification does not rely on it: process_data_packets\ntracks whether an MDC packet was seen in its local got_mdc variable\nand rejects the message if a required MDC is missing, while the\nuse_mdcbuf_filter path checks the hash in mdcbuf_finish().\n\nAuthor: Aleksander Alekseev \nDiscussion: https://postgr.es/m/CAJ7c6TNmHnnCkn3uZwRUE7WWYftW--48JFoDVDqoZqMrLYxUZw@mail.gmail.com", "completion": "pgcrypto: remove unused field mdc_checked from PGP_Context"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nMaintenance tasks like connection upkeep, liveliness checks and cache\neviction must only run on an admin handle, not the application transfer\nfrom the calling context.\n\nThen application transfers will get only attached to the connections\nthey actually work on. This makes `data->state.recent_conn_id`\nmeaningful for checks if a subsequent address is finding the previous\nconnection again.\n\nOne thing led to another:\n- add Curl_get_admin(data), to obtain an admin handle for\n an application handle, inheriting some properties for\n connection operation.\n- rename `Curl_easy *data` parameter to `Curl_easy *admin`\n where only admin handles should be passed. Add DEBUGASSERTs\n in the called function.\n- rename `Curl_conn_terminate()` to `Curl_conn_close()`\n because this makes connections enter the shutdown close\n where possible.\n- rename `Curl_cshutdn_terminate()` to `Curl_conn_terminate()`\n since this definitely kills the connection and does not\n involve a `cshutdn` instance.\n- add Curl_share_lock_share(), Curl_share_unlock_share()\n so it possible to operate on a share without the passed\n easy handle having the share set.\n This catches a case where a shared needed to be locked\n but was not before. Adjust test1554 results.\n\nFixes #22567\nReported-by: cybertron10 on github\nCloses #22572", "completion": "connections: use admin handles only for maintenance"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 560d3f04122889957bdca86787bc165a051bcfaa)", "completion": "docs: update naming-conventions skill"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nLoosen the RSS increase check slightly to make the test less flaky.\nAlso use 'rss-max' stat.\n\nCloses #22574", "completion": "test_20_11: more leniency"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis was harmless because the function (ThereAreNoReadyPortals()) has\nonly one caller, and that caller throws an error if the function\nreturns false and transaction abort cleans up the in-progress hash\nsearches. But if someone called the function in some other way,\nthey'd get a warning about a leaked hash_seq_search scan.", "completion": "Fix missing hash_seq_term()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit cba5b994c9 removed the call to poll() that needed it.", "completion": "Remove unnecessary #include "} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 647bf8e1436d5479b475d6364c427662586e4c88)", "completion": "docs: note SafeResourceUrl audio src change"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nvim.diagnostic.set() defers extmark position computation for an\nunloaded buffer via a once=true BufRead autocmd, registering a new one\non every call without replacing the previous one. Each pending autocmd\nalso retains that call's diagnostics.\n\nSolution:\nInstead of registering an autocmd per set() call, register a single\nstatic BufRead autocmd that computes positions from the diagnostic\ncache for any buffer with cached diagnostics when it is read. This\nremoves the per-call registration entirely (nothing left to\naccumulate) and means diagnostics cleared while the buffer was\nunloaded no longer produce stale extmarks.", "completion": "fix(diagnostic): don't accumulate BufRead autocmds for unloaded buffers #40869"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update all github actions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSo that frame-type check covers both frameworks\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Norbert Pocs \nMerge-date: Wed Sep 2 06:32:34 2026\nMerged-from: https://github.com/openssl/openssl/pull/32335", "completion": "Extend qlog coverage to radix test"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nImplement component highlighting on change detection cycles along with embedding\nthe component-specific data to the directive/component tree explorer.\n\nCloses #59057\n\nPR Close #70254", "completion": "feat(devtools): implement CD analyzer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSome places rejected individual tokens longer than MAXSTRLEN, while\nothers rejected ones longer than MAXSTRLEN-1. The data structure is\nperfectly capable of handling MAXSTRLEN, so there's nothing wrong\nwith using the looser bound. Moreover, as things stand there is a\ndump/reload hazard: some code paths permit construction of a tsvector\nor tsquery that would later be rejected by tsvectorin or tsqueryin.\nSo standardize on using MAXSTRLEN.\n\nIdentical remarks apply to MAXSTRPOS (the total data length),\nso fix that too.\n\nBack-patch, in hopes of avoiding cases where a value acceptable to\none supported release is not acceptable to another.\n\nAuthor: Tom Lane \nReviewed-by: Zsolt Parragi \nDiscussion: https://postgr.es/m/CAN4CZFNYQo4zfbRR435uD0vSfuy5y7dnFOXDfKr9zYoL1JnAxA@mail.gmail.com\nBackpatch-through: 14", "completion": "Consistently enforce tsvector/tsquery maximum lengths."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCurl_xfer_send() reports CURLE_AGAIN as a successful zero-byte send, so\nthe retry loop spun at 100% CPU and ignored the timeout when the peer\nstopped draining. Wait for writability and check the remaining time\nbetween retries.\n\nCloses #22576", "completion": "dict: avoid busy-loop in sendf() when the socket is not writable"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTo allow this we'll catch the errors during typechecking and discard it.\n\nAs context, when setting `isolatedDeclarations: true` this requires developers to explicitly type every property but the `private` ones. By allowing private properties to be used in templates we discard the actually for explicit typing for template only properties.", "completion": "feat(compiler): allow template to access private props"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf appending an additional certificate to the CA stack fails\nPKCS12_parse() leaves certificates appended earlier during the call\nin the output stack. If PKCS12_parse() allocated the stack\nthen the whole stack might be leaked if caller assumes failure.\n\nFix:\nRecord the original stack and its size then on failure\nremove certificates appended during the failed call.\nFree the stack if it was allocated by PKCS12_parse().\n\nFound by : store fuzzer (MFAIL-test)\n\nAssisted-by: ChatGPT:gpt-5.6\nReviewed-by: Dmitry Belyavskiy \nReviewed-by: Mounir Idrassi \nMerge-date: Thu Aug 27 16:49:42 2026\nMerged-from: https://github.com/openssl/openssl/pull/32407", "completion": "Fix memory leak in PKCS12_parse"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAngular's internal LView/TNode bookkeeping can get out of sync with the\nreal DOM: manual DOM manipulation, a browser extension, or an edge case in\nAngular's own view-insertion/reordering code can all leave Angular believing\na node is still attached at a given position when it isn't. The next time\nAngular's renderer calls `insertBefore` relative to that stale reference\nnode, the native DOM API throws an opaque `NotFoundError` with no indication\nof which node or component was involved, making these errors effectively\nundebuggable in production:\n\n NotFoundError: Failed to execute 'insertBefore' on 'Node': The node\n before which the new node is to be inserted is not a child of this node.\n at Node.insertBefore (native)\n at DefaultDomRenderer2.insertBefore (packages/platform-browser/src/dom/dom_renderer.ts)\n at nativeInsertBefore (packages/core/src/render3/dom_node_manipulation.ts)\n at nativeAppendOrInsertBefore (packages/core/src/render3/dom_node_manipulation.ts)\n ... (called while Angular inserts or moves a view during change detection)\n\nCheck the reference node's actual parent against the expected parent before\ncalling the native `insertBefore`, and throw a descriptive `RuntimeError`\n(NG05106) instead, following the same pattern already used for hydration\nnode mismatches.\n\n(cherry picked from commit 1cb3d606bf5bb01ec9c9e9289703a79f64c76e89)", "completion": "fix(platform-browser): throw a descriptive error when insertBefore reference node is missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAngular's internal LView/TNode bookkeeping can get out of sync with the\nreal DOM: manual DOM manipulation, a browser extension, or an edge case in\nAngular's own view-insertion/reordering code can all leave Angular believing\na node is still attached at a given position when it isn't. The next time\nAngular's renderer calls `insertBefore` relative to that stale reference\nnode, the native DOM API throws an opaque `NotFoundError` with no indication\nof which node or component was involved, making these errors effectively\nundebuggable in production:\n\n NotFoundError: Failed to execute 'insertBefore' on 'Node': The node\n before which the new node is to be inserted is not a child of this node.\n at Node.insertBefore (native)\n at DefaultDomRenderer2.insertBefore (packages/platform-browser/src/dom/dom_renderer.ts)\n at nativeInsertBefore (packages/core/src/render3/dom_node_manipulation.ts)\n at nativeAppendOrInsertBefore (packages/core/src/render3/dom_node_manipulation.ts)\n ... (called while Angular inserts or moves a view during change detection)\n\nCheck the reference node's actual parent against the expected parent before\ncalling the native `insertBefore`, and throw a descriptive `RuntimeError`\n(NG05106) instead, following the same pattern already used for hydration\nnode mismatches.", "completion": "fix(platform-browser): throw a descriptive error when insertBefore reference node is missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.1.4"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nActivated Route Injector feature was developed for resources. This moves the internal\nnaming (files and vars) to reflect this now that we have landed the core bits of plumbing\nand are ready to implement router resources.\n\nPR Close #70211", "completion": "refactor(router): rename activated route injector feature to resource feature"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is needed on 3.5 as that supports -ansi builds.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Richard Levitte \nReviewed-by: Milan Broz \nMerge-date: Fri Aug 21 10:49:43 2026\nMerged-from: https://github.com/openssl/openssl/pull/32356", "completion": "test_pending_limit(): Use OPENSSL_FUNC instead of __func__"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is needed on 3.5 as that supports -ansi builds.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Richard Levitte \nReviewed-by: Milan Broz \nMerge-date: Fri Aug 21 10:49:31 2026\nMerged-from: https://github.com/openssl/openssl/pull/32356", "completion": "test_pending_limit(): Use OPENSSL_FUNC instead of __func__"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis is needed on 3.5 as that supports -ansi builds.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Richard Levitte \nReviewed-by: Milan Broz \nMerge-date: Fri Aug 21 10:49:15 2026\nMerged-from: https://github.com/openssl/openssl/pull/32356", "completion": "test_pending_limit(): Use OPENSSL_FUNC instead of __func__"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22577", "completion": "file: support directory listing on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIn store_result.c:try_key_value() return value of\nOSSL_DECODER_CTX_new_for_pkey() is not checked so on\nfailed memory allocation OSSL_DECODER_CTX_set_passphrase_cb()\ndereferences NULL without any check.\n\nFound by : store fuzzer (MFAIL-test)\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Neil Horman \nMergeDate: Tue Sep 15 14:20:04 2026\n(Merged from https://github.com/openssl/openssl/pull/32413)", "completion": "Fix NULL dereference in try_key_value()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe introduction of the REPACK command also added support for\nCLUSTER (ANALYZE). Presumably this was unintentional, as the\nCLUSTER docs make no mention of it. CLUSTER (ANALYZE) on an\nordinary table succeeds and does indeed analyze the table, but a\ndatabase-wide CLUSTER (ANALYZE) or one on a partitioned table\nfails with an error like:\n\n ERROR: cannot execute REPACK (ANALYZE) on multiple tables\n\nRather than improving support for CLUSTER (ANALYZE) and thereby\nencouraging folks to use CLUSTER instead of REPACK, let's just\nreject it. This commit does so by teaching ExecRepack() to ERROR\nfor the ANALYZE option in anything except REPACK commands. Note\nthat VACUUM (FULL, ANALYZE) does not go through ExecRepack() and\ntherefore is unaffected by this change.\n\nOversight in commit ac58465e06.\n\nReported-by: Zsolt Parragi \nAuthor: Zsolt Parragi \nDiscussion: https://postgr.es/m/CAN4CZFMVcgv1b2G-i%2Bkhs2MDnzWSr7O_53j_x%2BuhAxUV5rwWqw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Reject CLUSTER (ANALYZE)."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOn failed memory allocation in decoder_lib.c and ossl_decoder_instance_new_forprov()\nallocation of return value OSSL_DECODER_INSTANCE* is not checked\ncausing decoderctx to leak.\n\nFound by : store fuzzer (MFAIL-test)\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Neil Horman \nMergeDate: Tue Sep 15 14:20:03 2026\n(Merged from https://github.com/openssl/openssl/pull/32413)", "completion": "Fix memory leak in ossl_decoder_instance_new_forprov()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nlocateOrCreateElementNodeImpl looks up the DOM node for an element\nduring hydration and immediately checks its nodeType. If the\nclient-rendered DOM has fewer nodes than the server-rendered HTML,\nthe lookup returns null, and in production that null flows straight\ninto the nodeType check and crashes with a raw, uncoded\n\"Cannot read properties of null (reading 'nodeType')\" TypeError.\n\nThe dev-mode check that would normally catch this (validateMatchingNode)\nalready handles a missing node, but it's compiled out of production\nbuilds, so the crash only shows up outside of dev mode.\n\nAdd a null check ahead of the nodeType check that throws a coded\nRuntimeError using the existing HYDRATION_MISSING_NODE (NG0502) code,\nwith a descriptive message in dev mode and a cheap fallback in\nproduction. Also add a regression test that removes a server-rendered\nelement before hydration runs and asserts a coded RuntimeError is\nthrown instead of a raw TypeError.\n\n(cherry picked from commit c6e4a36be1246e0fbe06d591a69ac79cd74348d2)", "completion": "fix(core): throw a descriptive error instead of crashing when a hydration node is missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nlocateOrCreateElementNodeImpl looks up the DOM node for an element\nduring hydration and immediately checks its nodeType. If the\nclient-rendered DOM has fewer nodes than the server-rendered HTML,\nthe lookup returns null, and in production that null flows straight\ninto the nodeType check and crashes with a raw, uncoded\n\"Cannot read properties of null (reading 'nodeType')\" TypeError.\n\nThe dev-mode check that would normally catch this (validateMatchingNode)\nalready handles a missing node, but it's compiled out of production\nbuilds, so the crash only shows up outside of dev mode.\n\nAdd a null check ahead of the nodeType check that throws a coded\nRuntimeError using the existing HYDRATION_MISSING_NODE (NG0502) code,\nwith a descriptive message in dev mode and a cheap fallback in\nproduction. Also add a regression test that removes a server-rendered\nelement before hydration runs and asserts a coded RuntimeError is\nthrown instead of a raw TypeError.", "completion": "fix(core): throw a descriptive error instead of crashing when a hydration node is missing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPresently, check_role_membership_authorization() decides whether\nthe current user may grant or revoke membership in a role by\ncalling is_admin_of_role(), which recurses through all grants,\nwhile it chooses the grantor to record for the resulting entry by\ncalling select_best_admin(), which recurses only through inherited\ngrants. When the two disagree, the permission check passes and the\ngrantor lookup then comes up empty, so the user sees an internal\n\"no possible grantors\" error. ALTER GROUP ... ADD USER reaches the\nsame error through the separate check in AlterRole().\n\nTo fix, teach both checks to search the same way\nselect_best_admin() does via a new has_admin_privs_of_role(). The\nnew check passes exactly when the grantor lookup was going to\nsucceed, so nothing that works today starts failing; the internal\nerror simply becomes a proper permission error. Note that this\nleaves the other callers of is_admin_of_role() alone, so a role\nreachable only through a non-inherited grant can still be dropped,\nrenamed, or altered. Whether that ought to change as well is left\nas a future exercise.\n\nOversight in commit ce6b672e44.\n\nReported-by: ChangAo Chen \nAuthor: ChangAo Chen \nReviewed-by: Chao Li \nReviewed-by: Pretham \nReviewed-by: Robert Haas \nReviewed-by: Jacob Champion \nDiscussion: https://postgr.es/m/tencent_ADCE2B34B230A9B631854806104FEF40C105%40qq.com\nDiscussion: https://postgr.es/m/CAJUn_kN%2BMhbb8fYP5xxQCq1KEziOinM6HgYx4ts_pPDnQ2y1nQ%40mail.gmail.com\nBackpatch-through: 16", "completion": "Fix authorization check for role membership changes."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, when you passed an object typed like\nRecord<'a' | 'b', number> into the `keyvalue` pipe, TypeScript would\n\"forget\" that the keys could only ever be 'a' or 'b', and just tell\nyou the key was a plain `string` instead. So code like this used to\nfail to compile, even though it's correct:\n\n```ts\n const input: Record<'a' | 'b', number> = {a: 1, b: 2};\n const result = pipe.transform(input);\n const key: 'a' | 'b' = result[0].key; // error: string is not 'a' | 'b'\n```\n\nThis happened because the pipe has multiple overloaded versions of\ntransform(), and TypeScript checks them top to bottom, using the\nfirst one that matches. The \"number keys\" overload was listed first,\nand it happened to also match string-keyed objects by accident, so\nit \"won\" before the correct \"string keys\" overload ever got a\nchance to run.\n\nThe fix just reorders those two overloads so the string-keys one is\nchecked first. Nothing about runtime behavior changes — objects with\nactual numeric keys (e.g. Record<1 | 2, string>) still correctly\nreport their keys as plain `string`, matching what Object.keys()\nreally returns at runtime.\n\n(cherry picked from commit 46d2cb7ff049dc4549080f64dceb1541b3a87cee)", "completion": "fix(common): preserve literal key union in KeyValuePipe.transform()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPreviously, when you passed an object typed like\nRecord<'a' | 'b', number> into the `keyvalue` pipe, TypeScript would\n\"forget\" that the keys could only ever be 'a' or 'b', and just tell\nyou the key was a plain `string` instead. So code like this used to\nfail to compile, even though it's correct:\n\n```ts\n const input: Record<'a' | 'b', number> = {a: 1, b: 2};\n const result = pipe.transform(input);\n const key: 'a' | 'b' = result[0].key; // error: string is not 'a' | 'b'\n```\n\nThis happened because the pipe has multiple overloaded versions of\ntransform(), and TypeScript checks them top to bottom, using the\nfirst one that matches. The \"number keys\" overload was listed first,\nand it happened to also match string-keyed objects by accident, so\nit \"won\" before the correct \"string keys\" overload ever got a\nchance to run.\n\nThe fix just reorders those two overloads so the string-keys one is\nchecked first. Nothing about runtime behavior changes — objects with\nactual numeric keys (e.g. Record<1 | 2, string>) still correctly\nreport their keys as plain `string`, matching what Object.keys()\nreally returns at runtime.", "completion": "fix(common): preserve literal key union in KeyValuePipe.transform()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:53 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Allow pushing an empty ASN1_UTF8STRING onto a CMP freeText stack"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Add test coverage for ASN1_UNIVERSALSTRING_to_string"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit touches both the libpq and backend-side code of channel\nbinding where respectively pgtls_get_peer_certificate_hash() and\nbe_tls_get_certificate_hash() are upgraded to retrieve digests using the\nmethod recommended by OpenSSL 3.0: no more direct EVP_sha256() or\nsimilar, just a EVP_MD_fetch() through EVP to get an algorythm type,\nbased on a name.\n\nThe pre-3.0 code is still required for LibreSSL and as long as we\nsupport OpenSSL 1.1.1.\n\nSimilar work has been done in b91f79cd08ab and 1f3b9bb109b8.\n\nAuthor: Mark Atwood \nCo-authored-by: Michael Paquier \nDiscussion: https://postgr.es/m/178596055149.1584250.13974609482797470185@reviewcommit.com", "completion": "Use explicit fetching of digests in channel binding (OpenSSL >= 3.0)"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`inputlist()` advertises \"click with the mouse\" purely because it\nimplements click selection, so under the default `'mouse'` of \"nvi\" it\noffers a click that command-line mode never receives.\n\nSolution:\nOnly offer the mouse when `'mouse'` covers command-line mode, the same\ncondition `:help inputlist()` already documents.", "completion": "fix(messages): `inputlist()` offers the mouse when it cannot be used"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis new structure is split depending on the stats kind it deals with:\n- PGSTAT_KIND_RELATION, for tables.\n- PGSTAT_KIND_INDEX, for indexes.\n\nThis change designs a cleaner barrier for the handling of stats data\nrelated to tables and indexes, by being able to track precisely what are\nthe counters used by one or the other for pending data. Using a common\nground for both eases the tracking of Relations in the relcache, with a\nstructure based on a union separated by stats kind.\n\nThe code originally pointed to some counters that may not be used at\nall. For example, indexes have no need for the tracking of\nsub-transaction data, still the code implied that these could be touched\nfor an index. A consequence is that PgStat_TableXactStatus is not\nrenamed, as it is not used by indexes.\n\nSome asserts are added as an extra layer of protection to prevent the\nupdate of fields that should not be touched. find_tabstat_entry() and\nfind_tabstat_entry_kind() are removed, replaced by a single\nfind_relstat_entry_kind() able to work for indexes and the rest.\n\n72a6dad1c911 took care of the shared memory and on-disk part of the\nsplit. This focuses on the pending data part at backend level.\n\nAuthor: Michael Paquier \nReviewed-by: Bertrand Drouvot \nDiscussion: https://postgr.es/m/f572abe7-a1bb-e13b-48c7-2ca150546822@gmail.com", "completion": "Refactor PgStat_TableStatus to new PgStat_RelationStatus"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(List): update with Listy migration guidance\n\n* update\n\n* Refine List deprecation notice in English docs", "completion": "docs(List): update with Listy migration guidance"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe error printed would always use a NULL value, due to OBJ_nid2sn()\nknown to fail. This updates the error message to use the algorithm\nnumber instead.\n\nOversight in 28995f051e72, in the shape of copy-pasto failure.\n\nReported-by: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwGPjENxX1SmkPrv9Rb-Fnij8jN4ginObmSTnWXqROS2+g@mail.gmail.com", "completion": "Fix thinko in error of algorithm type lookup for channel binding"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nMove isolated prop and slot source effects into a cache-owned scope so nested\nbranch teardown does not stop them. Pause the scope while deactivated, resume it\non activation, and stop it when the cached component is unmounted.", "completion": "fix(runtime-vapor): preserve cached input effects across nested branch teardown"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ninjection_points is extended so as a caller can attach a string value to\na point, checked with a value provided at runtime. There are a couple\nof use cases where this can be useful, to be able to target points for\nspecific object names.\n\nPID and string conditions can be combined together, so as a point can be\nallowed for a specific process and string value at the same time.\n\nThe condition string is capped at 255 characters. As the attach SQL\nfunction now takes an optional condition string, it is no longer STRICT,\nand rejects NULL inputs. Empty condition strings are also rejected, as\nthey don't make sense.\n\nAuthor: Sami Imseih \nReviewed-by: Bertrand Drouvot \nReviewed-by: Michael Paquier \nDiscussion: https://postgr.es/m/CAA5RZ0tsGHu2h6YLnVu4HiK05q+gTE_9WVUAqihW2LSscAYS-g@mail.gmail.com", "completion": "injection_points: Add support for string comparison in conditions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nquic_radix_test emits several MiB of diagnostics on stderr even when\nit succeeds. In #32128 the process was observed blocked in fwrite()\nwhile writing this output to its inherited stderr pipe.\n\nAs a targeted workaround, redirect stderr to a log during non-verbose\nharness runs. If the test fails, replay diagnostics from at most the\nfinal 32 KiB and report the log path. This preserves useful failure\ncontext without feeding the full multi-megabyte log back through the\nTAP pipe. Verbose and direct recipe runs remain unchanged.\n\nThis removes the observed writer-side backpressure point without\nchanging general harness behavior. The reason the harness reader\nstopped making progress remains unknown.\n\nRelated to #32128\n\nAssisted-by: Codex:gpt-5.6-sel\n\nReviewed-by: Neil Horman \nReviewed-by: Saša Nedvědický \nMergeDate: Mon Aug 17 20:19:49 2026\n(Merged from https://github.com/openssl/openssl/pull/32395)", "completion": "test: keep QUIC RADIX diagnostics out of TAP pipe"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(Form): correct required default value\n\n* docs(Form): clarify required behavior\n\n* docs(Form): align required descriptions", "completion": "docs(Form): correct required default value"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis serves as an in-core example of the condition-string API of\ninjection_points introduced in 0fd73cdffc18, where a wait at the\nbeginning of a replication slot creation is tightened to happen only for\na specific slot name.\n\nAuthor: Sami Imseih \nDiscussion: https://postgr.es/m/CAA5RZ0tsGHu2h6YLnVu4HiK05q+gTE_9WVUAqihW2LSscAYS-g@mail.gmail.com", "completion": "Add string-based injection point wait in 051_effective_wal_level.pl"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSets up a build rule to use Selenium Webdriver for e2e tests.\n\n(cherry picked from commit 4d2dc1fb08a1a587880fdb37ef5b74af8058f98c)", "completion": "build: add webdriver build rule"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSets up a build rule to use Selenium Webdriver for e2e tests.", "completion": "build: add webdriver build rule"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the `playground` tests not to depend on Protractor.\n\n(cherry picked from commit 3d43067e206eeb0a64772e79e0c9589153450860)", "completion": "build: switch playground away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the `playground` tests not to depend on Protractor.", "completion": "build: switch playground away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the tests under `core` not to depend on Protractor.\n\n(cherry picked from commit 413c79c10b51f0a90120a1561e022518c6c807a5)", "completion": "build: switch core tests away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the tests under `core` not to depend on Protractor.", "completion": "build: switch core tests away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the `examples` tests not to depend on Protractor.\n\n(cherry picked from commit 204265f9a3a754c9082733fb76bb90535cd16ab4)", "completion": "build: switch examples away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the `examples` tests not to depend on Protractor.", "completion": "build: switch examples away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the tests in adev not to depend on Protractor.\n\n(cherry picked from commit 7b74bee5b4485b2a42198db115abcfd5de103c71)", "completion": "build: switch adev tests away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nReworks the tests in adev not to depend on Protractor.", "completion": "build: switch adev tests away from protractor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen the time-out value is passed to the outside world it needs to fit\nin a signed 32-bit variable (on Windows and 32-bit architectures)\nanyway. Also, this is 3.5 weeks and we should not knowingly set timeouts\nthat long anyway.\n\nThe previous cap introduced in 3089e7eec8b694ff was only partial.\n\nCloses #22579", "completion": "multi: cap expire times to INT_MAX internally"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nResolves some e2e failures that only happened on CI.\n\n(cherry picked from commit 262fba7f7d1ec4ec5aba5295cda8fdb0474d65a9)", "completion": "build: resolve CI failures"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nResolves some e2e failures that only happened on CI.", "completion": "build: resolve CI failures"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe option added by commit 28972b6fc was named \"restore_stats\", because\nit was calling pg_restore_relation_stats()/pg_restore_attribute_stats()\nin place of fetching a remote rowsample. However, those code paths have\nbeen replaced with calls to\nimport_relation_statistics()/import_attribute_statistics() (cf. commit\n54cd6fc83), so the option is now slightly misnamed.\n\nSwitch the option to \"import_stats\", which more closely reflects both\nthe functions being called internally, and the user's perception of what\nthe operation is doing.\n\nBack-patch to v19 where commit 28972b6fc went in.\n\nSuggested-by: Etsuro Fujita \nAuthor: Corey Huinker \nDiscussion: https://postgr.es/m/CADkLM%3DezuspTk3VD-2EM6XtFP-Dfz7cJKtnbn0cB6gocsAgu1g%40mail.gmail.com\nBackpatch-through: 19", "completion": "postgres_fdw: Rename option \"restore_stats\" to \"import_stats\"."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIn GitHub runner image windows-2025-vs2026 v20260810.198.2, the default\nPerl binary changed from MSYS2 to Strawberry. The reason is that the MSYS2\ninstallation not longer has Perl preinstalled.\n\nAs seen in CMake configuration:\n```diff\n- -- Found Perl: C:/a/_temp/msys64/usr/bin/perl.exe (found version \"5.42.2\")\n+ -- Found Perl: C:/Strawberry/perl/bin/perl.exe (found version \"5.42.0\")\n```\n\ncurl's Perl scripts require an MSYS2 Perl. Fix by installing it manually\nin this one job.\n\nSymptom was `gencert.pl` no longer finding openssl.exe:\n```\nMissing or broken 'openssl' tool. openssl 1.0.2+ is required.\n```\nThen the script hanging while trying to trace it.\n\nAlso:\n- add distinct error message and list PATH elements if openssl is not\n found via `gencert.pl`.\n- tried falling back to Git for Windows Perl, which caused the test step\n to either hang or run too slowly to fit the time slot.\n\nRefs:\nhttps://github.com/actions/runner-images/pull/14541\nhttps://github.com/actions/runner-images/releases/tag/win25-vs2026%2F20260810.198\n\nBug: https://github.com/curl/curl/pull/22577#issuecomment-5286533641\nBug: https://github.com/curl/curl/pull/22577#issuecomment-5291468024\n\nCloses #22580", "completion": "GHA/windows: install MSYS2 Perl manually on Windows 2025 runner"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(FloatButton): keep BackTop progress ring visible\n\n* chore: retry CI", "completion": "fix(FloatButton): keep BackTop progress ring visible"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nDELETE FOR PORTION OF inserts temporal leftovers through ExecInsert(),\nbut the rewriter only attached view WCOs for INSERT/UPDATE. Leftover\nrows could therefore silently escape a WITH CHECK OPTION view, while\nthe equivalent UPDATE correctly raised an error.\n\nThis commit fixes it by attaching the WCOs for FOR PORTION OF deletes\ntoo.\n\nAuthor: Zsolt Parragi \nCo-authored-by: Paul A Jungwirth \nReviewed-by: solai v \nReviewed-by: Dean Rasheed \nDiscussion: https://www.postgresql.org/message-id/flat/CAN4CZFOuTyhGspG0Nyits8PiK2keoNXkLj-u3APzc66aRcWY9A%40mail.gmail.com", "completion": "Enforce WITH CHECK OPTION on DELETE FOR PORTION OF leftovers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTriggers the fuzzers\n\nCloses #22582", "completion": "multi: drop the assert from large expires"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nstruct SingleRequest tweaks\n\n- 'upgr101' from enum upgrade101 => 'unsigned char', saves three bytes\n- made some 'unsigned char' => uint8_t\n- moved 'io_flags' to fill a hole on 64-bit arch\n\nstruct UserDefined tweaks\n\n- Sort the fields by size. Larger to smaller. Helps avoding holes.\n- httpsig_algorithm moved\n- FTP uint8_t fields moved\n- new_file_perms moved\n- rtspreq moved\n- sort fields on size\n\n- urldata: drop 'struct Curl_data_priority'\n\n It only had a single struct member 'weight'. Use that directly instead\n to save indirections and struct alignments. Move field for size order.\n\n- urldata: move the RTSP fields in the UrlState struct to be ordered by\n size\n\nstruct PureInfo tweaks\n\n- make 'pxcode' a uint8_t\n- move 'conn_protocol' to fill a hole\n- sort 'struct PureInfo' fields by size\n\nCloses #22585", "completion": "lib: optimize struct layouts for reduced memory usage"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nIn case of a very long path pattern with each element pattern being\nresolved to many graph elements\ngenerate_queries_for_path_pattern_recurse() may take very long time to\ngenerate all the possible graph paths. Make\ngenerate_queries_for_path_pattern_recurse() interruptible so that a\nuser may be able to cancel such a query if required and the interrupts\nare processed in timely manner.\n\nAuthor: Satyanarayana Narlapuram \nReviewed-by: Ashutosh Bapat \nDiscussion: https://www.postgresql.org/message-id/flat/CAHg%2BQDfDwcM4%3DDSiAV6Ly89YQ5EcMhzO1-9x%3DmGG1WJzODcAig%40mail.gmail.com", "completion": "Make generate_queries_for_path_pattern_recurse() interruptible"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- Move expire timeout code from multi into splay.c\n- keep a \"time_base\" timestamp to calculate timediff_t for\n actual timeout values. Unfortunately this means our\n timeouts will go wrong after ~500,000 years of continuous\n operations...\n- use timediff_t as key in splay instead of curltime\n- use timediff_t in transfers expire times instead of curltime\n- re-comment splay.c for better understanding how it works\n- replace splay nodes double-linked \"same\" list with a single link,\n we almost never have duplicate keys\n- keep transfer `mid` in splay nodes instead of the transfer pointer\n- keep registered bit in splay node for tracking instead of separate\n bit in transfer\n- adapt unit1309.c to changes in timediff_t and mid\n\nCloses #22584", "completion": "multi: timeout improvements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Value transformation\" section taught readers to hand-roll\ntransformation with `linkedSignal()` and a manual parse method, even\nthough `@angular/forms/signals` ships `transformedValue()` for exactly\nthis case. Readers ended up with a weaker version of a feature the\nframework already provides — notably, no parse error reporting.\n\nRewrite the section around `transformedValue()` and document the parts\nthe manual pattern could not cover: returning `{error}` from `parse` to\nsurface parse errors on the field's `errors()`, and `reset()` clearing\nthem. This also makes good on the cross-reference from the validation\nguide, which pointed here for parse error details the section never\ncovered.\n\nFixes #70206\n\nCo-authored-by: Matthieu Riegler \n(cherry picked from commit 182c371d829375ac51d0b3f390c7da9c3c17e580)", "completion": "docs: use `transformedValue` in `Forms | Custom Controls | Value transformation` section"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe \"Value transformation\" section taught readers to hand-roll\ntransformation with `linkedSignal()` and a manual parse method, even\nthough `@angular/forms/signals` ships `transformedValue()` for exactly\nthis case. Readers ended up with a weaker version of a feature the\nframework already provides — notably, no parse error reporting.\n\nRewrite the section around `transformedValue()` and document the parts\nthe manual pattern could not cover: returning `{error}` from `parse` to\nsurface parse errors on the field's `errors()`, and `reset()` clearing\nthem. This also makes good on the cross-reference from the validation\nguide, which pointed here for parse error details the section never\ncovered.\n\nFixes #70206", "completion": "docs: use `transformedValue` in `Forms | Custom Controls | Value transformation` section"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Jakub Zelenka \nReviewed-by: Milan Broz \nMerge-date: Tue Sep 15 15:00:02 2026\nMerged-from: https://github.com/openssl/openssl/pull/32342", "completion": "Update corpora submodule"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBase on the idea of @Rydier.\n\nFixes #32179\n\nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 11:03:50 2026\nMerged-from: https://github.com/openssl/openssl/pull/32382", "completion": "Bugfix in the file BIO - avoiding false negatives based on previous errno."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBase on the idea of @Rydier.\n\nFixes #32179\n\nReviewed-by: Richard Levitte \nReviewed-by: Tomas Mraz \nMerge-date: Wed Aug 19 11:03:35 2026\nMerged-from: https://github.com/openssl/openssl/pull/32382", "completion": "Bugfix in the file BIO - avoiding false negatives based on previous errno."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThere is no unified notion of a \"user action\".\n\nVim processes input by one-char-at-a-time, and mostly throws away any\nhints it might gather about the user's action, with one exception: it\nstores the last _edit_ action (the \"redo buffer\", encoded as\nunstructured `[\"x][v][count]body` bytes).\n\nPlugins can only observe individual keys (vim.on_key) and high-level\neffects (TextChanged, CursorMoved).\n\nSolution:\n- Users can subscribe to `CmdAtom` events to handle any user action.\n - Event is deferred; handlers cannot cancel or interfere with user\n actions.\n- Capture `CmdSpec` from the normal/insert/visual subsystems.\n - typeahead/readahead stay unstructured (`buffheader_T`): they are key\n streams, not commands.\n - the redo/record buffers become `StringBuilder`: fewer\n allocations/copies.\n- Repurpose the input/redo engine to accept `CmdSpec` objects.\n\n\"atom\": one repeatable unit of user input, as a resolved (post-mapping)\nkeysequence plus structured fields. Only user actions, not `:normal`,\nAPI calls, or non-\"t\" `feedkeys`.\n\nBREAKING: dot-repeat of an Insert session, replays the entire session\nincluding cursor-moves (:help ins-repeat).\n\nBREAKING: dot-repeat of a Visual operation, replays the selection\ninstead of operating on a fixed-size region.", "completion": "feat(input)!: CmdAtom event #41297"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe fuzz_tests_mfail job ran malloc-failure injection over the full corpora.\nThe full run takes minutes, and with a bigger corpus, tens of minutes.\n\nCI should only confirm that the fuzzers still build and process inputs with mfail.\nReduce the run to just a few samples, which is enough to let the test run.\n\nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Jakub Zelenka \nReviewed-by: Richard Levitte \nReviewed-by: Neil Horman \nMerge-date: Tue Aug 18 12:17:34 2026\nMerged-from: https://github.com/openssl/openssl/pull/32384", "completion": "ci: Reduce mfail fuzz test to only few corpus samples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update dependency ng-packagr to v22.2.0-next.3"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhen SendQuery() is not told how many COPY FROM STDIN commands the\nquery string contains (as for -c, \\gexec, and \\watch), it scans the\nstring to count them itself. But it called psql_scan() only once,\nwhich stops at the first semicolon, so any COPY FROM STDIN past the\nfirst sub-command was not counted, causing failure of cases that used\nto work. Oversight in commit 3045a25ba.\n\nAuthor: Zsolt Parragi \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/CAN4CZFPqa6c+u4uX5jJ8LANHTQ4dxM3m4_8G9WmX_A4-2wuv2A@mail.gmail.com\nBackpatch-through: 14", "completion": "psql: count every COPY FROM STDIN when scanning a query string."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nDirectory listing entries cannot be customized (filtered, reordered).\nListings are read by a BufReadCmd, which suppresses BufReadPost, so they\nare the only buffers with no post-read event to hook.\n\nSolution:\nIntroduce a post-render User autocmd `DirReadPost`, marking the dir\nbuffer writable for the duration and before the cursor is placed, so\nhandlers can sort or filter it with ordinary commands. Document common\nrecipes", "completion": "feat(dir): user can sort/filter listings, DirReadPost event #41138"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPQfn() has been documented as somewhat obsolete since commit\nefc3a25bb0 (2003), and commit bd48114937 recently marked it unsafe\nbecause it may write past the end of result_buf when result_is_int\nis 0. Furthermore, searches of publicly available code turned up\nno callers, only language bindings that expose the function\nwithout using it, so removing it seems unlikely to cause too much\ntrouble.\n\nSince the symbol is exported, deleting it outright isn't an option,\nso instead this commit teaches PQfn() to fail unconditionally with\nan error that suggests alternatives. The documentation for the\nfast-path interface is replaced with a stub in the \"Obsolete or\nRenamed Features\" appendix. The server's fast-path support is\nretained for the benefit of older clients and the frontend large\nobject interface.\n\nThe frontend large object interface, the only in-tree caller, now\nuses PQnfn(), the private version of PQfn() added by commit\nbd48114937. I considered converting this code away from the\nfast-path protocol entirely, but prepared statements can be\ndeallocated out from under libpq (e.g., by DISCARD ALL), and\nPQexecParams() proved noticeably slower, so that is left as a\nfuture exercise.\n\nReviewed-by: Christoph Berg \nReviewed-by: Jacob Champion \nReviewed-by: Dagfinn Ilmari Mannsåker \nDiscussion: https://postgr.es/m/ahXE28klgxIJXBLq%40nathan", "completion": "Retire PQfn()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nSince #9285 this indirection is no longer really needed and perhaps\nit is time to mop up the internal uses of ASN1_ITEM_rptr(). I just\nwanted to point out that these are inconsistent with all the other\nuses of ASN.1 items, of which there are tons.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Nikola Pajkovsky \nMerge-date: Tue Aug 18 07:16:16 2026\nMerged-from: https://github.com/openssl/openssl/pull/32388", "completion": "Consistently use ASN1_ITEM_rptr() for ASN1_ITEMs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCancel the unread response body before reporting NG02825 when its declared Content-Length exceeds the configured buffer limit. Without cancellation, SSR can finish while the underlying connection remains open.\n\nAdd regression coverage for the declared-length rejection path.\n\n(cherry picked from commit 1a006a8f9794240a950c388387bd8b9a671801da)", "completion": "fix(http): cancel oversized fetch response bodies"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nCancel the unread response body before reporting NG02825 when its declared Content-Length exceeds the configured buffer limit. Without cancellation, SSR can finish while the underlying connection remains open.\n\nAdd regression coverage for the declared-length rejection path.", "completion": "fix(http): cancel oversized fetch response bodies"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIntroduces support for route-level resources via the `resources` property on route definitions, enabled with `withRouterResources()`.\n\nRouter resources provide a reactive, signal-based alternative to resolvers, allowing routes to declare resources tied to route parameters and route lifecycle:\n- The `resources` function executes during navigation transitions within an injection context scoped to the route (`_localInjector`).\n- It receives a `ResourceContext` containing signals for `params`, `queryParams`, `fragment`, and `data`, alongside the static `snapshot`.\n- For newly created routes, `resources` runs once and attaches to `ActivatedRoute.resources`. For reused routes, parameter signals update reactively to trigger new data fetches while keeping resource references stable.\n- Wrapped resources (`routerResource`) provide transactional stability: snapshots are frozen during active navigations to prevent UI jitter, unfreezing on `NavigationEnd`.\n- On cancelled navigations or errors, rollback recovery retains the frozen snapshot until reverted signals settle, avoiding flashes of loading state. Manual reloads are rejected while frozen.\n- Local injectors are automatically cleaned up if navigations are cancelled or rolled back.\n\nNote that this commit only implements non-blocking resources (marked with `nonBlocking()`), deferring blocking resource resolution to future work to keep the initial changeset smaller and less complex.\n\nPR Close #70211", "completion": "refactor(router): add support for non-blocking router resources"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAllow `@Component.deferredImports` to be an object mapping block names to arrays of dependencies, and support `@defer (name blockName)` syntax to configure block-specific dependency lists in both standard and local compilation modes.\n\nThis enables more targeted dependency chunk generation during local compilation instead of over-eagerly loading all deferred imports together.", "completion": "refactor(compiler): support block-specific deferredImports mapping"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nEnforces that components, directives, and pipes in @Component.deferredImports mapped to specific block keys are only used within their designated @defer blocks during template type checking, reporting out-of-band diagnostics when used eagerly or across mismatched blocks.", "completion": "feat(compiler-cli): scope type-checking of keyed defer blocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nOversight in commit ffca23839c.\n\nReported-by: Anton Voloshin \nAuthor: Anton Voloshin \nBackpatch-through: 14", "completion": "Add missing PGDLLIMPORT marker."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAnd remove the support for the padding extension (RFC7685).\n\nWith this change our client will cease sending the padding extension.\nIt was only ever sent, via SSL_OP_TLSEXT_PADDING, to work around a\nvery old bug in F5 middleboxes that choked on ClientHellos between 256\nand 511 bytes.\n\nThe fix shipped long ago from F5, and the affected hardware is long out of\nsupport, so nothing should still be running the problematic version.\n\nSSL_OP_TLSEXT_PADDING is now a no-op retained for compatibility and\nis no longer part of SSL_OP_ALL.\n\nIn case anyone wants to actually still use the padding extension\nfor some reason, as we no longer have a handler for this extension,\nthey can register a custom extension handler to do whatever they like\nwith it.\n\nReviewed-by: Viktor Dukhovni \nReviewed-by: Nikola Pajkovsky \nMerge-date: Tue Aug 18 08:39:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32389", "completion": "Remove the F5 ClientHello-padding workaround"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 13b935cd changed hash_get_num_entries to return int64 instead\nof long. This fixes a few more users of hash_get_num_entries which\nwere missed in the original commit.\n\nPGSS_FILE_HEADER is left unchanged since this only affects as of yet\nunreleased versions of PostgreSQL. Backpatch to v19 where the int64\nchange was performed.\n\nAuthor: Karina Litskevich \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CACiT8iYTkc33YWaA2D3t51Y5s=GqBO7T1zX7bkpSmet2njcLLw@mail.gmail.com\nBackpatch-through: 19", "completion": "Use int64 for number of entries in pg_stat_statements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPGSS_PG_MAJOR_VERSION is written as an uint32 field, but was read back\ninto an int32. Fix to make sure reading and writing use the same data\ntype.\n\nAuthor: Karina Litskevich \nDiscussion: https://postgr.es/m/CACiT8iYTkc33YWaA2D3t51Y5s=GqBO7T1zX7bkpSmet2njcLLw@mail.gmail.com", "completion": "Use correct data type for version identifier"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPresently, the documentation for logging_collector says that the\ncollector \"is designed to never lose messages,\" which reads as a\nstronger promise than we actually make. The collector does not\nfsync the log file or retry failed writes, so log messages can go\nmissing after an operating system crash, power loss, or a write\nerror. Reword that sentence and add a note about what is not\nguaranteed.\n\nAuthor: Daniel Bauman \nReviewed-by: Fujii Masao \nReviewed-by: Zhenwei Shang \nReviewed-by: Robert Treat \nDiscussion: https://postgr.es/m/CAMtj0_a86DdDKkW-ReVpQpqjndVS6GMrwXVpQY4G3-SGY7saMQ%40mail.gmail.com\nBackpatch-through: 14", "completion": "doc: Clarify the logging collector's guarantees."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIn `@for` blocks, tracking callable objects by reference (e.g. signal forms `FieldTree`, signals, or custom callable objects) is a valid pattern when tracking by object identity. Previously, `UninvokedTrackFunctionCheck` (NG8115) flagged any property read whose type has call signatures, regardless of whether the target was an actual track function expecting arguments or a method reference.\n\nThis commit updates `UninvokedTrackFunctionCheck` to only emit a diagnostic when the target expression has call signatures that declare parameters (functions/methods expecting arguments like `(item)` or `(index, item)`) or is a method declaration. Callable objects without parameters accessed as properties are now recognized as tracked values and not flagged as uninvoked track functions.\n\nFixes #70207\n\n(cherry picked from commit f0a271c7bd4be000c52592034573cda9866f26bb)", "completion": "fix(compiler-cli): do not flag callable objects with zero parameters in uninvoked track function check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nIn `@for` blocks, tracking callable objects by reference (e.g. signal forms `FieldTree`, signals, or custom callable objects) is a valid pattern when tracking by object identity. Previously, `UninvokedTrackFunctionCheck` (NG8115) flagged any property read whose type has call signatures, regardless of whether the target was an actual track function expecting arguments or a method reference.\n\nThis commit updates `UninvokedTrackFunctionCheck` to only emit a diagnostic when the target expression has call signatures that declare parameters (functions/methods expecting arguments like `(item)` or `(index, item)`) or is a method declaration. Callable objects without parameters accessed as properties are now recognized as tracked values and not flagged as uninvoked track functions.\n\nFixes #70207", "completion": "fix(compiler-cli): do not flag callable objects with zero parameters in uninvoked track function check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim's TerminalWinOpen seems to be required because of Vim\nbuffer-job-popupwin implementation.\nBased on the patch, I'm puzzled why fzf needs this on Vim.\n\nNvim's TermOpen, TermEnter, and detection mechanisms to know\nif buffer is on a (active,visible) window should suffice to not port it.\n\nIf there was a feature request or issue without a merged fix,\nthen I can't find it.\n\nhttps://github.com/junegunn/fzf/pull/2000", "completion": "build(vim-patch): v8.1.2219 is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nClose #15303", "completion": "fix(runtime-vapor): preserve nested vdom slot content"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(ColorPicker): keep color selection draggable after clearing\n\n* Remove test for clear button text selection\n\nRemoved test for preventing text selection from the clear button.\n\nSigned-off-by: 多格 <40968928+dogledogle@users.noreply.github.com>\n\n---------", "completion": "fix(ColorPicker): keep color selection draggable after clearing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(locale): validate Form message placeholders\n\nCorrect invalid min tokens in the Icelandic and Mongolian validation messages and add a cross-locale guard for missing or renamed Form placeholders.\n\nAI-assisted: Codex\nSigned-off-by: 陳廷安 <73953029+nrps9909@users.noreply.github.com>\n\n* test(locale): keep placeholder fix focused\n\nRemove the generalized cross-locale placeholder guard in response to maintainer feedback, leaving the PR scoped to the two invalid Form placeholder corrections.\n\nAI-assisted: Codex\nSigned-off-by: 陳廷安 <73953029+nrps9909@users.noreply.github.com>\n\n---------", "completion": "fix(locale): correct Form min placeholders"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n`opendir()` was used previously with mingw-w64 for `file://` directory\nlisting support. This was replaced by a native Win32 solution on all\nWindows platforms, leaving `opendir()` no longer used. Drop related\nfeature detections.\n\nFollow-up to c7c42afab91c46e6baaa0e2801626e13acd6c30a #22577\n\nCloses #22588", "completion": "build: drop `dirent.h` and `opendir()` detections on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* chore: bump select/tree-select/cascader\n\n* fix: update snapshot\n\n* size-limit", "completion": "fix: option position announcement for virtual mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCI jobs rely on defaults, sometimes to reduce log noise (possibly\nimprove performance a bit) or simplify, sometimes by accident. List them\nto help debug or optimize on changes.\n\nRefs:\nhttps://github.com/actions/runner-images/issues/14562#issuecomment-5301777198\nhttps://github.com/msys2/MSYS2-packages/commit/636489312cbc55011cb7ec493550598125e7716f\nhttps://github.com/msys2/MSYS2-packages/pull/6491\nhttps://github.com/msys2/MSYS2-packages/pull/6479\n\nFollow-up to d854ab4673c2f9d8048c7f0f6d164b7e4d5e0865 #22580\nFollow-up to c349bd668c91f2484ae21c0f361ddf497143093c #14097\n\nCloses #22589", "completion": "GHA/windows: log preinstalled MSYS2 packages"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nNew riscv64 job takes 4.5 minutes.\n\nAlso:\n- use prefill on riscv64 to save 2 minutes configure time.\n- disable manuals/perl on riscv64 to save ~1 minute (install, build).\n- cmake: fix `HAVE_GETHOSTBYNAME_R_6` prefill for FreeBSD.\n\nRef: https://github.com/cross-platform-actions/action/releases/tag/v1.4.0\n\nCloses #22590", "completion": "GHA/non-native: bump cross-build-actions, NetBSD 11.0, FreeBSD riscv64"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdd the ability to automatically destroy created highlights by a provided TTL;\nAdd the option for outline style of the highlight overlays;\nAdd `prefer-inset` label position;\n\nPR Close #70254", "completion": "refactor(devtools): add TTL and outline style to the highlighting mechanism"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe enum `exire_id` fits easily into a uint8_t. Use that type for\nstoring expire timeout list indices.\n\nCloses #22591", "completion": "multi: shrink expire timer indices"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSimple EXISTS subplans can be converted to hashed ANY subplans as\nan alternative implementation. Previously, both the original EXISTS\nsubplan and the converted ANY subplan used names with the\nexists_ prefix, making EXPLAIN output harder to read and\npg_plan_advice targets less clear.\n\nUse the exists_to_any_ prefix for converted ANY subplans so that\ntheir names distinguish them from the original EXISTS alternative.\nThis only changes the names shown by EXPLAIN and used by plan advice;\nit does not affect planner behavior.\n\nAuthor: Yugo Nagata \nReviewed-by: Tom Lane \nReviewed-by: solai v \nReviewed-by: Fujii Masao \nDiscussion: https://postgr.es/m/20260605165641.3950f99ace0aad8f807abe96@sraoss.co.jp\nBackpatch-through: 19", "completion": "Rename EXISTS-to-ANY converted subplan to exists_to_any"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nOnly collect connect/appconnect timer stats on the first socket.\n\nFixes #22587\nCloses #22592", "completion": "connect: only set connect timer on first socket"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSyncing with build systems, which already enforce this.\n\nCloses #22593", "completion": "curl_threads: always use native threads/mutex on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo remove a build difference between mingw-w64 and MSVC builds (where\nmingw-w64 has it, while MSVC does not). Also to simplify and save the\ncost of detection/verification in CI.\n\n`gettimeofday()` was used in `curl_threads.c` in codepath practically\nunreachable in Windows builds, and in `tool_writeout.c` that falls back\nto `time()` for targets without it.\n\nRef: #22593\n\nCloses #22594", "completion": "build: drop detecting `gettimeofday()` on Windows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\ngit \"-I\" regex seem to be \"extended\".\ngrep's default regex is \"basic\".\nFix regexps for switch/case \"runtime/doc/*.txt\"\nbased on the \"*.h\" switch/case.", "completion": "build(vim-patch): fix compiled,popup-window regexp for '|' #41326"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOCSP_check_validity() accepts GeneralizedTime forms that\nX509_cmp_time() cannot compare. The latter requires the canonical RFC\n5280 form and returns 0 for numeric UTC offsets and fractional seconds.\nThat error was treated as an in-range result, allowing OCSP freshness\nchecks to be bypassed.\n\nTreat errors from the initial thisUpdate and nextUpdate comparisons as\nfield errors. Run the optional maximum-age check only after the initial\nthisUpdate comparison succeeds, avoiding a duplicate field error.\n\nAdd regression coverage for offset and fractional forms, including the\nmaximum-age path.\n\nFixes #32377\n\nAssisted-by: Codex:gpt-5.6-sol\nSigned-off-by: Mounir IDRASSI \nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 15:15:28 2026\nMerged-from: https://github.com/openssl/openssl/pull/32396\n(cherry picked from commit 6ceaf1dfe6729853961c6f53e97e635e82da9168)", "completion": "ocsp: Reject update times X509_cmp_time() cannot compare"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOCSP_check_validity() accepts GeneralizedTime forms that\nX509_cmp_time() cannot compare. The latter requires the canonical RFC\n5280 form and returns 0 for numeric UTC offsets and fractional seconds.\nThat error was treated as an in-range result, allowing OCSP freshness\nchecks to be bypassed.\n\nTreat errors from the initial thisUpdate and nextUpdate comparisons as\nfield errors. Run the optional maximum-age check only after the initial\nthisUpdate comparison succeeds, avoiding a duplicate field error.\n\nAdd regression coverage for offset and fractional forms, including the\nmaximum-age path.\n\nFixes #32377\n\nAssisted-by: Codex:gpt-5.6-sol\nSigned-off-by: Mounir IDRASSI \nReviewed-by: Bob Beck \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 15:15:28 2026\nMerged-from: https://github.com/openssl/openssl/pull/32396", "completion": "ocsp: Reject update times X509_cmp_time() cannot compare"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nA mark created by `nvim_buf_set_extmark()` while an undo block is open\nnever comes back on redo.\n\nAnalysis:\nUndo deletes the text it covers and collapses the range; redo replays\nthe splices, which re-insert the text but cannot re-expand the mark.\n`extmark_set()` records a position only for a mark it moves, not for one\nit creates.\n\nSolution:\nRecord the created position for redo; undo leaves the mark to the splice\nreplay, since it did not exist before the edit. Each side of a paired\nmark gets its own entry. Redo also revives a mark that undo invalidated,\nelse its position returns but its highlight does not.", "completion": "fix(extmarks): redo of a mark created during an edit #41324"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPer buildfarm member koel.", "completion": "pgindent fix for commit 7b7c4a8dcc9"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThis is the only purpose it's maintained for.\n\nDrop mingw-w64 and other logic falling outside of VS2010-2013 needs.\n\nmingw-w64/MSVC platform differences keep being maintained/documented as\npart of the CMake pre-fill logic in `CMake/win32-cache.cmake`.\n\nFollow-up to ba8752e5566076acc8bdec7ae4ec78901f7050f4 #12224\n\nCloses #22595", "completion": "config-win32.h: limit use to MSVC IDE Project builds"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReplace the QUERY filter methods for connect and appconnect time with a\nnew control CF_CTRL_REPORT_STATS that is triggered when a connect ends\n(successful or not).\n\nFilters in the connection can then report their statistics. Socket and\nTLS filters do this only once. Subsequent CF_CTRL_REPORT_STATS will do\nnothing.\n\nThis prevents timers to be reported twice in STARTTLS scenarios.\n\nFixes #22587 (again)\nCloses #22596", "completion": "filter: change time reporting"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- config-*.h: 'handcrafted'\n- tool_operate: rename `CURL *` variable to `curl` to match rest\n of code.\n- urldata.h: drop redundant parentheses from macro values.\n- curlinfo, dnsd: omit unused main arguments.\n- easy: sync function name in error message with source code.\n- cmake: drop period from version requirement messages.\n- tests/server/util: link three signal-related articles.\n- inline comments, fix indent, newlines, clang-format.\n\nCloses #22774", "completion": "tidy-up: formatting, messages and comments"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAccording to the content of the latest downloadable builds available at\n(from 2022): https://www.riscos.info/packages/src/Network/, these builds\nused autotools, not the handcrafted header. Also the handcrafted header\ndid not see an update (that I could find) since\n0866c1b52dcff1f872860a42183397b4e8f6dedf (2002-04-08), other than\nsource-wide maintenance updates.\n\nCloses #22598", "completion": "config-riscos.h: delete handcrafted RISC OS config header, in favor of autotools"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nnvim_win_set_buf() on a non-current win, while the current win has\na win-local dir, changes the global CWD:\n\n :vsplit | lcd ..\n :call nvim_win_set_buf(other_win, buf)\n :wincmd l\n :verbose pwd\n [global] /parent \" expected: the initial cwd\n\nAnalysis:\n`globaldir` is where to return when no local dir applies; NULL means the\nprocess CWD is already there. Switching to a window with no local dir\nmakes update_cwd() chdir back to `globaldir` and clear it. kCtxKeepCwd\nrestores the process CWD but not that bookkeeping, so the restored\nwindow-local dir is mistaken for the global one.\n\nSolution:\nSave/restore `globaldir` with the CWD.", "completion": "fix(cwd): nvim_win_set_buf changes global CWD #41328"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nNo bug found in previous code, but it unnecessarily relied on grammar\nrules. Per complaint from Coverity.\n\nReported-by: Tom Lane \nDiscussion: https://postgr.es/m/1787286.1786328153@sss.pgh.pa.us\nBackpatch-through: 19", "completion": "Clarify logic in CreateSubscription()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSetting a :bcd buffer into another window, modifies the caller's CWD.\n\n local b = vim.api.nvim_create_buf(true, true)\n vim.api.nvim_buf_call(b, function() vim.cmd.bcd('..') end)\n vim.cmd('vsplit')\n vim.api.nvim_win_set_buf(vim.fn.win_getid(2), b)\n\n :echo haslocaldir(0) haslocaldir(-1,0) haslocaldir(-1,-1,0)\n 0 0 0\n :echo getcwd() ==# getcwd(-1,-1)\n 0\n\nAnalysis:\n`ctx_dirs_save` only saves CWD if it predicts the switch can change it.\nBut win_set_buf() replaces the target window's buffer *after* the\nswitch, which cannot be \"predicted\" from `ctx_dirs_save`.\n\nSolution:\nAlways snapshot whenever the switch enters another window.\nSkipping `os_dirname` was a micro-optimization.", "completion": "fix(cwd): nvim_win_set_buf of :bcd buf, changes caller CWD #41329"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nA named mark updated after a change is moved back (treated as the\noriginal mark) by undo:\n\n :1mark d\n :$\n dw\n :2mark d \" 'd is on line 2\n :undo \" 'd is back on line 1\n\nThe undo header snapshots `b_namedm` when the change is recorded, and\n`u_undoredo()` restores that snapshot indiscriminately.\n\nSolution:\nUpdate the pending header's snapshot when a mark is set explicitly.\nMarks that the change itself moved go through mark_adjust(), not\nsetmark_pos(), so those are still reverted.\n\nSimilar to 2546741d1b36 (for extmarks): an explicit set inside an undo\nblock is confused with an edit-driven adjustment. But the extmarks case\nis dealing with mid-edit moves, whereas named/regular marks only need\nthe stale snapshot dropped.", "completion": "fix(marks): undo reverts a mark set after the change #41330"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nStop auto-skipping tests on emulated CPUs, replace it with explicit\n`skipall` tags instead. To make it easier to enable tests on emulated\nCPUs and to align with rest of workflows.\n\nCloses #22599", "completion": "GHA/non-native: sync BSD test exclusion logic with rest of workflows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRef: https://www.stunnel.org/NEWS.html\n\nCloses #22600", "completion": "GHA/windows: bump stunnel to 5.80"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\n(cherry picked from commit 2edb1c000958952c87edda596ed9ed53628084ed)", "completion": "fix(lua): don't limit indexed vim.cmd positional argument count"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- show binary sizes and file types in 'curl -V' step, like rest of\n workflows.\n- make `build tests` step verbose.\n- disable typecheck on emulated CPUs.\n It results in 3-4x speed-up for riscv64, and ~2x for ARM64 when\n building tests (in particular the libtests binary.)\n Ref: 9e6f1c5efb7a70e1f33e467a738f3e3f652f3174 #19637\n- enable building tests in an ARM64 job.\n- move examples build test from ARM64 to riscv64 (to spread job times).\n\nCloses #22601", "completion": "GHA/non-native: BSD build improvements"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(Form): associate complex labels with controls\n\nDocument and test explicit htmlFor/id pairing when a layout-only Form.Item wraps a nested field.\n\nAI-assisted: Codex\nSigned-off-by: 陳廷安 <73953029+nrps9909@users.noreply.github.com>\n\n* test(form): refine complex control accessibility example\n\nUse valid JSX comments in the copyable documentation snippets and snapshot the labeled input in both test runners.\n\nAI-assisted: Codex\nSigned-off-by: 陳廷安 <73953029+nrps9909@users.noreply.github.com>\n\n---------", "completion": "docs: improve complex Form label association"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nFollow-up refactor patches, mixed with unrelated patches in the middle,\nis normal in vim-dev when the original patch is not fully tested\nacross all builds via CI or reviewed by others.\n\nUnless core maintainers push \"vim-patch:\" directly to master/main branch\nwithout running the full test-suite,\nthere is little reason to merge incomplete ports that will fail\non Nvim's CI or code review.\n\nRelevant changes in patches like v8.2.0514 are either ported\nor (will) become N/A.", "completion": "build(vim-patch): auto-n/a refactor patch like v8.2.0514"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOCSP_check_validity() already rejects an expired nextUpdate, but it\nreports the not yet valid reason. Raise OCSP_R_STATUS_EXPIRED instead.\n\nFixes #32399\n\nCLA: trivial\nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 10:50:59 2026\nMerged-from: https://github.com/openssl/openssl/pull/32400", "completion": "ocsp: Report expired nextUpdate with the correct reason"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOCSP_check_validity() already rejects an expired nextUpdate, but it\nreports the not yet valid reason. Raise OCSP_R_STATUS_EXPIRED instead.\n\nFixes #32399\n\nCLA: trivial\nReviewed-by: Tomas Mraz \nReviewed-by: Richard Levitte \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 10:50:46 2026\nMerged-from: https://github.com/openssl/openssl/pull/32400", "completion": "ocsp: Report expired nextUpdate with the correct reason"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: babel\nChanges:\n* Add AI policy\n\n* Update AGENTS.md\n\nCo-authored-by: Huáng Jùnliàng \n\n---------", "completion": "Add AI policy"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* fix: prevent unsafe `no-var` autofix with hoisted functions\n\n* apply suggestion\n\n* apply suggestion", "completion": "fix: prevent unsafe `no-var` autofix with hoisted functions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe were already reporting regular bindings but not 2way.\n\nfixes #70219\n\n(cherry picked from commit c819880b91bf5ff1c5aa71afd314ae7cae241065)", "completion": "fix(forms): report forbidden 2way bindings on when `FormField` is applied"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe were already reporting regular bindings but not 2way.\n\nfixes #70219", "completion": "fix(forms): report forbidden 2way bindings on when `FormField` is applied"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- CMake/win32-cache.cmake: sort and sync MSVC pre-fills with mingw-w64.\n\n- curl_sasl: use `uint32_t` for local `httpauth` value. To match struct.\n Follow-up to e3691612ea1acb28e77fee6b4b2b9da0ac2c8f8b #20209\n\n- libstests: move literal to the right-hand side of comparisons.\n\n- windows: drop `!= 0`/`== 0` from `WSAEventSelect()` result checks,\n to keep it short.\n\n- tool_cfgable: replace `CURL_GLOBAL_ALL` with `CURL_GLOBAL_DEFAULT` in\n debug builds to match the macro used in non-debug and libcurl init.\n (Both macros map to the same literal value; there is no code change.)\n\n- perf/urlparser: use double-const in test array.\n\n- examples: `CURL_GLOBAL_DEFAULT` -> `CURL_GLOBAL_ALL` to match rest of\n examples.\n\n- libtests: `CURL_GLOBAL_DEFAULT` -> `CURL_GLOBAL_ALL` to match rest of\n tests.\n\nCloses #22783", "completion": "tidy-up: misc C and CMake nits"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to bf594226d66dc2bbf62a18f3dea1ceabe5b26dcf #22601", "completion": "GHA/non-native: drop leftover perl5 install from riscv64 job [ci skip]"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo make it easier to customize tests for individual matrix jobs.\n\nAlso:\n- tested running riscv64 tests, but it takes too long (8.5-12 minutes,\n for ~1000 HTTP tests.)\n\nFollow-up to bf594226d66dc2bbf62a18f3dea1ceabe5b26dcf #22601\n\nCloses #22602", "completion": "GHA/non-native: sync BSD tflags logic with other workflows"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nUndo of a change spanning many paired marks is quadratic. A node's\n\"intersect\" array holds every pair crossing that node, and both\nintersect_node() and unintersect_node() walked it linearly. Undoing an\nedit over 1M paired marks spends 68% of its time in unintersect_node()'s\nscan alone.\n\nSolution:\nThe array is sorted, so binary search it.\n\n marks undo before after\n 200k 831ms 385ms\n 1M 14006ms 3820ms\n\nRedo is unaffected: it is dominated by marktree_move() actually\nrepositioning the marks.", "completion": "perf(marktree): binary search the node intersect array #41331"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: nestjs\nChanges:\nThe truthiness guard in reply() is there to skip the status call when no status is\npassed, but it also drops codes that were provided and happen to be falsy. NaN and 0\nnever reach response.status(), so the status set before the handler ran survives and\nthe exception goes out with a 200. Truthy invalid codes such as -1 or 99 already end\nup as a 500, because express and fastify reject them.\n\nSkip the call only when no status is given, so a provided code always reaches the\nframework that can validate it.", "completion": "fix(express,fastify): apply falsy status codes in reply()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`:rundo` on a corrupted undo file crashes or hangs, instead of failing\nwith E825. Patching one 4-byte field is enough:\n\n ue_size = 0xFFFFFFFF \" walks a NULL ue_array\n ue_size = 0x7FFFFFF0 \" 17 GB xmalloc + memset, then preserve_exit()\n ue_top = 0xFFFFFFFB \" negative lnum reaches ml_delete()\n\nAnalysis:\nEvery count in the file is read with `undo_read_4c()` and then checked,\ndifferently at each site. None bounds the value by what the file can\nhold, so a 2 GB count reaches `xmalloc()`.\n\nNote:\n- Vim doesn't have `bi_fsize` because it checks `U_ALLOC_LINE` result\n everywhere (thus doesn't crash, but may thrash...); those checks were\n dropped when Nvim moved to `xmalloc()`, and the `ue_size` loop counter\n became unsigned.\n- Vim *does* have the negative line numbers bug: `u_undoredo()` checks\n `top > ml_line_count || top >= bot || bot > ml_line_count + 1`, which\n rejects none of them.\n\nSolution:\n- Introduce `undo_read_len()` and use it to fail early instead of\n continuing with nonsense.\n- Validate `ue_top`/`ue_bot`/ `ue_lcount`.\n- Use `xcalloc()`, so no site can proceed with a NULL array.\n- Report a truncated \"U\" line, distinguish EOF from a 0xFFFFFFFF field,\n and free the header on the extmark error path.", "completion": "fix(undo): crash on corrupted undo file #41339"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nOn :restart, the new Nvim may \"inherit\" a local dir as its global CWD.\n\nSolution:\nInherit the global CWD explicitly.", "completion": "fix(restart): preserve global cwd on :restart #41304"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe genec test tested 912 curves with a spawn and teardown of an\nrun of the app each - this takes a long time, and is largely\nbound on how fast you can start up and tear down the app.\n\nInstead, let's test all the curves in a C program doing the same\nthing, which takes almost no time at all, and test the representative\nparameters in the app to ensure they also get test coverage. Doing\nthose same parameters 912 times in the app to make sure they function\n912 times buys us nothing for testing the app. So this will give\nus coverage while making the test run faster, and being less\ntrouble for OS zoo to run testing fork exec teardown instead\nof what we want to test.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:15 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Make the genec test not test process fork and teardown."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nCoverity can't follow kv_ensure_space()'s `kv_roundup32()` bit math, so\nevery kv_concat_len() looks like an overrun; and it doesn't know\n`kv_push()` allocates when `size == capacity`.\n\n _____________________________________________________________________________________________\n CID 653191: Memory - illegal accesses (OVERRUN)\n /src/nvim/input.c: 3536 in paste_store()\n 3530\n 3531 if (s > start) {\n 3532 if (need_redo) {\n 3533 kv_concat_len(redobuff.cur.keys, start, (size_t)(s - start));\n 3534 }\n 3535 if (need_record) {\n >>> CID 653191: Memory - illegal accesses (OVERRUN)\n >>> Overrunning dynamic array \"recordbuff.items\" at offset corresponding to index variable \"recordbuff.size\" through dereference in call to \"memcpy\".\n 3536 kv_concat_len(recordbuff, start, (size_t)(s - start));\n 3537 }\n 3538 }\n 3539\n 3540 if (s < str_end) {\n 3541 int c = (uint8_t)(*s++);\n\n _____________________________________________________________________________________________\n CID 653190: Memory - illegal accesses (OVERRUN)\n /src/nvim/input.c: 730 in redo_append_spec()\n 724 return;\n 725 }\n 726\n 727 while (*s != NUL) {\n 728 if ((uint8_t)(*s) == K_SPECIAL && s[1] != NUL && s[2] != NUL) {\n 729 // Insert special key literally.\n >>> CID 653190: Memory - illegal accesses (OVERRUN)\n >>> Overrunning dynamic array \"redobuff.cur.keys.items\" at offset corresponding to index variable \"redobuff.cur.keys.size\" through dereference in call to \"memcpy\".\n 730 kv_concat_len(redobuff.cur.keys, s, 3);\n 731 s += 3;\n 732 } else {\n 733 sb_add_char(&redobuff.cur.keys, mb_cptr2char_adv(&s));\n 734 }\n 735 }\n\n CID 653189: (OVERRUN)\n /src/nvim/input.", "completion": "fix(coverity): false positives in kvec usages #41341"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA single TEST_info() message is composed of several writes, each\ntaking the output lock independently, so concurrent callers\ninterleaved mid-line. This makes it annoying when we run multiple\nthreads in a test job and get interleaved output that is hard to\ndiagnose.\n\nTrack the lock depth per thread so it can be held across a whole\nrecord. A thread with no thread-local data cannot track the depth and\nfalls back to the previous per-write locking.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:16 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Make test framework output records atomic across threads"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`vim.fs.slug()` does not handle URIs like `term://foo//123:bash`,\nso callers (e.g. terminal persistence) must strip the scheme before\ncalling `slug()`.\n\nSolution:\nDetect `scheme://` from the raw input before `normalize()` and\nreplace it with a `=uri--` prefix.", "completion": "feat(vim.fs): slug() supports URI #41241"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe iteration and worker counts were not derived from what the test has\nto cover. What matters is each ordered pair of behaviours being\nexercised concurrently on the same key, and the chance of missing one\nfalls off exponentially with the iteration count, so 150000 iterations\ncovers that with a wide margin. The derivation is documented at the\nconstant.\n\nCap the workers at four rather than taking a quarter of HARNESS_JOBS.\nFour is enough to interleave more than a pair of threads on a key, which\ntwo cannot do, without tying up a machine.\n\n02-test_lhash was the longest recipe in the suite and set the floor for\nthe whole run. On a MacBook Pro with HARNESS_JOBS=14 it goes from 111\nseconds to 5.4 seconds.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Size the multithreaded lhash test to the coverage it needs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe roadmap header draws a road between a start pin and a destination\npin, but nothing travels it. Angie already appears on the 404 page, the\nembedded editor states and the error snack bar, so put her on the road\ntoo.\n\nDecorative headers are inlined into the page so the road can use CSS\nvariables for dark mode, which means the pose has to be embedded as\npaths, with its classes flattened and its ids prefixed to keep them out\nof document scope.\n\nNote this asset is also the essentials Next Steps header.", "completion": "feat(docs-infra): add Angie to the roadmap illustration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nSome names/comments are misleading.\nAlso add some asserts.", "completion": "refactor(cmdatom): atom_redo_keys #41345"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nThe cookie change from 51beed175dbfc37da (skipped the test part)", "completion": "CVE-2026-8924: trailing dot domain super cookie"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked 5c225384b8d52c6, except the test parts", "completion": "CVE-2026-8927: env-set cross-proxy Digest auth state leak"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from 88c7e16cceec (except the test changes)", "completion": "CVE-2026-9079: stale proxy password leak"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nUnify error handling in OSSL_STORE_attach with OSSL_STORE_open_ex.\n\nIf setting loader params fails loader_ctx is closed but not set to NULL.\nWhich leads to successful return with invalid object.\nFixed by setting loader_ctx to NULL triggering error return path.\n\nIf allocation OSSL_STORE_CTX fails after the loader context creation\nclose the loader context and release the fetched loader.\nThis covers both OSSL_STORE_CTX allocation failure and UI method setup failure.\n\nFound by : store fuzzer (MFAIL-test)\n\nAssisted-by: ChatGPT:gpt-5.6\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Neil Horman \nMergeDate: Tue Sep 15 14:20:01 2026\n(Merged from https://github.com/openssl/openssl/pull/32413)", "completion": "Fix bugs in OSSL_STORE_attach"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA defect either shows on a large fraction of random inputs or is not\nreachable by sampling in one run at all. Twenty rounds per factor size\ncovers the former.\n\nDrive the sizes from a table rather than a ladder of index ranges, which\nalso makes the bands equal.\n\nOn a MacBook Pro the exptest binary goes from 24.1 to 5.3 seconds.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:18 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Size test_mod_exp_x2 to the coverage it needs"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nChecking 136 parameter files with ecparam and pkeyparam cost a process\nper file per check, 641 in all, which is process startup rather than\ncoverage. Test all of these in one process per set in C instead.\n\nThe app keeps it's own test, covering the options and a few\nfiles through the output path, in 20-test_app_ecparam.t.\n\nTogether the two now take 1.0 seconds where the one took 24.5.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:19 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Stop running the entire ecparam corpus through the app"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`` mappings do not emit `CmdAtom.text`.\n`` and Lua-callback mappings that edit the buffer apply only at the\nprimary cursor, not cascaded (multicursor).\n\nSolution:\nCapture the `` command in getcmdkeycmd().\nAdd kKeyOpaque (\"no capturable keys\"); narrow kKeySynthetic (\"not\na keystroke\") to K_EVENT/K_IGNORE, so an opaque mapping's edit still\nsets `map_edit` and cascades via LHS-replay.", "completion": "fix(cmdatom): mappings #41347"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOSSL_sleep() takes milliseconds, so the contention == 0 path slept a\nsecond between writes and the low contention tests managed six writes\neach in their four second budget. The readers spun tens of millions of\ntimes over a value that was not changing.\n\nSleep a millisecond instead. In the same four seconds torture_rw_low\ngoes from 6 writes to 4940, and torture_rcu_low from 6 to 6344.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:19 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Make the low contention torture writers write"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe five torture tests ran their writers for four seconds each, so the\nwork done varied with the machine while the cost did not: this one\nperforms 8.8 million writes in torture_rcu_high where a loaded VM might\nmanage a hundredth of that, and both spend the same twenty seconds.\n\nGive the writers a number of writes to perform instead, so the sampling\nis the same everywhere and the time falls out of it. The elapsed time\ncheck stays as a backstop, so a machine too slow to reach the target\nstops where it stopped before and nothing gets slower than it was.\n\nOn a MacBook Pro 90-test_threads goes from 23.7 to 7.6 seconds, and from\n169 to 49 CPU seconds.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:20 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Bound the threadstest torture writers by writes rather than by time"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe forwarding loop waited a second at a time for data and gave up\nafter ten idle iterations. A TLS connection leaves the loop when the\nsockets close, so it never waits, but DTLS runs over UDP where there\nis no EOF, and a DTLS test whose handshake is not expected to complete\ncan only leave by exhausting the whole ten second budget. Two tests in\n70-test_sslrecords did exactly that.\n\nPoll at a tenth of a second instead. The iteration limit is unchanged,\nso a second of complete silence now ends the connection rather than ten,\nand a run that is only waiting for its exit condition notices ten times\nsooner.\n\n70-test_sslrecords goes from 32.3 to 13.7 seconds. The other TLSProxy\nrecipes are unaffected, as their loops exit on socket close without ever\nreaching the timeout.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:21 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Poll the TLSProxy test sockets ten times a second"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAs detected by ASAN, the scanner value used when parsing GUC files can\nbe indeterminate when the flex error handler sigjumps to the old cleanup\npath, before yylex_init() is called.\n\nThe flex scanner state is now made volatile in ParseConfigFp(), since\nits value is assigned after sigsetjmp() and cna be accessed after\nsiglongjmp(). yylex_init() cannot use a volatile pointer; a temporary\nvariable is used before assigning the result of yylex_init() to it.\n\nWhile on it, yy_create_buffer() is changed to detect the case where it\nreturns a NULL value. Based on my read of the flex code, this cannot be\nreached currently. Future upstream changes or changes in the error\nlogic of the GUC file parsing could make that reachable, and it is four\nextra lines of code.\n\nOversight in d663f150b5ed.\n\nReported-by: Ilia Kashintsev \nReviewed-by: Tom Lane \nReviewed-by: Andrey Rachitskiy \nDiscussion: https://postgr.es/m/19612-24ccb4fc6da7786f@postgresql.org\nBackpatch-through: 18", "completion": "Fix ASAN failure after flex errors in GUC file parsing"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nTLSProxy gave a DTLS s_server a stdin that was the read end of a pipe\nfrom a \"perl -e sleep(10)\" process, so that it would not see EOF while\nthe test ran. Nothing ever closed that early, so the recipe paid out\nthe remainder of the ten seconds before it could exit.\n\nUse a plain pipe and keep the write end in the proxy, closing it in the\nteardown that already reaps s_server. Stdin then stays open exactly as\nlong as the test needs and no longer, with no timer to tune.\n\n70-test_sslrecords goes from 13.7 to 4.0 seconds on my mac\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:22 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Hold DTLS s_server stdin open with a pipe rather than a timer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 18954ce7f69 has replaced hardcoded relreplident values in\ndescribe.c with CppAsString2 macros, but used a DEFAULT instead of a\nNOTHING at one location. This caused \\d+ on a table with REPLICA\nIDENTITY NOTHING to show incorrect data.\n\nAuthor: Shinya Kato \nDiscussion: https://postgr.es/m/CAOzEurRHWt+9XLBrbXQOSVkE45NksJ4F28twuqgZ7veW0RzpUQ@mail.gmail.com\nBackpatch-through: 18", "completion": "psql: Fix \\d+ display of REPLICA IDENTITY NOTHING"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:22 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Assert on the correct size."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe recipe passed all 102 valid parameter files as arguments, but a test\ncan be given at most 100 before test_get_argument() runs off the end of\nits bookkeeping array. The address sanitizer build caught it; on a\nnormal build it silently wrote past the end.\n\nWrite the file names to a list file and pass that instead, so the corpus\ncan grow without bound. The globbing and the sm2 filtering stay in the\nrecipe.\n\nReviewed-by: Andrew Dinh \nReviewed-by: Tomas Mraz \nMerge-date: Tue Sep 1 14:17:23 2026\nMerged-from: https://github.com/openssl/openssl/pull/32404", "completion": "Pass the ecparam corpus in a file rather than as arguments"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nTarget v8.1.2195 .\n\nNvim did not port Vim's \":terminal\" opts.\nIncompatible implementations.\nEx-command was ported from C to Lua.\nVim needs them partly because of splitting the current window.\n\nI keep forgetting `++close` option so I either run \":qall!\"\nor kill the parent process (ie. terminal emulator).\n\nUnsatisfied users should create their Ex-command that runs jobstart().", "completion": "build(vim-patch): n/a \":terminal\" opts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nKeep separate local and inherited ownership for component root bindings so\nparent attrs can override child values without discarding the latest local\nstate. Restore ordinary props when inherited keys are removed, merge class\nand style caches, and dispatch local and inherited dynamic listeners through\none stable native listener.\n\nInstall fallthrough effects for initially empty dynamic sources, apply the\nfunctional-component whitelist to component roots, and avoid capturing\nv-show's transient display state as local style.", "completion": "fix(runtime-vapor): preserve root bindings across attrs fallthrough"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nIgnoring incompatible implementation,\nTerminalOpen and TermOpen events are not 1-1.\n\"TerminalWinOpen\" was accepted as N/A in\ncommit c7ee6af777a9a0b1cd54817c646fe32fa7267c47 .\n\nI planned to not do this to have more test cases\nafter manipulating the hunks header to filter out more hunks\nbut Justin is eager to just mark these N/A\nto bump the Vim major.minor version.\n\nTime to move on from v8.1.x.", "completion": "build(vim-patch): n/a docs for v8.1.2219"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBefore: getSignalGraph only exposed debuggableFn on computed and template\nnodes, preventing DevTools from linking to source code for other node types.\n\nAfter: debuggableFn is also populated for linkedSignal, effect, and\nafterRenderEffectPhase nodes.\n\n(cherry picked from commit 0ddbc47e7f6a4eced3a1a986b260747dc37ee9c9)", "completion": "fix(core): expose debuggableFn for non-computed signal graph nodes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBefore: getSignalGraph only exposed debuggableFn on computed and template\nnodes, preventing DevTools from linking to source code for other node types.\n\nAfter: debuggableFn is also populated for linkedSignal, effect, and\nafterRenderEffectPhase nodes.", "completion": "fix(core): expose debuggableFn for non-computed signal graph nodes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Menu): prevent tooltip flash when collapsing while hovered\n\nCo-authored-by: Cursor \n\n* fix(Menu): respect controlled tooltip.open when collapsed\n\nCo-authored-by: Cursor \n\n---------", "completion": "fix(Menu): prevent tooltip flash when collapsing while hovered"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWhen `z=` delegates to `vim.ui.select()`, the picker may change the\ncurrent window before returning. `spell_suggest()` then continues to the\ncursor restoration branch with the new window and assigns `prev_cursor`,\nwhich belongs to the original window. This can leave Normal mode with an\ninvalid cursor position and produce E315.\n\nSolution:\nClean up the spell suggestion state and return immediately after handing\ncontrol to `vim.ui.select()`.", "completion": "fix(spell): avoid invalid window state after async spell select"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nMove the message bus subscription out of afterRenderEffect into constructor initialization and clean up the listener on destroy using DestroyRef.", "completion": "fix(devtools): prevent duplicate highlightComponent listener in injector tree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nRedo prep is scattered/duplicated.\n- `do_pending_operator()` has 3 prep blocks whose conditions must be in\n sync with `atom_capture_op()`.\n- insert.c, spell_suggest() hand-roll `redo_new()` + `redo_append_xx()`\n sequences.\n- prep_redo() has 2 roles, decided by `keys != NULL`.\n\nSolution:\n- `atom_capture_op()` is the \"operator\" entry point: capture, then\n prep.\n- Extract `prep_redo_visual()`, `atom_capturable()`.", "completion": "refactor(cmdatom): do \"redo prep\" in one place #41348"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- 'rtsp_transport'\n\n There is no need to keep this data around once the RTSP request has been\n issued.\n\n- 'accept_encoding'\n\n Only needed when creating the RTSP request.\n\n- 'uagent'\n\n The header is generated on demand from set.str[STRING_USERAGENT]\n\n- 'ref'\n\n Not necessary to keep around\n\nCloses #22603", "completion": "urldata: drop four strings from the aptr struct"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis is part of a more global effort to modernize the code tree with\nsafer allocation functions, which offer more protection in terms of:\n- stronger type safety guarantees\n- size overflow checks, particulary for arrays.\n\nThis set of updates includes allocation changes based on\npalloc_object(), palloc_array() and repalloc_array(). This work is\nsimilar to 1b105f9472bd, expanding more the new APIs in the tree in an\nincremental fashion.\n\nAuthor: Tristan Partin \nDiscussion: https://postgr.es/m/DKJB5887LGX9.359DV1UMZ1URK@partin.io", "completion": "Use safer allocation routines in more places of the tree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Anchor): avoid duplicate onChange with getCurrentAnchor\n\n* fix(Anchor): avoid remapping getCurrentAnchor results\n\n* fix(Anchor): preserve raw click identity\n\n* test(Anchor): use named demo props interface\n\n---------", "completion": "fix(Anchor): avoid duplicate onChange with getCurrentAnchor"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(upload): preserve files added during async removal\n\n* refactor(Upload): read latest file list with useEvent", "completion": "fix(Upload): preserve new files during async removal"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe semantics of optional chaining changes when there are extra parenthesis. We need to make sure that we do not introduce some unnecessary ones.\n\nfixes #70143\n\n(cherry picked from commit e9ba39d671a3645ef5ca8233c96bacc94f02d155)", "completion": "fix(compiler-cli): Produce correct tcb expression for optional chaining"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe semantics of optional chaining changes when there are extra parenthesis. We need to make sure that we do not introduce some unnecessary ones.\n\nfixes #70143", "completion": "fix(compiler-cli): Produce correct tcb expression for optional chaining"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nLabel the two unnamed demo switches and restore axe button-name enforcement across every Badge demo.\n\nAI-assisted: Codex", "completion": "test(Badge): enable button-name accessibility checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`RedoBuf` is mostly indirection. It has a mild benefit as an \"ownership\"\nsignal but it counteracts the general goal of unifying how \"redo state\"\nis passed throughout the system, tends to sprout redundant interfaces,\nand reduces clarity.\n\nSolution:\nAdd `CmdSpec.body` to hold the \"prefixless\" key sequence.\nReuse `CmdSpec` to represent a \"redo\" buf.", "completion": "refactor(cmdatom): drop RedoBuf #41351"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nethan changed his nick, this was causing some pullapproves errors when a pr hit the primitives-shared scope.\n\n(cherry picked from commit 28f323a57810ae4da3fafab150f1ef355c8f44a6)", "completion": "ci: update github nick"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nethan changed his nick, this was causing some pullapproves errors when a pr hit the primitives-shared scope.", "completion": "ci: update github nick"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- sockindex: int -> int8_t\n- move connectdata members around for fun and profit\n- remove data->state.current_speed as unused\n- remove data->state.trailers_bytes_sent as unsed\n- remove data->state.trailers_buf as unsed\n\nThe sockindex type change spread a little.\n\nCloses #22604", "completion": "urldata: cleanups"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22605", "completion": "scorecard: fix argument handling when count and parallel are both 1"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`buffheader_T` is a linked list (Vim's favorite data structure) with\ncomplex bookkeeping, optimized for ancient hardware:\n\n1. Memory topology: On old platforms (Amiga 512KB without MMU, MS-DOS\n 64KB segments), large contiguous allocations were hazardous (no VM).\n2. Never-move appends: `add_buff()` fills spare space or links a new\n block.\n3. OOM \"recovery\": a failed block allocation only loses one append.\n\nTo avoid OOM, it prefers to allocate small, linked chunks, instead of\nresizing one continguous slice. Each stuff/drain cycle costs\na malloc+free.\n\nSolution:\nReplace Vim's favorite data structure with Nvim's favorite data structure.\n\nNvim doesn't have granular handling of OOM (`xmalloc`), and hardware has\nchanged: caches favor contiguous memory, allocators handle\nfragmentation. And these buffers are ~kb scale, so OOM is irrelevant on\nany system that can run Nvim.\n\n- Use a flat `StringBuilder` + `read`/`insert` offsets.\n- Keeps capacity (does not shrink) until `free_buff`.\n- \"Steady state\" allocates nothing: 1 fewer malloc+free per dot-repeat.", "completion": "perf(input): drop buffheader_T #41353"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen creating a multi handle, global_init() may not have been\ninvoked that. There is a lazy check for this in easy_init()\nthat trigger global_init().\n\nCreate the admin handle for a multi first, before any further\noperations, so easy_init() can trigger a global_init() when\nnecessary.\n\nCloses #22606", "completion": "multi: initialisation order"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe routing header draws a serpentine route with map pins on it but\nnobody travelling it. Angie now stands on the top segment, the same way\nshe stands on the road in the roadmap header.\n\nShe needs more headroom than the canvas had, so the viewBox gains 12\nunits at the top and the illustration carries its own max-height, which\nkeeps the rest of the drawing at the size it rendered before.\n\n(cherry picked from commit 064530447e7834ac672a33c4dff612ea7dc2d46a)", "completion": "feat(docs-infra): add Angie to the routing illustration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe routing header draws a serpentine route with map pins on it but\nnobody travelling it. Angie now stands on the top segment, the same way\nshe stands on the road in the roadmap header.\n\nShe needs more headroom than the canvas had, so the viewBox gains 12\nunits at the top and the illustration carries its own max-height, which\nkeeps the rest of the drawing at the size it rendered before.", "completion": "feat(docs-infra): add Angie to the routing illustration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAfter telemetry data from Mozilla reported the P99 DNS resolution\ndifferences between A and AAAA responses to by 21ms, reduce curl's\nresolution delay to 25ms.\n\nWhat could possibly go wrong?\n\nCloses #22612", "completion": "Happy Eyeballing v3: resolution delay of 25ms"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA DTLS listener, and the connections it accepts, now default to\nblocking mode. The dtlslistenerecho demo drives the listener and its\nconnections with SSL_poll() and uses SSL_ACCEPT_CONNECTION_NO_BLOCK,\nso call SSL_set_blocking_mode() on the listener to put it back into\nnon-blocking mode. The accepted connections inherit that mode.\n\nAlso update the DTLS 1.3 guide (ossl-guide-dtlsv13) to mention\nSSL_set_blocking_mode() and SSL_get_blocking_mode() for DTLS\nlisteners and to note that a listener is blocking by default.\n\nReviewed-by: Tomas Mraz \nReviewed-by: Jakub Zelenka \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:50:38 2026\nMerged-from: https://github.com/openssl/openssl/pull/31983", "completion": "DTLS 1.3 Set the listener demo to non-blocking mode"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nas is PostgreSQL standard", "completion": "Replace printf format %i by %d"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFollow-up to bb406386d9e088873f5f640c55e14a69390abd01 #22229\n\nCloses #22607", "completion": "curlx_inet_pton: drop setting `errno` on error"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nextract_autovac_opts() returns a palloc'd copy of just the\nAutoVacOpts portion of a relation's reloptions, but upcoming work\nneeds the other StdRdOptions fields, too. Remove it in favor of\ncalling extractRelOptions() directly. av_relation now caches the\nmain table's whole StdRdOptions.\n\nReviewed-by: Michael Paquier \nReviewed-by: Sami Imseih \nTested-by: Greg Burd \nTested-by: solai v \nDiscussion: https://postgr.es/m/aFRxC1W_kZU9OjJ9%40nathan", "completion": "Remove extract_autovac_opts()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nExtract vimscript.txt from repeat.txt", "completion": "docs: misc, cwd, vimscript.txt #41356"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCoverity flagged a few instances of the above test calling\nSSL_SESSION_set_time_ex and casting the result to an int for comparison,\nbut ints are smaller than time_t's so we may get faulty comparisons.\n\nFix it by using the proper TEST_time_t_gt check instead of TEST_int_gt\n\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1700237\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1700236\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1700235\nFixes https://scan5.scan.coverity.com/#/project-view/60762/10222?selectedIssue=1700234\n\nReviewed-by: Daniel Kubec \nReviewed-by: Bob Beck \nReviewed-by: Paul Dale \nReviewed-by: Andrew Dinh \nMergeDate: Wed Aug 19 03:31:50 2026\n(Merged from https://github.com/openssl/openssl/pull/32410)", "completion": "Fix time_t / integer compares in tls13tickettest"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit reimplements autovacuum_enabled as a ternary, using the\nsupport added in commit 4d6a66f675 and following the example of\nvacuum_truncate. This changes only the internal representation: an\nunset value still behaves as enabled, and the option accepts the\nsame input as before.\n\nThis is preparatory work for a follow-up commit that will make use\nof the new \"unset\" state.\n\nReviewed-by: Michael Paquier \nReviewed-by: Greg Burd \nReviewed-by: Sami Imseih \nTested-by: solai v \nDiscussion: https://postgr.es/m/aFRxC1W_kZU9OjJ9%40nathan", "completion": "Make autovacuum_enabled a ternary reloption."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nplperl_func_handler()'s stanza for handling an arrayref result in\na SETOF function could loop forever (or at least till OOM) when\ngiven a tied array, since av_fetch won't necessarily ever return\na null pointer in that case. Be consistent with the other places\nwhere we traverse a perl array: call av_len() once and use len+1\nas the loop limit, silently ignoring any null pointers we get back\nfrom that range of subscripts.\n\nBut actually, Perl's preferred locution for this seems to be to\nuse av_count() not av_len()+1. av_count() seems better since\nthere's less risk of forgetting to add 1. Also, both of those\nfunctions return Size_t (or SSize_t) not int, creating at least\na theoretical overflow hazard. While we're modernizing this,\nlet's use the correct variable type where we can, and include an\noverflow check where we can't.\n\nReported-by: Claude Code (via Noah Misch)\nAuthor: Tom Lane \nReviewed-by: Andrey Rachitskiy \nDiscussion: https://postgr.es/m/569769.1786901901@sss.pgh.pa.us\nBackpatch-through: 14", "completion": "Make plperl's handling of Perl arrays safer and more consistent."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis commit adds a new value to StdRdOptIndexCleanup to distinguish\nwhether it is explicitly set, similar to ViewOptCheckOption's\nVIEW_OPTION_CHECK_OPTION_NOT_SET. This changes only the internal\nrepresentation; an unset value still defaults to AUTO, and the\noption accepts the same input as before.\n\nThis is preparatory work for a follow-up commit that will make use\nof the new \"unset\" state.\n\nReviewed-by: Michael Paquier \nReviewed-by: Sami Imseih \nTested-by: Greg Burd \nTested-by: solai v \nDiscussion: https://postgr.es/m/aFRxC1W_kZU9OjJ9%40nathan", "completion": "Add an \"unset\" value for vacuum_index_cleanup."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nMake sure the launcher cancels the currently running worker by calling\nTerminateBackgroundWorker when it receives SIGINT. In order to handle\ncases where SIGINT arrives while tje launcher is waiting for a worker\nto start or exit, implement a version of WaitForBackgroundWorkerStartup\nand WaitForBackgroundWorkerShutdown which checks the abort_requested\nsignalling. A new test which kills processing with SIGINT is added.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Fujii Masao \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAHGQGwEQ1-+iPQnUpTXYiHmzSz9ufFVkOK4kL_uyTdYt7jgg0Q@mail.gmail.com\nBackpatch-through: 19", "completion": "Make data checksums launcher cancel its worker at SIGINT"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWhile purely aesthetic, it makes reading the code easier to rearrange\nbefore the feature has shipped since doing it after risk backpatching\nconflicts. Also add missing prototypes.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Fujii Masao \nDiscussion: https://postgr.es/m/CAHGQGwEQ1-+iPQnUpTXYiHmzSz9ufFVkOK4kL_uyTdYt7jgg0Q@mail.gmail.com\nBackpatch-through: 19", "completion": "Reorder function prototypes to match definition order"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdd the error guide URL when a compiler diagnostic uses a negative\nmarked error code.\n\n(cherry picked from commit 45ebb127e32182e2635cc441c56a7adb94aca8b8)", "completion": "refactor(compiler-cli): add error guide links to diagnostics"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdd the error guide URL when a compiler diagnostic uses a negative\nmarked error code.", "completion": "refactor(compiler-cli): add error guide links to diagnostics"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nExercise allocation failures across OSSL_STORE_attach() and\nOSSL_STORE_load().\n\nAlso test that rejected loader parameters make OSSL_STORE_attach()\nreturn NULL instead of returning a context containing a dangling\nloader context.\n\nAssisted-by: ChatGPT:gpt-5.6\n\nReviewed-by: Jakub Zelenka \nReviewed-by: Neil Horman \nMergeDate: Tue Sep 15 14:20:06 2026\n(Merged from https://github.com/openssl/openssl/pull/32413)", "completion": "Add OSSL_STORE store regression tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThis flag hasn't been useful since the removal of old-style VACUUM FULL,\nso remove it now (this includes removing vestigial code that\nunnecessarily set the flag).\n\nAlso add test coverage of gistprunepage(). Had that test case been\navailable before now, the issue fixed by this commit would have been\ndetected by wal_consistency_checking buildfarm animals.\n\nAuthor: Peter Geoghegan \nReviewed-by: Michael Paquiër \nDiscussion: https://postgr.es/m/CAH2-WznbTsQCrjmd=eSawfPqcxCjSFUkk6Qzd3z+gpNte5i03Q@mail.gmail.com\nBackpatch-through: 14", "completion": "GiST: Deprecate F_TUPLES_DELETED opaque area flag."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPrevent arbitrary MetaDefinition properties from writing on* handlers directly to meta elements. Browser events can execute these handlers, including on meta elements rendered in the document body.\n\n(cherry picked from commit 6f9a6bea50944fff894eb5629075b13f8c3090d7)", "completion": "fix(platform-browser): disallow event handler attributes in Meta"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nPrevent arbitrary MetaDefinition properties from writing on* handlers directly to meta elements. Browser events can execute these handlers, including on meta elements rendered in the document body.", "completion": "fix(platform-browser): disallow event handler attributes in Meta"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ntsqueryrecv() accepted zero-length lexemes, which tsqueryin() doesn't.\nIt also accepted phrase distance values larger than MAXENTRYPOS,\nwhich tsqueryin() doesn't. While neither of these omissions are\nvery harmful in themselves, they do allow accepting tsquery values\nthat will fail in a subsequent textual dump/reload.\n\nCommit 23d9ad771 performed similar tightening of tsvectorrecv(),\nbut I left off these changes at the time because they didn't seem\nto have security implications.\n\nReported-by: Claude Code (via Noah Misch)\nAuthor: Tom Lane \nReviewed-by: Chao Li \nDiscussion: https://postgr.es/m/455079.1786897319@sss.pgh.pa.us\nBackpatch-through: 14", "completion": "Tighten up tsqueryrecv()."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\ntextsearch.sgml neglected to mention that the MAXSTRPOS total-length\nlimit applies to tsquery as well as tsvector. It also claims that\nthere is a 32K limit on the total number of nodes in a tsquery, which\nis wrong. (I suspect that QueryOperator.left may once have been\nint16, which would give rise to such a limit. But it's uint32 now,\nso you'd hit the 1GB varlena limit well before overflowing that.)\n\nWhile at it, re-order the bullet points into an order that makes\nmore sense, to me anyway.\n\nReported-by: Claude Code (via Noah Misch)\nAuthor: Tom Lane \nReviewed-by: Chao Li \nDiscussion: https://postgr.es/m/455079.1786897319@sss.pgh.pa.us\nBackpatch-through: 14", "completion": "Doc: clean up documentation about text search datatype limits."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs(transfer): sync `local.notFoundContent` default value\n\n* chore: rerun CI\n\n---------", "completion": "docs: sync Transfer `local.notFoundContent` default value"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nEnsure that srclen >= 0 before calling strlower_c(), etc.\n\nCommit 5f003855e7 backported strlower_c(), etc., to 18, but did not\naccount for the srclen < 0 behavior that existed in 18 (and was\nremoved later in version 19 with commit 6d22c67c3b).\n\nNo callers in core use the srclen < 0 behavior, but it's possible\n(though unlikely) that extensions do.\n\nThis applies to REL_18_STABLE only.\n\nDiscussion: https://postgr.es/m/v36ssaygf7grb3qzfsjhtdzi7kqd45ds56nyuf7gi5qjml4qbb@ezmfqzmhlrs2", "completion": "pg_locale.c: Fix REL_18_STABLE for srclen < 0."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nri_FastPathFlushArray() rechecked a concurrently updated PK tuple with a\nscan key it built itself, putting found_val, the key of the tuple it had\njust locked, into sk_argument, and passing that same slot to\nrecheck_matched_pk_tuple(). Both operands therefore came from the locked\ntuple, and since sk_argument is the operator's right-hand input, the PK\nvalue was read as an FK value. For a foreign key using a cross-type\nequality operator, such as a \"date\" primary key referenced by a \"timestamp\"\ncolumn, that compares days against microseconds, so the recheck always\nfailed and a batch that had to follow an update chain reported a violation\neven though the version it locked still had the key.\n\nRemove the recheck. For a same-type key it compared the tuple against\nitself and so never rejected anything, which was harmless only because the\nloop a few lines below does the real work: it already compares found_val,\nread after the chain has been followed, against every buffered FK value,\nwith the arguments in the order the operator expects. That makes the\nrecheck redundant as well as wrong. Detection is not weakened by dropping\nit, since the buffered value that led the scan to a tuple can be matched by\nno other row visible to our snapshot.\n\nri_FastPathProbeOne() passes its original scan key, with the FK value still\nin sk_argument, and was never affected; nor were single-row statements or\nmulti-column foreign keys, which go through it.\n\nAdd an isolation test covering the cross-type case, a permutation where\nthe key really does move away, and a same-type permutation that should\nbehave identically.\n\nReported-by: Peter Geoghegan \nCo-authored-by: Peter Geoghegan \nDiscussion: https://postgr.es/m/CAH2-WznQjX3GByh_Ju7unuzMcik_5PJ5D7i_=qhwk=gPEkhfVQ@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix cross-type foreign keys in the batched fast-path FK check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nLabel the loading demo switch and restore axe button-name enforcement across every Card demo.\n\nAI-assisted: Codex", "completion": "test(Card): enable button-name accessibility checks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nhstore has been relying on a set of int/int32 to count the total length\nof all the keys and values constructed, relying on the maximum values of\nthe arguments rather than proper bound checks. As proved in the\nreported thread, these counters could overflow and wrap, leading to\nincorrect allocations.\n\nThis commit replaces the int/int32 values with a set of Size values,\nwith add_size() and mul_size() in charge of checking for overflows when\nconstructing hstore values before doing any allocation.\n\nThe changes that matter in terms of the report are mostly in\nhstore_io.c. hstore_compat.c is adjusted for consistency, to keep the\nallocation maths uniform across the module.\n\nThis is an old bug. A backpatch should perhaps be done but I cannot get\nexcited about a change like that in stable branches.\n\nReported-by: Man Zeng \nAuthor: Tender Wang \nAuthor: Michael Paquier \nDiscussion: https://postgr.es/m/CAHewXNmfD6-9MDxgpRfTzjVj0mhBw3JMoNOHeTiPOjZGhNzd=g@mail.gmail.com", "completion": "hstore: Rework module to use Size and {add,mul}_size for allocation sizes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCloses #22611", "completion": "tests: fix Content-Length mismatch in test 2064"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: vue-core\nChanges:\nReplace the post-render scope id walkers with a creation-time ambient\nmodel aligned with VDOM semantics. Scope ids are compile-time\nconstants: elements receive their attributes when created.", "completion": "refactor(runtime-vapor): creation-time scope id model"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nExpose Upload onFocus at the component root so focus entering select, drag, and picture-card layouts reaches consumers exactly once.\n\nAI-assisted: Codex", "completion": "fix(Upload): forward focus events"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from 862e8a74a84478d (excluding the tests)", "completion": "CVE-2026-9546: sending old referer"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from 849317ff5c5a5e13f50ec3d0", "completion": "CVE-2026-11586: WS Auto-PONG memory exhaustion"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from ab3bb8cd8be8f9d4ac", "completion": "CVE-2026-12064: proto-default skips SSH verification"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\n%L was described as showing in output the client IP, but it shows the\nlocal IP of the server connected to.\n\nAuthor: Keisuke Kuroda \nReviewed-by: Greg Sabino Mullane \nDiscussion: https://postgr.es/m/CANDwggK8AZJx+tGKY+h_8a90rqZ_+4dvGOFvDuRVVSjQvAafbg@mail.gmail.com\nBackpatch-through: 18, only", "completion": "doc: Fix description of log_line_prefix %L in release notes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe RI fast path reads pg_constraint.conindid before taking\nRowShareLock on the referenced table. REINDEX CONCURRENTLY can\nrepoint the constraint and mark the old index dead, or drop it,\nbetween those operations. A backend in that window does not yet\nhold a relation lock, so it is not covered by REINDEX CONCURRENTLY's\nwaits for lockers.\n\nOpening an index that has already been dropped produces \"could not open\nrelation with OID\". Opening one that has only been marked dead can\nproduce wrong answers: the index is no longer maintained or vacuumed,\nso a scan can miss a referenced row or follow a stale entry to a reused\nheap line pointer.\n\nAfter locking the referenced table, reload the constraint and use its\ncurrent conindid. LockRelationOid() processes invalidation messages\nafter acquiring the lock, so the reload sees a committed index swap.\nIf the lock was already held, REINDEX CONCURRENTLY cannot mark the old\nindex dead or drop it until the transaction releases that lock, so\ncontinuing to use the old conindid is safe.\n\nDo this at both RI fast-path call sites. Add injection-point coverage\nfor old indexes that have either been dropped or marked dead.\n\nAuthor: Mihail Nikalayeu \nDiscussion: https://postgr.es/m/CADzfLwUJiVuv69uwuF5z4TrMhNkVwQUXW03q+uVNwmYFLtjEhw@mail.gmail.com\nBackpatch-through: 19", "completion": "Fix RI fast-path race with REINDEX CONCURRENTLY"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nNative Lua modules loaded with `require` or `package.loadlib` resolve Lua\nC API symbols from the nvim executable itself. Those symbols must stay in\nthe binary even when nothing inside nvim references them.\n\n`rdynamic` is enough on Linux. On macOS the linker dead-strips\nunreferenced symbols before rdynamic exports them, so `_lua_tothread` is\nmissing from the executable and loading such a module fails with:\n\n symbol not found in flat namespace '_lua_tothread'\n\nDisable section garbage collection so all non-static symbols are kept.", "completion": "build(zig): keep all symbols for native Lua modules #41361"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe keep getting PRs that target single usages of `hasOwnProperty` and we have ~100 of them. These changes aim to address the issue centrally by swapping out all the instances and adding a lint rule against introducing new ones.\n\n(cherry picked from commit 732e5050180190df24768ace7aa3e785ca0dcc0a)", "completion": "fix(core): replace all hasOwnProperty usages with Object.hasOwn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nWe keep getting PRs that target single usages of `hasOwnProperty` and we have ~100 of them. These changes aim to address the issue centrally by swapping out all the instances and adding a lint rule against introducing new ones.", "completion": "fix(core): replace all hasOwnProperty usages with Object.hasOwn"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nSmall rearrangements to avoid having to cast away qualifiers. In some\ncases, the whole cast was unnecessary.\n\nReviewed-by: Heikki Linnakangas \nDiscussion: https://www.postgresql.org/message-id/flat/459217ca-3840-4452-8cd1-8f9b47e8d479%40eisentraut.org", "completion": "Fix some -Wcast-qual warnings"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUWP requires VS2015+. Project files have no support for c-ares.\nDrop redundant guard, merge `#if` blocks.\n\nFollow-up to 1db93bdb7c1943132b13543539aaaf4866f31419 #22595\n\nCloses #22613", "completion": "config-win32.h: drop UWP, c-ares, simplify more"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nWith the addition of the `:help al` text object, you can now easily\nformat the whole buffer with `gqal`. However, `vim.lsp.formatexpr` only\nuses `textDocument/rangeFormatting` which some language servers (like\ngopls) don't support.\n\nSolution:\n- Fall back to `textDocument/formatting` if the whole buffer is being formatted\n and the server doesn't support `textDocument/rangeFormatting`.\n - In theory, these two methods should return the same response if the whole\n buffer is being formatted, but I preserved the existing behaviour of\n prioritising `textDocument/rangeFormatting` in case that does not hold (i.e.\n LS bug).\n- Also: `vim.lsp.formatexpr` had no tests at all, so actually add tests for it.", "completion": "feat(lsp): fallback to textDocument/formatting from vim.lsp.formatexpr #40079"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nimplemented\n\nFollow-up to 6c31df453b02597e90c27c2e0bc69bb114105005", "completion": "TODO: remove \"Support MQTTS\""} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n- The ancient Negotiate ones are just outdated\n- NTLM is going away, no need to list the bugs anymore\n\nCloses #22615", "completion": "KNOWN_BUGS: remove old entries and NTLM related"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nTo make it easier to run different subsets of the tests in separate\ninvokes.\n\nCloses #22616", "completion": "runtests: introduce a subset option"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAlso:\n- drop most hand-tuned `--min` options, in favor of defaults.\n- enable tests on emulated riscv64.\n Suggested-by: Dan Fandrich\n Ref: https://github.com/curl/curl/pull/22590#issuecomment-5303238102\n- drop building examples on emulated riscv64.\n\nAdding around 3.5 minutes to the riscv64 job:\n0.5 Perl install, 2 minutes to build tests, 1 minute to run 100 tests.\n\nFollow-up to 66486691ee1c5c768c74e402b8b95902b88d90fb #22619\nFollow-up to e669179681044514099ca726dbaa55653528f4fb #22616\nFollow-up to 58cb1e2f1fa8d8f1c71596918707e566c6353cb2 #22618\nFollow-up to d00000673d05fdf6ceee8941ccd63ad2906257e4 #22602\n\nCloses #22617", "completion": "GHA: use `--subset` runtests option, run random subset in riscv64 job"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nFlaky test:\n\n RUN T1158 nvim.zip reports an incorrect archive password: 11092.84 ms FAIL\n\nThe prompt is detected only if the pty output *ends* with \"password: \",\nbut a read may return the prompt plus following bytes.\n\nSolution:\n- Match anywhere in the output since the last password was sent. The\n buffer is cleared before each send, so won't match stale text.\n- Assert on the reported message, so a failure shows what was reported.", "completion": "fix(zip): missed \"password:\" prompt if output trails it #41364"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nSet the default to `CURL_TEST_MIN` if set, first. Then process the\ncommand-line options to override it. Previously, the env took over if\nthe command-line explicitly tried to set it to zero.\n\nRef: #22617\n\nFollow-up to 3f1cd809eeae05f39fec72fe780f3a69d21972fb #19942\n\nCloses #22618", "completion": "runtests: allow resetting `CURL_TEST_MIN` via `--min=0`"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\nThe CLI help text and the missing-config error each listed only\neslint.config.js, eslint.config.mjs, and eslint.config.cjs, omitting\nthe TypeScript config files that `FLAT_CONFIG_FILENAMES` already\nincludes. The glob covers all six without enumerating them, and it\nmatches the `config` typedef in `lib/options.js`, which already uses\n`eslint.config.*`.\n\n`-c` now says it replaces the lookup rather than a single file, since\nmultiple default config files can apply in one run and `-c` disables\nthat lookup entirely.\n\nFixes #21111", "completion": "docs: use eslint.config.* wherever config file names are listed"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWaitLSNCleanup() was called from ProcKill(), but not from\nAuxiliaryProcKill(), even though xlogwait.c sizes its shared memory to\ninclude NUM_AUXILIARY_PROCS and thus accepts calls from auxiliary\nprocesses. Such a process exiting while waiting would leave its entry in\nthe heap.\n\nRegister an on_shmem_exit callback lazily before a process enters a\nwait-for-lsn heap instead, as suggested by Noah: that keeps the cleanup\nlocal to xlogwait.c and makes it harder to miss a caller that needs it,\nrather than having to remember every process-kill path.\n\nReported-by: Noah Misch \nAuthor: Xuneng Zhou \nReviewed-by: Alexander Korotkov \nDiscussion: https://postgr.es/m/20260706012642.f9.noahmisch%40microsoft.com\nDiscussion: https://postgr.es/m/CABPTF7UtW_cAa%3DQh4RDfKiUqu3pJJE22ai9tbWJVERbeRyssLw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Add wait-for-lsn process-exit cleanup callback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nPad example LSNs to match pg_lsn_out() output, and use\n\"standby_replay LSN\" in the timeout error to match the server message.\n\nAuthor: Xuneng Zhou \nReviewed-by: Alexander Korotkov \nDiscussion: https://postgr.es/m/CABPTF7UtW_cAa%3DQh4RDfKiUqu3pJJE22ai9tbWJVERbeRyssLw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Fix WAIT FOR LSN documentation examples"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWaitLSNWakeup() removes each selected waiter from its heap and clears\nits inHeap flag before setting its latch. When such a waiter later\ncalls deleteLSNWaiter(), it acquires WaitLSNLock exclusively only to\ndiscover that there is nothing left to remove. Waking many waiters can\ntherefore make them serialize on the lock for no useful work.\n\nCheck inHeap before acquiring WaitLSNLock. A lockless false value is\nconclusive because only the owning backend can change inHeap from false\nto true. A concurrent waker can only clear it. A stale true value\nfalls through to the existing recheck under the lock.\n\nWaitLSNCleanup() performed the same lockless check before calling\ndeleteLSNWaiter(). Drop it there, as it is now redundant.\n\nAuthor: Xuneng Zhou \nReviewed-by: Alexander Korotkov \nDiscussion: https://postgr.es/m/CABPTF7UtW_cAa%3DQh4RDfKiUqu3pJJE22ai9tbWJVERbeRyssLw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Avoid locking when an LSN waiter is already removed"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWaitLSNWakeup() can be called by several processes, not only the startup\nprocess. Update the cleanup comment to explain that another process may\nremove the waiter before waking it and that inHeap prevents double\ndeletion.\n\nAuthor: Xuneng Zhou \nReviewed-by: Alexander Korotkov \nDiscussion: https://postgr.es/m/CABPTF7UtW_cAa%3DQh4RDfKiUqu3pJJE22ai9tbWJVERbeRyssLw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Clarify LSN waiter cleanup after wakeup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nWaitLSNWakeup() removes a waiter from the heap before setting its latch.\nIf the position that caused the wakeup moves backwards before the waiter\nrechecks it, as can happen when WAL streaming restarts, the waiter may\nsleep again while no longer registered. Subsequent WAL progress then\ncannot wake it.\n\nWhen an unmet waiter finds that it is no longer in the heap, add it back\nand restart the loop. Rereading the position after registration also\nprevents missing an advance between the previous read and the re-add.\n\nProcess interrupts before re-registering rather than after, so that a\nwakeup which goes stale again cannot postpone cancellation, however often\nit repeats. As a side effect, a pending cancel now wins over an expired\ntimeout, which previously reported a timeout instead.\n\nAdd deterministic TAP coverage that simulates a stale standby_write\nwakeup without advancing the actual write or replay positions.\n\nAuthor: Xuneng Zhou \nReviewed-by: Alexander Korotkov \nDiscussion: https://postgr.es/m/CABPTF7UtW_cAa%3DQh4RDfKiUqu3pJJE22ai9tbWJVERbeRyssLw%40mail.gmail.com\nBackpatch-through: 19", "completion": "Re-register LSN waiters after stale wakeups"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nWhen the minimum comes from `CURL_TEST_MIN`, to improve the default\nbehavior. It may still need manual adjustment in cases.\n\nFollow-up to e669179681044514099ca726dbaa55653528f4fb #22616\nFollow-up to 58cb1e2f1fa8d8f1c71596918707e566c6353cb2 #22618\nCherry-picked from #22617\n\nCloses #22619", "completion": "runtests: divide minimum required tests by subsets"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n- Dot-repeat of a Visual selection prepared by a `` mapping,\n results in E1255 and leaves Visual mode active.\n- Visual-mode capture is implemented as a second, parallel \"capture\n engine\": it re-composes a CmdSpec from cmdarg_T per key and decides\n replayability from its own table of \"void\" key classes.\n\nSolution:\n- Model nested `normal_execute()` as a `CmdFrame` stack,\n instead of a single module-scoped `stage`.\n - Capture `` \":norm …\" commands as subatoms from its nested frames.\n- Produce every command exactly once; atom_push_raw() routes the atom to\n the Visual composite while a selection is open, like it already does\n for mapping composites.\n - `v/patd` is now repeatable and cascades.", "completion": "fixfix(cmdatom): repeat Visual ; CmdFrame + stage #41355"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\nUpdate default notFoundContent documentation to reflect actual Empty component defaults:\n- English: 'No data' (not 'Not Found')\n- Chinese: '暂无数据' (not 'Not Found')\n\nAffected components: Select, TreeSelect, Cascader, Mentions, Transfer\n\nAll these components use DefaultRenderEmpty which renders the Empty component with locale-aware defaults.", "completion": "docs: align notFoundContent default values across components"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nLeak reported by ASAN CI, always at Lua state init.\n\n ERROR: LeakSanitizer: detected memory leaks\n strbuf_init src/cjson/strbuf.c:62:22\n json_create_config src/cjson/lua_cjson.c:635:5\n lua_cjson_new src/cjson/lua_cjson.c:2060:5\n nlua_state_add_stdlib src/nvim/lua/stdlib.c:840:3\n nlua_state_init src/nvim/lua/executor.c:973:3\n ...\n SUMMARY: AddressSanitizer: 1055 byte(s) leaked in 2 allocation(s).\n\nAnalysis:\n`getout()` may run during `free_all_mem()` (that's why it checks\n`!entered_free_all_mem`). If that happens, the second `os_exit()`\nreturns early from `free_all_mem()` then `exit()` is called and Lua\nstate is never closed.\n\nSolution:\nAlways call `nlua_free_all_mem()` in the early-return case.", "completion": "fix(lifecycle): Lua state not freed if free_all_mem() is re-entered #41366"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nImplemented differently that official fix", "completion": "CVE-2025-14524: bearer token leak on cross-protocol redirect"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA comma following a file ref in a perl print statement makes the\nstatement just print the file's GLOB rather than redirecting the\nfollowing arguments to the file. This meant the test was not testing any\ncontents and the logs were instead bulked up with what the test was\nsupposed to be testing.\n\nAlso, run_log() returns 1 for success, not 0, so the tests for the\nreturn values were wrong. (We were getting 0 because of the comma error\nabove.)\n\nBackpatch-thru: 17", "completion": "test_json_parser: Fix broken file ref and inverted result check"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nUnreliable test on slow CI (ASAN/TSAN):\n\n FAILED .../tui_spec.lua @ 3054: TUI exits immediately when stdin is closed\n retry() attempts: 1\n Expected: vim.NIL\n Actual: { name = \"nvim\", pid = 33201, ppid = -1 }\n\nThe test asserts \"immediate\" exit of the Nvim process, but this may be\nsubject to OS delays outside of our control.\n\nSolution:\nMake the \"timed out waiting for DA1\" log conditional on the actual\ntimeout, and assert the logs in the test.", "completion": "test(tui): unreliable \"TUI exits immediately when stdin is closed\" #41367"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBackpatch-through: 19 only", "completion": "doc PG 19: update to current"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nRefuse SMB connections to do connection reuse. Different fix than the\nofficial one.", "completion": "CVE-2026-5773: wrong reuse of SMB connection"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nTSan CI, always at exit:\n\n WARNING: ThreadSanitizer: use of an invalid mutex (e.g. uninitialized or destroyed)\n #1 uv_mutex_lock\n #2 tui_flush src/nvim/tui/tui.c:1708\n #3 ui_client_event_flush\n #4 parse_msgpack src/nvim/msgpack_rpc/channel.c:259\n ...\n #10 event_teardown src/nvim/main.c:187\n #11 os_exit src/nvim/main.c:720\n ...\n #19 tinput_done_event src/nvim/tui/input.c:184\n\nAnalysis (guess):\n`rpc_close_event()` may run during `event_teardown()` and reattach to\na restarted server, then `ui_client_attached=true` gets set and redraws\nresume in an already-stopped TUI.\n\nSolution:\nCheck `!exiting` in `rpc_close_event`, like we already do in\n`channel_proc_exit_cb()`.", "completion": "fix(tui): ui may attempt reattach during shutdown #41368"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nSIGTERM received during `os_exit()` can cause it to \"nest\":\n\n os_exit src/nvim/main.c:720\n preserve_exit src/nvim/main.c:910\n deadly_signal src/nvim/os/signal.c:205\n on_signal src/nvim/os/signal.c:240\n signal_event src/nvim/event/signal.c:45\n multiqueue_process_events src/nvim/event/multiqueue.c:159\n event_teardown src/nvim/main.c:178\n os_exit src/nvim/main.c:720\n\nSolution:\nCall `signal_reject_deadly()` at the start of `os_exit()` like\n`preserve_exit()` already does.", "completion": "fix(lifecycle): ignore signals during os_exit"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n613c51e wasn't enough to exclude dev-infra\n\n(cherry picked from commit d364c83c44309fa2a1adfd6fb3ccd9f933e0472c)", "completion": "ci: exclude markdown files from requiring dev-infra review"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n613c51e wasn't enough to exclude dev-infra", "completion": "ci: exclude markdown files from requiring dev-infra review"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReplace SSL_LISTENER_FLAG_REQUIRE_HVR and SSL_LISTENER_FLAG_REQUIRE_HRR\nwith a single SSL_LISTENER_FLAG_ADDRESS_VALIDATION, and make address\nvalidation the default. A DTLS listener now validates (HVR for DTLS\n1.0/1.2, HRR cookie for DTLS 1.3) unless SSL_LISTENER_FLAG_NO_VALIDATE\nis set. If both NO_VALIDATE and ADDRESS_VALIDATION are given, the\nlistener fails safe and validates.\n\nUpdate the tests, the dtlslistenerecho demo, util/other.syms and the\nlistener documentation to match.\n\nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Tomas Mraz \nReviewed-by: Jakub Zelenka \nReviewed-by: Matt Caswell \nMerge-date: Thu Aug 20 09:50:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/31983", "completion": "DTLS SSL Listener default address validation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis forwards the `AbortSignal` natively supplied by Chrome 153.0.8009.0's update to `registerTool` executions down into the Angular context. This helps tools gracefully handle execution cancellations initiated by agents or users, preventing unnecessary background work and leaking resources.\n\nWe combine the injector/component destruction abort signals with the native WebMCP execution cancellation signals so the underlying tools correctly cancel long-running requests without producing invalid states.\n\nJustification:\nhttps://groups.google.com/a/chromium.org/g/chrome-ai-dev-preview/c/9291sjhIRz0/m/RFuyRrs5AAAJ\n(cherry picked from commit e041f9483e577cbc8cf32afe8aaebdef0903e082)", "completion": "refactor(core): pass AbortSignal to WebMCP tools to handle cancellation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis forwards the `AbortSignal` natively supplied by Chrome 153.0.8009.0's update to `registerTool` executions down into the Angular context. This helps tools gracefully handle execution cancellations initiated by agents or users, preventing unnecessary background work and leaking resources.\n\nWe combine the injector/component destruction abort signals with the native WebMCP execution cancellation signals so the underlying tools correctly cancel long-running requests without producing invalid states.\n\nJustification:\nhttps://groups.google.com/a/chromium.org/g/chrome-ai-dev-preview/c/9291sjhIRz0/m/RFuyRrs5AAAJ", "completion": "refactor(core): pass AbortSignal to WebMCP tools to handle cancellation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 072ee847ad4 taught logical decoding to discard the changes of a\ntransaction that is already known to be aborted when it is picked for\neviction. That path reuses ReorderBufferTruncateTXN(), which marks\nevery subtransaction that still has in-memory changes as\nstreamed. Since nothing is streamed in that path, and the top-level\ntransaction is never marked, a subtransaction ends up flagged as\nstreamed even though the output plugin has never seen it. Decoding the\nsubsequent abort record then makes ReorderBufferAbort() invoke the\nstream_abort callback for that subtransaction.\n\nFor pgoutput this sends a Stream Abort ('A') message to a subscriber\nthat requested streaming = off, and it does so regardless of the\nnegotiated protocol version, so even a client speaking a version that\npredates transaction streaming receives a message it cannot\nparse. test_decoding dereferences a NULL pointer and crashes, since it\nallocates its per-transaction state in the begin or stream start\ncallback, neither of which runs for a transaction discarded as\naborted.\n\nThis commit fixes this by marking a subtransaction as streamed only\nwhen it has changes and its top-level transaction is already marked as\nstreamed. All streaming call sites mark the top-level transaction\nbefore truncating it, so their behavior is unchanged, while the\nabort-discard path never marks the top-level transaction and therefore\nnow leaves its subtransactions unmarked.\n\nBackpatch to v18, where commit 072ee847ad4 was introduced.\n\nBug: #19616\nReported-by: Tyler Smart \nAuthor: Andrey Rachitskiy \nReviewed-by: Hayato Kuroda \nReviewed-by: Fujii Masao \nReviewed-by: Masahiko Sawada \nDiscussion: https://postgr.es/m/19616-f6153af509910853@postgresql.org\nBackpatch-through: 18", "completion": "Fix stream abort for a transaction that was never streamed."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAs it turns out, when you have 17 different ways to \"exit\", you need to\nplug 17 different holes.\n\nLeak still reported by ASAN CI, even after 1eae512285e7 f238788601eb.\n\n ERROR: LeakSanitizer: detected memory leaks\n strbuf_init src/cjson/strbuf.c:62:22\n json_create_config src/cjson/lua_cjson.c:635:5\n lua_cjson_new src/cjson/lua_cjson.c:2060:5\n nlua_state_add_stdlib src/nvim/lua/stdlib.c:840:3\n nlua_state_init src/nvim/lua/executor.c:973:3\n\nAnalysis:\n`os_breakcheck()` may process a `exit_event` placed by\n`exit_on_closed_chan()` during shutdown. This would re-enter\n`preserve_exit()`, which then skips everything because it sees\n`really_exiting=true`.\n\nSolution:\nSet `exiting` in `preserve_exit()`, not only in `getout()`.", "completion": "fix(lifecycle): json_create_config leak"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA connection's assist thread reads from its network BIO, which for a\ndgram BIO pair belongs to the linked listener. Freeing a listener while\nthe connection's assist thread is still running is a use-after-free.\nFreeing connections first joins their assist threads, so no thread is\nreading when the listener BIOs are freed.\n\nFixes #32420\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Fri Aug 21 11:07:27 2026\nMerged-from: https://github.com/openssl/openssl/pull/32421", "completion": "Free connections before listeners in the radix test cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA connection's assist thread reads from its network BIO, which for a\ndgram BIO pair belongs to the linked listener. Freeing a listener while\nthe connection's assist thread is still running is a use-after-free.\nFreeing connections first joins their assist threads, so no thread is\nreading when the listener BIOs are freed.\n\nFixes #32420\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Fri Aug 21 11:07:16 2026\nMerged-from: https://github.com/openssl/openssl/pull/32421", "completion": "Free connections before listeners in the radix test cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA connection's assist thread reads from its network BIO, which for a\ndgram BIO pair belongs to the linked listener. Freeing a listener while\nthe connection's assist thread is still running is a use-after-free.\nFreeing connections first joins their assist threads, so no thread is\nreading when the listener BIOs are freed.\n\nFixes #32420\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Fri Aug 21 11:07:04 2026\nMerged-from: https://github.com/openssl/openssl/pull/32421", "completion": "Free connections before listeners in the radix test cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA connection's assist thread reads from its network BIO, which for a\ndgram BIO pair belongs to the linked listener. Freeing a listener while\nthe connection's assist thread is still running is a use-after-free.\nFreeing connections first joins their assist threads, so no thread is\nreading when the listener BIOs are freed.\n\nFixes #32420\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Tomas Mraz \nReviewed-by: Andrew Dinh \nMerge-date: Fri Aug 21 11:06:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32421", "completion": "Free connections before listeners in the radix test cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAdd missing comments and fix outdated/incorrect comments in\npg_locale.c and related files.\n\nSuggested-by: Andres Freund \nDiscussion: https://postgr.es/m/v3nniwcrxejmcfvz56xbd22hphprqleuornd6hqkmw2bl7kgmz@cnytz2ee5ltk\nBackpatch-through: 18", "completion": "pg_locale.c: comment improvements."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe controlfile records the current state of data checksums, which\nalso used to be the initial state from initdb when checksums could\nnot be altered after initialization. pg_control_init is documented\nto return information about cluster initialization state, which it\nno longer will if data checksums have been changed either using the\noffline tool or with online processing.\n\nFix by adding a new field in the control file which tracks the init\nvalue of data checksums, and is left read only after initialization.\n\nWhile this is a regression dating back to when changing checksum\nstate was made possible offline with pg_checksums, it is a control\nfile change so it cannot be backpatched.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Daniel Gustafsson \nReviewed-by: Bertrand Drouvot \nDiscussion: https://postgr.es/m/B87ABFBE-A304-4839-8706-C80D73E6BF5C@yesql.se\nBackpatch-through: 19", "completion": "Record initial state of data checksums in controlfile"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit f19c0eccae added the data_checksum_version to the pg_controldata\noutput, but omitted a corresponding change to the pg_control_checkpoint\nSQL function, which reports the same checkpoint information. The field\nis named to match what pg_control_init already reports for consistency.\n\nThe integer version reported is an implementation detail which bleeds\nthrough, but it is quite widely used and a more holistic approach to\nimproving this is left as an excercise for the next major version. The\nmapping between states and versions is added to the documentation to\nmake it easier for users.\n\nBackpatch to v19 where online checksums were introduced.\n\nAuthor: Ian Barwick \nCo-authored-by: Daniel Gustafsson \nReviewed-by: Fujii Masao \nReviewed-by: Chao Li \nReviewed-by: Bertrand Drouvot \nDiscussion: https://postgr.es/m/CAB8KJ=hb765sE8bKC-6sh=Yp3sCjN8xs474yuBrkwyoTM2pgZA@mail.gmail.com\nBackpatch-through: 19", "completion": "Add data_page_checksum_version to pg_control_checkpoint"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nEnabling data checksums in a running cluster changes the state to \"on\"\nbefore the checkpoint which flushes the pages the worker rewrote. A\nbase backup which started before that transition absorbs the barrier\nmid-run and starts verifying pages whose on-disk copies legitimately\nlack checksums, and whose LSNs predate the backup start, so the LSN\ncheck does not skip them either. The backup fails with bogus\ncorruption warnings. The same applies to checksums being disabled and\nre-enabled while the backup runs: hint bits set while checksums were\noff reach disk without a checksum update and without moving the page\nLSN, tripping verification once the re-enabling completes.\n\nTo fix, verify checksums only while they have been continuously\nenabled since the checkpoint the backup started from: track the\nlocation of the last XLOG2_CHECKSUMS record inserted or replayed, and\nverify only when the state is \"on\" and the last change predates the\nbackup start. The starting checkpoint then guarantees that every page\nflushed before it has a checksum written, and any later change\ndisables verification for the rest of the backup.\n\nA standby loses the tracked location when restarting, while pg_control\nalready carries the new state, so it could reach consistency below the\nrecord and serve base backups with the location unknown. To prevent\nthis, replaying XLOG2_CHECKSUMS advances minRecoveryPoint to the\nrecord, like XLOG_PARAMETER_CHANGE does.\n\nThe tests hold the enabling between the state change and its final\ncheckpoint with injection points, straddling it with backups on the\nprimary and across a standby crash-restart.\n\nAuthor: Zsolt Parragi \nReviewed-by: Bertrand Drouvot \nReviewed-by: Daniel Gustafsson \nDiscussion: https://postgr.es/m/CAN4CZFP=-cVVVPue+e8qqPtDfuLuQn=ZB4Mw_C9-Ncru2wqAsQ@mail.gmail.com\nBackpatch-through: 19", "completion": "basebackup: do not verify checksums on pages from before enabling"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA few catalog queries were missing proper schema qualification in the\ntest_checksums module test suites, and one suite contained a disable\ncall right before tearing down the test which can be removed.\n\nBackpatch to v19 where the test suite was added.\n\nAuthor: Daniel Gustafsson \nDiscussion: https://postgr.es/m/8CF9B235-AEE9-4E68-93DD-DF4F29E2FCE5@yesql.se\nBackpatch-through: 19", "completion": "Minor test suite cleanup"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 51f55b13a4d added a test where DROP DATABASE ... WITH (FORCE)\nterminates a session holding a temporary table in the target database.\nWhile exiting, the terminated session drops its temporary table and\ncommits, and the commit waits for a WAL flush behind the backlog\ngenerated by the checksum workers. On machines with slow storage this\ncan exceed the five seconds DROP DATABASE waits for terminated backends\nto exit, making the test fail with \"database \"dropmeforce\" is being\naccessed by other users\", as observed on buildfarm member turaco.\n\nTo fix, use asynchronous commit in the terminated session, so that its\nexit does not wait for a WAL flush, and checkpoint before the drop so\nthat the exit-time WAL records do not queue up behind the backlog.\n\nAuthor: Zsolt Parragi \nReported-by: Alexander Lakhin \nDiscussion: https://postgr.es/m/361531e2-52b5-499c-a126-815f277bbef2@gmail.com\nBackpatch-through: 19", "completion": "Stabilize the FORCE drop test for online data checksums"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nThe zh_TW catalog was stale, omitted 743 messages from the current source, and contained empty, fuzzy, and format-unsafe translations.\n\nSolution:\nRegenerate the catalog with the official translation build, preserve the focused translation repairs, and translate the reported E5200 diagnostic.", "completion": "fix(l10n): refresh Traditional Chinese message catalog #41273"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nVirtual generated columns are stored in tuples as null values, so\nheap_getattr() in tuple_to_stringinfo() always returns null for them.\ntest_decoding printed such a column as null, which is\nindistinguishable from a column that genuinely holds null.\n\nThis commit skips virtual generated columns in tuple_to_stringinfo(),\nthe only place that prints a tuple. Stored generated columns continue\nto be printed, since their values do live in the heap tuple.\n\nThis is a behavior change rather than a bug fix, and it changes\ntest_decoding's output for tables that have virtual generated columns,\nwhich could affect consumers that parse it. Therefore it is not\nback-patched.\n\nAuthor: SATYANARAYANA NARLAPURAM \nCo-authored-by: Bharath Rupireddy \nReviewed-by: Euler Taveira \nReviewed-by: Masahiko Sawada \nDiscussion: https://postgr.es/m/CAHg+QDfTh3UbB-Ed--o2Bd=SBDJoEiG-qp3C0+ETDibF63y=dw@mail.gmail.com", "completion": "test_decoding: Don't print virtual generated columns."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe write macros in include/openssl/pem.h take const TYPE *x, but\nPEM_read_bio_PrivateKey.pod still documented several write functions\nwithout const. Match the public headers.\n\nFixes: https://github.com/openssl/openssl/issues/31169\n\nAssisted-by: Hermes Agent:gpt-5.6-sol\nReviewed-by: Jakub Zelenka \nReviewed-by: Frederik Wedel-Heinen \nMerge-date: Fri Sep 4 17:37:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32422\n(cherry picked from commit 4ddd1002cd41750ee644478a84306be2c59d775a)", "completion": "doc: add missing const to PEM write SYNOPSIS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe write macros in include/openssl/pem.h take const TYPE *x, but\nPEM_read_bio_PrivateKey.pod still documented several write functions\nwithout const. Match the public headers.\n\nFixes: https://github.com/openssl/openssl/issues/31169\n\nAssisted-by: Hermes Agent:gpt-5.6-sol\nReviewed-by: Jakub Zelenka \nReviewed-by: Frederik Wedel-Heinen \nMerge-date: Fri Sep 4 17:37:17 2026\nMerged-from: https://github.com/openssl/openssl/pull/32422", "completion": "doc: add missing const to PEM write SYNOPSIS"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTreat link targets as file paths so crafted documentation cannot select arbitrary VS Code resource providers.\n\nFixes https://github.com/angular/angular/issues/70512\n\n(cherry picked from commit 69c87301aa545adb2c842cac31f062848c48ede9)", "completion": "fix(vscode-extension): prevent JSDoc link provider injection"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nTreat link targets as file paths so crafted documentation cannot select arbitrary VS Code resource providers.\n\nFixes https://github.com/angular/angular/issues/70512", "completion": "fix(vscode-extension): prevent JSDoc link provider injection"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nTied hashes, and probably tied arrays, are capable of returning Perl\nvalue pointers that are actually NULL, not the usual pointer to an\nundef SV. We were not defending against that everywhere, leading\nto possible SIGSEGV. Fix the code to consistently treat a null\npointer returned from hv_iternext or av_fetch like a !SvOK one.\n(Note that the large diff in SV_to_JsonbValue is actually quite\ntrivial, but it required reindenting a chunk of existing code.)\n\nClaude Code found the instance in hstore_plperl, and I found the\nothers by code auditing. Perhaps the other instances aren't\nactually reachable, but I see little reason to assume that.\n\nThe known test cases for these errors require perl's Tie modules,\nwhich may not be present, so it doesn't seem worth the trouble\nto create regression test cases that would cover them.\n\nReported-by: Claude Code (via Noah Misch)\nAuthor: Tom Lane \nDiscussion: https://postgr.es/m/569769.1786901901@sss.pgh.pa.us\nBackpatch-through: 14", "completion": "Defend against null \"SV *\" pointers in plperl modules."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nMake hek2cstr() available in plperl.h, so that it can be used\nin hstore_plperl and jsonb_plperl. Those modules were previously\nusing different coding techniques that probably don't get\nconversion from Perl strings to the database encoding quite right.\n(I'd prefer to make hek2cstr() non-inline, but cross-extension calls\nare messy and plperl has avoided them up to now, so stick with the\nexisting approach.)\n\nConsistently use hv_iternext, hek2cstr, and HeVAL for hash iterations,\nwith one exception in plperl_trusted_init: there, hv_iternextsv is\nfine since we don't actually care about the hash keys. (A later\npatch will remove the HeVAL calls again, but for now we just want\nconsistency.)\n\nRemove unnecessary extra calls of hv_iterinit.\n\nRemove duplicative pstrdup's in plperl_to_hstore.\n\nThe meat of this change is to use hek2cstr() in the contrib modules,\nwhich makes a user-visible change in encoding conversion behavior.\nWhile it's certainly a bug fix, we've had no field complaints about\nthose modules, so I'm hesitant to make this change in the back\nbranches. Hence, apply to master only.\n\nAuthor: Tom Lane \nReviewed-by: Andrey Rachitskiy \nDiscussion: https://postgr.es/m/569769.1786901901@sss.pgh.pa.us", "completion": "Make plperl's handling of Perl hashes more consistent."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: tmux\nChanges:\nScale SIXEL rasters uniformly when clients have different cell dimensions, while retaining the original logical cell canvas as blank padding.\n\nMap crops using real cell boundaries so partial final cells are not stretched or compressed.", "completion": "sixel: preserve image aspect across client geometries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nMove the two remaining fields into the state struct instead, within the\nHTTP ifdef.\n\nAlso: make the AWS sigv4 code always rely on the http_host value. It\nwas previously conditionally trying to also work if it was not set, but\nthat logic was not creating an identical copy so it would fail.\n\nCloses #22620", "completion": "urldata: remove the aptr struct"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThis adds a timeout that will self-terminate a test with a\nsigabrt after a timeout - in the hope that if a test is wedged\nwe now get diagnostic information (like a core dump or stack trace)\ninstead of the CI job timing out globally\n\nThe default timeout for a single C test is 30 minutes, which should\nbe plenty, and it is configurable via environment variable\ndocumented in the test README.md file\n\nThis does nothing to the invocation yet to ensure we can get a\ncore dump.\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Neil Horman \nMergeDate: Fri Sep 11 19:12:58 2026\n(Merged from https://github.com/openssl/openssl/pull/32424)", "completion": "Add a watchdog timeout to the C tests built with testutil/main"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nBase backups reported checksum failures to pg_stat_database only for\nfiles with more than one failing page. Commit 6b9e875f728 placed the\nreport inside the block emitting the per-file summary WARNING, which\nwas skipped for a single failure. As a result, a backup failing on\nfiles with one corrupted page each left checksum_failures untouched.\n\nTo fix, emit the per-file summary and the pgstat report for any\nnon-zero failure count. The end-of-backup total WARNING had the same\noff-by-one and is now also emitted for a single failure.\n\nAuthor: Zsolt Parragi \nReviewed-by: Nazir Bilal Yavuz \nDiscussion: https://postgr.es/m/CAN4CZFN+Bi6XmaH8zOdMWjoycYFx9nKtOr+dzQf0o-UQ+Rdqmw@mail.gmail.com\nBackpatch-through: 14", "completion": "Report single-page checksum failures in pg_stat_database"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf we manage to have a test crash, let's get the core and\nbinary in the artifacts\n\nI mostly want this for https://github.com/openssl/openssl/pull/32424\nbut it has other uses.\n\nReviewed-by: Neil Horman \nReviewed-by: Norbert Pocs \nMergeDate: Fri Sep 11 19:22:23 2026\n(Merged from https://github.com/openssl/openssl/pull/32425)", "completion": "Add core dumps and matching binary to CI artifacts on linux"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nCommit 4e8593e7ebbb added a session ID match in ssl_get_prev_session()\nguarded by !SSL_CONNECTION_IS_TLS13(s). That macro excludes DTLS, so\nthe pre-1.3 check wrongly ran for DTLS 1.3, where legacy_session_id is\na meaningless compatibility field.\n\nOpenSSL DTLS 1.3 clients send an empty legacy_session_id, so this went\nunnoticed. Peers that send a non-empty one (e.g. wolfSSL) tripped the\nmismatch and were refused resumption. Use SSL_CONNECTION_IS_VERSION13(s),\nwhich covers both TLS 1.3 and DTLS 1.3.\n\nAdd a DTLS 1.3 TLSProxy test that injects a mismatching\nlegacy_session_id and confirms the server still resumes.\n\nAssisted-by: Claude:claude-opus-4-8\nReviewed-by: Matt Caswell \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 21 18:24:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32435", "completion": "Skip the legacy session ID check for DTLS 1.3 resumption"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nreduce_outer_joins() turns a LEFT JOIN into an ANTI JOIN when some Var\nthat an upper qual requires to be NULL is actually non-nullable in any\nmatching row. When that holds, only null-extended (unmatched) rows\ncan satisfy the upper qual, which is exactly anti-join semantics.\nUntil now we recognized such a Var as non-nullable only when the\njoin's own clauses were strict for it, or when it was defined NOT NULL\nby table constraints.\n\nThis patch allows strict quals applied within the RHS subtree to serve\nas the proof as well. Because such quals hold for every row the RHS\nemits, they hold for every matching row, so a Var they force non-null\ncan become NULL above the join only by null-extension.\n\nTo avoid re-walking the jointree at decision time, the first pass of\nthe reduce-outer-joins process gathers these proving quals into its\nper-subtree state, alongside nullable_rels. The second pass then\nproves non-nullness from the RHS subtree's collected quals together\nwith the join's own ON quals. As before, the reduction fires only\nwhen the proven, forced-null Var belongs to the RHS of the join.\n\nAuthor: Richard Guo \nReviewed-by: wenhui qiu \nDiscussion: https://postgr.es/m/CAMbWs49H9khf+1GwyzD0TYaks6cE-OU+1mbUiOn3gZSoBiO7zg@mail.gmail.com", "completion": "Reduce LEFT JOIN to ANTI JOIN using quals within the RHS subtree"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nreduce_outer_joins() already recognizes that a LEFT JOIN is really an\nanti-join when an upper qual forces a nullable-side Var to be NULL but\nthat Var is provably non-null in every row the nullable side emits.\nOnly null-extended rows can then satisfy the qual, so the matched rows\nall drop out and JOIN_LEFT becomes JOIN_ANTI.\n\nThe same reasoning applies to a FULL JOIN. If a forced-null Var on\none side is proven non-null, every row where that side is present,\nmatched or not, has the Var non-null and is dropped by the qual. Only\nthe rows where that side was null-extended survive, which is an\nanti-join that keeps the other side's unmatched rows.\n\nWhen the proven Var is on the RHS, the surviving LHS rows are already\nthe left input, so this is a plain JOIN_ANTI. When it is on the LHS,\nthe surviving RHS rows must become the left input, so we tag the join\nJOIN_RIGHT_ANTI and let the existing input-switching step, the one\nthat flips JOIN_RIGHT to JOIN_LEFT, normalize it to JOIN_ANTI. Unlike\nthe LEFT JOIN case, the join's own ON quals cannot serve as proof\nhere, because they do not hold for the unmatched rows the proof must\ncover.\n\nReducing the full join this way also lets qual constraints reach its\ninputs. reduce_outer_joins_pass2() passes nothing down through a\nJOIN_FULL, but it does pass the join's own quals down through the\nresulting JOIN_ANTI, so outer joins below it can now be reduced too.\nThat is sound for the same reason it is for any anti-join: a row that\na lower join null-extends cannot satisfy those quals, so it can never\nmatch, and removing it does not change which rows the anti-join emits.\n\nThe proof that a forced-null Var is non-null, from the quals that hold\nfor every row a subtree emits (optionally plus extra quals the caller\nsupplies) or from a NOT NULL constraint, is factored into\nforced_null_var_is_nonnullable() and shared by the LEFT and FULL\npaths.\n\nAuthor: Richard Guo \nReviewed-by: wenhui qiu \nDiscussion", "completion": "Reduce FULL JOIN to ANTI JOIN"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nreduce_outer_joins() recognizes \"WHERE b.z IS NULL\" above an outer\njoin as an anti-join condition, but not the whole-row \"WHERE b IS\nNULL\", which is a natural way to ask for an anti-join without naming a\nspecific column. Teach it to recognize the whole-row form too.\n\nA row that the join null-extends has all of b's columns set to NULL,\nso it satisfies \"b IS NULL\". A matched row satisfies the test only if\nits columns happen to be all NULL. Hence proving any one column of b\nnon-null in matching rows rules out every matched row, leaving only\nnull-extended rows: exactly anti-join semantics. This mirrors the\nsingle-column case, and the same proofs apply: a NOT NULL table\nconstraint, a strict join clause (for LEFT joins), or strict quals\nwithin the relation's subtree. Because any one column suffices, the\nwhole-row test reduces in a strict superset of the cases a\nsingle-column test does.\n\nTo implement this, find_forced_null_vars() now reports a whole-row Var\ntested with row-format IS NULL as a varattno-zero entry meaning that\nall of the relation's columns are forced null. Row-format tests on\nordinary composite-type columns remain excluded, since such a test\ndoes not force the column null: it is also true when the column is a\nnon-null row whose fields are all NULL. The proof functions in\nreduce_outer_joins() treat a whole-row entry accordingly: it is\nrefuted by proving any one column of its relation non-null. A match\non the whole-row attribute itself proves nothing, because a non-null\ncomposite datum can still have all columns NULL, so the per-column\nmatching now explicitly excludes that attribute.\n\nAuthor: Richard Guo \nReviewed-by: wenhui qiu \nDiscussion: https://postgr.es/m/CAMbWs49H9khf+1GwyzD0TYaks6cE-OU+1mbUiOn3gZSoBiO7zg@mail.gmail.com", "completion": "Reduce outer joins to anti joins for whole-row IS NULL tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nfind_nonnullable_rels() and find_nonnullable_vars() declined to look\nthrough a NullTest with argisrow set, treating row-format IS NOT NULL\nas proving nothing. But such a test returns FALSE, not TRUE, both\nwhen the composite datum is NULL and when any of its fields is NULL,\nso its truth implies a non-null input just as the plain test does.\nThat is the only property strictness detection relies on, so the\nargisrow restriction can simply be dropped.\n\nThis lets \"a LEFT JOIN b ... WHERE b IS NOT NULL\" reduce to an inner\njoin, the IS NOT NULL counterpart of the whole-row anti-join reduction\nin the preceding commit. make_outerjoininfo() likewise picks up such\ntests when it computes join strictness for outer-join ordering.\nRow-format tests on composite-type columns now also prove those\ncolumns non-null, which can feed the anti-join proofs.\n\nThe stronger implication of a row-format test, that every field of the\nrow is non-null, remains unexploited: a whole-row Var reported by\nfind_nonnullable_vars() promises only a non-null datum, since the same\nentry can arise from contexts that are merely strict at the datum\nlevel, such as record comparisons.\n\nAuthor: Richard Guo \nReviewed-by: wenhui qiu \nDiscussion: https://postgr.es/m/CAMbWs49H9khf+1GwyzD0TYaks6cE-OU+1mbUiOn3gZSoBiO7zg@mail.gmail.com", "completion": "Relax strictness detection for row-format IS NOT NULL tests"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nswitch/case and goto labels v9.0.1481 and similar patches\nfrom auto-N/A.\nBlacklist as much as possible to auto-N/A later crypt patches.\n\nHunks without header in \"*.h\" is valid if only littered with #ifdefs\nor change is isolated to 1st line\nbut \"src/feature.h\" should be mostly N/A\nafter Nvim removed \"FEAT_\" guards.\nWonder if certain patches with only \"*.h\" changes were mistakenly\nmarked N/A.", "completion": "build(vim-patch): n/a docs from 9.0.1481, keep hunks without header"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDeclare a zero payload length and supply AAD while deliberately omitting\nthe payload Update. Check that streaming and one-shot Final generate the\nsame tag, accept the correct tag, and reject a modified tag for every\navailable built-in CCM cipher.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 10:04:28 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "test: cover CCM empty Final without a payload Update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDeclare a zero payload length and supply AAD while deliberately omitting\nthe payload Update. Check that streaming and one-shot Final generate the\nsame tag, accept the correct tag, and reject a modified tag for every\navailable built-in CCM cipher.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 10:00:13 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "test: cover CCM empty Final without a payload Update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDeclare a zero payload length and supply AAD while deliberately omitting\nthe payload Update. Check that streaming and one-shot Final generate the\nsame tag, accept the correct tag, and reject a modified tag for every\navailable built-in CCM cipher.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:57:47 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "test: cover CCM empty Final without a payload Update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDeclare a zero payload length and supply AAD while deliberately omitting\nthe payload Update. Check that streaming and one-shot Final generate the\nsame tag, accept the correct tag, and reject a modified tag for every\navailable built-in CCM cipher.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:54:30 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "test: cover CCM empty Final without a payload Update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nDeclare a zero payload length and supply AAD while deliberately omitting\nthe payload Update. Check that streaming and one-shot Final generate the\nsame tag, accept the correct tag, and reject a modified tag for every\navailable built-in CCM cipher.\n\nAssisted-by: Codex:gpt-5.6-sol\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Fri Aug 21 09:37:18 2026\nMerged-from: https://github.com/openssl/openssl/pull/32427", "completion": "test: cover CCM empty Final without a payload Update"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nReorderBufferProcessTXN() opens every relation referenced by a\nTRUNCATE change. When RelationIsLogicallyLogged() returns false,\nit skips the relation without releasing the reference acquired\nby RelationIdGetRelation().\n\nLooking at the in-core code paths building XLOG_HEAP_TRUNCATE records,\nno relation OIDs would be included if they do not satisfy\nRelationIsLogicallyLogged(). One pattern that could go through is if a\ntable is switched to SET UNLOGGED, but that would not be reachable in\npractice as the decoding happens after a historical snapshot is taken,\nso the relation should still be valid.\n\nThis is a defense-in-depth measure in practice, and we tend to be\ncareful about how Relations are handled when sending changes to output\nplugins, so backpatch all the way down.\n\nAuthor: Chao Li \nReviewed-by: Xuneng Zhou \nDiscussion: https://postgr.es/m/7DD65D03-3B5A-43B2-99AD-8E6AF5372BAB@gmail.com\nBackpatch-through: 14", "completion": "Fix relcache reference leak when decoding TRUNCATE"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npsql_scan_slash_command() builds the command name in a local\nPQExpBufferData and returns the buffer's data pointer to its caller. If\neither the initial allocation or a later enlargement failed, that data\npointer could be the static PQExpBuffer OOM buffer rather than malloc-owned\nstorage. HandleSlashCmds() could then eventually pass it to free(), causing\nundefined behavior.\n\nDetect a broken command-name buffer before returning it, report OOM, and\nreturn NULL instead. Teach HandleSlashCmds() to treat a NULL command name\nas a command error before trying to compare or dispatch it.\n\nBackpatch to all supported versions.\n\nReported-by: Junwang Zhao \nAuthor: Fujii Masao \nReviewed-by: Chao Li \nReviewed-by: Junwang Zhao \nDiscussion: https://postgr.es/m/CAHGQGwEh3R3=1tx_a5=fTDJ+ycuwxWMEn6bG_Yt4B5P+hE7AVw@mail.gmail.com\nBackpatch-through: 14", "completion": "psql: Avoid returning oom_buffer from psql slash command scanner"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npsql_scan_slash_option() builds option text in a local PQExpBufferData\nand returns the buffer's data pointer to its caller. If either the initial\nallocation or a later enlargement failed, that data pointer could be\nthe static PQExpBuffer OOM buffer rather than malloc-owned storage.\nThe callers could then eventually pass it to free(), causing undefined\nbehavior.\n\nDetect a broken option buffer before returning it, report OOM, and return\nNULL instead. Also avoid evaluating a backtick substitution when the option\nbuffer is already broken, since doing so could otherwise touch the static\nOOM buffer.\n\nThis keeps the existing NULL-return convention for slash options. Callers\nare not generally changed to distinguish OOM from no option.\n\nBackpatch to all supported versions.\n\nReported-by: Junwang Zhao \nAuthor: Fujii Masao \nReviewed-by: Chao Li \nReviewed-by: Junwang Zhao \nDiscussion: https://postgr.es/m/CAHGQGwEh3R3=1tx_a5=fTDJ+ycuwxWMEn6bG_Yt4B5P+hE7AVw@mail.gmail.com\nBackpatch-through: 14", "completion": "psql: Avoid returning oom_buffer from psql slash option scanner"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\npsql_scan_slash_option() returns a malloc'd string, but \\getresults,\n\\gset in pipeline mode, \\restrict, and \\unrestrict did not free it\nafter consuming or copying the value.\n\nFree these option strings after use.\n\nBackpatch to all supported versions. In v17 and older, only \\restrict\nand \\unrestrict are affected, so those branches need only that part of\nthe fix.\n\nAuthor: Fujii Masao \nReviewed-by: Chao Li \nDiscussion: https://postgr.es/m/CAHGQGwEh3R3=1tx_a5=fTDJ+ycuwxWMEn6bG_Yt4B5P+hE7AVw@mail.gmail.com\nBackpatch-through: 14", "completion": "psql: Fix psql slash option leaks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nVim9script has incompatible lambda syntax to support argument types.\nTarget v9.1.0270.", "completion": "build(vim-patch): vim9 parse_argument_types is n/a"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRESOURCE_COMPLETED_BEFORE_PRODUCING_VALUE had no guide, no JSDoc on\nRxResourceOptions.stream, and — since the code was positive rather\nthan negative — could never get an auto-linked docs page even if one\nexisted. Flip it to -991, add the NG0991 reference page, and document\nthe \"stream must emit a value or an error before completing\"\nrequirement on stream's JSDoc and in the RxJS interop guide.\n\nAlso documents and tests that an unguarded template read of an\nerrored resource's .value() propagates to the global ErrorHandler,\nand recommends guarding with .hasValue() as defense in depth.\n\nhttpResource can throw the same error, but for a different reason:\nits internal request Observable isn't something app code writes\ndirectly, so an empty completion there is almost always an\nHttpInterceptor swallowing the response (catchError(() => EMPTY))\nrather than a stream authored in the resource() call itself. The page\ncovers both APIs with guidance matched to what's actually going on\nfor each.\n\n(cherry picked from commit 8975b4346d5d3a4b9ed5a7c34026fe0a824ed0ab)", "completion": "docs: add NG0991 error page and document rxResource's completion contract"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nRESOURCE_COMPLETED_BEFORE_PRODUCING_VALUE had no guide, no JSDoc on\nRxResourceOptions.stream, and — since the code was positive rather\nthan negative — could never get an auto-linked docs page even if one\nexisted. Flip it to -991, add the NG0991 reference page, and document\nthe \"stream must emit a value or an error before completing\"\nrequirement on stream's JSDoc and in the RxJS interop guide.\n\nAlso documents and tests that an unguarded template read of an\nerrored resource's .value() propagates to the global ErrorHandler,\nand recommends guarding with .hasValue() as defense in depth.\n\nhttpResource can throw the same error, but for a different reason:\nits internal request Observable isn't something app code writes\ndirectly, so an empty completion there is almost always an\nHttpInterceptor swallowing the response (catchError(() => EMPTY))\nrather than a stream authored in the resource() call itself. The page\ncovers both APIs with guidance matched to what's actually going on\nfor each.", "completion": "docs: add NG0991 error page and document rxResource's completion contract"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nReimplemented 3a19987a87f393d93", "completion": "CVE-2026-6276: stale custom cookie host causes cookie leak"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nBased on b4024bf808bd558026fdc6\n\nImported Curl_url_same_origin() from 32a513e180ce83d5e9b708 (and edited)", "completion": "CVE-2026-6429: netrc credential leak with reused proxy connection"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nBased on c1cfdf59acbaf9504c45 (edited)", "completion": "CVE-2026-7168: cross-proxy Digest auth state leak"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis started from a real production crash trace:\n\n TypeError: Cannot read properties of null (reading 'nextSibling')\n\nTraced through a minified bundle back to siblingAfter() in\npackages/core/src/hydration/node_lookup_utils.ts. It walks forward a\nfixed number of DOM siblings during hydration, based on how many the\nserver rendered. Its only guard, validateSiblingNodeExists(), is\ngated behind ngDevMode and stripped from production builds. If the\nclient DOM has fewer real siblings than the server-serialized data\nexpects — client/server render diverged, or something outside\nAngular (a browser extension, an injected script) removed a node —\nthe loop ran fully unguarded in production: currentNode went null\npartway through, and the next iteration's currentNode.nextSibling\nthrew a raw, uncoded TypeError instead of a coded, debuggable one.\n\nReproduced first, not just theorized: added a test that server-\nrenders a @for loop with 3 items, removes 2 of them before hydration\nruns, and confirmed it actually throws that exact TypeError against\nthe original code before touching anything.\n\nFix: add a null check at the top of the loop, matching the pattern\nalready used for the existing NG0500/NG0502 hydration checks in\nelement.ts — the dev-mode check runs first as before (a no-op in\nproduction), and the new check is a pure safety net that only fires\nonce that dev-mode check has already been compiled away. In dev mode\nthis is provably dead code, so nothing about dev behavior changes.\nCoded as NG0501 (HYDRATION_MISSING_SIBLINGS, already existed).\n\nWhile investigating, found and fixed two more call sites with the\nexact same shape of bug — a dev-only check that leaves production\ncompletely unguarded:\n\n- navigateToNode() (same file): walks an explicit \"firstChild /\n nextSibling\" navigation path recorded for nodes that can't rely on\n simple sibling-walking (e.g. content right after an \n slot). Its only guard was also ngDevMode-only. Added the same\n production safety net,", "completion": "fix(core): throw coded RuntimeErrors instead of crashing when hydration/rendering can't find an expected DOM node"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n'local $/ = undef' leaks into OpenSSL::Test::run(), which then\nemits a bare \"# \" that glues onto the following 'ok' line.\nScope the slurping properly.\n\n'pkeyutl -verifyrecover' outputs binary on stdout; redirect it.\n\nFixes: https://github.com/openssl/openssl/issues/32428\nAssisted-by: Pi:moonshotai/kimi-k3\nSigned-off-by: Richard Levitte \nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:20:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32429", "completion": "test: fix TAP stream corruption in three test recipes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n'local $/ = undef' leaks into OpenSSL::Test::run(), which then\nemits a bare \"# \" that glues onto the following 'ok' line.\nScope the slurping properly.\n\n'pkeyutl -verifyrecover' outputs binary on stdout; redirect it.\n\nFixes: https://github.com/openssl/openssl/issues/32428\nAssisted-by: Pi:moonshotai/kimi-k3\nSigned-off-by: Richard Levitte \nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:20:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32429\n(cherry picked from commit 936250eef1c319c905af85639dcc2e3f67712f94)", "completion": "test: fix TAP stream corruption in three test recipes"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nEspecially important if reading cookies from HTTP headers, which is a\nstyle we discourage.\n\nReported-by: accl on hackerone\nCloses #22621", "completion": "docs: clarify that cookies need domain set to match"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit e484b0eea6 made InvalidateConstraintCacheCallBack() pfree an\nentry's FastPathMeta to plug a leak, but that breaks the rule stated\natop the callback: entries may have active references at invalidation\ntime, so we mark them invalid rather than removing them.\n\nThe metadata is subject to the same rule. ri_FastPathCheck() and\nri_FastPathBatchFlush() copy riinfo->fpmeta into a local, and\nri_FastPathFlushArray() additionally takes FmgrInfo pointers into it\nbefore its \"walk all matches\" loop. That loop runs\nindex_getnext_slot(), ri_LockPKTuple(), and user-supplied cast and\nequality functions, any of which can accept invalidation messages, and\na user function that performs DDL triggers one deliberately, no\nconcurrency required. The callback then freed the object still in use,\nso the loop read freed memory and called through FmgrInfos in it.\n\nFix by unlinking the metadata from the entry, so the next check\nrebuilds it as before, but deferring the actual free to AtEOXact_RI(),\nwhich runs from CommitTransaction() / PrepareTransaction() /\nAbortTransaction() with no RI check on the stack. Detached objects\nare chained through a new next_dead field and released there.\n\nThe queue holds a few kB per detached object until the transaction\nends, which only affects transactions that interleave DDL with\nFK-checking DML. That seems clearly preferable to a use-after-free.\n\nUnlinking alone is not enough for the multi-column path.\nri_FastPathFlushLoop() calls build_index_scankeys() once per buffered\nrow, and that function re-read riinfo->fpmeta each time. A cast\ninvoked for one row can accept an invalidation that clears the field,\nso the next row found NULL there. Pass the metadata down from\nri_FastPathBatchFlush() instead, as the array path already did, so one\nreference covers the whole batch. That is only safe because of the\ndeferred release above; latching without it would turn the NULL\ndereference into a use-after-free.\n\nReported-by: Jacob Brazeal (o", "completion": "Don't free fast-path FK metadata from the inval callback"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nri_populate_fastpath_metadata() copies the cast and equality FmgrInfos\ninto the cached FastPathMeta with fn_mcxt set to TopMemoryContext, the\ncontext active at the copy. fn_mcxt is scratch space for the called\nfunction: record_eq(), and the record I/O functions generally, allocate\ntheir per-call cache there and keep a pointer to it in fn_extra.\n\nBecause that scratch is in TopMemoryContext, it outlives the metadata.\nWhen the metadata is discarded on invalidation, whatever the cast and\nequality functions cached is left behind, with nothing pointing at it.\nEach subsequent repopulation allocates afresh, so a session that\nrepeatedly invalidates a foreign key constraint grows TopMemoryContext\nwithout bound.\n\nGive the metadata its own context for the FmgrInfos' fn_mcxt and delete\nit along with the metadata, so the cached scratch is freed with the\nFmgrInfos that point at it. Since the preceding commit defers release\nof the metadata to AtEOXact_RI(), the context is deleted there rather\nthan in InvalidateConstraintCacheCallBack().\n\nThe context deliberately is not reset while the metadata is in use.\nfn_extra points into fn_mcxt, so resetting it would leave those\npointers dangling; the next call would find fn_extra non-NULL and read\nfreed memory. fmgr_info_copy() zeroing fn_extra in the copy is the\nsame invariant seen from the other side. Nothing accumulates in the\ncontext during use in any case: record_eq() and friends allocate only\nwhen fn_extra is NULL and reuse the cache afterwards.\n\nReported-by: Noah Misch \nReviewed-by: Ayush Tiwari \nDiscussion: https://postgr.es/m/20260705210533.ee.noahmisch@microsoft.com\nDiscussion: https://postgr.es/m/CA+HiwqFFB6vzx8v3t2=rbNYyxMistLf5kkJfqzJ81nadFyLrxA@mail.gmail.com\nBackpatch-through: 19", "completion": "Give RI fast-path cached FmgrInfos their own memory context"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nAs documented and as it does for other methods.\n\nDifficult to test since it needs a successful kerberos ticket.\n\nReported-by: sdgh179 on github\nFixes #22610\nCloses #22622", "completion": "http: custom Authorization: header overrides Negotiate"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf a recipe played with $/ (slurp or paragraph mode), the pipe read\nwould misbehave and emit a bare \"# \" prefix, or prefix only the\nfirst line of a multi-line read, risking TAP stream corruption.\n\nFixes: https://github.com/openssl/openssl/issues/32428\nAssisted-by: Pi:moonshotai/kimi-k3\nSigned-off-by: Richard Levitte \nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:20:36 2026\nMerged-from: https://github.com/openssl/openssl/pull/32429", "completion": "test framework: always read child output line by line in run()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nIf a recipe played with $/ (slurp or paragraph mode), the pipe read\nwould misbehave and emit a bare \"# \" prefix, or prefix only the\nfirst line of a multi-line read, risking TAP stream corruption.\n\nFixes: https://github.com/openssl/openssl/issues/32428\nAssisted-by: Pi:moonshotai/kimi-k3\nSigned-off-by: Richard Levitte \nReviewed-by: Mounir Idrassi \nReviewed-by: Nikola Pajkovsky \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:20:36 2026\nMerged-from: https://github.com/openssl/openssl/pull/32429\n(cherry picked from commit 4fb28c19f5e2e9b9139c603b224a7142996f7ada)", "completion": "test framework: always read child output line by line in run()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(Menu): upgrade dependencies for unique popup ids\n\n* test(Layout): update Menu id snapshots\n\n* test: update dependent Menu id snapshots\n\n* test(Dropdown): update semantic Menu id snapshot", "completion": "fix(Menu): upgrade dependencies for unique popup ids"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nBackport of #70224, which landed in main as 1c2b0575ed with a feat\ncommit and so is only eligible for minor.\n\nadev deploys main to next.angular.dev and the stable release branch to\nangular.dev, so the mascot is live on next but not on the site itself.\nTyped as a refactor here so it can ride a patch. The file is byte\nidentical to the one that landed in main.", "completion": "refactor(docs-infra): add Angie to the roadmap illustration"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`routing.svg` and `directives.svg` each carry leftover text after a\n`stroke-miterlimit` attribute, which has made them invalid XML since the\nangular.dev import. They render only because decorative headers inline\nthem into the page, where the HTML parser turns the leftovers into empty\nattributes, but the files fail anywhere they are parsed as XML,\nincluding when served directly as `image/svg+xml`.\n\nNeither drops anything from the drawing. The `directives.svg` leftover\nrepeats a path the file already declares.\n\n(cherry picked from commit f35a3961c422e8d26892af21672841597e00486f)", "completion": "fix(docs-infra): remove stray tokens from adev illustrations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`routing.svg` and `directives.svg` each carry leftover text after a\n`stroke-miterlimit` attribute, which has made them invalid XML since the\nangular.dev import. They render only because decorative headers inline\nthem into the page, where the HTML parser turns the leftovers into empty\nattributes, but the files fail anywhere they are parsed as XML,\nincluding when served directly as `image/svg+xml`.\n\nNeither drops anything from the drawing. The `directives.svg` leftover\nrepeats a path the file already declares.", "completion": "fix(docs-infra): remove stray tokens from adev illustrations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAvoid the leak by unsubscribing from the profiler when the performance track is disabled.\nAdditionally, drop the duplicated performance track state flag.", "completion": "refactor(devtools): unsubs from profiler when the perf track is disabled"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Mounir Idrassi \nReviewed-by: Simo Sorce \nMergeDate: Thu Sep 10 19:05:26 2026\n(Merged from https://github.com/openssl/openssl/pull/31636)\n\n(cherry picked from commit 2564382c0bfd5c8d5cfb28671457878ee61ed6df)", "completion": "Documentation for X509V3_EXT_nconf and X509V3_EXT_nconf_int"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nReviewed-by: Mounir Idrassi \nReviewed-by: Simo Sorce \nMergeDate: Thu Sep 10 19:05:26 2026\n(Merged from https://github.com/openssl/openssl/pull/31636)", "completion": "Documentation for X509V3_EXT_nconf and X509V3_EXT_nconf_int"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nrepack_is_permitted_for_relation() uses pg_class_aclcheck_ext()\nto silently skip a concurrently-dropped relation. That's wrong\nfor a caller that may already hold a lock on the relation whose\nACL is checked, where missing a relation is not fine, and it\nmakes the single-relation REPACK and CLUSTER cases more brittle.\nSo only detect a missing relation where that's expected,\nfollowing the fix for vacuum_is_permitted_for_relation() in\ncommit 824d5f6241ea.\n\nThe new already_locked behavior is limited to get_tables_to_repack()\nand get_tables_to_repack_partitioned(). All other callers of\nrepack_is_permitted_for_relation() hold a lock on the relation\nthat prevents it from being concurrently dropped, so this commit\nalso adds an assertion to that effect.\n\nWhile at it, update the comment in RangeVarCallbackMaintainsTable to\nalso mention REPACK.\n\nAuthor: Bharath Rupireddy \nBackpatch-through: 19\nDiscussion: https://www.postgresql.org/message-id/CALj2ACX3pyuRS8%2B%2B6L20cJUMRTf_qbbVp69J1btJ3y6%3D77e5gw%40mail.gmail.com", "completion": "Tighten ACL check in repack_is_permitted_for_relation()"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA foreign join planning hook now considers a (foreign-table x function-RTE)\nINNER join as a push-down candidate when the function expression is\nIMMUTABLE and otherwise shippable. The remote query absorbs the function\ncall as a FROM-list item (e.g. unnest(...) AS f(c1, c2, ...)), so the\nforeign side returns only rows that match the function-produced set and the\njoin executes entirely on the remote.\n\nAn IMMUTABLE function gives the same result on any server, so the same\nfunction RTE can be a push-down candidate for several distinct foreign\nservers without semantic risk. To keep the planner state consistent\nacross those independent attempts, the per-call stub fpinfo for the\nfunction side lives on the joinrel's PgFdwRelationInfo (new\nouter_func_fpinfo / inner_func_fpinfo), never on the function rel itself,\nand the function side is detected via rtekind rather than fdw_private.\n\nset_foreign_rel_properties() propagates fdwroutine onto a joinrel that\npairs a foreign rel with an RTE_FUNCTION rel so GetForeignJoinPaths gets\ncalled; the FDW retains full control over whether to actually generate a\npath. deparseRangeTblRef and deparseColumnRef gain a FUNCTION-RTE branch\nthat emits the function expression and resolves Vars to the generated\ncolumn aliases.\n\nDiscussion: https://postgr.es/m/e3af56f9b2f1bd9fdf12aff6ca25b18d%40postgrespro.ru\nAuthor: Alexander Pyhalov ", "completion": "postgres_fdw: push down FUNCTION RTE into foreign joins"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked from 308adae518b9f3f7057 (which is the fix from the 8.20.X\nbranch) and edited. Fixed differently than official patch due to lack of\nCurl_creds", "completion": "CVE-2026-8458: wrong reuse for different services"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFixed differently than official patch due to lack of Curl_creds", "completion": "CVE-2026-8458: wrong reuse for different services"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nA deadly signal arriving during teardown can kill Nvim while it is\npreserving swapfiles. `os_exit()` ignores deadly signals via\n`signal_reject_deadly()`, but `signal_teardown()` => `uv_signal_stop()`\nresets them to the default behavior, so SIGHUP arriving after that\nkills the process:\n\n [Process exited 129] // 128 + SIGHUP\n\nThis is a race when closing a pty: kernel sends SIGHUP to foreground\nprocess group *and* the reads return EOF, so `chanclose()` on a TUI job\nprepares to exit twice. This means it is unpredictable whether Nvim\nexits 1 or is terminated.\n\nSolution:\nIgnore deadly signals once the watchers are closed. Only SIGKILL\ninterrupts it now.", "completion": "fix(lifecycle): late signal kills Nvim mid-teardown"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFix implemented differently due to lack of Curl_creds - and the original\nfix is a larger netrc retake.\n\nTest 1304 extended in similar spirit as in the original patch.", "completion": "CVE-2026-8926: password leak with netrc and user in URL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:11:10 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:10:52 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:10:35 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:10:00 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:09:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nBoth msblob2obj_decode() and pvk2obj_decode() computed an\nattacker-influenced buffer size (from `bitlen`, or from\n`saltlen + keylen`) and passed it to BUF_MEM_grow() without an\nupper bound.\n\nResolves #31684\n\nFixes: f40c5f2c53b9 \"PROV & STORE: Make the 'file:' store loader understand more binary formats\"\nFixes: 0f5493e60b9e \"storemgmt: Validate msblob length before buffer allocation\"\nReviewed-by: Eugene Syromiatnikov \nReviewed-by: Neil Horman \nReviewed-by: Matt Caswell \nMerge-date: Fri Aug 21 10:09:11 2026\nMerged-from: https://github.com/openssl/openssl/pull/31704", "completion": "file_store_any2obj.c: validate blob length before allocation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe --wrap link option rewrites the stdio symbols of everything linked\ninto the test binary. In --coverage builds libgcov reads and writes the\n.gcda files at process exit through fread/fwrite/fseek/ftell/fclose,\nwhich then hit the cmocka mocks with no expectations queued and make\nthe binary exit with 255 after all tests have passed. Forward calls on\nany stream other than the fake test pointers to the real functions.\n\nAssisted-by: Claude:claude-fable-5\nReviewed-by: Tomas Mraz \nReviewed-by: Bob Beck \nMerge-date: Thu Aug 20 07:50:12 2026\nMerged-from: https://github.com/openssl/openssl/pull/32431", "completion": "test: forward real stdio calls in bss_file unit test mocks"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nCherry-picked 7541ae569d82fb308a5e2d then edited", "completion": "CVE-2026-8932: incomplete mTLS config matching in conn reuse"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Crash when closing the new current window during CTRL-W_x.\nSolution: Remove a duplicate redraw of a window that should normally be\n already mark for redraw in the previous call.\n(cherry picked from commit 2cd4229d01df4176527e8e8a04eb82abcfa7e2a1)", "completion": "fix(window): crash when closing new curwin during CTRL-W_x"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem: Crash when closing the new current window during CTRL-W_x.\nSolution: Remove a duplicate redraw of a window that should normally be\n already mark for redraw in the previous call.", "completion": "fix(window): crash when closing new curwin during CTRL-W_x"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\n`signal_ignore_deadly` doesn't work for Windows, where the console still\nmay terminate Nvim during teardown (after `signal_teardown`), while it\nis already trying to exit. Besides interrupting any housekeeping we are\ndoing, it results in an unpredictable exit code (flaky tests).\n\n [Process exited -1073741510] // 0xC000013A STATUS_CONTROL_C_EXIT\n\nSolution:\nRegister our own CTRL_CLOSE_EVENT handler which \"blocks\" the signal.\nNote: if exit takes longer than 5s, Windows will consider the process\n\"hung\" and kill it anyway.", "completion": "fix(lifecycle): on Windows, CTRL_CLOSE kills Nvim mid-teardown"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nThe QUIC radix test translation unit is now large enough to exceed the\nPA-RISC 1.x short-call range. This causes the HPPA test binary to branch\ninto data and terminate with SIGILL under QEMU.\n\nBuild the HPPA CI target with -mlong-calls so calls can always reach\nlinker-generated stubs.\n\nAssisted-by: Codex:gpt-5\nSigned-off-by: Nikola Pajkovsky \nReviewed-by: Matt Caswell \nReviewed-by: Bob Beck \nMerge-date: Wed Aug 19 13:47:32 2026\nMerged-from: https://github.com/openssl/openssl/pull/32432", "completion": "ci: use long calls for HPPA cross-compilation"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nDiscussion: https://postgr.es/m/CAO6_XqrGH2NRe0oFx_00nLXra1UZezd3jbS9pgoRhZtgzHD9gg%40mail.gmail.com\nAuthor: Anthonin Bonnefoy ", "completion": "Fix compilation warning in 0ee83dd4a994"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe quick fix and completion auto-import always generated the module specifier with double quotes, ignoring the user's quote preference and the style used in the file.\n\nThe generated import now respects the `quotePreference` from the TypeScript user preferences. When the preference is `auto` (or absent), the style is inferred from the first existing import in the file, mirroring TypeScript's own behavior. Files with no imports\nkeep the previous double-quote default.\n\nFixes #67108\n\n(cherry picked from commit 0f0d52e9c1154f8db9a4a8d9d0ff73f0afdc7031)", "completion": "fix(language-service): honor quote style preference when generating imports"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe quick fix and completion auto-import always generated the module specifier with double quotes, ignoring the user's quote preference and the style used in the file.\n\nThe generated import now respects the `quotePreference` from the TypeScript user preferences. When the preference is `auto` (or absent), the style is inferred from the first existing import in the file, mirroring TypeScript's own behavior. Files with no imports\nkeep the previous double-quote default.\n\nFixes #67108", "completion": "fix(language-service): honor quote style preference when generating imports"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStore transfer state and serialization callbacks in null-prototype dictionaries, and only read values that belong to the store. This keeps special state keys from changing lookup behavior or exposing inherited cache entries.\n\nFixes #70265\n\n(cherry picked from commit 168a324cce0f133ed92953374c2510a75868b790)", "completion": "fix(core): prevent TransferState prototype pollution"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nStore transfer state and serialization callbacks in null-prototype dictionaries, and only read values that belong to the store. This keeps special state keys from changing lookup behavior or exposing inherited cache entries.\n\nFixes #70265", "completion": "fix(core): prevent TransferState prototype pollution"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ntls13_check_resumption_psk() tells tls_construct_ctos_early_data()\nwhether the resumption session can key 0-RTT, but compared the session\nversion against TLS1_3_VERSION only. A DTLS 1.3 session records\nDTLS1_3_VERSION, so the check never matched for DTLS.\n\nThe caller then fell back to the external PSK session, which is NULL\nwhen resuming, and took the suppression path: max_early_data was set to\n0, early_data_suppressed was set, and the early_data extension was not\nsent. SSL_connect() ran an ordinary handshake and returned WANT_READ\nwith an empty error queue, so SSL_write_early_data() returned 0 with\nnothing to indicate why.\n\nCompare against DTLS1_3_VERSION for DTLS, using the version1_3 idiom\nthe calling function already uses.\n\nThe helper is newer than the DTLS 1.3 work: it was factored out of\ntls_construct_ctos_early_data() after that function had been made\nversion aware, so it never picked up the DTLS case.\n\nFixes the DTLS 1.3 iterations of nine sslapitest early data tests.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 21 18:10:39 2026\nMerged-from: https://github.com/openssl/openssl/pull/32441", "completion": "Make the TLS 1.3 resumption PSK check aware of DTLS 1.3"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\ndtls_listener_cookie_hmac() fetched an EVP_MAC for \"HMAC\" on every call.\nIt runs once per cookie generation and once per verification, so a DTLS\nlistener paid a provider fetch for every ClientHello it answered.\n\nSSL_CTX already holds a pre-fetched EVP_MAC for exactly this purpose.\nSSL_CTX_new() fetches it up front and fails if it cannot, so ctx->hmac\nis always usable, and ssl_hmac_init() in ssl/t1_lib.c uses it the same\nway. Take the MAC from there instead, which also removes the local\nfetch and free.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 21 18:10:40 2026\nMerged-from: https://github.com/openssl/openssl/pull/32441", "completion": "Use the SSL_CTX cached HMAC for DTLS listener cookies"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nIf nghttpx is available but lacks QUIC support, disable the tests that\ndepend on that support.\n\nCo-authored-by: Stefan Eissing\nFixes #22609\nCloses #22624", "completion": "test_07_upload: skip tests if nghttpx lacks QUIC"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nginVacuumPostingTreeLeaves swaps a shared buffer lock for an exclusive\none when it encounters a leaf page. It neglected to re-verify whether a\npage that was initially a leaf root page became an internal page due to\na concurrent root page split (during the window when no lock was held).\nIt was therefore possible for GIN VACUUM to spuriously treat an internal\npage as a leaf page, leading to data corruption. VACUUM could miss dead\nTIDs that it was required to remove, leaving behind dangling references\nin the index.\n\nTo fix, re-verify that a leaf page is still a leaf page after an\nexclusive lock is acquired. If it isn't, drop our exclusive lock and\nacquire a shared lock so that the non-leaf root page gets processed in\nthe usual way.\n\nOversight in commit fd83c83d, which fixed a deadlock bug in GIN posting\ntree vacuuming.\n\nAuthor: Peter Geoghegan \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/CAH2-Wz=RBpJTQgvOxr6C=J04dExmFSt1E3F-r+cRTQ56hEotkg@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix GIN VACUUM posting tree root split bug."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.1.3"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\n'pkeyutl -verifyrecover' outputs binary on stdout; redirect it.\n\nFixes: https://github.com/openssl/openssl/issues/32428\nAssisted-by: Pi:moonshotai/kimi-k3\nSigned-off-by: Richard Levitte \nReviewed-by: Mounir Idrassi \nReviewed-by: Tomas Mraz \nMerge-date: Thu Aug 27 14:30:54 2026\nMerged-from: https://github.com/openssl/openssl/pull/32436", "completion": "test: fix TAP stream corruption in 20-test_pkeyutl.t"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAlready done by e615da8cb21b in master. Backpatch these particular\ncases to make other backpatches in this area safer, and to be safe for\ncallers in extensions that we don't know about.\n\nThis applies to REL_19_STABLE and REL_18_STABLE only.\n\nSuggested-by: Andres Freund \nReviewed-by: Andres Freund \nDiscussion: https://postgr.es/m/v36ssaygf7grb3qzfsjhtdzi7kqd45ds56nyuf7gi5qjml4qbb@ezmfqzmhlrs2", "completion": "pg_locale.c, unicode_case.c: use size_t for iteration."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nginbulkdelete performs pending list cleanup before it searches the entry\ntree (and any posting trees) for dead TIDs. This is necessary to avoid\nleaving behind dangling TID references that index vacuuming is required\nto remove; nothing prevents recently inserted pending list tuples from\ncontaining TIDs that VACUUM already considers dead.\n\nHowever, ginbulkdelete neglected to perform pending list cleanup on\nVACUUM's second or subsequent call. It was therefore possible for a\nVACUUM that requires multiple rounds of index vacuuming to leave behind\ndangling references.\n\nTo fix, teach ginbulkdelete to perform pending list cleanup during every\ncall. In passing, tweak some related comments in the pending list\ncleanup path to make it clear why it's safe for VACUUM to not _fully_\nempty an index's pending list.\n\nThis was arguably an oversight in commit e2c79e14, which fixed a similar\nissue where pending list cleanup by VACUUM could end early, but missed\nthis closely related problem.\n\nAuthor: Peter Geoghegan \nReviewed-by: Andrey Borodin \nDiscussion: https://postgr.es/m/CAH2-Wzmsa-RPA2Ko8A5LaGOnmbpimJ--71xkiBqwgjk3Fq8YEg@mail.gmail.com\nBackpatch-through: 14", "completion": "Fix GIN multiple-VACUUM-scans pending list bug."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nUntil 8.17.0 the --silent check lived in voutf(), so it covered every\nmessage type that went through it. 56450ce26f moved that check out to\nthe callers so that errorf() could honour --show-error, and warnf() and\nerrorf() got the check back, but notef() did not. Since then \"Note:\"\nmessages have been printed even with --silent, as long as tracing was\non.\n\nReported-by: Jace Laquerre\nFixes #22623\nCloses #22625", "completion": "tool_msgs: make notef() respect --silent"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nUp to now, if you passed a \"tied\" object to a PL/Perl operation,\nit would most likely get treated as \"undef\", since we failed to\nperform get magic on values we're passed. Tied hashes worked\npartially, in that you could read out their keys, but the values\nalways read as undef.\n\nTo fix, use hv_iterval() not HeVAL() to fetch values from perl\nhashes, and be careful to apply plperl_materialize_sv() before\ntesting SvOK() or SvROK() on any perl SV.\n\nAdd regression test cases exercising some typical usage scenarios\nfor tied objects.\n\nArguably this is a bug fix, but in view of the lack of field\ncomplaints to date, let's treat it as a new feature instead.\nThe risk/reward ratio for back-patching isn't attractive.\n\nAuthor: Andrey Rachitskiy \nReviewed-by: Tom Lane \nDiscussion: https://postgr.es/m/569769.1786901901@sss.pgh.pa.us", "completion": "Support tied Perl objects in plperl and associated contrib modules."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.2.0-next.2"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nGiST neglected to invalidate its killedItems[] array on a rescan. As a\nresult, it was just about possible for the wrong tuples from the wrong\nindex page to be LP_DEAD-marked on a rescan. The scan mistakenly\nbelieved that the previous rescan's killedItems[] were for this rescan's\ncurBlkno, causing index corruption.\n\nTo fix, bring GiST in line with nbtree and hash: call gistkillitems from\nboth gistrescan and gistendscan (the existing gistgettuple caller still\nhandles the common case where we need to LP_DEAD-mark before moving on\nto the next page). That way the scan's pending killedItems[] are passed\nto gistkillitems while they still describe items from curBlkno. When\ngistkillitems runs, it'll invalidate the array in passing (and won't\nneedlessly miss out on an opportunity to LP_DEAD-mark eligible index\ntuples). Back branches just get minimal hardening: we invalidate\nkilledItems[] at the places where the master branch gets new calls to\ngistkillitems (and we invalidate curBlkno and curPageLSN on a rescan).\n\nThe test that proved corruption on master didn't result in corruption on\nany stable branch, though only because, without commit 9c9ddf109, we'd\nclobber curPageLSN without also updating curBlkno -- which accidentally\nprevented it. Relying on gistkillitems to not LP_DEAD-mark by passing\nit a curBlkno whose curPageLSN was taken from an entirely different page\nseems like a very bad idea, which is why this issue is being treated as\na bug affecting all stable branches.\n\nAuthor: Peter Geoghegan \nReviewed-By: Andrey Borodin \nDiscussion: https://postgr.es/m/CAH2-WzmwEThnQf17Ju+t0N9_KJLsEQSXzYrFnaS2=s4KnGGrqw@mail.gmail.com\nBackpatch-through: 14", "completion": "GiST: Invalidate killed items consistently."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nA negative length is never valid here, so store an empty string\ninstead, while taking ownership of the data pointer as usual.\n\nReviewed-by: Neil Horman \nReviewed-by: Andrew Dinh \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 27 13:52:55 2026\nMerged-from: https://github.com/openssl/openssl/pull/32178", "completion": "Clamp negative lengths to 0 in ASN1_STRING_set0"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSwitches to using an object with a `null` prototype to avoid collisions.\n\n(cherry picked from commit 862a0c8ab3403242eeac3b2fb80f7cf63cf0c892)", "completion": "fix(common): avoid prototype member collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSwitches to using an object with a `null` prototype to avoid collisions.", "completion": "fix(common): avoid prototype member collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSwitches to using an object with a `null` prototype to avoid collisions.\n\n(cherry picked from commit 7ba082e08e59eadec4594ad80661d5c1ec08cb2a)", "completion": "fix(core): avoid prototype member collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSwitches to using an object with a `null` prototype to avoid collisions.", "completion": "fix(core): avoid prototype member collisions"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nSee associated pull request for more information.", "completion": "build: update cross-repo angular dependencies to v22.1.5"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit ad3c16562bba0c9895ee770f3d30604495888682)", "completion": "docs: add guidelines for Object.create(null) PRs to PR review skill"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis fix ensures that metadata is properly retained when processing\nstrict standalone component errors for improved error diagnostics.\n\n(cherry picked from commit 74b294cd51b0f73e3a71e0cd13a176b1d0f3a89f)", "completion": "fix(compiler-cli): retain metadata for strict standalone errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThis fix ensures that metadata is properly retained when processing\nstrict standalone component errors for improved error diagnostics.", "completion": "fix(compiler-cli): retain metadata for strict standalone errors"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\n`zizmor` keeps being confused by non-\"well-known\" shell designators\n`msys2 {0}`, `\\bash.exe '{0}'`, `cpa.sh {0}`, while `actionlint`\nsilently skips checking such shell code. Though it's all POSIX/bash.\nReplace the unrecognized shell designators with `bash` before running\nthe linters, to remove these blind spots.\n\nzizmor pedantic persona:\nBefore: `No findings to report. Good job! (1 ignored, 61 suppressed)`\nAfter: `No findings to report. Good job! (1 ignored)`\n\nzizmor auditor persona:\nBefore: `No findings to report. Good job! (62 ignored)`\nAfter: `No findings to report. Good job! (1 ignored)`\n\nCloses #22626", "completion": "GHA/checksrc: preprocess workflows to lint more shell code"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nForward the insertion namespace when creating dynamic component hosts inside SVG or MathML.\n\n(cherry picked from commit 2ab5ff56ded8c6246c0035d9df62a0c7fc9e1308)", "completion": "fix(core): preserve namespace for dynamic component hosts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nForward the insertion namespace when creating dynamic component hosts inside SVG or MathML.", "completion": "fix(core): preserve namespace for dynamic component hosts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nThe number of trigger arguments is stored as a smallint, but there was\nno check that the number of arguments fits with the catalog data type.\nThis could result in an invalid negative value being stored once one\ndefined more than INT16_MAX arguments, with an overflowed value stored\nin the catalogs.\n\nLooking at other catalogs that store a number of arguments, we have\nsimilar protections already in place (aggregates, functions, etc.).\n\nReported-by: Xingwang Xiang \nAuthor: Kyotaro Horiguchi \nDiscussion: https://postgr.es/m/19627-5b72a57e332e2b3f@postgresql.org\nBackpatch-through: 14", "completion": "Reject too many arguments in CREATE TRIGGER"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGuard any `OP_SET_INJECT_WORD`+`OP_WRITE` with 2 new functions\n`OP_ENGINE_TICK_ENABLE`/`OP_ENGINE_TICK_DISABLE` that enable/disable ticking\nin the QUIC engine. Otherwise, the radix test interpreter can tick between the\n2 ops and cause the peer to close the connection prematurely\n\nReviewed-by: Mounir Idrassi \nReviewed-by: Tomas Mraz \nReviewed-by: Nikola Pajkovsky \nMerge-date: Wed Aug 26 12:00:35 2026\nMerged-from: https://github.com/openssl/openssl/pull/32406", "completion": "Fix tick race in radix fault-injection scripts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nAfterTriggerEndQuery(), AfterTriggerFireDeferred(), and\nAfterTriggerSetState() bracket their firing loops with\nfiring_depth++/--. The decrement runs after the loop and is not\nprotected by PG_FINALLY, so an error caught by a subtransaction (e.g. a\nPL/pgSQL EXCEPTION block) leaves firing_depth too high. Separately,\nAfterTriggerEndSubXact() unconditionally cleared\nfiring_batch_callbacks, even if the subtransaction began while an outer\nbatch-callback loop was active.\n\nfiring_depth feeds AfterTriggerIsActive(), which the RI fast path uses\nto decide whether an FK check is running inside trigger firing and may\nbatch. A stranded firing_depth makes AfterTriggerIsActive() wrongly\nreport firing as active afterwards. This is reachable and results in\nsilent data corruption: after a caught FK-check error, an ALTER TABLE ...\nADD FOREIGN KEY whose validation runs per-row (RI_Initial_Check() having\nbailed, e.g. because RLS is enabled on the referenced table) calls\nRI_FKey_check() with AfterTriggerIsActive() wrongly true. The check is\nrouted into the batched fast path, but a utility command has no\nAfterTriggerEndQuery() to fire the flush callback. The violating row is\nnot reported, the constraint is marked validated, and the cached PK\nrelation and index leak.\n\nSave firing_depth and firing_batch_callbacks at subtransaction start and\nrestore them in AfterTriggerEndSubXact(), next to the existing query_depth\nhandling. Restoring, rather than zeroing or clearing, is required because\na subtransaction can begin and end while an outer query is firing, where\nfiring_depth is legitimately positive and firing_batch_callbacks may be\nlegitimately set.\n\nReported-by: Noah Misch \nDiscussion: https://postgr.es/m/20260705222115.be.noahmisch@microsoft.com\nBackpatch-through: 19", "completion": "Restore after-trigger firing context at subtransaction end"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* fix(List): recommend Listy in deprecation warning\n\n* Update components/list/index.tsx\n\nCo-authored-by: lijianan <574980606@qq.com>\nSigned-off-by: 高艳兵 \n\n* fix(List): escape warning text and refresh snapshots\n\n---------", "completion": "fix(List): recommend Listy in deprecation warning"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOPENSSL_LIBRARIES only exported OPENSSL_SSL_LIBRARIES,\nwhich can cause application link failures when libcrypto\ndependencies are not propagated through `target_link_libraries()`.\n\nAppend `OPENSSL_CRYPTO_LIBRARIES` to ensure consumers linking\nagainst `OPENSSL_LIBRARIES` also receive the required crypto\nlibraries.\n\nFixes: https://github.com/openssl/openssl/issues/31318\nReviewed-by: Richard Levitte \nReviewed-by: Andrew Dinh \nReviewed-by: Mounir Idrassi \nMerge-date: Thu Aug 27 09:17:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/31363\n(cherry picked from commit 1b543af5e4fb0dd81a1fe7118bd9735c61fe05b7)", "completion": "exporters/cmake/OpenSSLConfig.cmake.in: Added missing crypto libs."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOPENSSL_LIBRARIES only exported OPENSSL_SSL_LIBRARIES,\nwhich can cause application link failures when libcrypto\ndependencies are not propagated through `target_link_libraries()`.\n\nAppend `OPENSSL_CRYPTO_LIBRARIES` to ensure consumers linking\nagainst `OPENSSL_LIBRARIES` also receive the required crypto\nlibraries.\n\nFixes: https://github.com/openssl/openssl/issues/31318\nReviewed-by: Richard Levitte \nReviewed-by: Andrew Dinh \nReviewed-by: Mounir Idrassi \nMerge-date: Thu Aug 27 09:17:29 2026\nMerged-from: https://github.com/openssl/openssl/pull/31363", "completion": "exporters/cmake/OpenSSLConfig.cmake.in: Added missing crypto libs."} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 9b43e6793b0f removed the PM_STARTUP shortcut that exited the\npostmaster directly when the startup process died, routing the case\nthrough HandleChildCrash() so that children processes running during\nPM_STARTUP are cleaned up rather than orphaned.\n\nHowever, HandleChildCrash() does nothing if FatalError is already set,\nand that is exactly the case while reinitializing after a crash: a\nrelaunched startup process that dies before WAL redo starts would leave\nthe state machine stuck at PM_STARTUP, preventing the postmaster to shut\ndown.\n\nThis issue is fixed by restoring the pre-9b43e6793b0f shortcut behavior:\nif FatalError is set when the startup process crashes, signal the\nremaining children and move to PM_NO_CHILDREN, so as the postmaster can\nproperly exit with nothing orphaned. This is only reachable in v18 and\nnewer versions, the early return of HandleChildCrash() on FatalError\nbeing introduced in f0b7ab725139.\n\nThis issue has been reported on Windows, for a postmaster with its\nconsole gone. A trick to make InitPostmasterChild() fail aggressively\nwas equally able to stuck a postmaster.\n\nReported-by: Kuan-Ting Kuo \nAuthor: Zexin Li \nDiscussion: https://postgr.es/m/19623-f9bd331940be1273@postgresql.org\nBackpatch-through: 18", "completion": "Fix postmaster failing to exit when startup crashes during crash restart"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nInspired by d69bfad3fa3daf5e72331, implemented differently", "completion": "CVE-2026-11564: Native CA trust persist"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nand some small style improvements", "completion": "Unify error messages"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* docs: add Upload data version\n\n* docs: remove Upload RequestOptions.data version\n\nCo-authored-by: Cursor \n\n---------", "completion": "docs: add Upload data version"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nCommit 34a30786293 fixed an RI fast-path crash under nested C-level SPI\nby keeping batch-callback lists per after-trigger query depth. That fix\nwas incomplete: the RI fast path still tracked callback registration\nwith one global flag. Once an outer firing cycle had registered its\ncallback, the flag suppressed registration for a nested cycle, leaving\nthe nested batch to be handled by the outer callback, too late and with\nthe wrong snapshot, potentially after the ResourceOwner holding its\nrelations had gone away.\n\nNor is per-depth callback registration sufficient while the cache is\nkeyed only by constraint OID. If nested firing checks the same\nconstraint, it reuses the outer entry, combining rows that must be\nchecked in separate firing cycles.\n\nKey the cache by both constraint OID and query depth. Register a callback\nfor each depth that creates an entry, and make ri_FastPathEndBatch() flush\nand release only entries belonging to the ending depth. Add\nAfterTriggerCurrentQueryDepth() so ri_triggers.c can obtain the current\ndepth; depth -1 represents deferred firing.\n\nAdd regression coverage for nested firing through a cursor portal, whose\nresources must not outlive the nested cycle, nested firing of the same\nconstraint at different query depths, and deferred firing at query depth\n-1.\n\nReported-by: Noah Misch \nReported-by: Peter Geoghegan \nDiscussion: https://postgr.es/m/20260705222115.be.noahmisch@microsoft.com\nDiscussion: https://postgr.es/m/CAH2-Wz=D533JbF_ak_Pc8kP0FKse-ju8DnMxtjvY==yHsP4xgw@mail.gmail.com\nBackpatch-through: 19", "completion": "Track RI fast-path FK-check batches per firing cycle"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds an internal config options that allows us to enable source locations.\n\n(cherry picked from commit f3c093df24b7c87e4caee51a10a070a2baab2f34)", "completion": "refactor(compiler-cli): add compiler option for enabling source locations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nAdds an internal config options that allows us to enable source locations.", "completion": "refactor(compiler-cli): add compiler option for enabling source locations"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: postgres\nChanges:\nA sequence has no rowtype. We called\nfind_composite_type_dependencies() with InvalidOid, which is harmless\nbut pointless. Skip it.\n\nThis started to happen with commit 344d62fb9a97 in v15, which added\nthe ALTER SEQUENCE ... SET LOGGED/UNLOGGED subcommand. Before that,\nsequences were never rewritten. While this is harmless, backpatch to\nkeep the code the same on all branches, to make backpatching future\npatches a little easier.\n\nBackpatch-through: 15", "completion": "Skip bogus find_composite_type_dependencies() call on sequences"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: neovim\nChanges:\nProblem:\nAn unreplayable Visual operation does not emit a CmdAtom event. That's\nmaybe not super important, but it hints at a flaw in how `vatom`\n\"voiding\" is plumbed: `vatom.state=kVatomVoid` replaces the \"kind\", so\nthat info is lost to later parts in the lifecycle.\n\nSolution:\n- Define `VatomState` as \"flags\", so `kVatomVoid` can \"poison\"\n `vatom.state` without losing its kind flag.\n- Unify `lhs`: always report the original user input in `CmdAtom.lhs`,\n for all kinds of user actions: visual, \"translated\"/\"stuffed\" cmds,\n and dot-repeat (\".\") itself.\n- Unreplayable Visual atom emits CmdAtom with non-empty `lhs` and empty\n `keys`, like a mapping/macro composite.", "completion": "fix(cmdatom): lhs not always reported in CmdAtom #41386"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: ant-design\nChanges:\n* feat(Typography): support shimmer effect\n\n* refactor(Typography): use CSS variable helpers\n\n* refactor(Typography): simplify shimmer configuration\n\n* refactor(Typography): streamline shimmer config merging\n\n* fix(Typography): adjust shimmer animation timing\n\n* fix(Typography): refine shimmer animation and demo\n\n* feat(Typography): support separate shimmer motion and wait times\n\n* chore: update size limit\n\n* test(site): update Typography table snapshots\n\n* test(Typography): cover shimmer duration tuple", "completion": "feat(Typography): support shimmer effect"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nGuard any `OP_SET_INJECT_WORD`+`OP_WRITE` with 2 new functions `OP_ENGINE_TICK_ENABLE`/`OP_ENGINE_TICK_DISABLE` that enable/disable ticking in the QUIC engine. Otherwise, the radix test interpreter can tick between the 2 ops and cause the peer to close the connection prematurely\n\nReviewed-by: Saša Nedvědický \nReviewed-by: Norbert Pocs \nMerge-date: Wed Sep 2 06:32:35 2026\nMerged-from: https://github.com/openssl/openssl/pull/32335", "completion": "Fix tick race in radix fault-injection scripts"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe angular.dev origin was declared twice as a local `ANGULAR_DEV`\nconst and hardcoded inline in two more places. It now lives once in\n`core/constants/links.ts`, next to `ANGULAR_LINKS`.\n\n(cherry picked from commit 593f2d7e2ed548c557ad4aba43803b89f5db42fc)", "completion": "refactor(docs-infra): share the angular.dev origin constant"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe angular.dev origin was declared twice as a local `ANGULAR_DEV`\nconst and hardcoded inline in two more places. It now lives once in\n`core/constants/links.ts`, next to `ANGULAR_LINKS`.", "completion": "refactor(docs-infra): share the angular.dev origin constant"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\npoll_translate() calls ossl_quic_poll_translate_test_step_cb, a test\ninstrumentation hook whose declaration and definition both sit inside\n#ifndef OPENSSL_NO_QUIC. On master that is safe, because the whole of\npoll_translate() is inside the same guard.\n\nThis branch widens that guard to\n\n #if !defined(OPENSSL_NO_QUIC) || !defined(OPENSSL_NO_DTLS)\n\nso that SSL_poll() works for DTLS, so poll_translate() is now also\ncompiled when QUIC is disabled. The hook call came along into the wider\nregion and does not compile there.\n\nGuard the call itself. Configurations that disable QUIC, directly or by\ncascade from no-tls1_3 or no-tls, then build again.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 21 18:10:41 2026\nMerged-from: https://github.com/openssl/openssl/pull/32441", "completion": "Guard the QUIC poll test hook so no-quic builds compile"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nossl_dgram_conn_lookup_foreach() calls a struct member named foreach.\nclang-format has a built-in ForEachMacros list which contains foreach,\nand it formats anything on that list like a control statement, with a\nspace before the parenthesis. The space was therefore correct when this\ncode was written, and check-style accepted it.\n\nMaster has since set ForEachMacros explicitly, to name the OSSL_RBT_*\nmacros. Setting the option replaces the built-in list rather than adding\nto it, so foreach is no longer on it and is now formatted as an ordinary\nfunction call, with no space. That turned an already compliant line into\na check-style failure without the line itself changing.\n\ngit rebase does not run the pre-commit hooks over the commits it\nreplays, so nothing reformatted this on the way past.\n\nAssisted-by: Claude Code:claude-opus-5\nReviewed-by: Ryan Hooper \nReviewed-by: Tomas Mraz \nMerge-date: Fri Aug 21 18:10:42 2026\nMerged-from: https://github.com/openssl/openssl/pull/32441", "completion": "Reformat a foreach member call for the new ForEachMacros list"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`DiagnosticsState` carried a TODO to move off `BehaviorSubject` once\nzoneless was turned on. adev has been zoneless for a while now, with no\nzone.js dependency and an empty `polyfills` array, so the condition is\nmet and the TODO can go.\n\nBoth consumers now derive from the signal instead of subscribing. The\nConsole tab badge becomes a `computed`, and so does the code editor's\nerror list: the diagnostics are produced by a `linter()` configured with\na 400ms delay rather than arriving as a stream, so the rxjs chain was\nonly adding a further second before they were displayed. The errors box\nstays dismissable through a `linkedSignal`, which reverts as soon as the\ndiagnostics change.\n\n(cherry picked from commit 238d8bf98aaeaa9ce4ceddff26eb15aab5d013b6)", "completion": "refactor(docs-infra): hold editor diagnostics in a signal"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`DiagnosticsState` carried a TODO to move off `BehaviorSubject` once\nzoneless was turned on. adev has been zoneless for a while now, with no\nzone.js dependency and an empty `polyfills` array, so the condition is\nmet and the TODO can go.\n\nBoth consumers now derive from the signal instead of subscribing. The\nConsole tab badge becomes a `computed`, and so does the code editor's\nerror list: the diagnostics are produced by a `linter()` configured with\na 400ms delay rather than arriving as a stream, so the rxjs chain was\nonly adding a further second before they were displayed. The errors box\nstays dismissable through a `linkedSignal`, which reverts as soon as the\ndiagnostics change.", "completion": "refactor(docs-infra): hold editor diagnostics in a signal"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nLine should already have been removed in 7103a93, but neither\nhumans nor clankers caught it. tststs...\n\nPrior to this change it appears all reuse of empty cred connection was\nblocked for ntlm instead of the intended behavior of allowing\nreuse in the limited circumstance when it is the same connection used by\nthe transfer before.\n\nCloses https://github.com/curl/curl/pull/22629", "completion": "url: fix handling of empty user in ntml matching"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nFixed differently than original fix", "completion": "CVE-2026-8926: password leak with netrc and user in URL"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 3438614f5e7dd495f13a9f5823694945c18f3fa7)", "completion": "docs: warn against using in-memory-web-api in production"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nOtherwise ssl3_get_cipher_by_id() cannot work properly.\n\nReviewed-by: Richard Levitte \nReviewed-by: Nikola Pajkovsky \nMerge-date: Thu Aug 20 12:59:43 2026\nMerged-from: https://github.com/openssl/openssl/pull/32443", "completion": "cipher_overhead_test.c: Init libssl to sort the ciphers"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: eslint\nChanges:\n* fix: handle underflow in no-loss-of-precision\n\n* chore: retrigger CI\n\n* refactor: address review feedback", "completion": "feat: handle underflow in no-loss-of-precision"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n(cherry picked from commit 045746c18ce3081c5f26aabc0097dcfa1715730b)", "completion": "docs(core): clarify toObservable synchronization behavior"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`getApiNavigationItems` cast the manifest to `any` behind a TODO waiting\non #66252, which was closed without merging, so the three `any`s it\nguarded were never going away on their own.\n\nThe real `ApiManifestPackage` cannot be imported here: navigation\nentries are built as a standalone `ts_project` so the route generator\ncan consume them at build time, and it has no dependency on the app\ntree. Declaring the handful of fields this file reads gets rid of the\n`any`s without touching the build graph.\n\n(cherry picked from commit 4997521685eec564d684eb23664f0e3a5530ea83)", "completion": "refactor(docs-infra): type the API manifest in the nav entries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\n`getApiNavigationItems` cast the manifest to `any` behind a TODO waiting\non #66252, which was closed without merging, so the three `any`s it\nguarded were never going away on their own.\n\nThe real `ApiManifestPackage` cannot be imported here: navigation\nentries are built as a standalone `ts_project` so the route generator\ncan consume them at build time, and it has no dependency on the app\ntree. Declaring the handful of fields this file reads gets rid of the\n`any`s without touching the build graph.", "completion": "refactor(docs-infra): type the API manifest in the nav entries"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAccording to lightship, we can allow X448MLKEM1024 to be an approved\nhybrid kem, we just can't allow it for use in TLS1.3 (which isn't\ncurrently possible anyway, given that there is no code point for it).\nSo set FIPS_DEFAULT_PROPERTIES on this alg rather than\nFIPS_UNAPPROVED_PROPERTIES.\n\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMerge-date: Fri Aug 21 14:34:08 2026\nMerged-from: https://github.com/openssl/openssl/pull/32444", "completion": "Allow X448MLKEM1024 to be fips approved"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAccording to lightship, we can allow X448MLKEM1024 to be an approved\nhybrid kem, we just can't allow it for use in TLS1.3 (which isn't\ncurrently possible anyway, given that there is no code point for it).\nSo set FIPS_DEFAULT_PROPERTIES on this alg rather than\nFIPS_UNAPPROVED_PROPERTIES.\n\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMerge-date: Fri Aug 21 14:33:14 2026\nMerged-from: https://github.com/openssl/openssl/pull/32444", "completion": "Allow X448MLKEM1024 to be fips approved"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAccording to lightship, we can allow X448MLKEM1024 to be an approved\nhybrid kem, we just can't allow it for use in TLS1.3 (which isn't\ncurrently possible anyway, given that there is no code point for it).\nSo set FIPS_DEFAULT_PROPERTIES on this alg rather than\nFIPS_UNAPPROVED_PROPERTIES.\n\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMerge-date: Fri Aug 21 14:15:23 2026\nMerged-from: https://github.com/openssl/openssl/pull/32444", "completion": "Allow X448MLKEM1024 to be fips approved"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: openssl\nChanges:\nAccording to lightship, we can allow X448MLKEM1024 to be an approved\nhybrid kem, we just can't allow it for use in TLS1.3 (which isn't\ncurrently possible anyway, given that there is no code point for it).\nSo set FIPS_DEFAULT_PROPERTIES on this alg rather than\nFIPS_UNAPPROVED_PROPERTIES.\n\nReviewed-by: Milan Broz \nReviewed-by: Tomas Mraz \nReviewed-by: Paul Dale \nMerge-date: Fri Aug 21 14:15:07 2026\nMerged-from: https://github.com/openssl/openssl/pull/32444", "completion": "Allow X448MLKEM1024 to be fips approved"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe new home page in #63662 stopped rendering `HomeAnimationComponent`\nand its directory was left behind. The animation that runs today lives\nin `features/home/animation`, which replaced it.\n\nNothing references the class, its `adev-home-animation` selector, or any\nfile in the directory, and no stylesheet or build target pulls it in.\n\n(cherry picked from commit eb6570b06dda4252da9f3f83672c4457279f1b29)", "completion": "refactor(docs-infra): remove the orphaned home animation component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: angular\nChanges:\nThe new home page in #63662 stopped rendering `HomeAnimationComponent`\nand its directory was left behind. The animation that runs today lives\nin `features/home/animation`, which replaced it.\n\nNothing references the class, its `adev-home-animation` selector, or any\nfile in the directory, and no stylesheet or build target pulls it in.", "completion": "refactor(docs-infra): remove the orphaned home animation component"} {"prompt": "You are a git commit message writer. Given the repository and a description of the changes, write the commit message subject line.\nRespond with only the commit message, no quotes, no explanation.\n\nRepository: curl\nChanges:\nDifferent than original patch", "completion": "CVE-2026-19931: Negotiate ambient user conn reuse"}