search

andykenward / github-actions-cloudflare-pages

GitHub Action to deploy to Cloudflare Pages
MIT License
16 stars 0 forks source link

chore(deps): bump wrangler from 3.62.0 to 3.63.1 in the cloudflare group #393

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the cloudflare group with 1 update: wrangler.

Updates wrangler from 3.62.0 to 3.63.1

Release notes

Sourced from wrangler's releases.

wrangler@3.63.1

Patch Changes

  • #6192 b879ce4 Thanks @​petebacondarwin! - fix: do not report D1 user errors to Sentry

  • #6150 d993409 Thanks @​CarmenPopoviciu! - fix: Fix pages dev watch mode [_worker.js]

    The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "_worker.js" file, but not for changes in any of its imported dependencies. This means that given the following "_worker.js" file

    import { graham } from "./graham-the-dog";
export default {
    fetch(request, env) {
        return new Response(graham)
    }
}

    pages dev will reload for any changes in the _worker.js file itself, but not for any changes in graham-the-dog.js, which is its dependency.

    Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.

    This commit fixes all the aforementioned issues.

wrangler@3.63.0

Minor Changes

  • #6167 e048958 Thanks @​threepointone! - feature: alias modules in the worker

    Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might have imported node-fetch, which will probably never work in workerd. You can use the alias config to replace any of these imports with a module of your choice.

    Let's say you make a fetch-nolyfill.js

    export default fetch; // all this does is export the standard fetch function`

    You can then configure wrangler.toml like so:

    # ...
[alias]
"node-fetch": "./fetch-nolyfill"

    So any calls to import fetch from 'node-fetch'; will simply use our nolyfilled version.

    You can also pass aliases in the cli (for both dev and deploy). Like:

    npx wrangler dev --alias node-fetch:./fetch-nolyfill

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.63.1

Patch Changes

  • #6192 b879ce4 Thanks @​petebacondarwin! - fix: do not report D1 user errors to Sentry

  • #6150 d993409 Thanks @​CarmenPopoviciu! - fix: Fix pages dev watch mode [_worker.js]

    The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "_worker.js" file, but not for changes in any of its imported dependencies. This means that given the following "_worker.js" file

    import { graham } from "./graham-the-dog";
export default {
    fetch(request, env) {
        return new Response(graham)
    }
}

    pages dev will reload for any changes in the _worker.js file itself, but not for any changes in graham-the-dog.js, which is its dependency.

    Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.

    This commit fixes all the aforementioned issues.

3.63.0

Minor Changes

  • #6167 e048958 Thanks @​threepointone! - feature: alias modules in the worker

    Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might have imported node-fetch, which will probably never work in workerd. You can use the alias config to replace any of these imports with a module of your choice.

    Let's say you make a fetch-nolyfill.js

    export default fetch; // all this does is export the standard fetch function`

    You can then configure wrangler.toml like so:

    # ...
[alias]
"node-fetch": "./fetch-nolyfill"

    So any calls to import fetch from 'node-fetch'; will simply use our nolyfilled version.

    You can also pass aliases in the cli (for both dev and deploy). Like:

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
changeset-bot[bot] commented 2 months ago

⚠️ No Changeset found

Latest commit: a1b7ae7a588c7e68e030eae6080ad1655edee1b7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

dependabot[bot] commented 2 months ago

Superseded by #396.