4da40a8...
by
Sheng Yu
on 2024-03-13
fix(test): do not create 2 snapcraft.yaml and confuse location
The old fixture may create 2 snapcraft.yaml in different locations.
And when both /snap and /build-aux exist, build-aux fallback got
ignored.
c492c94...
by
Tiago Nobrega
on 2024-03-14
fix: use "devel" bases on build plan (#4663)
For the BuildInfos we want to use "devel" bases, as that is the term
that craft-providers expects to create instances based on the
development track. We still need to use the regular "base" (e.g.
"core24") in other places, so add a customization parameter to
get_effective_ base() to use either behavior.
2423be3...
by
Sheng Yu
on 2024-03-12
refactor(test): versioned remote-build tests
b601c77...
by
Callahan Kovacs
on 2024-03-13
build(deps): add craft-application to doc requirements
Signed-off-by: Callahan Kovacs <email address hidden>
aab0797...
by
Tiago Nobrega
on 2024-03-11
fix(tests): create a suitable build plan
Create a default build plan with a build info matching the host's architecture
and base, so that individual plan-dependent tests don't have to worry about
tweaking the plan.
7814ba7...
by
Alex Lowe
on 2024-03-09
fix(application): update configure_services
16e66c8...
by
Callahan Kovacs
on 2024-03-11
feat: get build env from command line, env, and snap config
Signed-off-by: Callahan Kovacs <email address hidden>
f771a4a...
by
Callahan Kovacs
on 2024-03-11
feat: add platforms and drop architectures for core24 (#4630)
- Add `platforms` in core24
- Drop `architectures` in core24
Similar to `architectures`, the `platforms` keyword is optional and
defaults to building-on and building-for the host architecture.
As much as possible, I tried to follow charmcraft's and rockcraft's
implementation of platform support.
---------
Signed-off-by: Callahan Kovacs <email address hidden>
3f2ab25...
by
Tiago Nobrega
on 2024-03-08
fix(application): fallback earlier for managed core20 (#4642)
Co-authored-by: Matt Culler <email address hidden>
69e25e1...
by
Sergio Schvezov
on 2024-03-07
feat: setup_assets for core24 metadata (#4622)
The PrimeCommand calls
self._services. package. write_metadata( self._services. lifecycle. prime_dir)
Which makes it simple to hook up.
- [ ] Have you followed the [guidelines for
contributing](https:/ /github. com/snapcore/ snapcraft/ blob/master/ CONTRIBUTING. md )?
- [ ] Have you signed the
[CLA](http:// www.ubuntu. com/legal/ contributors/ )?
- [ ] Have you successfully run `tox run -m lint`?
- [ ] Have you successfully run `tox run -e test-py310`? (supported
versions: `py39`, `py310`, `py311`, `py312`)
-----
Fixes #4592
Signed-off-by: Sergio Schvezov <email address hidden>