-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update rust crate lofty to 0.21.0 #22
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/lofty-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
October 1, 2023 16:40
d09f45a
to
2926b79
Compare
renovate
bot
changed the title
Update Rust crate lofty to 0.15.0
Update Rust crate lofty to 0.16.0
Oct 1, 2023
renovate
bot
changed the title
Update Rust crate lofty to 0.16.0
Update Rust crate lofty to 0.16.1
Oct 15, 2023
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
October 15, 2023 19:39
2926b79
to
cde5439
Compare
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
October 29, 2023 19:03
cde5439
to
30ea7c1
Compare
renovate
bot
changed the title
Update Rust crate lofty to 0.16.1
fix(deps): update rust crate lofty to 0.16.1
Oct 29, 2023
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
November 15, 2023 18:51
30ea7c1
to
99eb0ce
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.16.1
fix(deps): update rust crate lofty to 0.17.0
Nov 15, 2023
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.17.0
fix(deps): update rust crate lofty to 0.17.1
Nov 26, 2023
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
November 26, 2023 19:06
99eb0ce
to
522fcb1
Compare
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
January 12, 2024 13:48
522fcb1
to
e8810b6
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.17.1
fix(deps): update rust crate lofty to 0.18.0
Jan 12, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
January 23, 2024 22:37
e8810b6
to
ef0a536
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.18.0
fix(deps): update rust crate lofty to 0.18.2
Jan 23, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
April 21, 2024 20:27
ef0a536
to
4fd02e8
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.18.2
fix(deps): update rust crate lofty to 0.19.0
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
April 26, 2024 15:34
4fd02e8
to
b35f328
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.19.0
fix(deps): update rust crate lofty to 0.19.2
Apr 26, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
May 5, 2024 10:02
b35f328
to
3545b9b
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.19.2
fix(deps): update rust crate lofty to 0.19.0
May 5, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
June 6, 2024 18:06
3545b9b
to
776b50d
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.19.0
fix(deps): update rust crate lofty to 0.20.0
Jun 6, 2024
renovate
bot
force-pushed
the
renovate/lofty-0.x
branch
from
July 29, 2024 14:28
776b50d
to
7969e86
Compare
renovate
bot
changed the title
fix(deps): update rust crate lofty to 0.20.0
fix(deps): update rust crate lofty to 0.21.0
Jul 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.1
->0.21.0
Release Notes
Serial-ATA/lofty-rs (lofty)
v0.21.1
Compare Source
Changed
Fixed
PADDING
blocks (issue) (PR)PADDING
block existed in the original file, and it wasn't placed at the end of the header, it would bemoved without setting the
Last-metadata-block
flag. This would cause decoders to believe that the file was corrupted.v0.21.0
Compare Source
Added
ParseOptions::read_tags
to skip the parsing of tags (issue) (PR)ParseOptions::read_cover_art
(issue) (PR)ParseOptions::implicit_conversions
to prevent automatic data conversions (PR)WriteOptions::use_id3v23
totrue
.Tag::take_filter
(PR)Tag::take
, but allows for per-TagItem
filtering.TagType::Id3v2
, as it allows specifying descriptions and languages for frames.See the docs and PR description for more details.
Changed
Timestamp::parse
with empty inputs will returnNone
when not usingParsingMode::Strict
(PR)ParsingMode::Relaxed
(PR)PopularimeterFrame::as_bytes()
is now falliblePrivateFrame::as_bytes()
is now fallibleFixed
data
atom length is less than 16 bytes (issue)hdlr
atom is an unexpected length (issue)stts
atom has an unrealistically large entry count (issue) (PR)v0.20.1
Compare Source
Fixed
v0.20.0
Compare Source
Added
ItemKey::ParentalAdvisory
forIlst
andId3v2Tag
(issue) (PR)numeric representation. For more information, see: https://docs.mp3tag.de/mapping/#itunesadvisory.
tag::items
module for generic representations of complex tag itemsTimestamp
item for ISO 8601 timestamps (PR)Frame::Timestamp
(PR)preserve_format_specific_items()
(issue) (PR)Tag
. Now they are storedin an immutable container, and silently rejoined with the tag when converting back to the original format
or when writing.
set_lang
andset_description
to allow for generic conversions of additional ID3v2 frames (such as comments) (issue) (PR)BoundTaggedFile::into_inner
to get the original file handle (PR)Changed
ItemKey::FlagCompilation
duringTag
merge (PR)Frame
has been converted to anenum
(PR):AttachedPictureFrame
with the ID"TALB"
, for example.See the PR for a full description of the changes.
Popularimeter
->PopularimeterFrame
SynchronizedText
->SynchronizedTextFrame
Fixed
ItemKey
(issue) (PR)udta
atom is encountered (PR)v0.19.2
Compare Source
Added
impl<T: Length> Truncate for &mut T
v0.19.1
Compare Source
Added
impl<T: Truncate> Truncate for &mut T
(PR)impl<T: Length> Truncate for &T
(PR)Changed
free
atoms will be used when writingilst
tags (issue) (PR)free
atoms immediately surrounding theilst
atom were used.v0.19.0
Compare Source
Added
WriteOptions
to allow for finer grained control over howLofty writes tags. These are best used as global user-configurable options, as most options will
not apply to all files. The defaults are set to be as safe as possible,
see here.
FileLike
, which is a combination of theTruncate
+Length
traitsthat allows one to write to more than just
File
s. In short,Cursor<Vec<u8>>
can now be written to.BitAnd
andBitOr
implementations (PR)ChannelMask::FRONT_LEFT
(PR)ChannelMask::from_{mp4, opus}_channels
OpusProperties
now contains the channel maskAacProperties
now contains the channel masklofty::prelude
module to make trait imports easier (PR)Changed
is the only one that gets preserved, we now check if the frame is empty before replacing.
FileProperties
andChannelMask
have been moved from the root to the newlofty::properties
module (PR)
lofty::config
(PR)lofty::file
(PR)lofty::tag
(PR):Tag
Accessor
TagType
TagItem
ItemKey
ItemValue
lofty::probe
(PR):lofty::picture
(PR):Picture
PictureType
PictureInformation
MimeType
AIFFTextChunks
renamed toAiffTextChunks
RIFFInfoList
renamed toRiffInfoList
Fixed
{PartialOrd, Ord}
(PR)ogg_pager
See [ogg_pager's changelog].
v0.18.2
Compare Source
Fixed
v0.18.1
Compare Source
Fixed
v0.18.0
Compare Source
Added
Mp4Properties::is_drm_protected()
(PR)Id3v2ErrorKind::EmptyFrame
(PR)TagItem
s (PR)ItemKey::IntegerBpm
(issue) (PR)Changed
GENRES[14]
to"R&B"
(Previously"Rhythm & Blues"
) (PR)ParsingMode::Strict
(PR)ItemKey::FlagCompilation
,ItemKey::FlagPodcast
) (PR)Id3v2Tag::get_text()
will now return the raw, unedited string (PR)"/"
to make the string easier to display.Now, null separators are only replaced in
Accessor
methods.It is up to the caller to decide how to handle all other strings.
max_junk_bytes
will now be searched for tags between the start of the file and the first MPEG frame (PR)ItemKey::PodcastReleaseDate
toItemKey::ReleaseDate
(PR)ItemKey::{PodcastURL, PoddcastGlobalUniqueID}
toItemKey::{PodcastUrl, PoddcastGlobalUniqueId}
(issue) (PR)Fixed
dfLa
atom for FLAC streams will now be found, providing better properties (PR)stco
,co64
, andtfhd
) will now be updated when writing (issue) (PR)ItemKey::FlagPodcast
will be checked inTag
->Ilst
conversion (PR)on the stream length, which may or may not be entirely accurate.
Removed
ItemKey::InvolvedPeople
MimeType::None
,Picture
now stores anOption<MimeType>
.TextSizeRestrictions::None
andImageSizeRestrictions::None
TagRestrictions
now stores anOption<TextSizeRestrictions>
andOption<ImageSizeRestrictions>
.Emphasis::None
,MpegProperties
now stores anOption<Emphasis>
.v0.17.1
Compare Source
Changed
ilst
atoms by default (issue) (PR)v0.17.0
Compare Source
Added
ParseOptions::allocation_limit
to change the default allocation limit. (PR)Id3v2Tag::genres
to handle all the ways genres can be stored inTCON
frames. (PR)Changed
Tag
toVorbisComments
,ItemKey::Unknown
s will be checked for spec compliance. (PR)Probe::set_file_type()
will return theProbe
to allow for builder-style usage. (PR)Fixed
parse it as another atom definition. As the specification is broad, there is no way for us to say with certainty
that an identifier is invalid. Now we unfortunately have to guess the validity based on the commonly known atoms.
For this, we follow [TagLib]'s checks.
Removed
Ilst::{track_total, disc_number, disc_total}
(PR)Accessor
. There is no need to keep them around, as they behave the same.v0.16.1
Compare Source
Fixed
ilst
item to have both emptydata
atoms and unexpected (likely vendor-specific) atoms other thandata
.These are both cases we can safely ignore unless using
ParsingMode::Strict
.v0.16.0
Compare Source
Added
id3::v2::{RelativeVolumeAdjustmentFrame, OwnershipFrame, EventTimingCodesFrame, PrivateFrame}
(PR)FrameId
now implementsDisplay
(PR)Id3v2Tag::get_texts
for multi-value text frames (PR)Atom::into_data
Atom::merge
Changed
ParsingMode::Strict
(PR)Id3v2Tag::insert
will now check for frames that are only meant to appearin a tag once and remove them. Those frames are: "MCDI", "ETCO", "MLLT", "SYTC", "RVRB", "PCNT", "RBUF", "POSS", "OWNE", "SEEK", and "ASPI". (PR)
Id3v2Tag::remove
will now take aFrameId
rather than&str
(PR)FrameId
now implementsInto<Cow<'_, str>>
, making it possible to use it inFrame::new
(PR)Id3v2Tag
getters will now use&FrameId
instead of&str
for IDs (PR)Ilst::remove
will now return all of the removed atomsIlst::insert_picture
will now combine all pictures into a singlecovr
atomIlst::insert
will now merge atoms with the same identifier into a single atomParsingMode::Strict
(PR)to encounter in the wild. Now we will just take whichever tag happens to be latest in the stream and
use it, they will not be merged.
ParsingMode::Strict
(issue) (PR)in the wild. Now we will just cap the picture type at 255.
Fixed
incorrect duration and bitrate values.
v0.15.0
Compare Source
Added
Id3v2ErrorKind::UnsupportedFrameId
(PR)FrameValue::KeyValue
for TIPL/TMCL frames (PR)Id3v2Tag::get_user_text
,Id3v2Tag::insert_user_text
, andId3v2Tag::remove_user_text
for working with TXXX frames (PR)ParseOptions::max_junk_bytes
, allowing the parser to sift through junk bytes to find required information, rather thanimmediately declare a file invalid. (discussion) (PR)
WavPackProperties
now contains the channel mask, accessible throughWavPackProperties::channel_mask()
(PR)AiffProperties
to hold additional AIFF-specific informationAiffCompressionType
Changed
Id3v2ErrorKind::BadFrameId
now contains the frame ID (PR)ParsingMode::{Relaxed, BestAttempt}
. The parser will now just move on to the next frame. (PR)0
to line up with ID3v2.This is only used when
set_{track, disk}_total
is used without a correspondingset_{track, disk}
.u32::MAX
will throwErrorKind::TooMuchData
, rather than be silently discarded.AiffFile
will no longer useFileProperties
. It now usesAiffProperties
.Fixed
v0.14.0
Compare Source
Added
BestAttempt
will attempt to fill holes in otherwise valid tag items (PR)Changed
ParsingMode
is nowParsingMode::BestAttempt
(It was previouslyParsingMode::Strict
)This is not configurable yet (issue).
Fixed
plID
atoms (issue) (PR)Removed
id3::util::synchsafe::unsynch_content
. This has been replaced with UnsynchronizedStream.v0.13.0
Compare Source
Added
Tag::remove_empty
/ItemValue::is_empty
(PR)ItemKey::{Barcode, CatalogNumber}
mappings (PR)SynchsafeInteger
trait to convert multiple integer types to/from their unsynchronized variants (PR)FrameValue
variants (PR)ItemKey::Barcode
mapping (PR)Changed
ID3v1Tag
->Id3v1Tag
SyncTextInformation
no longer uses a String for its language (PR)FrameID
->FrameId
ID3v2Version
->Id3v2Version
ID3v2TagFlags
->Id3v2TagFlags
ID3v2Tag
->Id3v2Tag
MPEGFile
->MpegFile
MPEGProperties
->MpegProperties
Fixed
Removed
ID3v2ErrorKind::Other
have been replaced with concrete errorsSyncTextInformation
andGEOBInformation
have been flattened into their respective items (PR)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.
This PR was generated by Mend Renovate. View the repository job log.