-
Notifications
You must be signed in to change notification settings - Fork 22
Update charmcraft.yaml build tools #554
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
Merged
Merged
Conversation
This file contains hidden or 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
carlcsaposs-canonical
approved these changes
Jan 15, 2025
1f71829
to
74c253f
Compare
paulomach
approved these changes
Jan 17, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checked rebase for getting test fixes
74c253f
to
42f4e7d
Compare
taurus-forever
approved these changes
Jan 17, 2025
5aa28c8
to
48e2706
Compare
2f138d3
to
930f3ed
Compare
b6eafe6
to
adce40b
Compare
058900d
to
c7d5f43
Compare
c7d5f43
to
24248d0
Compare
0e43b10
to
b651623
Compare
04ce57e
to
4d37a42
Compare
4d37a42
to
6569cb4
Compare
d69cd6c
to
3fe8cbf
Compare
b6753f8
to
6924e7f
Compare
6924e7f
to
41eb6e2
Compare
b143fa7
to
7e4b398
Compare
7e4b398
to
e8b08a2
Compare
e8b08a2
to
576960d
Compare
76b084e
to
dfca9d6
Compare
2d4c952
to
9c4ca89
Compare
9c4ca89
to
a0f3c93
Compare
9b778fd
to
5df45d9
Compare
88fe2ff
to
2557901
Compare
2557901
to
bb160b6
Compare
bb160b6
to
83c52b9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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:
2.0.0
->2.1.4
1.8.0
->1.9.0
1.83.0
->1.89.0
0.5.15
->0.8.12
Release Notes
python-poetry/poetry (poetry)
v2.1.4
Compare Source
Changed
virtualenv<20.33
to work around an issue where Poetry uses the wrong Python version (#10491).pyproject.toml
file (#10471).Fixed
poetry install
was called with--no-plugins
(#10405).Docs
poetry add
if no version constraint is explicitly specified (#10445).v2.1.3
Compare Source
Changed
importlib-metadata<8.7
for Python 3.9 because of a breaking change in importlib-metadata 8.7 (#10374).Fixed
--directory
option did not work if a plugin, which accesses the poetry instance during its activation, was installed (#10352).poetry env activate -v
printed additional information to stdout instead of stderr so that the output could not be used as designed (#10353).poetry-core (
2.1.3
)project
section were treated as non-optional when a source was defined for them in thetool.poetry
section (#857).===
were not parsed correctly (#860).extra
markers with a value starting with "in" were not validated correctly (#862).v2.1.2
Compare Source
Changed
Fixed
poetry lock
was not deterministic (#10276).poetry env activate
returned the wrong command fortcsh
(#10243).poetry env activate
returned the wrong command forpwsh
on Linux (#10256).Docs
poetry-core (
2.1.2
)#846).
extra
markers were not simplified (#842,#845,
#847).
python_version
markers was not recognized as empty (#849).python_version
markers were not simplified (#848,#851).
v2.1.1
Compare Source
Fixed
poetry env use python
does not choose the Python from the PATH (#10187).poetry-core (
2.1.1
)python_version
marker resulted in an invalid marker (#838).v2.1.0
Compare Source
Added
build
command build-system agnostic (#10059,#10092).
--config-settings
option topoetry build
(#10059).config-settings
when building dependencies (#10129).findpython
to find the Python interpreters (#10097).--no-truncate
option topoetry show
(#9580).#10065,
#10126,
#10127,
#10132).
Changed
poetry new
defaults to "src" layout by default (#10135).#10114,
#10138,
#10146).
--priority
(#10134).Fixed
#10067,
#10128).
poetry init
was not able to find a package on PyPI while adding dependencies interactively (#10055).@latest
descriptor was incorrectly passed to the core requirement parser (#10069).True
(in contrast totrue
) were interpreted asfalse
(#10080).poetry env activate
reported a misleading error message (#10087).poetry add --optional
would not correctly update the lock file (#10076).pip
was not installed/updated before other dependencies resulting in a race condition (#10102).keyring
simultaneously (#10062).zipapp
(#10074).Docs
env
commands (#10027).name
andversion
fields are always required if theproject
section is specified (#10033).project.gui-scripts
#10121.#10133).
poetry-core (
2.1.0
)__pycache__
directory and*.pyc
files were included in sdists and wheels (#835).v2.0.1
Compare Source
Added
poetry search
in legacy sources (#9949).poetry source show
output when PyPI is implicitly enabled (#9974).Changed
Fixed
poetry sync
did not remove packages that were not requested (#9946).poetry check
failed even though there were just warnings and add a--strict
option to fail on warnings (#9983).poetry update
,poetry add
andpoetry remove
with--only
uninstalled packages from other groups (#10014).poetry update
,poetry add
andpoetry remove
uninstalled all extra packages (#10016).poetry self update
did not recognize Poetry's own environment (#9995).poetry install
started withWarning:
instead ofError:
(#9945).Command.set_poetry
, which is used by plugins, was removed (#9981).poetry build --clean
showed a malformed short option instead of the description (#9994).Docs
project
section (#9996).project.readme
andproject.urls
(#9948).poetry install --sync
withpoetry sync
in the section about synchronizing dependencies (#9944).poetry shell
withpoetry env activate
in the basic usage section (#9963).project.name
is always required when theproject
section is used (#9989).poetry-plugin-export
in the section aboutpoetry export
(#9954).poetry-core (
2.0.1
)Home-page
withProject-URL: Homepage
(#807).tool.poetry.packages
without a specifiedformat
were not initialized with the default value resulting in aKeyError
(#805).project.urls
entries were not processed correctly resulting in aKeyError
(#807).project.dependencies
viatool.poetry.dependencies
were ignored ifproject.optional-dependencies
were defined (#811).python-poetry/poetry-plugin-export (poetry-plugin-export)
v1.9.0
Compare Source
Added
--all-groups
option to export dependencies from all groups (#294).Changed
--with
and--only
and deprecate--without
(#212).poetry.lock
file is not consistent with thepyproject.toml
file (#310).Fixed
"dependency walk failed"
.This fix requires a
poetry.lock
file created with Poetry 2.x (#286).pre-commit
hook regex matched wrong files (#285).rust-lang/rust (rust-lang/rust)
v1.89.0
Compare Source
==========================
Language
feature(generic_arg_infer)
)mismatched_lifetime_syntaxes
lint.This lint detects when the same lifetime is referred to by different syntax categories between function arguments and return values, which can be confusing to read, especially in unsafe code.
This lint supersedes the warn-by-default
elided_named_lifetimes
lint.unpredictable_function_pointer_comparisons
to also lint on function pointer comparisons in external macrosdangerous_implicit_autorefs
lint deny-by-defaultkl
andwidekl
target features for x86sha512
,sm3
andsm4
target features for x86f
,d
,frecipe
,lasx
,lbt
,lsx
, andlvz
i128
andu128
fromimproper_ctypes_definitions
repr128
(#[repr(u128)]
,#[repr(i128)]
)#![doc(test(attr(..)))]
everywhereextern "C"
functions on thewasm32-unknown-unknown
target now have a standards compliant ABICompiler
Platform Support
loongarch32-unknown-none
andloongarch32-unknown-none-softfloat
x86_64-apple-darwin
is in the process of being demoted to Tier 2 with host toolsRefer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
file!
format_args!()
in a variable#[must_use]
to[T; N]::map
DerefMut
forLazy{Cell,Lock}
Default
forarray::IntoIter
Clone
forslice::ChunkBy
io::Seek
forio::Take
Stabilized APIs
NonZero<char>
SHA512
,SM3
andSM4
intrinsicsFile::lock
File::lock_shared
File::try_lock
File::try_lock_shared
File::unlock
NonNull::from_ref
NonNull::from_mut
NonNull::without_provenance
NonNull::with_exposed_provenance
NonNull::expose_provenance
OsString::leak
PathBuf::leak
Result::flatten
std::os::linux::net::TcpStreamExt::quickack
std::os::linux::net::TcpStreamExt::set_quickack
These previously stable APIs are now stable in const contexts:
<[T; N]>::as_mut_slice
<[u8]>::eq_ignore_ascii_case
str::eq_ignore_ascii_case
Cargo
cargo fix
andcargo clippy --fix
now default to the same Cargo target selection as other build commands. Previously it would apply to all targets (like binaries, examples, tests, etc.). The--edition
flag still applies to all targets.runner
setting to run the tests. If you need to disable tests for a target, you can use the ignore doctest attribute to specify the targets to ignore.Rustdoc
Compatibility Notes
missing_fragment_specifier
an unconditional errorneon
target feature onaarch64-unknown-none-softfloat
causes a warning because mixing code with and without that target feature is not properly supported by LLVM?Sized
bounds on impls on recursive types which contain associated type projections. It is not expected to affect any existing published crates. Can be fixed by refactoring the involved types or opting into thesized_hierarchy
unstable feature. See the FCP report for a code example.elided_named_lifetimes
lint is superseded by the warn-by-defaultmismatched_lifetime_syntaxes
lint.Copy
are now only available at the end of type checkingstd::intrinsics::{copy,copy_nonoverlapping,write_bytes}
are now proper intrinsics. There are no debug assertions guarding against UB, and they cannot be coerced to function pointers.std::intrinsics::drop_in_place
!
) are now reported in dependenciesstd::ptr::copy_*
intrinsics also perform the static self-init checksextern "C"
functions on thewasm32-unknown-unknown
target now have a standards compliant ABIInternal 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.
rustc-dev
componentv1.88.0
Compare Source
==========================
Language
#![feature(let_chains)]
in the 2024 edition.This feature allows
&&
-chaininglet
statements insideif
andwhile
, allowing intermixture with boolean expressions. The patterns inside thelet
sub-expressions can be irrefutable or refutable.#![feature(naked_functions)]
.Naked functions allow writing functions with no compiler-generated epilogue and prologue, allowing full control over the generated assembly for a particular function.
#![feature(cfg_boolean_literals)]
.This allows using boolean literals as
cfg
predicates, e.g.#[cfg(true)]
and#[cfg(false)]
.#[bench]
attribute. Usage of#[bench]
without#![feature(custom_test_frameworks)]
already triggered a deny-by-default future-incompatibility lint since Rust 1.77, but will now become a hard error.dangerous_implicit_autorefs
lint against implicit autoref of raw pointer dereference.The lint will be bumped to deny-by-default in the next version of Rust.
invalid_null_arguments
lint to prevent invalid usage of null pointers.This lint is uplifted from
clippy::invalid_null_ptr_usage
.Compiler
-Cdwarf-version
for selecting the version of DWARF debug information to generate.Platform Support
i686-pc-windows-gnu
to Tier 2.Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
#[should_panic]
test failure message.[T; N]::from_fn
is generated in order of increasing indices., for those passing it a stateful closure.--nocapture
is deprecated in favor of the more consistent--no-capture
flag.{float}::NAN
is a quiet NaN.Stabilized APIs
Cell::update
impl Default for *const T
impl Default for *mut T
HashMap::extract_if
HashSet::extract_if
hint::select_unpredictable
proc_macro::Span::line
proc_macro::Span::column
proc_macro::Span::start
proc_macro::Span::end
proc_macro::Span::file
proc_macro::Span::local_file
<[T]>::as_chunks
<[T]>::as_chunks_mut
<[T]>::as_chunks_unchecked
<[T]>::as_chunks_unchecked_mut
<[T]>::as_rchunks
<[T]>::as_rchunks_mut
mod ffi::c_str
These previously stable APIs are now stable in const contexts:
NonNull<T>::replace
<*mut T>::replace
std::ptr::swap_nonoverlapping
Cell::replace
Cell::get
Cell::get_mut
Cell::from_mut
Cell::as_slice_of_cells
Cargo
zlib-rs
for gzip compression in rust codeRustdoc
ignore-*
attributes.--test-runtool
and--test-runtool-arg
CLI options to specify a program (like qemu) and its arguments to run a doctest.Compatibility Notes
tt
fragment specifier can often fix these macros.#[bench]
attribute. Usage of#[bench]
without#![feature(custom_test_frameworks)]
already triggered a deny-by-default future-incompatibility lint since Rust 1.77, but will now become a hard error.The borrow checker was overly permissive in some cases, allowing programs that shouldn't have compiled.
v1.87.0
Compare Source
==========================
Language
asm_goto
feature..EXPR
) after unary operators!
,-
, and*
.Self: Sized
bounds inimpl
s for unsized typesfeature(precise_capturing_in_traits)
allowinguse<...>
bounds on return positionimpl Trait
intrait
sCompiler
Platform Support
i586-pc-windows-msvc
targetRefer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
Debug
impl of raw pointersVec::with_capacity
guarantees it allocates with the amount requested, even ifVec::capacity
returns a different number.std::arch
intrinsics which don't take pointer arguments can now be called from safe code if the caller has the appropriate target features already enabled (https://github.com/rust-lang/stdarch/pull/1714, https://github.com/rust-lang/stdarch/pull/1716, https://github.com/rust-lang/stdarch/pull/1717)env::home_dir
ControlFlow
as#[must_use]
assert_eq!
andvec!
now supportconst {...}
expressionsStabilized APIs
Vec::extract_if
vec::ExtractIf
LinkedList::extract_if
linked_list::ExtractIf
<[T]>::split_off
<[T]>::split_off_mut
<[T]>::split_off_first
<[T]>::split_off_first_mut
<[T]>::split_off_last
<[T]>::split_off_last_mut
String::extend_from_within
os_str::Display
OsString::display
OsStr::display
io::pipe
io::PipeReader
io::PipeWriter
impl From<PipeReader> for OwnedHandle
impl From<PipeWriter> for OwnedHandle
impl From<PipeReader> for Stdio
impl From<PipeWriter> for Stdio
impl From<PipeReader> for OwnedFd
impl From<PipeWriter> for OwnedFd
Box<MaybeUninit<T>>::write
impl TryFrom<Vec<u8>> for String
<*const T>::offset_from_unsigned
<*const T>::byte_offset_from_unsigned
<*mut T>::offset_from_unsigned
<*mut T>::byte_offset_from_unsigned
NonNull::offset_from_unsigned
NonNull::byte_offset_from_unsigned
<uN>::cast_signed
NonZero::<uN>::cast_signed
.<iN>::cast_unsigned
.NonZero::<iN>::cast_unsigned
.<uN>::is_multiple_of
<uN>::unbounded_shl
<uN>::unbounded_shr
<iN>::unbounded_shl
<iN>::unbounded_shr
<iN>::midpoint
<str>::from_utf8
<str>::from_utf8_mut
<str>::from_utf8_unchecked
<str>::from_utf8_unchecked_mut
These previously stable APIs are now stable in const contexts:
core::str::from_utf8_mut
<[T]>::copy_from_slice
SocketAddr::set_ip
SocketAddr::set_port
,SocketAddrV4::set_ip
SocketAddrV4::set_port
,SocketAddrV6::set_ip
SocketAddrV6::set_port
SocketAddrV6::set_flowinfo
SocketAddrV6::set_scope_id
char::is_digit
char::is_whitespace
<[[T; N]]>::as_flattened
<[[T; N]]>::as_flattened_mut
String::into_bytes
String::as_str
String::capacity
String::as_bytes
String::len
String::is_empty
String::as_mut_str
String::as_mut_vec
Vec::as_ptr
Vec::as_slice
Vec::capacity
Vec::len
Vec::is_empty
Vec::as_mut_slice
Vec::as_mut_ptr
Cargo
Compatibility Notes
#![crate_name]
attributeDebug
impl of raw pointers print metadata if presentdyn
types are no longer deduplicated..
inside of struct patterns (let Struct { #[attribute] .. }) =
ptr_cast_add_auto_to_object
lint into hard errorstd::arch
intrinsics are now safe to call in some contexts, there may now be newunused_unsafe
warnings in existing codebases.width
andprecision
formatting options to 16 bits on all targetsControlFlow
as#[must_use]
advapi32
, except on win7. Code such as C libraries that were relying on this assumption may need to explicitly link advapi32.cfg(true)
attributes.tt
fragment specifier can often fix these macros.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.86.0
Compare Source
==========================
Language
#[target_feature]
attribute.missing_abi
lint now warns-by-default.--x
) as written in other languages. This was previously a clippy lint,clippy::double_neg
, and is now available directly in Rust asdouble_negations
.repr()
attribute applied to invalid items are now correctly rejected.#![test]
and#![rustfmt::skip]
are no longer accepted in more places than intended.Compiler
-O
to mean-C opt-level=3
instead of-C opt-level=2
to match Cargo's defaults.overflowing_literals
under certain macro environments.Platform Support
i686-unknown-redox
target withi586-unknown-redox
.i686-unknown-hurd-gnu
to Pentium 4.{aarch64-unknown,x86_64-pc}-nto-qnx710_iosock
.For supporting Neutrino QNX 7.1 with
io-socket
network stack.{aarch64-unknown,x86_64-pc}-nto-qnx800
.For supporting Neutrino QNX 8.0 (
no_std
-only).{x86_64,i686}-win7-windows-gnu
.Intended for backwards compatibility with Windows 7.
{x86_64,i686}-win7-windows-msvc
are the Windows MSVC counterparts that already exist as Tier 3 targets.