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.

Sign up for GitHub

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

Jump to bottom

Bump wrangler from 3.9.0 to 3.9.1 #15

Merged
merged 1 commit into from
Sep 26, 2023
Merged

Bump wrangler from 3.9.0 to 3.9.1 #15

merged 1 commit into from
Sep 26, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 26, 2023

Bumps wrangler from 3.9.0 to 3.9.1.

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

  • #3992 35564741 Thanks @​edevil! - Add AI binding that will be used to interact with the AI project.

    Example wrangler.toml

    name = "ai-worker"
main = "src/index.ts"

    [ai]
binding = "AI"

    Example script:

    import Ai from "@cloudflare/ai"

    export default {
async fetch(request: Request, env: Env): Promise<Response> {
const ai = new Ai(env.AI);
    

        const story = await ai.run({
        model: 'llama-2',
        input: {
            prompt: 'Tell me a story about the future of the Cloudflare dev platform'
        }
    });

    return new Response(JSON.stringify(story));
    
},
    

    

    };
    

    export interface Env {
AI: any;
}

  • #4006 bc8c147a Thanks @​rozenmd! - fix: remove warning around using D1's binding, and clean up the epilogue when running D1 commands

  • #4027 9e466599 Thanks @​jspspike! - Add WebGPU support through miniflare update

  • #3986 00247a8d Thanks @​edevil! - Added AI related CLI commands

Changelog

Sourced from wrangler's changelog.

3.9.1

Patch Changes

  • #3992 35564741 Thanks @​edevil! - Add AI binding that will be used to interact with the AI project.

    Example wrangler.toml

    name = "ai-worker"
main = "src/index.ts"

    [ai]
binding = "AI"

    Example script:

    import Ai from "@cloudflare/ai"

    export default {
async fetch(request: Request, env: Env): Promise<Response> {
const ai = new Ai(env.AI);
    

        const story = await ai.run({
        model: 'llama-2',
        input: {
            prompt: 'Tell me a story about the future of the Cloudflare dev platform'
        }
    });

    return new Response(JSON.stringify(story));
    
},
    

    

    };
    

    export interface Env {
AI: any;
}

  • #4006 bc8c147a Thanks @​rozenmd! - fix: remove warning around using D1's binding, and clean up the epilogue when running D1 commands
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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump wrangler from 3.9.0 to 3.9.1
fa0bd14 
Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 3.9.0 to 3.9.1.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/[email protected]/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 26, 2023
@socket-security
Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
wrangler 3.9.0...3.9.1 None +7/-7 399 MB wrangler-publisher

@github-actions github-actions bot merged commit c8226f3 into main Sep 26, 2023
6 of 9 checks passed
@socket-security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Chronological version anomaly workerd 1.20230922.0
Chronological version anomaly @cloudflare/workerd-linux-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-linux-arm64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-windows-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-darwin-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-darwin-arm64 1.20230922.0
Chronological version anomaly wrangler 3.9.1

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/wrangler-3.9.1 branch September 26, 2023 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@NikolaRHristov NikolaRHristov Awaiting requested review from NikolaRHristov

Assignees

@NikolaRHristov NikolaRHristov

Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@NikolaRHristov