# Create release from .sh file

**URL:** <https://hub.mender.io/t/create-release-from-sh-file/7704>\
**Category:** General Discussions\
**Created:** [April 9, 2025, 1:19am UTC](https://hub.mender.io/t/create-release-from-sh-file/7704 "2025-04-09T01:19:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [April 9, 2025, 11:11am UTC](https://hub.mender.io/t/create-release-from-sh-file/7704/2 "2025-04-09T11:11:40Z")

</div>

Hi @thiagonzalez,

Two things:

- If you want your update essentially to run a script, well then… use the script Update Module: [Script](https://hub.mender.io/t/script/328)
- second, `ArtifactInstall` state scripts need to be bundled with the artifact. See: [State scripts | Mender documentation](https://docs.mender.io/artifact-creation/state-scripts#root-filesystem-and-artifact-scripts)

But generally, I’d consider your approach a really bad practice. What’s the point of rolling out an update which then relies on an additional mechanism - hopes for it not to fail - and leaves out most of the system?  
So in a nutshell, if you want up keep your system current including the latest Firefox maintenance release, why don’t you just do a full system update?

Greetz,  
Josef

---

_[View the full topic](https://hub.mender.io/t/create-release-from-sh-file/7704)._