Keywords: Release | CLI

When running the VTEX IO CLI command vtex release, it returns an EBADF (error bad file descriptor) message. This happens because a file descriptor variable does not correctly point to a file during command execution.

The vtex release command creates a new version of a VTEX IO app by rewriting the CHANGELOG.md and the manifest.json files. For more details about this process, see Releasing a new app version.

The vtex release command creates a release commit and a release tag and sends the changes to the app repository. Thus, a possible cause of the EBADF message could be improper GitHub configuration. For more details, see the external GitHub documentation.

Instead of depending on the vtex release command to make the changes in the app files for a new version, make the changes manually and continue deploying a new app version.

Consider your app was at version 0.1.0 and a new version 0.1.1 was created on July 15, 2024. Follow the steps below to create a new app version without using the vtex release command:

1. Open the CHANGELOG.md file of your app.

2. Update the version header from ## [Unreleased] to ## [0.1.1] - 2024-07-15, as follows:

   
   

   _12

   - ## [Unreleased]

   _12

   + ## [0.1.1] - 2024-07-15

   _12

   +

   _12

   + ### Added

   _12

   +

   _12

   + * New feature

   _12

   _12

   ## [0.1.0] - 2024-06-03

   _12

   _12

   ### Fixed

   _12

   _12

   * Bug fixes

   
   

3. Open the manifest.json file of your app and change the app version to the new version. In this example, we are changing the version from 0.1.0 to 0.1.1.

   
   

   _10

   "version": “0.1.1”

   
   

4. Open a terminal in the root folder of your app.

5. Run the vtex publish command. This command creates a release candidate version of the app and makes it available for installation using the vtex install command. For more details, see Publishing an app.