Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.9.2
->4.9.3
4.9.2
->4.9.3
16.18.46
->16.18.48
6.4.1
->6.5.0
6.4.1
->6.5.0
3.0.2
->3.0.3
0.10.0
->0.13.0
Release Notes
apollographql/apollo-server (@apollo/server)
v4.9.3
Compare Source
Patch Changes
a1c725eaf
Thanks @trevor-scheer! - Ensure API keys are valid header values on startupApollo Server previously performed no sanitization or validation of API keys on startup. In the case that an API key was provided which contained characters that are invalid as header values, Apollo Server could inadvertently log the API key in cleartext.
This only affected users who:
node-fetch
fetcherApollo Server now trims whitespace from API keys and validates that they are valid header values. If an invalid API key is provided, Apollo Server will throw an error on startup.
For more details, see the security advisory:
GHSA-j5g3-5c8r-7qfx
apollographql/apollo-server (@apollo/server-integration-testsuite)
v4.9.3
Compare Source
Patch Changes
a1c725eaf
]:typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.5.0
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
6.4.1 (2023-08-21)
Bug Fixes
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.5.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.4.1 (2023-08-21)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
prettier/prettier (prettier)
v3.0.3
Compare Source
diff
Add
preferUnplugged: true
topackage.json
(#15169 by @fisker and @so1ve)Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add
preferUnplugged: true
topackage.json
, so Yarn will install Prettier as unplug by default.Support shared config that forbids
require()
(#15233 by @fisker)If an external shared config package is used, and the package
exports
don't haverequire
ordefault
export.In Prettier 3.0.2 Prettier fails when attempt to
require()
the package, and throws an error.Allow argument of
require()
to break (#15256 by @fisker)Do not print trailing commas in arrow function type parameter lists in
ts
code blocks (#15286 by @sosukesuzuki)Support TypeScript 5.2
using
/await using
declaration (#15321 by @sosukesuzuki)Support for the upcoming Explicit Resource Management feature in ECMAScript.
using
/await using
declarationgoogle/wireit (wireit)
v0.13.0
Compare Source
Changed
v0.12.0
Compare Source
v0.11.0
Compare Source
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.