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

Update Rust crate base64 to 0.22.0 #18

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2022

This PR contains the following updates:

Package Type Update Change
base64 dependencies minor 0.13.0 -> 0.22.0

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

marshallpierce/rust-base64 (base64)

v0.22.1

Compare Source

  • Correct the symbols used for the predefined alphabet::BIN_HEX.

v0.22.0

Compare Source

  • DecodeSliceError::OutputSliceTooSmall is now conservative rather than precise. That is, the error will only occur if the decoded output cannot fit, meaning that Engine::decode_slice can now be used with exactly-sized output slices. As part of this, Engine::internal_decode now returns DecodeSliceError instead of DecodeError, but that is not expected to affect any external callers.
  • DecodeError::InvalidLength now refers specifically to the number of valid symbols being invalid (i.e. len % 4 == 1), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for either InvalidLength or InvalidByte being appropriate.
  • Decoding is somewhat faster (5-10%)

v0.21.7

Compare Source

  • Support getting an alphabet's contents as a str via Alphabet::as_str()

v0.21.6

Compare Source

  • Improved introductory documentation and example

v0.21.5

Compare Source

  • Add Debug and Clone impls for the general purpose Engine

v0.21.4

Compare Source

  • Make encoded_len const, allowing the creation of arrays sized to encode compile-time-known data lengths

v0.21.3

Compare Source

  • Implement source instead of cause on Error types
  • Roll back MSRV to 1.48.0 so Debian can continue to live in a time warp
  • Slightly faster chunked encoding for short inputs
  • Decrease binary size

v0.21.2

Compare Source

  • Rollback MSRV to 1.57.0 -- only dev dependencies need 1.60, not the main code

v0.21.1

Compare Source

  • Remove the possibility of panicking during decoded length calculations
  • DecoderReader no longer sometimes erroneously ignores
    padding #​226

Breaking changes

  • Engine.internal_decode return type changed
  • Update MSRV to 1.60.0

v0.21.0

Compare Source

Migration

Functions
< 0.20 function 0.21 equivalent
encode() engine::general_purpose::STANDARD.encode() or prelude::BASE64_STANDARD.encode()
encode_config() engine.encode()
encode_config_buf() engine.encode_string()
encode_config_slice() engine.encode_slice()
decode() engine::general_purpose::STANDARD.decode() or prelude::BASE64_STANDARD.decode()
decode_config() engine.decode()
decode_config_buf() engine.decode_vec()
decode_config_slice() engine.decode_slice()

The short-lived 0.20 functions were the 0.13 functions with config replaced with engine.

Padding

If applicable, use the preset engines engine::STANDARD, engine::STANDARD_NO_PAD, engine::URL_SAFE,
or engine::URL_SAFE_NO_PAD.
The NO_PAD ones require that padding is absent when decoding, and the others require that
canonical padding is present .

If you need the < 0.20 behavior that did not care about padding, or want to recreate < 0.20.0's predefined Configs
precisely, see the following table.

0.13.1 Config 0.20.0+ alphabet encode_padding decode_padding_mode
STANDARD STANDARD true Indifferent
STANDARD_NO_PAD STANDARD false Indifferent
URL_SAFE URL_SAFE true Indifferent
URL_SAFE_NO_PAD URL_SAFE false Indifferent

v0.20.0

Compare Source

Breaking changes

  • Update MSRV to 1.57.0
  • Decoding can now either ignore padding, require correct padding, or require no padding. The default is to require
    correct padding.
    • The NO_PAD config now requires that padding be absent when decoding.

0.20.0-alpha.1

Breaking changes
  • Extended the Config concept into the Engine abstraction, allowing the user to pick different encoding / decoding
    implementations.
    • What was formerly the only algorithm is now the FastPortable engine, so named because it's portable (works on
      any CPU) and relatively fast.
    • This opens the door to a portable constant-time
      implementation (#​153,
      presumably ConstantTimePortable?) for security-sensitive applications that need side-channel resistance, and
      CPU-specific SIMD implementations for more speed.
    • Standard base64 per the RFC is available via DEFAULT_ENGINE. To use different alphabets or other settings (
      padding, etc), create your own engine instance.
  • CharacterSet is now Alphabet (per the RFC), and allows creating custom alphabets. The corresponding tables that
    were previously code-generated are now built dynamically.
  • Since there are already multiple breaking changes, various functions are renamed to be more consistent and
    discoverable.
  • MSRV is now 1.47.0 to allow various things to use const fn.
  • DecoderReader now owns its inner reader, and can expose it via into_inner(). For symmetry, EncoderWriter can do
    the same with its writer.
  • encoded_len is now public so you can size encode buffers precisely.

v0.13.1

Compare Source

  • More precise decode buffer sizing, avoiding unnecessary allocation in decode_config.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate bot changed the title Update Rust crate base64 to 0.13.1 Update Rust crate base64 to 0.20.0 Dec 10, 2022
@renovate renovate bot changed the title Update Rust crate base64 to 0.20.0 Update Rust crate base64 to 0.21.0 Jan 8, 2023
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.0 Update Rust crate base64 to 0.21.2 May 28, 2023
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.2 Update Rust crate base64 to 0.21.3 Aug 26, 2023
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.3 Update Rust crate base64 to 0.21.4 Sep 10, 2023
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.4 Update Rust crate base64 to 0.21.5 Oct 23, 2023
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.5 Update Rust crate base64 to 0.21.6 Jan 8, 2024
@renovate renovate bot force-pushed the renovate/base64-0.x branch 2 times, most recently from 1ec3c74 to 7771696 Compare January 11, 2024 17:34
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.6 Update Rust crate base64 to 0.21.7 Jan 11, 2024
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.7 Update Rust crate base64 to 0.22.0 Mar 2, 2024
@renovate renovate bot changed the title Update Rust crate base64 to 0.22.0 Update Rust crate base64 to 0.22.1 May 1, 2024
@renovate renovate bot changed the title Update Rust crate base64 to 0.22.1 Update Rust crate base64 to 0.22.0 May 5, 2024
@lilioid lilioid closed this Oct 22, 2024
@lilioid lilioid deleted the renovate/base64-0.x branch October 22, 2024 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant