Bump the dependencies group across 1 directory with 5 updates
Bumps the dependencies group with 5 updates in the / directory:
| Package | From | To |
|---|---|---|
| magnus | 0.7.1 |
0.8.2 |
| bytes | 1.8.0 |
1.10.1 |
| wasi-vfs-cli | v0.5.3-p1 |
v0.5.6 |
| wit-component | 0.216.0 |
0.240.0 |
| wasm-compose | 0.219.1 |
0.240.0 |
Updates magnus from 0.7.1 to 0.8.2
Release notes
Sourced from magnus's releases.
0.8.2
Magnus 0.8.2 is a patch release, with 1 bug fix.
Fixes an incorrect error message when converting a Ruby string to a Rust string fails. Thanks to
@jeffcharlesfor this fix.See the 0.8.0 release for what's new in 0.8.
0.8.1
Magnus 0.8.1 is a patch release, with 1 bug fix.
Fixes a compilation error on 32-bit platforms. Thanks to
@jonianfor reporting this issue.See the 0.8.0 release for what's new in 0.8.
0.8.0
Magnus 0.8.0 adds a handful of features and fixes. The
old-apifeature introduced in 0.7.0 is no longer a default feature, so functions marked as part of the old API will be deprecated by default. Otherwise it is largely compatible with 0.7.Magnus is a Rust library providing a high-level easy-to-use interface to the C API of the Ruby programming language. Magnus lets you write Ruby extension libraries (or 'gems') in Rust, or embed Ruby in your Rust program.
Fixes
- The
fatalexception raised when a Rust function bound to Ruby panics can no longer be caught withrescue Exception.- Fixed type bounds for
TryConvertOwnedfor(T, ...)so thatTmust beTryConvertOwned.API changes
The minimum supported Rust version in now 1.65.
Magnus 0.5 and earlier would allow you to create Ruby objects with associated functions, like
RArray::new. In Magnus 0.6 a new set of APIs for creating Ruby objects was added, as methods on aRubyhandle that can only be obtained on a Ruby thread. The older associated functions API is now marked as deprecated by default. Theold-apifeature can be enabled to disable deprecation warnings for the old API. In a future version of Magnus will remove this feature.The
FStringtype has been removed as it can not safely uphold the promise it was making. Either due to Ruby's apis changing or a misinterpretation of old documentation it had been designed assuming interned strings (aka 'fstrings') would not be garbage collected, which is not the case.Conversions between Ruby's
Timeand Rust'sSystemTimenow preserve nanosecond precision.
RString::to_stringwill now use a Ruby utf-8 validation api that caches the results of the validity check. This will greatly improve performance in the case a string is already known to be utf-8, but may slightly reduce performance when not known.New Features
Ruby::time_nano_new,Ruby::time_timespec_new, andTime::timespec.- The
chronofeature can be enabled to allow automatic conversions betweenchrono::DateTime<Utc>andchrono::DateTime<FixedOffset>and RubyTimeobjects.typed_data::Writebarrier::writebarrierandwritebarrier_unprotect.- Automatic type conversions for
NonZerotypes,i128/u128, andBTreeMap.Ruby::io_extract_modeenc.Upgrading
Upgrading from Magnus 0.6 or 0.7 should be straightforward. If upgrading from 0.5 or earlier, it's recommended to upgrade to 0.6 first.
... (truncated)
Changelog
Sourced from magnus's changelog.
[0.8.2] - 2025-10-07
Fixed
- Fixed error message when converting Ruby string to a Rust string.
[0.8.1] - 2025-09-06
Fixed
- Fixed error compiling on 32-bit platforms.
[0.8.0] - 2025-08-25
Added
Ruby::time_nano_new,Ruby::time_timespec_new, andTime::timespec.- The
chronofeature can be enabled to allow automatic conversions betweenchrono::DateTime<Utc>andchrono::DateTime<FixedOffset>and RubyTimeobjects.typed_data::Writebarrier::writebarrierandwritebarrier_unprotect.- Implement
TryConvertforNonZerotypes.iomodule available withiofeature, supportingio_extract_modeenc,OpenFlags,FMode, andIoEncoding.Ruby::io_extract_modeenc, a safe wrapper aroundrb_io_extract_modeenc, allowing structured extraction of open flags, mode flags, and IO encoding metadata.OpenFlagsstruct, which wraps Ruby'sO_open flags (e.g.O_RDONLY,O_CREAT) in a convenient bitflag-like interface.FModestruct, representingFMODE_flags used internally by Ruby to represent IO modes (READ,WRITE,BINARY_MODE, etc.).IoEncoding, a safe Rust struct for temporarily owning and inspectingrb_io_encoding, including safe accessors for internal/external encoding and encoding options.- Automatic type conversions to/from
i128/u128.to_i128/to_u128forFixnum/Bignum/Integer.Ruby::integer_from_i128&Ruby::integer_from_u128.RHash::to_btree_mapand automatic conversion fromHashtoBTreeMap.Changed
- Minimum supported Rust version is now 1.65.
- Conversions between Ruby's
Timeand Rust'sSystemTimenow preserve nanosecond precision.- 'old-api' feature, which disables deprecation warnings for the old api is no longer a default feature.
RString::to_stringwill now use a Ruby utf-8 validation api that caches the results of the validity check. This will greatly improve performance in the case a string is already known to be utf-8, but may slightly reduce performance when not known.RString::to_interned_strnow returns anRStringrather than anFString.Deprecated
thread_fd_closeas it will be a no-op as of Ruby 3.5Removed
FStringas it can not safely uphold the promise it was making. Either due
... (truncated)
Commits
bca4ea7bump version to 0.8.2feeb66bFix error message when there's an invalid byte sequence6bbb0e2bump version to 0.8.1020eb2dfix for 32bit platforms8fd9288update changelog for 0.8.0 release108c87eMerge pull request #154 from sandbergja/singleton-typo5347568Fix typo: singlton should be singleton56bb429update examples in magnus-macros16c1cc9better fix for change in rb_fiber_raise00db8b1fix doc- Additional commits viewable in compare view
Updates bytes from 1.8.0 to 1.10.1
Release notes
Sourced from bytes's releases.
Bytes v1.10.1
1.10.1 (March 5th, 2025)
Fixed
- Fix memory leak when using
to_vecwithBytes::from_owner(#773)Bytes v1.10.0
1.10.0 (February 3rd, 2025)
Added
- Add feature to support platforms without atomic CAS (#467)
try_get_*methods forBuftrait (#753)- Implement
Buf::chunks_vectoredforTake(#617)- Implement
Buf::chunks_vectoredforVecDeque<u8>(#708)Fixed
- Remove incorrect guarantee for
chunks_vectored(#754)- Ensure that tests pass under
panic=abort(#749)Bytes v1.9.0
1.9.0 (November 27, 2024)
Added
- Add
Bytes::from_ownerto enable externally-allocated memory (#742)Documented
- Fix typo in Buf::chunk() comment (#744)
Internal changes
Changelog
Sourced from bytes's changelog.
1.10.1 (March 5th, 2025)
Fixed
- Fix memory leak when using
to_vecwithBytes::from_owner(#773)1.10.0 (February 3rd, 2025)
Added
- Add feature to support platforms without atomic CAS (#467)
try_get_*methods forBuftrait (#753)- Implement
Buf::chunks_vectoredforTake(#617)- Implement
Buf::chunks_vectoredforVecDeque<u8>(#708)Fixed
- Remove incorrect guarantee for
chunks_vectored(#754)- Ensure that tests pass under
panic=abort(#749)1.9.0 (November 27, 2024)
Added
- Add
Bytes::from_ownerto enable externally-allocated memory (#742)Documented
- Fix typo in Buf::chunk() comment (#744)
Internal changes
Commits
19d1427chore: prepare bytes v1.10.1 (#774)3667543Fix memory leak inowned_to_vec(#773)e0f3a25chore: prepare bytes v1.10.0 (#766)16fd473Add feature to support platforms without atomic CAS (#467)71824b0ci: test AArch64 and run tests instead of build in cross job (#763)7a87660Use [lints] to address unexpected_cfgs lint (#762)3ab876fTry get methods for Buf trait (#753)a1b1208Disable test_bytes_vec_alloc test on miri (#755)aae4969Add specializedBuf::chunks_vectoredforTake(#617)103d7bfRemove incorrect guarantee forchunks_vectored(#754)- Additional commits viewable in compare view
Updates wasi-vfs-cli from v0.5.3-p1 to v0.5.6
Commits
660c2ccStop inheriting all env vars, instead set only specific ones.a2da9b6Update wizer to v836ed250Update minimum node version to 202736b8fbump version 0.5.5b8c5017bump wizer 6.0.0 -> 7.0.010d78aebump version 0.5.4d0c1a5eUpdate upload-artifact and download-artifact to v41987925Use actions-rust-cross for release41e7595Add release version for Linux aarch64- See full diff in compare view
Updates wit-component from 0.216.0 to 0.240.0
Commits
- See full diff in compare view
Updates wasm-compose from 0.219.1 to 0.240.0
Commits
- See full diff 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) -
@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) -
@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) -
@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency -
@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions