search

palantir / conjure-rust-runtime

Rust implementation of the Conjure runtime
10 stars 7 forks source link

Update http requirement from 0.2 to 1.0 #170

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 1 year ago

Updates the requirements on http to permit the latest version.

Release notes

Sourced from http's releases.

v1.0.0

What's Changed

  • Implement Clone for Request, Response, and Extensions. This breaking change requires that all extensions now implement Clone.
  • Add a default-on std feature. Disabling it currently is not supported.
  • Fix MIRI warnings in HeaderMap::iter().

New Contributors

Changelog

Sourced from http's changelog.

1.0.0 (November 15, 2023)

  • Implement Clone for Request, Response, and Extensions. This breaking change requires that all extensions now implement Clone.
  • Add a default-on std feature. Disabling it currently is not supported.
  • Fix MIRI warnings in HeaderMap::iter().

0.2.10 (November 10, 2023)

  • Fix parsing of Authority to handle square brackets in incorrect order.
  • Fix HeaderMap::with_capacity() to handle arithmetic overflow.

0.2.9 (February 17, 2023)

  • Add HeaderName constants for cache-status and cdn-cache-control.
  • Implement Hash for PathAndQuery.
  • Re-export HeaderName at crate root.

0.2.8 (June 6, 2022)

  • Fix internal usage of uninitialized memory to use MaybeUninit inside HeaderName.

0.2.7 (April 28, 2022)

  • MSRV bumped to 1.49.
  • Add extend() method to Extensions.
  • Add From<Authority> and From<PathAndQuery> impls for Uri.
  • Make HeaderName::from_static a const fn.

0.2.6 (December 30, 2021)

  • Upgrade internal itoa dependency to 1.0.

0.2.5 (September 21, 2021)

  • Add is_empty() and len() methods to Extensions.
  • Add version_ref() method to request::Builder.
  • Implement TryFrom<Vec<u8>> and TryFrom<String> for Authority, Uri, PathAndQuery, and HeaderName.
  • Make HeaderValue::from_static a const fn.

0.2.4 (April 4, 2021)

  • Fix Uri parsing to allow {, ", and } in paths.

0.2.3 (January 7, 2021)

  • Upgrade internal (private) bytes dependency to 1.0.

0.2.2 (December 14, 2020)

... (truncated)

Commits


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 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)
changelog-app[bot] commented 1 year ago

Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir

What do the change types mean? - `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._
How are new versions calculated? - ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.

Type

- [ ] Feature - [ ] Improvement - [ ] Fix - [ ] Break - [ ] Deprecation - [ ] Manual task - [ ] Migration

Description

Update http requirement from 0.2 to 1.0 **Check the box to generate changelog(s)** - [ ] Generate changelog entry
dependabot[bot] commented 10 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.