-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update all non-major dependencies #75
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/all-minor-patch
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+938
−490
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
renovate
bot
changed the title
Update devDependency @cloudflare/workers-types to v4.20241004.0
Update all non-major dependencies
Oct 6, 2024
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 6, 2024 04:06
9f5bc93
to
436e7a4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 6, 2024 07:37
436e7a4
to
7592f8c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 7, 2024 13:44
7592f8c
to
e68009e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 7, 2024 17:01
e68009e
to
174b004
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 7, 2024 19:03
174b004
to
a0504e0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 7, 2024 21:30
a0504e0
to
7d028bc
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 8, 2024 10:08
7d028bc
to
a71cc04
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 8, 2024 14:13
a71cc04
to
9ea404b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 8, 2024 19:53
9ea404b
to
67528b7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 23, 2024 16:19
ec65f77
to
b3bff0a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 23, 2024 19:44
b3bff0a
to
16dce95
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2024 02:20
16dce95
to
b7221ac
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2024 13:13
b7221ac
to
69f5087
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2024 19:33
69f5087
to
3713a30
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 25, 2024 00:14
3713a30
to
99d66d4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 25, 2024 12:20
99d66d4
to
212b307
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 25, 2024 21:06
212b307
to
73a48bb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 26, 2024 01:40
73a48bb
to
226f217
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 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.5.14
->0.5.22
4.20240925.0
->4.20241022.0
1.14.2
->1.21.0
1.47.2
->1.48.2
4.7.2
->4.7.4
2.6.1
->2.7.3
4.0.0-next.7
->4.0.0
0.63.3
->0.63.6
11.3.0
->11.5.0
0.24.2
->0.26.2
0.33.0
->0.35.3
3.2.0
->3.2.2
9.12.0
->9.12.2
1.79.4
->1.80.4
5.0.0-next.262
->5.1.3
4.0.4
->4.0.5
2.7.0
->2.8.0
5.6.2
->5.6.3
0.63.3
->0.63.6
5.4.8
->5.4.10
2.1.2
->2.1.3
3.80.0
->3.83.0
Release Notes
cloudflare/workers-sdk (@cloudflare/vitest-pool-workers)
v0.5.22
Compare Source
Patch Changes
760e43f
,cef32c8
,4aa35c5
,3f1d79c
,1de309b
,e7ea600
,a2afcf1
,b219296
,a90980c
,5ef6231
,80e5bc6
]:v0.5.21
Compare Source
Patch Changes
809193e
,9bf51d6
,1f6ff8b
,244aa57
,e44f496
,e1b93dc
,48152d6
,045787b
,127615a
,a8ca700
,6131ef5
,6b97353
,f9d5fdb
,c794935
]:v0.5.20
Compare Source
Patch Changes
a5ac45d
,586c253
,b8ab809
]:v0.5.19
Compare Source
Patch Changes
5761020
,7859a04
]:v0.5.18
Compare Source
Patch Changes
51aedd4
,c863183
]:v0.5.17
Compare Source
Patch Changes
2af75ed
,eaf71b8
,2e64968
,4c6aad0
]:v0.5.16
Compare Source
Patch Changes
1320f20
]:v0.5.15
Compare Source
Patch Changes
#6835
5c50949
Thanks @emily-shen! - feature: enable asset routing in the vitest integration for Workers + static assetsIntegration tests (using the SELF binding) in Workers + assets projects will now return static assets if present on that path. Previously all requests went to the user worker regardless of whether static assets would have been served in production.
Unit style tests intentionally do not return static assets.
Updated dependencies [
d696850
,5c50949
,dc92af2
,82180a7
,54924a4
,30b7328
]:cloudflare/workerd (@cloudflare/workers-types)
v4.20241022.0
Compare Source
v4.20241018.0
Compare Source
v4.20241011.0
Compare Source
v4.20241004.0
Compare Source
dotenvx/dotenvx (@dotenvx/dotenvx)
v1.21.0
Compare Source
Changed
🎓 now if you choose to single quote, double quote, no quote, or backtick your value it will be respected - including for encrypted values. this more intuitively handles complex cases like escaped characters, literals, and json.
v1.20.1
Compare Source
Changed
v1.20.0
Compare Source
see CHANGELOG
v1.19.3
Compare Source
Changed
v1.19.2
Compare Source
Changed
SIGUSR2
(#403)v1.19.1
Compare Source
Changed
SIGTERM
orSIGINT
sent, don't bubble wrapped process error (#402)v1.19.0
Compare Source
Added
encrypt
anddecrypt
. example:dotenvx encrypt -ek "NEXT_PUBLIC_*"
(#397)v1.18.1
Compare Source
Added
$1
or$2
. (#396)v1.18.0
Compare Source
Added
set
andencrypt
preserve leading spaces (#395)Changed
set
,encrypt
, anddecrypt
(#395)encrypt
, thendecrypt
, thenencrypt
on a json value (#377)Note: the underlying
replace
engine to support these changes now wraps your values in single quotes. the priorreplace
engine wrapped in double quotes.So where your
.env
used to look like this with double quotes:It will now begin looking like this with single quotes:
It's an aesthetic side effect only. Your values will continue to be decrypted and encrypted correctly.
v1.17.0
Compare Source
Added
--format=eval
option forget
(#393)v1.16.1
Compare Source
Changed
options.stdio
(#391)v1.16.0
Compare Source
Changed
dotenvx keypair
call out todotenvx pro keypair
if pro installed (#390)v1.15.0
Compare Source
Added
--format=shell
option forkeypair
(#389)microsoft/playwright (@playwright/test)
v1.48.2
Compare Source
v1.48.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/33023 - [Bug]: command line flag --headed has no effect in ui modehttps://github.com/microsoft/playwright/issues/331077 - [REGRESSION]: page.waitForRequest does not get resolved since 1.48.https://github.com/microsoft/playwright/issues/3308585 - [Bug]: WebSocket route does not handle full URLs in Playwrighttps://github.com/microsoft/playwright/issues/33052052 - [Regression]: Inspector not showing recorded sthttps://github.com/microsoft/playwright/issues/331323132 - [Bug]: Wrong Ubuntu release name in Dockerfile.nhttps://github.com/microsoft/playwright/pull/3299632996 - [BUG] Trace attachments have small unusable height
Browser Versions
This version was also tested against the following stable channels:
v1.48.0
Compare Source
sveltejs/kit (@sveltejs/adapter-cloudflare)
v4.7.4
Compare Source
Patch Changes
docs: update URLs for new svelte.dev site (#12857)
Updated dependencies [
dcbe4222a194c5f90cfc0fc020cf065f7a4e4c46
,4cdbf76fbbf0c0ce7f574ef69c8daddcf954d39d
,3a9b78f04786898ca93f6d4b75ab18d26bc45192
,723eb8b31e6a22c82f730c30e485386c8676b746
,8ec471c875345b751344e67580ff1b772ef2735b
]:v4.7.3
Compare Source
Patch Changes
fix: correctly handle relative paths when fetching assets on the server (#12113)
Updated dependencies [
df48fc6ede3859beabaae9fd7c6f722215bb8a42
,5780deba8e3ebd0e2b0abea029068ad0c6daf6ad
,6f9aefdb8699fc126d76a88471602cb9a80822eb
,8aa95b4b3431e79f62f580abdcdcb157b4de86cd
]:sveltejs/kit (@sveltejs/kit)
v2.7.3
Compare Source
Patch Changes
fix: include importer in illegal import error message (#12820)
fix: don't try reading assets directly that aren't present (#12876)
fix: decode non-latin characters when previewing prerendered pages (#12874)
fix: better error message when a
Result
is returned from a form action (#12829)docs: update URLs for new svelte.dev site (#12857)
v2.7.2
Compare Source
Patch Changes
v2.7.1
Compare Source
Patch Changes
chore: upgrade to sirv 3.0 (#12796)
fix: warn when form action responses are lost because SSR is off (#12063)
v2.7.0
Compare Source
Minor Changes
Patch Changes
fix: correctly handle relative paths when fetching assets on the server (#12113)
fix: decode non ASCII anchor hashes when scrolling into view (#12699)
fix: page response missing CSP and Link headers when return promise in
load
(#12418)v2.6.4
Compare Source
Patch Changes
fix: only preload links that have a different URL than the current page (#12773)
fix: revert change to replace version in generateBundle (#12779)
fix: catch stack trace fixing errors thrown in web containers (#12775)
fix: use absolute links in JSDoc comments (#12772)
v2.6.3
Compare Source
Patch Changes
fix: ensure a changing
version
doesn't affect the hashes for chunks without any actual code changes (#12700)fix: prevent crash when logging URL search params in a server load function (#12763)
chore: revert update dependency cookie to ^0.7.0 (#12767)
v2.6.2
Compare Source
Patch Changes
sveltejs/vite-plugin-svelte (@sveltejs/vite-plugin-svelte)
v4.0.0
Compare Source
Major Changes
only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#901)
remove support for Svelte 4 (#892)
breaking(types): some types that have been unintentionally public are now private (#934)
disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)
replaced svelte-hmr with Svelte 5 compiler hmr integration (#892)
Minor Changes
allow infix notation for svelte modules (#901)
Previously, only suffix notation
.svelte.js
was allowed, now you can also use.svelte.test.js
or.svelte.stories.js
.This helps when writing testcases or other auxillary code where you may want to use runes too.
feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#941)
feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call
DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build
. (#989)Patch Changes
fix: make defaultHandler a required argument for onwarn in plugin options (#895)
prebundle with dev: true by default (#901)
fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#950)
fix: ensure svelte modules correctly run in DEV mode (#906)
ensure consistent use of compileOptions.hmr also for prebundling (#956)
fix(optimizeDeps): avoid to optimise server only entrypoints of svelte that are never used on the client (#941)
update peer on workspace packages to avoid packages bumping each other (#916)
export PluginOptions interface (#976)
Remove log about experimental status of Svelte 5. Note that breaking changes can still occur while vite-plugin-svelte 4 is in prerelease mode (#894)
fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#912)
fix(vitePreprocess): default to build config so that svelte-check does not trigger dev-only plugins (#931)
fix: only apply infix filter to basename (#920)
fix: disable hmr when vite config server.hmr is false (#913)
fix(dev): make sure custom cssHash is applied consistently even for prebundled components to avoid hash mismatches during hydration (#950)
Updated dependencies [
22baa25
,49324db
,e9f048c
,213fedd
]:v4.0.0-next.8
Compare Source
Minor Changes
DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build
. (#989)unocss/unocss (@unocss/reset)
v0.63.6
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.63.5
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.63.4
Compare Source
🐞 Bug Fixes
c9d2e01
, fix #4189 - by @antfu in https://github.com/unocss/unocss/issues/4189 (cbf68)View changes on GitHub
WiseLibs/better-sqlite3 (better-sqlite3)
v11.5.0
Compare Source
What's Changed
Full Changelog: WiseLibs/better-sqlite3@v11.4.0...v11.5.0
v11.4.0
Compare Source
What's Changed
New Contributors
Full Changelog: WiseLibs/better-sqlite3@v11.3.0...v11.4.0
drizzle-team/drizzle-orm (drizzle-kit)
v0.26.2
Compare Source
v0.26.1
Compare Source
data is malformed
for viewsv0.26.0
Compare Source
New Features
Checks support in
drizzle-kit
You can use drizzle-kit to manage your
check
constraint defined in drizzle-orm schema definitionFor example current drizzle table:
will be generated into
The same is supported in all dialects
Limitations
generate
will work as expected for all check constraint changes.push
will detect only check renames and will recreate the constraint. All other changes to SQL won't be detected and will be ignored.So, if you want to change the constraint's SQL definition using only
push
, you would need to manually comment out the constraint,push
, then put it back with the new SQL definition andpush
one more time.Views support in
drizzle-kit
You can use drizzle-kit to manage your
views
defined in drizzle-orm schema definition. It will work with all existing dialects and view optionsPostgreSQL
For example current drizzle table:
will be generated into
Views supported in all dialects, but materialized views are supported only in PostgreSQL
Limitations
generate
will work as expected for all view changespush
limitations:push
, you would need to manually comment out the view,push
, then put it back with the new SQL definition andpush
one more time.Updates for PostgreSQL enums behavior
We've updated enum behavior in Drizzle with PostgreSQL:
Add value after or before in enum: With this change, Drizzle will now respect the order of values in the enum and allow adding new values after or before a specific one.
Support for dropping a value from an enum: In this case, Drizzle will attempt to alter all columns using the enum to text, then drop the existing enum and create a new one with the updated set of values. After that, all columns previously using the enum will be altered back to the new enum.
Support for dropping an enum
Support for moving enums between schemas
Support for renaming enums
v0.25.0
Compare Source
Breaking changes and migrate guide for Turso users
If you are using Turso and libsql, you will need to upgrade your
drizzle.config
and@libsql/client
package.@libsql/[email protected]
or higher if you are using themigrate
function. For other use cases, you can continue using previous versions(But the suggestion is to upgrade)To install the latest version, use the command:
drizzle.config
for SQLite and Turso users, which allowed a shared strategy for both dialects. Starting with this release, we are introducing the turso dialect in drizzle-kit. We will evolve and improve Turso as a separate dialect with its own migration strategies.Before
After
If you are using only SQLite, you can use
dialect: "sqlite"
LibSQL/Turso and Sqlite migration updates
SQLite "generate" and "push" statements updates
Starting from this release, we will no longer generate comments like
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 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.
This PR was generated by Mend Renovate. View the repository job log.