⬆️(dependencies) update js dependencies #468
Merged
Conversation
This file contains hidden or 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
renovate
bot
added
dependencies
renovate
bot
force-pushed
the
renovate/js-dependencies
branch
7 times, most recently
from
2fda16b to
e395c43
Compare
renovate
bot
force-pushed
the
renovate/js-dependencies
branch
2 times, most recently
from
c62b9ea to
abf4fcd
Compare
In the 1.8.0 we experienced issues with the service worker not updating properly. We suspect that the workbox-webpack-plugin is the cause of this issue. Better to downgrade to the last version that worked until we have time to investigate the issue. We add workbox-webpack-plugin to the renovate.json file to avoid future updates.
An upgrade to @sentry/nextjs@8.42.0 changed some typing. It is not from @sentry/types but from @sentry/core now.
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
abf4fcd to
69655f6
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This looks like an instability in the openai library's definition of dependencies.
AntoLC
force-pushed
the
renovate/js-dependencies
branch
4 times, most recently
from
3430be2 to
f27a0c2
Compare
Last upgrade of Blocknote changes the editor method getSelection, the blocks were not being selected in certain cases. We updated the methods to select the blocks correctly.
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
f27a0c2 to
7554650
Compare
AntoLC
approved these changes
Dec 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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:
0.19.2->0.20.00.19.2->0.20.00.19.2->0.20.08.40.0->8.42.05.61.3->5.62.15.61.3->5.62.25.61.3->5.62.222.9.3->22.10.18.15.0->8.17.08.15.0->8.17.016.4.5->16.4.724.0.0->24.0.53.3.3->3.4.215.1.1->15.1.316.10.0->16.11.05.96.1->5.97.07.1.0->7.3.0Release Notes
TypeCellOS/BlockNote (@blocknote/core)
v0.20.0Compare Source
💖 Moving blocks as well as indentation & toolbar navigation changes have been sponsored by DINUM 🇫🇷 and ZenDiS 🇩🇪
💖 Table cell navigation changes have been sponsored by DeepOrigin💖
Moving blocks
[Breaking]
moveBlocksUp/moveBlocksDownmethodsThe previously undocumented
moveBlockUp&moveBlockDownmethods have been renamed tomoveBlocksUp&moveBlocksDownas they now support selections that span multiple blocks.Additionally, their behaviour is now more inline with Notion and they now work better with
"column"and"columnList"blocks from the@blocknote/xl-multi-columnpackage.Docs have also been added for both methods.
Keyboard shortcuts
The
Cmd+Shift+Up/Cmd+Shift+Downkeyboard shortcuts (Ctrl+Shift+Up/Ctrl+Shift+Downfor Windows) previously used themoveBlockUp&moveBlockDownmethods, which are nowmoveBlocksUp&moveBlocksDown. This means that all the changes mentioned above also apply to those shortcuts.Improved
Tab/Shift+TabhandlingIndentation & toolbar navigation
Previously, while the formatting or link toolbars were open,
Tab&Shift+Tabwas used to navigate them for keyboard accessibility. In order to useTab/Shift+Tabto indent/unindent the selected blocks, the user would have to first hitEscapeto close the toolbar(s). However, they would then immediately reopen, which would be frustrating when trying to move blocks up/down multiple nesting levels.Now, the formatting and link toolbars remain closed after indenting/unindenting with
Tab/Shift+Tab.Additionally, setting the new
tab-behavioureditor option to"prefer-indent"will causeTab/Shift+Tabto always indent/unindent the selected blocks, regardless of any open toolbars. Note that this will make the toolbars no longer keyboard accessible.Table cell navigation
Tab/Shift+Tabnow navigate through cells when the selection is inside a table block, instead of indenting/unindenting the block.Updated editor methods
getBlockPreviously could only get regular blocks, now also works with
"column"and"columnList"blocks from the@blocknote/xl-multi-columnpackage.getSelection[Breaking]Previously,
getSelection().blockswould return blocks spanned by the selection at all nesting levels. This release changes that behaviour.In most cases,
getSelection().blocksnow returns only the blocks spanned by the selection at the shared depth, i.e. the minimum depth at which the blocks share a common ancestor.However, when the block in which the selection starts is at a higher depth than the shared depth, we omit the first block at the shared depth. Instead, we include the first block at its depth, and any blocks at a higher index up to the shared depth. The following example illustrates this:
Here, each block is represented by its ID, and the selection is represented by the
>|and|<markers. So the selection starts in blockid-2and ends in blockid-9.In this case, the blocks
id-6,id-7, andid-8set the shared depth, as they are the least nested blocks spanned by the selection. Therefore, these blocks are all added to theblocksarray.Technically, the selection also spans block
id-0, which is also at the shared depth, as the selection starts in blockid-2which is its descendant. Becauseid-0is the first block in the selection, it's omitted and insteadid-2, where the selection starts, is added. Additionally, its later siblings (in this case,id-3) are added to theblocksarray, and we move up one level of depth. The ancestor of blockid-2at this depth is blockid-1. Its later siblings are also added to theblocksarray, and we again move up one level of depth.Since we're now at the shared depth, we are done, so the final
blocksarray for this example would be:[id-2, id-3, id-4, id-6, id-7, id-8, id-9]New editor methods
getPrevBlockDocs reference
getNextBlockDocs reference
getParentBlockDocs reference
setSelectionDocs reference
What's Changed
New Contributors
Full Changelog: TypeCellOS/BlockNote@v0.19.2...v0.20.0
getsentry/sentry-javascript (@sentry/nextjs)
v8.42.0Compare Source
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptionsin favor ofvueIntegration(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()tracingOptionsinSentry.init()For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()and itstracingOptionsoption to configure tracing options in the Nuxt SDK:Other Changes
web-vitalsto v4.2.4 (#14439)vueIntegration(#14526)Bundle size 📦
v8.41.0Compare Source
Important Changes
meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
Additionally, the SDK requires the implicit
nitropackdependency to satisfy version^2.10.0andofetchto satisfy^1.4.0.It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.
Deprecations
We are deprecating a few APIs which will be removed in the next major.
The following deprecations will potentially affect you:
feat(core): Update & deprecate
undefinedoption handling (#14450)In the next major version we will change how passing
undefinedtotracesSampleRate/tracesSampler/enableTracingwill behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRatekey is present in the options object.In the next major version, this behavior will be changed so that passing
undefined(or rather having atracesSampleRatekey) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefinedbeing passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0instead, which will also enable tracing in v9.The same applies to
tracesSamplerandenableTracing.feat(core): Log warnings when returning
nullinbeforeSendSpan(#14433)Currently, the
beforeSendSpanoption inSentry.init()allows you to drop individual spans from a trace by returningnullfrom the hook.Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.
With the next major version the
beforeSendSpanAPI can only be used to mutate spans, but no longer to drop them.With this release the SDK will warn you if you are using this API to drop spans.
Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.
Additionally, with the next major version, root spans will also be passed to
beforeSendSpan.feat(utils): Deprecate
@sentry/utils(#14431)With the next major version the
@sentry/utilspackage will be merged into the@sentry/corepackage.It is therefore no longer recommended to use the
@sentry/utilspackage.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration'stracingOptionsoption (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()tracingOptionsinSentry.init()vueIntegration()optionstracingOptionsin thevueIntegration()optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptionsin thevueIntegration().The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.exclude(#14486)Currently it is possible to define
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.excludeoptions inSentry.init()to only apply ESM loader hooks to a subset of modules.This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.
Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
To only wrap modules that have instrumentation, it is recommended to instead set
registerEsmLoaderHooks.onlyIncludeInstrumentedModulestotrue.Note that
onlyIncludeInstrumentedModules: truewill become the default behavior in the next major version and theregisterEsmLoaderHookswill no longer accept fine-grained options.The following deprecations will most likely not affect you unless you are building an SDK yourself:
arrayify(#14405)flatten(#14454)urlEncode(#14406)validSeverityLevels(#14407)getNumberOfUrlSegments(#14458)memoBuilder,BAGGAGE_HEADER_NAME, andmakeFifoCache(#14434)addRequestDataToEventandextractRequestData(#14430)Other Changes
sentry-trace,baggageand DSC handling (#14364)openTelemetryInstrumentationsoption (#14484)NEXT_REDIRECTfrom browser (#14440)Work in this release was contributed by @NEKOYASAN and @fmorett. Thank you for your contributions!
Bundle size 📦
TanStack/query (@tanstack/eslint-plugin-query)
v5.62.1Compare Source
Version 5.62.1 - 12/2/24, 6:40 PM
Changes
Fix
d9d2728) by ParbezChore
b7bad3d) by ArnoudTest
queryObserver(#8304) (12b6782) by Sol LeePackages
v5.61.6Compare Source
Version 5.61.6 - 11/28/24, 1:59 PM
Changes
Fix
ebcaa55) by Arnoudc402a2b) by Eliya CohenPackages
v5.61.4Compare Source
Version 5.61.4 - 11/26/24, 1:39 PM
Changes
Fix
3b7556f) by Jonathan ToungChore
dfe2cd1) by renovate[bot]8b0756a) by Arnoudef0b7b2) by Dominik Dorfmeisterecc17d5) by renovate[bot]c69f302) by Lachlan Collins5cd9611) by Lachlan CollinsPackages
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.17.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.16.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.17.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.16.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
motdotla/dotenv (dotenv)
v16.4.7Compare Source
Changed
.tapfolder when publishing. (oops, sorry about that everyone. - @motdotla) #848v16.4.6Compare Source
Changed
i18next/i18next (i18next)
v24.0.5Compare Source
v24.0.4Compare Source
v24.0.3Compare Source
v24.0.2Compare Source
v24.0.1Compare Source
prettier/prettier (prettier)
v3.4.2Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on(#16887 by @fisker)