# Combine several artifact in a single release
**URL:** https://hub.mender.io/t/combine-several-artifact-in-a-single-release/4426
**Category:** General Discussions
**Created:** [December 24, 2021, 7:45am UTC](https://hub.mender.io/t/combine-several-artifact-in-a-single-release/4426 "2021-12-24T07:45:53Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@dimaxano](https://hub.mender.io/u/dimaxano)
#### Post date: [December 24, 2021, 7:45am UTC](https://hub.mender.io/t/combine-several-artifact-in-a-single-release/4426/1 "2021-12-24T07:45:53Z")
Hi!
I have several microcontrollers connected to my Raspberry and can update them via custom mender from Raspberry.
But also I have some software running on Raspberry that also should be updated from mender (and it can be)
What I want is to create a single release with Artifact1 (for microcontrollers) + Artifact2 (raspberry software), and deploy them one after the other in single deployment process
I see from Mender docs that there is such entity as Release, but in practice I can add multiple artifact to it only if they are for different Devices
So the question is Can I create a release with several artifact for the same device?
---
### Author:  [@oleorhagen](https://hub.mender.io/u/oleorhagen)
#### Post date: [December 24, 2021, 10:51am UTC](https://hub.mender.io/t/combine-several-artifact-in-a-single-release/4426/2 "2021-12-24T10:51:51Z")
Hi @dimaxano
This is not supported at the moment.
@eystein can probably give you more information on the schedule here.
In general there are two ways, and none of them are supported at the moment.
1. Multi payload Artifacts → read more [here](https://hub.mender.io/t/creation-of-artifact-which-supports-multiple-payloads/1952)
2. Multi Artifact deployments → Also not supported at the moment, but is an interesting application imo.
---
### Author:  [@eystein](https://hub.mender.io/u/eystein)
#### Post date: [January 3, 2022, 5:23pm UTC](https://hub.mender.io/t/combine-several-artifact-in-a-single-release/4426/3 "2022-01-03T17:23:04Z")
Hello @dimaxano
Is your Raspberry Pi and Microcontroller software dependent on each other? In other words, do you always want to update _both_ at the same time?
If not, then I think you could simply use an Update Module to update your micro-controller and a different one (e.g. the built-in rootfs-image) to update your Raspberry Pi with independent Artifacts (and Releases).
If they _are_ always dependent then I would use a custom Update Module or State scripts to “mimic” support for multi-payload Artifacts (e.g. see the link posted above).
Does it make sense?