Skip to content

chore(deps): update graphqlcodegenerator monorepo (major) - #96

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo
Open

chore(deps): update graphqlcodegenerator monorepo (major)#96
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2021 •
edited
Loading

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) 1.21.8 → 7.4.2 age confidence
@graphql-codegen/introspection (source) 1.18.2 → 6.1.0 age confidence
@graphql-codegen/typescript (source) 1.23.0 → 6.1.0 age confidence
@graphql-codegen/typescript-operations (source) 1.18.4 → 6.1.7 age confidence
@graphql-codegen/typescript-react-apollo (source) 2.3.1 → 5.0.0 age confidence

Release Notes

dotansimha/graphql-code-generator (@​graphql-codegen/cli)

v7.4.2

Compare Source

Patch Changes

  • #​10956
    cec9c1c
    Thanks @​eddeee888! - Fix dynamically-loaded plugins/presets in ESM
    builds. Previously, ESM used the bare module specifier without resolving it relative to the
    consuming project first, so a plugin only loaded if it happened to be reachable from the CLI
    package's own node_modules. Resolving it the same way the CJS build already does
    (relativeRequire.resolve(mod)) fixes that, but the resolved absolute path also has to be
    converted to a file:// URL (pathToFileURL(...).href) before being passed to import() —
    otherwise, on Windows, the loader misparses a raw path like C:\... as a c: protocol scheme and
    throws ERR_UNSUPPORTED_ESM_URL_SCHEME.

  • #​10966
    3029b60
    Thanks @​eddeee888! - Fix lifecycle hook scripts (e.g.
    hooks: { afterAllFileWrite: ['prettier --write'] } }) failing on Windows when the file paths
    passed to them contain a backslash or other POSIX shell-special character. Hook arguments were
    always quoted using POSIX single-quoting, but child_process.exec() runs through cmd.exe on
    Windows by default, which doesn't strip single quotes — so the hook script received the literal
    quote characters as part of its argument and failed to find the file. Arguments are now quoted
    per-platform: POSIX quoting stays unchanged elsewhere, and Windows arguments are wrapped in double
    quotes only when they actually need it, matching cmd.exe's own convention.

  • #​10959
    7dffaae
    Thanks @​eddeee888! - Fix the CLI reporting success (exit code 0)
    when a generates output's preset can't be resolved. The error was shown in the terminal but
    never counted toward the run's failure state, so allowPartialOutputs: false (the default) never
    took effect for this case.

v7.4.1

Compare Source

Patch Changes

  • #​10935
    fb1a7c4
    Thanks @​eddeee888! - dependencies updates:

  • #​10942
    57c3e7b
    Thanks @​eddeee888! - dependencies updates:

  • #​10942
    57c3e7b
    Thanks @​eddeee888! - Bump @graphql-tools/merge from ^9.0.6 to
    ^9.2.4.

  • #​10935
    fb1a7c4
    Thanks @​eddeee888! - Fix a Windows-specific import() failure on
    absolute paths when loading a schema/document from a .js/.cjs/.mjs file (via
    @graphql-tools/code-file-loader), and when loading modules passed to that loader's own require
    option. Node's dynamic import() rejects raw absolute Windows paths (the drive letter is parsed
    as a URL scheme). Fixed by bumping @graphql-tools/code-file-loader to 8.1.39, which contains
    the upstream fix
    (ardatan/graphql-tools#8421).

  • #​10936
    9521c0c
    Thanks @​eddeee888! - Fix watch mode's generated ignore glob
    patterns using the platform path separator (\ on Windows), which @parcel/watcher never
    matched, so generated output files were watched (and could re-trigger builds) instead of being
    ignored. Ignore patterns are now always forward-slash, as @parcel/watcher expects.

    Also fixes the test suite's TempDir.clean() helper on Windows, where rimraf.sync() rejected
    its own glob-style cleanup pattern as containing illegal path characters; now passes
    { glob: true }. This is a test-only change (tests/utils.ts is not part of the published
    package) included here since it was needed to get the suite green on Windows alongside the
    watch-mode fix.

v7.4.0

Compare Source

Minor Changes

  • #​10928
    90229a5
    Thanks @​eddeee888! - Add
    contentComparison?: 'cache-first' | 'disk' to control disk-vs-cache write comparison in watch
    mode.

    In watch mode the CLI caches the hash of the content it last wrote per file and compares new
    output against that cached hash to skip redundant writes. This assumes generated output is a pure
    function of the codegen inputs. An output whose content depends on the file's existing content
    (e.g. a preset that reads the file and rewrites part of it) breaks that assumption: if the file is
    changed on disk and codegen regenerates content identical to a previous run, the cached hash still
    matches and the write is skipped, so the on-disk change is never corrected.

    contentComparison: 'disk' opts an output into comparing the generated content against the file
    on disk instead of the in-memory record of what codegen last wrote, so the file is rewritten when
    it was changed externally. It can be set:

    • by a preset, on the GenerateOptions it returns from buildGeneratesSection, or
    • on the output config (generates[output].contentComparison) for any output, including plain
      plugin outputs without a preset.

    When both are present, the preset's value takes precedence. The default, 'cache-first', keeps
    the existing in-memory-cache behaviour for outputs that are a pure function of their inputs.

Patch Changes

  • #​10930
    448431a
    Thanks @​eddeee888! - Fix overwrite being ignored for
    preset-based generates outputs.

    A generates entry that used a preset and set overwrite (e.g.
    overwrite: { removeStaleFiles: false }) had that setting silently ignored, so in watch mode its
    generated files could still be deleted as stale.

    The CLI resolved overwrite per generated file by looking the file's path up in
    config.generates. That fails for a preset: its generates entry is keyed by the preset's
    baseOutputDir, not by any generated file's path (and a preset can emit files outside that
    directory), and the lookup additionally required a plugins key that preset entries don't have.
    Both cases fell through to the global config.overwrite (default true).

  • Updated dependencies
    [90229a5,
    448431a]:

v7.3.1

Compare Source

Patch Changes

  • #​10924
    0c8f5ba
    Thanks @​eddeee888! - Fix profiler output not being written to the
    filesystem in watch mode (--profile --watch)

    The profiler trace was only written on the non-watch code path, after the watch-mode early return,
    so a profiled watch session never produced a codegen-*.json file.

    The profiler now writes a fresh trace file after the initial run and after every rebuild, with
    each file containing only that run's events. A failed rebuild does not produce a trace and its
    events are discarded so they don't leak into the next successful run.

    The Profiler now owns its own trace lifecycle:

    • a new clear() method starts a new trace
    • a new outputName property provides the filename for the current trace (null for the noop
      profiler)
    • filename generation was removed from CodegenContext

  • Updated dependencies
    [0c8f5ba]:

v7.3.0

Compare Source

Minor Changes

  • #​10921
    58cdb31
    Thanks @​eddeee888! - Extend overwrite with
    overwrite.removeStaleFiles and overwrite.updateExistingFiles

    overwrite was being used to both remove stale files in watch mode and update existing files.
    Some plugins such as Server Preset may dynamically return files to write between watch runs (for
    performance purposes).

    The overwrite can now take an object with overwrite.removeStaleFiles and
    overwrite.updateExistingFiles fields to allow granular control over actions.

    This is not a breaking change because overwrite=true|false still works.

Patch Changes

v7.2.0

Compare Source

Minor Changes
Patch Changes

v7.1.3

Compare Source

Patch Changes

  • #​10335
    3280ace
    Thanks @​Diluka! - Fix graphql-config loading order to correctly
    detect codegen projects

    Previously, a graphql-config file like this failed:

    projects:
  default:
    schema: 'default/schema.graphql'
  project1:
    schema: 'project1/schema.graphql'
    extensions:
      codegen:
        generates:
          'project1/__generated__/types.ts':
            plugins: ['typescript']

    This is because the default project doesn't have a codegen extension, which caused previous
    logic to short circuit before reading project1's config.

    The fix reads every named project first, before reading the default project to exhaustively go
    through every single project.

v7.1.2

Compare Source

Patch Changes

v7.1.1

Compare Source

Patch Changes

v7.1.0

Compare Source

Minor Changes
Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Set noSilentErrors: true
    by default

    When multiple files match documents pattern, and there are syntax errors in some but not others,
    then the operations with errors are not included in the loaded documents list by default
    (noSilentErrors: false). This is annoying for users as there is no feedback loop during
    development.

    noSilentErrors: true is used as the default for Codegen users to make the feedback loop faster.
    It can still overriden in Codegen Config if desired.

Patch Changes

v6.3.1

Compare Source

Patch Changes
  • #​10737
    be85118
    Thanks @​eddeee888! - Fix issue where same SDL in different
    documents are ignored when handling documents vs externalDocuments

v6.3.0

Compare Source

Minor Changes

  • #​10659
    e65d303
    Thanks @​ikusakov2! - Add support for externalDocuments

    externalDocuments declares GraphQL documents that will be read but will not have type files
    generated for them. These documents are available to plugins for type resolution (e.g. fragment
    types), but no output files will be generated based on them. Accepts the same formats as
    documents.

    This config option is useful for monorepos where each project may want to generate types for its
    own documents, but some may need to read shared fragments from across projects.

Patch Changes

v6.2.1

Compare Source

Patch Changes
  • #​10618
    e804925
    Thanks @​PalmerTurley34! - Honor per-output preset
    importExtension and emitLegacyCommonJSImports config instead of always using the root config
    values.

v6.2.0

Compare Source

Minor Changes
Patch Changes

v6.1.3

Compare Source

Patch Changes

v6.1.2

Compare Source

Patch Changes
  • #​10590
    e173e11
    Thanks @​ya2s! - Fix GraphQL Config loading to forward nested
    extensions.codegen.config options when loading schemas/documents, matching codegen.ts
    behavior.

v6.1.1

Compare Source

Patch Changes

  • #​10569
    8cb7d43
    Thanks @​etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs
    are found

    Fixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.

v6.1.0

Compare Source

Minor Changes
Patch Changes

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

  • #​10468
    cb1b9d9
    Thanks @​eddeee888! - In watch mode, do not write output on failure

    Previously, on partial or full failure, watch mode still write to output. However, since the
    output'd be an empty array, it will then call removeStaleFiles internally to remove all
    previously generated files.

    This patch puts a temporary fix to avoid writing output on any failure to fix the described
    behaviour.

    This also means the config.allowPartialOutputs does not work in watch mode for now.

v6.0.0

Compare Source

Major Changes
Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "on saturday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Aug 6, 2021
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from be7c02a to 28a8751 Compare August 6, 2021 16:52
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from ba0f498 to eb4dd8c Compare August 20, 2021 09:41
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 34dad81 to b8b0833 Compare August 25, 2021 20:02
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 3d2c608 to 867c571 Compare September 7, 2021 12:15
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from b1146b0 to 846e9d9 Compare September 17, 2021 15:43
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 27e30d9 to 2a41189 Compare September 29, 2021 15:41
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0d2362d to f361c53 Compare October 3, 2021 13:41
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 5 times, most recently from ed82939 to 366f66c Compare October 15, 2021 17:01
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 366f66c to f08b4e6 Compare October 22, 2021 17:20
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 5 times, most recently from 2a3b06d to 959cc61 Compare November 5, 2021 17:25
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 810e9c2 to dcafca0 Compare February 17, 2022 09:17
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from dcafca0 to fbc9977 Compare March 26, 2022 15:27
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from fbc9977 to 66a52b5 Compare May 15, 2022 20:11
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 66a52b5 to 156ae63 Compare June 18, 2022 16:48
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 156ae63 to 01b0b72 Compare September 25, 2022 19:07
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 01b0b72 to 732d3fd Compare November 20, 2022 16:50
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo (major) chore(deps): update graphqlcodegenerator monorepo to v2 (major) Nov 24, 2022
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 382369e to 9ac47e5 Compare November 30, 2022 13:09
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from f5cc959 to d8eba09 Compare December 7, 2022 23:48
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo to v2 (major) Update graphqlcodegenerator monorepo to v2 (major) Dec 17, 2022
@renovate renovate Bot changed the title Update graphqlcodegenerator monorepo to v2 (major) chore(deps): update graphqlcodegenerator monorepo to v2 (major) Dec 17, 2022
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d8eba09 to 81bab5e Compare December 27, 2022 21:25
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 9759a43 to 055f51e Compare January 10, 2023 22:59
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 055f51e to 22d5967 Compare January 14, 2023 07:50
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo to v2 (major) chore(deps): update graphqlcodegenerator monorepo (major) Jan 14, 2023
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 22d5967 to 71ac11f Compare March 16, 2023 23:57
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo (major) chore(deps): update graphqlcodegenerator monorepo to v3 (major) Mar 16, 2023
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 71ac11f to 5491e56 Compare April 17, 2023 12:25
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 5491e56 to a0036ad Compare May 28, 2023 11:27
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo to v3 (major) chore(deps): update graphqlcodegenerator monorepo (major) May 28, 2023
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a0036ad to 9934119 Compare June 2, 2023 17:31
@coderabbitai

coderabbitai Bot commented Sep 5, 2024 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: b2d5c5ae-96b2-44be-8185-e3ea92d4b014

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

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

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants