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

chore(deps): update all non-major dependencies #52

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2024

This PR contains the following updates:

Package Type Update Change
cocogitto/cocogitto-action action minor v3.8 -> v3.9
lalrpop build-dependencies minor 0.20.0 -> 0.22.0
lalrpop-util dependencies minor 0.20.0 -> 0.22.0
logos (source) dependencies minor 0.12 -> 0.14
rowan dependencies minor 0.15 -> 0.16
rust minor 1.80.0 -> 1.82.0
smol_str dependencies minor 0.2 -> 0.3

Release Notes

cocogitto/cocogitto-action (cocogitto/cocogitto-action)

v3.9

Compare Source

What's Changed

Full Changelog: cocogitto/cocogitto-action@v3.8...v3.9

lalrpop/lalrpop (lalrpop)

v0.22.0

Compare Source

Breaking changes
  • The lexer feature no longer implies the std feature. Now lexer is
    usable in no_std environments. In no_std, ParseError only implements the
    Error trait in rust 1.81 or later (since core::error was stablized in 1.81).
Features
  • Overhaul cfg attributes. You can now include or omit grammar rules and
    alternatives based on cargo features with not(), any() and all() support
Bugfixes
  • Improvements to error message reporting to improve clarity and suppress extra noise
  • lalrpop_mod!() now handles imports correctly
  • Reenable some warnings on user code for custom lexers

v0.21.0

Compare Source

Since the last release, a fair number of the commits have been focused on cleaning
up and improving LALRPOP's documentation. Shout out to Yudai Takada, George
White, and Dinu Blanovschi.

Features
  • LALRPOP now throws an error in more cases where it would previously just write
    out an error message and exit.
  • lalrpop::process_src is now the recommended function to use in build.rs
    files. Previously the documentation incorrectly suggested that
    lalrpop::process_root looked in ./src instead of .
Bugfixes
  • A long-standing bug where LALRPOP would throw a "no entry found for key"
    exception when trying to handle certain grammars has been resolved.
  • LALRPOP will stop expanding macros infinitely during build time via a new
    macro_expansion_limit.
Compatibility note

Adding a limit to the number of times that LALRPOP will attempt to expand a
macro is technically a breaking change. However, the default limit of 200
should be more than enough for the grammars we are currently aware of (which
almost always need a limit of less than 5). This limit is customizable via Configuration::set_macro_expansion_limit.

If you have a grammar that uses a significant amount of macro expansion steps,
we would be very interested in a PR that adds it to the test suite.

v0.20.2

Compare Source

Special thanks to our newest maintainers, Daniel Burgener and Patrick LaFontaine for helping to coordinate this release.

Features
  • Lalrpop no longer depends on the is-terminal crate (thanks to Kmeakin!)
  • Better performance with the default lexer using the underlying regex-automata crate (thanks to QuarticCat!)
  • Allow the catch-all _ case for token matching can now be set to a higher precedence in match (thanks to fpoli!)
  • Fewer clippy lints triggered in generated code
  • Lalrpop now traverses symlinks to find .lalrpop files(thanks mbid!)
  • Lalrpop now supports block comments including nestings(thanks seanbright!)
Bugfixes
  • Lalrpop now uses the ascii-aware space regex when the unicode feature is not enabled (thanks to QuarticCat!)
  • Dangling symlinks in crate no longer cause build failure (thanks to legeana
    for the report!)
  • Unicode is now set as a default feature in lalrpop-util to align with
    lalrpop's defaults
Compatibility note
  • MSRV increased to 1.70.
  • process_root_unconditionally now correctly lints as having been deprecated.
  • Internal types which lead with a __ and should not be relied upon are no longer publicly exposed (thanks to arnaudgolfouse!)
  • Lalrpop files containing a space in their name now return an error.

v0.20.1

Compare Source

Yanked

maciejhirsz/logos (logos)

v0.14.2: - Optional forbid_unsafe feature, fuzzing, book, and more!

Compare Source

What's Changed

New Contributors

Full Changelog: maciejhirsz/logos@v0.14.1...v0.14.2

v0.14.1: 0.14.1 - Debug feature and fixes

What's Changed

New Contributors

Full Changelog: maciejhirsz/logos@v0.14...v0.14.1

rust-analyzer/rowan (rowan)

v0.16.0

Compare Source

rust-lang/rust (rust)

v1.82.0

Compare Source

==========================

Language

Compiler

Libraries

Stabilized APIs

These APIs are now stable in const contexts:

Cargo

Compatibility Notes

  • We now disallow setting some built-in cfgs via the command-line with the newly added explicit_builtin_cfgs_in_flags lint in order to prevent incoherent state, eg. windows cfg active but target is Linux based. The appropriate rustc flag should be used instead.
  • The standard library has a new implementation of binary_search which is significantly improves performance (#​128254). However when a sorted slice has multiple values which compare equal, the new implementation may select a different value among the equal ones than the old implementation.
  • illumos/Solaris now sets MSG_NOSIGNAL when writing to sockets. This avoids killing the process with SIGPIPE when writing to a closed socket, which matches the existing behavior on other UNIX targets.
  • Removes a problematic hack that always passed the --whole-archive linker flag for tests, which may cause linker errors for code accidentally relying on it.
  • The WebAssembly target features multivalue and reference-types are now
    both enabled by default. These two features both have subtle changes implied
    for generated WebAssembly binaries. For the multivalue feature, WebAssembly
    target support has changed when upgrading to LLVM 19. Support for generating
    functions with multiple returns no longer works and
    -Ctarget-feature=+multivalue has a different meaning than it did in LLVM 18
    and prior. There is no longer any supported means to generate a module that has
    a function with multiple returns in WebAssembly from Rust source code. For the
    reference-types feature the encoding of immediates in the call_indirect, a
    commonly used instruction by the WebAssembly backend, has changed. Validators
    and parsers which don't understand the reference-types proposal will no
    longer accept modules produced by LLVM due to this change in encoding of
    immediates. Additionally these features being enabled are encoded in the
    target_features custom section and may affect downstream tooling such as
    wasm-opt consuming the module. Generating a WebAssembly module that disables
    default features requires -Zbuild-std support from Cargo and more information
    can be found at
    rust-lang/rust#128511.
  • Rust now raises unsafety errors for union patterns in parameter-position

Internal Changes

These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.

v1.81.0

Compare Source

==========================

Language

Compiler

Libraries

Stabilized APIs

These APIs are now stable in const contexts:

Cargo

Compatibility Notes

  • Usage of the wasm32-wasi target will now issue a compiler warning and request users switch to the wasm32-wasip1 target instead. Both targets are the same, wasm32-wasi is only being renamed, and this change to the WASI target is being done to enable removing wasm32-wasi in January 2025.

  • We have renamed std::panic::PanicInfo to std::panic::PanicHookInfo. The old name will continue to work as an alias, but will result in a deprecation warning starting in Rust 1.82.0.

    core::panic::PanicInfo will remain unchanged, however, as this is now a different type.

    The reason is that these types have different roles: std::panic::PanicHookInfo is the argument to the panic hook in std context (where panics can have an arbitrary payload), while core::panic::PanicInfo is the argument to the #[panic_handler] in no_std context (where panics always carry a formatted message). Separating these types allows us to add more useful methods to these types, such as std::panic::PanicHookInfo::payload_as_str() and core::panic::PanicInfo::message().

  • The new sort implementations may panic if a type's implementation of Ord (or the given comparison function) does not implement a total order as the trait requires. Ord's supertraits (PartialOrd, Eq, and PartialEq) must also be consistent. The previous implementations would not "notice" any problem, but the new implementations have a good chance of detecting inconsistencies, throwing a panic rather than returning knowingly unsorted data.

  • In very rare cases, a change in the internal evaluation order of the trait
    solver may result in new fatal overflow errors.

Internal Changes

These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.

v1.80.1

Compare Source

===========================

rust-analyzer/smol_str (smol_str)

v0.3.2

Compare Source

  • Fix SmolStrBuilder::push incorrectly padding null bytes when spilling onto the heap on a
    multibyte character push

v0.3.1

Compare Source

  • Fix SmolStrBuilder leaking implementation details

v0.3.0

Compare Source

  • Remove deprecated SmolStr::new_inline_from_ascii function
  • Remove SmolStr::to_string in favor of ToString::to_string
  • Add impl AsRef<[u8]> for SmolStr impl
  • Add impl AsRef<OsStr> for SmolStr impl
  • Add impl AsRef<Path> for SmolStr impl
  • Add SmolStrBuilder

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 requested a review from alixinne as a code owner August 19, 2024 22:19
@renovate renovate bot enabled auto-merge (rebase) August 19, 2024 22:19
Copy link
Contributor Author

renovate bot commented Aug 19, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5ed377c to a7f7cab Compare August 19, 2024 22:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a7f7cab to def604b Compare August 26, 2024 22:31
@renovate renovate bot changed the title fix(deps): update rust crate logos to 0.14 chore(deps): update all non-major dependencies Aug 26, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3c1a59b to 81f55c6 Compare September 5, 2024 20:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 197ca6c to 1c502f4 Compare October 2, 2024 16:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from ec33010 to 67d8727 Compare November 11, 2024 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants