-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(aws-user-migrate): update all non-major dependencies #629
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
6e3e4d9
to
d1612fc
Compare
d1612fc
to
73e68de
Compare
73e68de
to
775ce0d
Compare
775ce0d
to
c3b013f
Compare
c3b013f
to
bcd4fa2
Compare
bcd4fa2
to
67f4b56
Compare
67f4b56
to
3065583
Compare
3065583
to
fcad9ab
Compare
fcad9ab
to
b4c2171
Compare
b4c2171
to
bf0ad4b
Compare
bf0ad4b
to
b99bb6d
Compare
b99bb6d
to
e36f8df
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
e36f8df
to
3d88a4a
Compare
Kudos, SonarCloud Quality Gate passed!
|
1 similar comment
Kudos, SonarCloud Quality Gate passed!
|
JoeKarow
approved these changes
Jun 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
📦 api
📦 app
📦 auth
automerge
Enable Kodiak auto-merge
📦 aws-cache
📦 aws-messaging
📦 aws-user-migrate
📦 config
📦 db
dependencies
Change in project dependencies.
📦 env
📦 eslint-config
kodiak: merge.method = 'squash'
Kodiak will squash merge this PR.
📦 ui
📦 web
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:
1.9.0
->1.10.0
3.358.0
->3.360.0
3.358.0
->3.360.0
1.1.57
->1.1.58
0.4.1
->0.6.0
4.29.15
->4.29.17
4.29.15
->4.29.17
8.9.2
->8.9.3
18.2.13
->18.2.14
5.60.0
->5.60.1
5.60.0
->5.60.1
0.18.6
->0.18.10
1.10.5
->1.10.6
8.6.3
->8.6.5
1.12.3
->1.12.4
1.10.5
->1.10.6
Release Notes
aws-powertools/powertools-lambda-typescript (@aws-lambda-powertools/logger)
v1.10.0
Compare Source
Bug Fixes
Features
aws/aws-sdk-js-v3 (@aws-sdk/client-cognito-identity-provider)
v3.360.0
Compare Source
Note: Version bump only for package @aws-sdk/client-cognito-identity-provider
v3.359.0
Compare Source
Note: Version bump only for package @aws-sdk/client-cognito-identity-provider
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
v3.360.0
Compare Source
Note: Version bump only for package @aws-sdk/client-s3
v3.359.0
Compare Source
Note: Version bump only for package @aws-sdk/client-s3
t3-oss/t3-env (@t3-oss/env-nextjs)
v0.6.0
Compare Source
Minor Changes
#90
1f6de0f
Thanks @juliusmarminge! - feat: addshared
section for shared variablesshared variables are variables that are available in all runtimes despite them not being prefixed by anything, and is not manually supplied by the user.
Patch Changes
1f6de0f
]:v0.5.1
Compare Source
Patch Changes
c19acc0
Thanks @juliusmarminge! - fix: ensure NODE_ENV is present in build outputUpdated dependencies []:
v0.5.0
Compare Source
Minor Changes
#75
8568a9b
Thanks @juliusmarminge! - introduce a newexperimental__runtimeEnv
that only requires manual destruction of client side variables.next.js 13.4.4 dropped the static analysis of serverside environment variables, which means that the manual destruction is no longer necessary for serverside variables
Patch Changes
tanstack/query (@tanstack/react-query)
v4.29.17
Compare Source
Version 4.29.17 - 6/25/2023, 2:33 PM
Changes
Refactor
9077bb9
) by GLabatPackages
v4.29.16
Compare Source
Version 4.29.16 - 6/25/2023, 2:21 PM
Changes
Refactor
3e25f51
) by Dominik DorfmeisterPackages
tanstack/table (@tanstack/react-table)
v8.9.3
Compare Source
Version 8.9.3 - 6/23/2023, 8:17 PM
Changes
Fix
17a0373
) by Tanner LinsleyOther
38563b7
) by Tanner Linsleya539d5a
) by Tanner LinsleyPackages
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.60.1
Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.60.1
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
evanw/esbuild (esbuild)
v0.18.10
Compare Source
Fix a tree-shaking bug that removed side effects (#3195)
This fixes a regression in version 0.18.4 where combining
--minify-syntax
with--keep-names
could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because--keep-names
generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then--minify-syntax
could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.Fix an incorrect warning about CSS nesting (#3197)
A warning is currently generated when transforming nested CSS to a browser that doesn't support
:is()
because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as@top-left
within@page
. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.v0.18.9
Compare Source
Fix
await using
declarations insideasync
generator functionsI forgot about the new
await using
declarations when implementing lowering forasync
generator functions in the previous release. This change fixes the transformation ofawait using
declarations when they are inside loweredasync
generator functions:Insert some prefixed CSS properties when appropriate (#3122)
With this release, esbuild will now insert prefixed CSS properties in certain cases when the
target
setting includes browsers that require a certain prefix. This is currently done for the following properties:appearance: *;
=>-webkit-appearance: *; -moz-appearance: *;
backdrop-filter: *;
=>-webkit-backdrop-filter: *;
background-clip: text
=>-webkit-background-clip: text;
box-decoration-break: *;
=>-webkit-box-decoration-break: *;
clip-path: *;
=>-webkit-clip-path: *;
font-kerning: *;
=>-webkit-font-kerning: *;
hyphens: *;
=>-webkit-hyphens: *;
initial-letter: *;
=>-webkit-initial-letter: *;
mask-image: *;
=>-webkit-mask-image: *;
mask-origin: *;
=>-webkit-mask-origin: *;
mask-position: *;
=>-webkit-mask-position: *;
mask-repeat: *;
=>-webkit-mask-repeat: *;
mask-size: *;
=>-webkit-mask-size: *;
position: sticky;
=>position: -webkit-sticky;
print-color-adjust: *;
=>-webkit-print-color-adjust: *;
tab-size: *;
=>-moz-tab-size: *; -o-tab-size: *;
text-decoration-color: *;
=>-webkit-text-decoration-color: *; -moz-text-decoration-color: *;
text-decoration-line: *;
=>-webkit-text-decoration-line: *; -moz-text-decoration-line: *;
text-decoration-skip: *;
=>-webkit-text-decoration-skip: *;
text-emphasis-color: *;
=>-webkit-text-emphasis-color: *;
text-emphasis-position: *;
=>-webkit-text-emphasis-position: *;
text-emphasis-style: *;
=>-webkit-text-emphasis-style: *;
text-orientation: *;
=>-webkit-text-orientation: *;
text-size-adjust: *;
=>-webkit-text-size-adjust: *; -ms-text-size-adjust: *;
user-select: *;
=>-webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;
Here is an example:
Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate.
Fix an obscure identifier minification bug (#2809)
Function declarations in nested scopes behave differently depending on whether or not
"use strict"
is present. To avoid generating code that behaves differently depending on whether strict mode is enabled or not, esbuild transforms nested function declarations into variable declarations. However, there was a bug where the generated variable name was not being recorded as declared internally, which meant that it wasn't being renamed correctly by the minifier and could cause a name collision. This bug has been fixed:Fix a bug in esbuild's compatibility table script (#3179)
Setting esbuild's
target
to a specific JavaScript engine tells esbuild to use the JavaScript syntax feature compatibility data from https://kangax.github.io/compat-table/es6/ for that engine to determine which syntax features to allow. However, esbuild's script that builds this internal compatibility table had a bug that incorrectly ignores tests for engines that still have outstanding implementation bugs which were never fixed. This change fixes this bug with the script.The only case where this changed the information in esbuild's internal compatibility table is that the
hermes
target is marked as no longer supporting destructuring. This is because there is a failing destructuring-related test for Hermes on https://kangax.github.io/compat-table/es6/. If you want to use destructuring with Hermes anyway, you can pass--supported:destructuring=true
to esbuild to override thehermes
target and force esbuild to accept this syntax.This fix was contributed by @ArrayZoneYour.
v0.18.8
Compare Source
Implement transforming
async
generator functions (#2780)With this release, esbuild will now transform
async
generator functions into normal generator functions when the configured target environment doesn't support them. These functions behave similar to normal generator functions except that they use theSymbol.asyncIterator
interface instead of theSymbol.iterator
interface and the iteration methods return promises. Here's an example (helper functions are omitted):This is an older feature that was added to JavaScript in ES2018 but I didn't implement the transformation then because it's a rarely-used feature. Note that esbuild already added support for transforming
for await
loops (the other part of the asynchronous iteration proposal) a year ago, so support for asynchronous iteration should now be complete.I have never used this feature myself and code that uses this feature is hard to come by, so this transformation has not yet been tested on real-world code. If you do write code that uses this feature, please let me know if esbuild's
async
generator transformation doesn't work with your code.v0.18.7
Compare Source
Add support for
using
declarations in TypeScript 5.2+ (#3191)TypeScript 5.2 (due to be released in August of 2023) will introduce
using
declarations, which will allow you to automatically dispose of the declared resources when leaving the current scope. You can read the TypeScript PR for this feature for more information. This release of esbuild adds support for transforming this syntax to target environments without support forusing
declarations (which is currently all targets other thanesnext
). Here's an example (helper functions are omitted):The injected helper functions ensure that the method named
Symbol.dispose
is called onnew Foo
when control exits the scope. Note that as with all new JavaScript APIs, you'll need to polyfillSymbol.dispose
if it's not present before you use it. This is not something that esbuild does for you because esbuild only handles syntax, not APIs. Polyfilling it can be done with something like this:This feature also introduces
await using
declarations which are likeusing
declarations but they callawait
on the disposal method (not on the initializer). Here's an example (helper functions are omitted):The injected helper functions ensure that the method named
Symbol.asyncDispose
is called onnew Foo
when control exits the scope, and that the returned promise is awaited. Similarly toSymbol.dispose
, you'll also need to polyfillSymbol.asyncDispose
before you use it.Add a
--line-limit=
flag to limit line length (#3170)Long lines are common in minified code. However, many tools and text editors can't handle long lines. This release introduces the
--line-limit=
flag to tell esbuild to wrap lines longer than the provided number of bytes. For example,--line-limit=80
tells esbuild to insert a newline soon after a given line reaches 80 bytes in length. This setting applies to both JavaScript and CSS, and works even when minification is disabled. Note that turning this setting on will make your files bigger, as the extra newlines take up additional space in the file (even after gzip compression).vercel/turbo (eslint-plugin-turbo)
v1.10.6
: Turborepo v1.10.6Compare Source
What's Changed
Changelog
Full Changelog: vercel/turborepo@v1.10.5...v1.10.6
pnpm/pnpm (pnpm)
v8.6.5
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.6.4
Compare Source
Patch Changes
.npmrc
file #6354.Our Gold Sponsors
Our Silver Sponsors
blitz-js/superjson (superjson)
v1.12.4
Compare Source
What's Changed
New Contributors
Full Changelog: flightcontrolhq/superjson@v1.12.3...v1.12.4
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.