[dependabot]

Bumps cf from 1.0.0-beta.26 to 1.0.0-beta.27.

Release notes

Sourced from cf's releases.

cf@1.0.0-beta.27

Minor Changes

• bbe47a8: Give API fields that collide with cf's own flags distinct names

  Generated commands no longer drop, merge, or shadow API fields whose names match a cf flag. cf precursor update --detection-mode sets the previously unreachable mode, and cf o11y telemetry query and cf o11y shared-queries create gain --preview.

  One behavior change: on cf cloudforce-one priority-intelligence profile update, the organization profile is now --organization-profile, and --profile selects the auth profile again. An API parameter named force can no longer take cf's confirmation --force. cf ai run and cf registrar registrations create accept schema fields named after cf flags as --input-<name> (for example --input-quiet), and cf schema lists the flag behind a path or query parameter when it has one.

• 8129166: Update the generated command surface for Forge OpenAPI release 319dc756af2a642b3122b4db7e3b79ac1fbec7d8

  Keep cf auth scopes working with the OAuth scope catalogue's new IAM group.

• aaa712d: Update the generated command surface for Forge OpenAPI release ec5b5772f5cf7dfb16c49f3527671edfa37bb666.

Patch Changes

• cde5fa3: Explain how account-or-zone commands pick their scope

  Commands that serve either an account or a zone, such as cf rulesets list and cf load-balancers account list, now say in --help that they run against your account unless you pass --zone, and that they ignore CLOUDFLARE_ZONE_ID.

• edc13df: Prepare generated commands to preserve audio API responses

  Recognize audio/* responses as binary data in the command generator and its operation descriptors, including schemas without format: binary. Future commands generated for audio endpoints will write the exact bytes to stdout so they can be redirected to a file. No commands generated from the currently pinned OpenAPI specification declare audio responses, so this change does not alter the behavior of any currently shipped command.

• cde5fa3: Reject --zone without a value

  An empty --zone used to fall back to CLOUDFLARE_ZONE_ID, and --dry-run previewed a /zones// path. On commands that serve both an account and a zone, it also switched to zone scope. cf now stops with --zone requires a non-empty value. and, as with --mode, rejects a repeated --zone.

  Commands that forward arguments, such as cf containers ssh, used to drop a -z with no value, so cf containers ssh <id> ls -z ran plain ls. That now stops with the same error. Put forwarded arguments after --, as in cf containers ssh <id> -- ls -z.

• 8e5f074: Keep required HTTP header parameters out of generated JSON request bodies.

  Flags such as --if-match are now sent only as headers rather than also being copied into the body under a generated field name.

... (truncated)

Changelog

Sourced from cf's changelog.

1.0.0-beta.27

Minor Changes

• bbe47a8: Give API fields that collide with cf's own flags distinct names

  Generated commands no longer drop, merge, or shadow API fields whose names match a cf flag. cf precursor update --detection-mode sets the previously unreachable mode, and cf o11y telemetry query and cf o11y shared-queries create gain --preview.

  One behavior change: on cf cloudforce-one priority-intelligence profile update, the organization profile is now --organization-profile, and --profile selects the auth profile again. An API parameter named force can no longer take cf's confirmation --force. cf ai run and cf registrar registrations create accept schema fields named after cf flags as --input-<name> (for example --input-quiet), and cf schema lists the flag behind a path or query parameter when it has one.

• 8129166: Update the generated command surface for Forge OpenAPI release 319dc756af2a642b3122b4db7e3b79ac1fbec7d8

  Keep cf auth scopes working with the OAuth scope catalogue's new IAM group.

• aaa712d: Update the generated command surface for Forge OpenAPI release ec5b5772f5cf7dfb16c49f3527671edfa37bb666.

Patch Changes

• cde5fa3: Explain how account-or-zone commands pick their scope

  Commands that serve either an account or a zone, such as cf rulesets list and cf load-balancers account list, now say in --help that they run against your account unless you pass --zone, and that they ignore CLOUDFLARE_ZONE_ID.

• edc13df: Prepare generated commands to preserve audio API responses

  Recognize audio/* responses as binary data in the command generator and its operation descriptors, including schemas without format: binary. Future commands generated for audio endpoints will write the exact bytes to stdout so they can be redirected to a file. No commands generated from the currently pinned OpenAPI specification declare audio responses, so this change does not alter the behavior of any currently shipped command.

• cde5fa3: Reject --zone without a value

  An empty --zone used to fall back to CLOUDFLARE_ZONE_ID, and --dry-run previewed a /zones// path. On commands that serve both an account and a zone, it also switched to zone scope. cf now stops with --zone requires a non-empty value. and, as with --mode, rejects a repeated --zone.

  Commands that forward arguments, such as cf containers ssh, used to drop a -z with no value, so cf containers ssh <id> ls -z ran plain ls. That now stops with the same error. Put forwarded arguments after --, as in cf containers ssh <id> -- ls -z.

• 8e5f074: Keep required HTTP header parameters out of generated JSON request bodies.

... (truncated)

Commits

• d90de18 Version Packages (beta) (#452)
• 3043819 fix(deps): update workers-sdk derived dependencies (#482)
• 476caa1 chore(deps): update all non-major dependencies (#480)
• aaa712d chore: update OpenAPI to ec5b5772f5cf (#476)
• bbe47a8 fix: give API fields that collide with cf flags their own names (#461)
• 874b8a8 chore(deps): update dependency minimatch to v11 [security] (#473)
• 8129166 chore: update OpenAPI to 319dc756af2a (#447)
• aa0ee04 Correct generated validation for nested optional request-body objects (#459)
• 57bca06 fix: validate nested tagged union request bodies (#336)
• 8e5f074 Keep required HTTP header parameters out of generated JSON request bodies (#460)
• Additional commits viewable in compare view

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 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)