Skip to content
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

chore(deps): update astro-dev (sushichan.live) #173

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types 4.20241218.0 -> 4.20250121.0 age adoption passing confidence
@double-great/stylelint-a11y 3.0.2 -> 3.0.3 age adoption passing confidence
@iconify/json (source) 2.2.286 -> 2.2.298 age adoption passing confidence
@types/node (source) 22.10.2 -> 22.10.7 age adoption passing confidence
@virtual-live-lab/eslint-config (source) 2.2.15 -> 2.2.16 age adoption passing confidence
@virtual-live-lab/prettier-config (source) 2.0.14 -> 2.0.15 age adoption passing confidence
@virtual-live-lab/stylelint-config (source) 2.0.17 -> 2.0.18 age adoption passing confidence
@virtual-live-lab/tsconfig (source) 2.1.15 -> 2.1.16 age adoption passing confidence
daisyui (source) 4.12.22 -> 4.12.23 age adoption passing confidence
eslint (source) 9.17.0 -> 9.18.0 age adoption passing confidence
postcss (source) 8.4.49 -> 8.5.1 age adoption passing confidence
postcss-html 1.7.0 -> 1.8.0 age adoption passing confidence
sass 1.83.0 -> 1.83.4 age adoption passing confidence
stylelint (source) 16.12.0 -> 16.13.2 age adoption passing confidence
typescript (source) 5.7.2 -> 5.7.3 age adoption passing confidence
typescript-eslint (source) 8.18.1 -> 8.21.0 age adoption passing confidence
wrangler (source) 3.99.0 -> 3.103.2 age adoption passing confidence

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
saadeghi/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

President Alloces seal

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 to Input#css.

root.source.input.document //=> "<p>Hello</p>
                           //    <style>
                           //    p {
                           //      color: green;
                           //    }
                           //    </style>"
root.source.input.css      //=> "p {
                           //      color: green;
                           //    }"

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

  • No user-visible changes.

v1.83.3

Compare Source

  • No user-visible changes.

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.

v16.13.1

Compare Source

It fixes one bug due to an upstream change in our ignore dependency.

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.

  • Deprecated: ambiguous position arguments passed to utils.report() (#​8244) (@​romainmenke).
  • Added: lax/strict values to the fix Node.js API option and CLI flag (#​8106) (@​ryo-manba).
  • Added: support for profiling rule performance via the TIMING environment variable (#​8108) (@​ryo-manba).
  • Added: at-rule-descriptor-no-unknown rule (#​8197) (@​ryo-manba).
  • Added: at-rule-descriptor-value-no-unknown rule (#​8211) (@​ryo-manba).
  • Added: at-rule-no-deprecated rule (#​8251) (@​jeddy3).
  • Added: at-rule-prelude-no-invalid rule (#​8268) (@​ryo-manba).
  • Added: declaration-property-value-keyword-no-deprecated rule (#​8223) (@​Mouvedia).
  • Added: "ignore": ["at-rule-preludes", "declaration-values"] to string-no-newline (#​8214) (@​ryo-manba).
  • Added: messageArgs to declaration-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 and selector-pseudo-element-colon-notation (#​8285 & #​8252) (@​Mouvedia).
  • Fixed: deprecation warnings to only display once per (custom) rule (#​8265) (@​romainmenke).
  • Fixed: *-no-vendor-prefix message ambiguity (#​8239) (@​Mouvedia).
  • Fixed: at-rule-(dis)allowed-list, at-rule-no-vendor-prefix, at-rule-property-required-list message argument (#​8277) (@​Mouvedia).
  • Fixed: at-rule-property-required-list message for inclusion of properties and descriptors (#​8207) (@​jeddy3).
  • Fixed: at-rule-* false positives and negatives for @charset rule (#​8215) (@​jeddy3).
  • Fixed: declaration-property-value-no-unknown false positives for descriptors (#​8240) (@​jeddy3).
  • Fixed: property-(dis)allowed-list false negatives for custom properties, use /^--/ to (dis)allow them (#​8209) (@​fbasmaison-lucca).
  • Fixed: property-no-unknown false positives for descriptors (#​8203) (@​jeddy3).
  • Fixed: selector-pseudo-class-no-unknown false positives for deprecated pseudo-classes (#​8264) (@​Mouvedia).
  • Fixed: selector-type-case false positives for hatchPath (#​8264) (@​Mouvedia).
  • Fixed: selector-type-no-unknown false positives for shadow, hatch and hatchpath (#​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
  • eslint-plugin: [no-misused-spread] add new rule (#​10551)
❤️ Thank You
  • Josh Goldberg ✨

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
  • typescript-eslint: export types so that declarations can be named for dts files (#​10513)
❤️ 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

v3.103.1

Compare Source

Patch Changes

v3.103.0

Compare Source

Minor Changes
  • #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

    add a new --strict-vars option to wrangler types that developers can (by setting the
    flag to false) use to disable the default strict/literal types generation for their variables

    opting 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
Patch Changes

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 file

    //.dev.vars
    KEY=VALUE
    KEY_2=VALUE

    This 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 commands

    This 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:

{ "configPath": "../../path/to/wrangler.json" }

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.

    name = "my-worker"
    main = "src/index.ts"
    [[kv_namespaces]]
    binding = "<BINDING_NAME1>"
    id = "<NAMESPACE_ID1>"

    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:

    - dist
      - index.js
    	- wrangler.json
    - .wrangler
      - deploy
    	  - config.json
    

    The dist/wrangler.json will contain:

    {
      "name": "my-worker",
      "main": "./index.js",
      "kv_namespaces": [
        { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
      ]
    }

    And the .wrangler/deploy/config.json will contain:

    {
      "configPath": "../../dist/wrangler.json"
    }
  • #​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 failing

Patch Changes

v3.100.0

Compare Source

Minor Changes
  • #​7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

    We 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 version

    unenv now uses the workerd implementation on node:dns
    See the unjs/unenv#376

  • #​7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

    Moving 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 version

    The 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

cloudflare-workers-and-pages bot commented Dec 22, 2024

Deploying sushichan-live with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2a92166
Status: ✅  Deploy successful!
Preview URL: https://d5d608f7.sushichan-live.pages.dev
Branch Preview URL: https://renovate-sushichan-live-astr.sushichan-live.pages.dev

View logs

@renovate renovate bot added the renovate label Dec 22, 2024
@github-actions github-actions bot added the astro label Dec 22, 2024
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch from 13566b8 to c640910 Compare December 23, 2024 12:57
@renovate renovate bot changed the title chore(deps): update dependency @iconify/json to v2.2.287 (sushichan.live) chore(deps): update dependency @iconify/json to v2.2.288 (sushichan.live) Dec 23, 2024
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch from c640910 to 9d3994f Compare December 23, 2024 17:47
@renovate renovate bot changed the title chore(deps): update dependency @iconify/json to v2.2.288 (sushichan.live) chore(deps): update astro-dev (sushichan.live) Dec 23, 2024
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch 6 times, most recently from bc582ef to 29275a0 Compare December 31, 2024 10:06
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch 6 times, most recently from ae2b4a8 to 5068402 Compare January 5, 2025 09:32
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch 11 times, most recently from 1365ed1 to 62d0fff Compare January 14, 2025 09:32
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch 10 times, most recently from 0ddd03d to 1417c7a Compare January 21, 2025 01:35
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch 6 times, most recently from 64159da to 50b0b36 Compare January 22, 2025 16:52
@renovate renovate bot force-pushed the renovate/sushichan.live-astro-dev branch from 50b0b36 to 2a92166 Compare January 22, 2025 16:54
@sushichan044 sushichan044 merged commit 5f6037a into main Jan 22, 2025
9 checks passed
@renovate renovate bot deleted the renovate/sushichan.live-astro-dev branch January 22, 2025 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant