Repository navigation

Use the combined bundle when queries may need other languages' library packs - #4184

Merged

henrymercer merged 31 commits into

mainfrom

henrymercer/per-language-pr-check-failures

Oct 6, 2026

Commits on Sep 29, 2026
- Disable per-language bundles in the file baseline PR check
  
  henrymercer
  and
  Copilot
  committed
  b5a476b
- Move `defaultSuites` to `config/db-config.ts`
  
  henrymercer
  and
  Copilot
  committed
  5e3132d
Commits on Sep 30, 2026
- Avoid per-language bundles when queries may need other languages' library packs
  
  henrymercer
  and
  Copilot
  committed
  1609a51
- Always use the combined bundle in `setup-codeql`
  
  henrymercer
  and
  Copilot
  committed
  d8b6f2a
- Fix the docs for the `languages` and `analysis-kinds` inputs of `setup-codeql`
  
  henrymercer
  and
  Copilot
  committed
  7816c33
Commits on Oct 1, 2026
- Use a new feature flag for per-language bundles
  
  henrymercer
  and
  Copilot
  committed
  87a1923
- Omit the feature flag name from the per-language bundle debug log
  
  henrymercer
  and
  Copilot
  committed
  2da0d29
- Read the `config` and `queries` inputs once in `init`
  
  henrymercer
  and
  Copilot
  committed
  a98f604
- Extract parsing of the `queries` input and the extra queries repository property
  
  henrymercer
  and
  Copilot
  committed
  a4fbe39
- Reuse the parsing of query inputs when choosing a bundle
  
  henrymercer
  and
  Copilot
  committed
  70897a7
- Explain that the `config` input can configure queries
  
  henrymercer
  and
  Copilot
  committed
  725421c
- Explain what a reason to use the combined bundle means where it's checked
  
  henrymercer
  and
  Copilot
  committed
  1bb99cb
- Check what the `config` input sets instead of exempting dynamic workflows
  
  henrymercer
  and
  Copilot
  committed
  a6cd2a5
Commits on Oct 2, 2026
- Explain why the file baseline PR check uses the combined bundle
  
  henrymercer
  and
  Copilot
  committed
  ce28f3e
- Parse lists of queries with a single function
  
  henrymercer
  and
  Copilot
  committed
  1c0814d
- Share the check of the properties that Default Setup sets in the `config` input
  
  henrymercer
  and
  Copilot
  committed
  e869836
- Parse the `config` input once
  
  henrymercer
  and
  Copilot
  committed
  113b18e
- Point to the Default Setup config schema from the per-language bundle check
  
  henrymercer
  and
  Copilot
  committed
  f6a7f00
- Merge remote-tracking branch 'origin/main' into henrymercer/per-language-pr-check-failures
  
  Copilot
  and
  henrymercer
  authored
  a47cc9f
- Merge branch 'main' into henrymercer/per-language-pr-check-failures
  henrymercer
  authored
  c275b4a
Commits on Oct 5, 2026
- Reword the JSDoc for `parseQueriesFromInput`
  
  henrymercer
  and
  Copilot
  committed
  c1e7769
- Return early from `parseQueriesFromInput` when there are no queries
  
  henrymercer
  and
  Copilot
  committed
  ac4b9b8
- Remove the `checkDefaultSetupConfig` wrapper around `checkSchema`
  
  henrymercer
  and
  Copilot
  committed
  711f3bf
- Say that the Default Setup config schema reflects what Default Setup is known to send
  
  henrymercer
  and
  Copilot
  committed
  966f3c3
- Explain that the `config` input is written to disk without merging
  
  henrymercer
  and
  Copilot
  committed
  a4a04dc
- Construct `UserConfig` objects directly in the `config-utils` tests
  
  henrymercer
  and
  Copilot
  committed
  6cb83fa
- Parse the `config` input in `init` without the `parseConfigInput` wrapper
  
  henrymercer
  and
  Copilot
  committed
  e0b8480
- Say that `parseUserConfig`'s `pathInput` may not be a file path
  
  henrymercer
  and
  Copilot
  committed
  9d3242e
- Compare `originalUserInput` with a separate object in the `config` input test
  
  henrymercer
  and
  Copilot
  committed
  8e6b600
- Describe what `parseUserConfig` accepts, returns and throws more precisely
  
  henrymercer
  and
  Copilot
  committed
  55e4091
- Explain why the `config` input test compares with a separate object
  
  henrymercer
  and
  Copilot
  committed
  12db63b

Navigation Menu

Repository navigation

Use the combined bundle when queries may need other languages' library packs - #4184

Use the combined bundle when queries may need other languages' library packs#4184
henrymercer merged 31 commits into
mainfrom
henrymercer/per-language-pr-check-failures

Commits on Sep 29, 2026

Disable per-language bundles in the file baseline PR check

Move `defaultSuites` to `config/db-config.ts`

Commits on Sep 30, 2026

Avoid per-language bundles when queries may need other languages' library packs

Always use the combined bundle in `setup-codeql`

Fix the docs for the `languages` and `analysis-kinds` inputs of `setup-codeql`

Commits on Oct 1, 2026

Use a new feature flag for per-language bundles

Omit the feature flag name from the per-language bundle debug log

Read the `config` and `queries` inputs once in `init`

Extract parsing of the `queries` input and the extra queries repository property

Reuse the parsing of query inputs when choosing a bundle

Explain that the `config` input can configure queries

Explain what a reason to use the combined bundle means where it's checked

Check what the `config` input sets instead of exempting dynamic workflows

Commits on Oct 2, 2026

Explain why the file baseline PR check uses the combined bundle

Parse lists of queries with a single function

Share the check of the properties that Default Setup sets in the `config` input

Parse the `config` input once

Point to the Default Setup config schema from the per-language bundle check

Merge remote-tracking branch 'origin/main' into henrymercer/per-language-pr-check-failures

Merge branch 'main' into henrymercer/per-language-pr-check-failures

Commits on Oct 5, 2026

Reword the JSDoc for `parseQueriesFromInput`

Return early from `parseQueriesFromInput` when there are no queries

Remove the `checkDefaultSetupConfig` wrapper around `checkSchema`

Say that the Default Setup config schema reflects what Default Setup is known to send

Explain that the `config` input is written to disk without merging

Construct `UserConfig` objects directly in the `config-utils` tests

Parse the `config` input in `init` without the `parseConfigInput` wrapper

Say that `parseUserConfig`'s `pathInput` may not be a file path

Compare `originalUserInput` with a separate object in the `config` input test

Describe what `parseUserConfig` accepts, returns and throws more precisely

Explain why the `config` input test compares with a separate object