chore(deps): update astro-dev (sushichan.live) #173
Merged
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.20241218.0
->4.20250121.0
3.0.2
->3.0.3
2.2.286
->2.2.298
22.10.2
->22.10.7
2.2.15
->2.2.16
2.0.14
->2.0.15
2.0.17
->2.0.18
2.1.15
->2.1.16
4.12.22
->4.12.23
9.17.0
->9.18.0
8.4.49
->8.5.1
1.7.0
->1.8.0
1.83.0
->1.83.4
16.12.0
->16.13.2
5.7.2
->5.7.3
8.18.1
->8.21.0
3.99.0
->3.103.2
Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20250121.0
Compare Source
v4.20250109.0
Compare Source
v4.20241230.0
Compare Source
v4.20241224.0
Compare Source
double-great/stylelint-a11y (@double-great/stylelint-a11y)
v3.0.3
Compare Source
iconify/icon-sets (@iconify/json)
v2.2.298
Compare Source
v2.2.297
Compare Source
v2.2.296
Compare Source
v2.2.295
Compare Source
v2.2.294
Compare Source
v2.2.293
Compare Source
v2.2.292
Compare Source
v2.2.291
Compare Source
v2.2.290
Compare Source
v2.2.289
Compare Source
v2.2.288
Compare Source
v2.2.287
Compare Source
VirtualLiveLab/js-config (@virtual-live-lab/eslint-config)
v2.2.16
Compare Source
VirtualLiveLab/js-config (@virtual-live-lab/prettier-config)
v2.0.15
Compare Source
@virtual-live-lab/prettier-config
2.0.6
Patch Changes
d8facac
Thanks @sushichan044! - weekly updatesaadeghi/daisyui (daisyui)
v4.12.23
Compare Source
eslint/eslint (eslint)
v9.18.0
Compare Source
postcss/postcss (postcss)
v8.5.1
Compare Source
v8.5.0
: 8.5 “Duke Alloces”Compare Source
PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.
@romainmenke during his work on Stylelint added
Input#document
in additional toInput#css
.Thanks to Sponsors
This release was possible thanks to our community.
If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:
ota-meshi/postcss-html (postcss-html)
v1.8.0
Compare Source
What's Changed
Full Changelog: ota-meshi/postcss-html@v1.7.0...v1.8.0
sass/dart-sass (sass)
v1.83.4
Compare Source
v1.83.3
Compare Source
v1.83.2
Compare Source
Properly display deprecation IDs for the JS Sass API.
Don't display deprecation IDs for user-defined deprecations.
v1.83.1
Compare Source
Fix a bug where
--quiet-deps
would get deactivated for@content
blocks,even when those blocks were entirely contained within dependencies.
Include deprecation IDs in deprecation warnings to make it easier to determine
what to pass to
--silence-deprecation
or--fatal-deprecation
.stylelint/stylelint (stylelint)
v16.13.2
Compare Source
It fixes a regression bug with
--fix
.--fix
CLI flag raising unknown value error (#8313) (@ybiquitous).v16.13.1
Compare Source
It fixes one bug due to an upstream change in our
ignore
dependency.ignore.default is not a function
(#8305) (@romainmenke).v16.13.0
Compare Source
It adds 3 rules to help you write error-free at-rules and 2 rules to warn you about deprecated CSS features. We've turned these rules on in our standard config.
It also adds new rule options, a feature to display how long rules take, lax autofix and support for
messageArgs
in more rules. It fixes 7 bugs.Lastly, we've made a deprecation that may affect some plugins. We've updated our docs for plugin authors and end users on how to silence deprecation warnings.
utils.report()
(#8244) (@romainmenke).lax
/strict
values to thefix
Node.js API option and CLI flag (#8106) (@ryo-manba).TIMING
environment variable (#8108) (@ryo-manba).at-rule-descriptor-no-unknown
rule (#8197) (@ryo-manba).at-rule-descriptor-value-no-unknown
rule (#8211) (@ryo-manba).at-rule-no-deprecated
rule (#8251) (@jeddy3).at-rule-prelude-no-invalid
rule (#8268) (@ryo-manba).declaration-property-value-keyword-no-deprecated
rule (#8223) (@Mouvedia)."ignore": ["at-rule-preludes", "declaration-values"]
tostring-no-newline
(#8214) (@ryo-manba).messageArgs
todeclaration-property-value-no-unknown
,font-family-name-quotes
,font-family-no-duplicate-names
,function-calc-no-unspaced-operator
,import-notation
,media-feature-name-unit-allowed-list
,selector-attribute-quotes
andselector-pseudo-element-colon-notation
(#8285 & #8252) (@Mouvedia).*-no-vendor-prefix
message ambiguity (#8239) (@Mouvedia).at-rule-(dis)allowed-list
,at-rule-no-vendor-prefix
,at-rule-property-required-list
message argument (#8277) (@Mouvedia).at-rule-property-required-list
message for inclusion of properties and descriptors (#8207) (@jeddy3).at-rule-*
false positives and negatives for@charset
rule (#8215) (@jeddy3).declaration-property-value-no-unknown
false positives for descriptors (#8240) (@jeddy3).property-(dis)allowed-list
false negatives for custom properties, use/^--/
to (dis)allow them (#8209) (@fbasmaison-lucca).property-no-unknown
false positives for descriptors (#8203) (@jeddy3).selector-pseudo-class-no-unknown
false positives for deprecated pseudo-classes (#8264) (@Mouvedia).selector-type-case
false positives forhatchPath
(#8264) (@Mouvedia).selector-type-no-unknown
false positives forshadow
,hatch
andhatchpath
(#8264) (@Mouvedia).microsoft/TypeScript (typescript)
v5.7.3
Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.21.0
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.20.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.19.1
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.19.0
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.18.2
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
cloudflare/workers-sdk (wrangler)
v3.103.2
Compare Source
Patch Changes
16a9460
Thanks @vicb! - fix(wrangler): use require.resolve to resolve unenv pathv3.103.1
Compare Source
Patch Changes
a1ff045
Thanks @CarmenPopoviciu! - Reverts #7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)v3.103.0
Compare Source
Minor Changes
#5086
8faf2c0
Thanks @dario-piotrowicz! - add--strict-vars
option towrangler types
add a new
--strict-vars
option towrangler types
that developers can (by setting theflag to
false
) use to disable the default strict/literal types generation for their variablesopting out of strict variables can be useful when developers change often their
vars
values,even more so when multiple environments are involved
v3.102.0
Compare Source
Minor Changes
f613276
Thanks @garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLIPatch Changes
#7750
df0e5be
Thanks @andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output ofwrangler dev
, and adds-in the same tag for Durable Objects (which are emulated locally inwrangler dev
).#7732
d102b60
Thanks @Ankcorn! - fix pages secret bulk copy#7706
c63f1b0
Thanks @penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.Updated dependencies [
8e9aa40
]:v3.101.0
Compare Source
Minor Changes
#7534
7c8ae1c
Thanks @cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines#7674
45d1d1e
Thanks @Ankcorn! - Add support for env files to wrangler secret bulk i.e..dev.vars
Run
wrangler secret bulk .dev.vars
to add the env fileThis will upload the secrets KEY and KEY_2 to your worker
#7442
e4716cc
Thanks @petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commandsThis new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
which Wrangler can use instead of user configuration when running deploy-related commands.
It is not expected that developers of Workers will need to use this feature directly.
Affected commands
The commands that use this feature are:
wrangler deploy
wrangler dev
wrangler versions upload
wrangler versions deploy
wrangler pages deploy
wrangler pages build
wrangler pages build-env
Config redirect file
When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path
.wrangler/deploy/config.json
. This file must contain only a single JSON object of the form:When this file exists Wrangler will follow the
configPath
(relative to the.wrangler/deploy/config.json
file) to find an alternative Wrangler configuration file to load and use as part of this command.When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.
Custom build tool example
A common approach that a build tool might choose to implement.
The user writes code that uses Cloudflare Workers resources, configured via a user
wrangler.toml
file.Note that this configuration points
main
at user code entry-point.The user runs a custom build, which might read the
wrangler.toml
to find the entry-point:> my-tool build
This tool generates a
dist
directory that contains both compiled code and a new deployment configuration file, but also a.wrangler/deploy/config.json
file that redirects Wrangler to this new deployment configuration file:The
dist/wrangler.json
will contain:And the
.wrangler/deploy/config.json
will contain:#7685
9d2740a
Thanks @vicb! - allow overriding the unenv preset.By default wrangler uses the bundled unenv preset.
Setting
WRANGLER_UNENV_RESOLVE_PATHS
allow to use another version of the preset.Those paths are used when resolving the unenv module identifiers to absolute paths.
This can be used to test a development version.
#7694
f3c2f69
Thanks @joshthoward! - Default wrangler d1 export to --local rather than failingPatch Changes
#7456
ff4e77e
Thanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.#7712
6439347
Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview#7703
e771fe9
Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure#7576
773bda8
Thanks @cmackenzie1! - Remove defaults forbatch-max-*
pipeline parameters and define value rangesUpdated dependencies [
2c76887
,78bdec5
]:v3.100.0
Compare Source
Minor Changes
#7604
6c2f173
Thanks @CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry dataWe want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.
These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.
N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.
Patch Changes
#7581
cac7fa6
Thanks @vicb! - chore(wrangler): update unenv dependency versionunenv now uses the workerd implementation on node:dns
See the unjs/unenv#376
#7625
d8fb032
Thanks @vicb! - feat(wrangler): use unenv builtin dependency resolutionMoving away from
require.resolve()
to handle unenv aliased packages.Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
and to override the base path so that we can test the dev version of the preset.
#7533
755a27c
Thanks @danielgek! - Add warning about the browser rendering not available on local#7614
8abb43f
Thanks @vicb! - chore(wrangler): update unenv dependency versionThe updated unenv contains a fix for the module resolution,
see unjs/unenv#378.
That bug prevented us from using unenv module resolution,
see #7583.
Updated dependencies [
b4e0af1
]:Configuration
📅 Schedule: Branch creation - "before 4:00am on Monday" in timezone Asia/Tokyo, 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.