github-action-bump-eas-buildnumber

Bumps the buildNumber and versionCode in app.json

MIT License

Stars
1
Committers
2

Usage

This action bumps the versionCode and buildNumber in app.json for Expo projects. In your workflow you probably want to commit/push the changes after your build is successful.

Input:

  • filepath - path to your app.json (optional, defaults to './app.json')
  • platforms - Comma-separated list of platforms to bump (optional, defaults to 'ios,android')

Output:

  • versioncode - The bumped Android versioncode
  • buildnumber - The bumped iOS buildnumber

Limitations:

  • This solely bumps the app.json and does not commit/push the change, which is probably something you want to do after the build is successful.
  • Please note that it will only work for app.json and not app.config.js, then you'll have to roll your own.

Contribution Guide

Create a JavaScript Action using TypeScript

Use this template to bootstrap the creation of a TypeScript action.🚀

This template includes compilation support, tests, a validation workflow, publishing, and versioning guidance.

If you are new, there's also a simpler introduction. See the Hello World JavaScript Action

Create an action from this template

Click the Use this Template and provide the new repo details for your action

Code in Main

First, you'll need to have a reasonably modern version of node handy. This won't work with versions older than 9, for instance.

Install the dependencies

npm install

Build the typescript and package it for distribution

npm run build && npm run package

Run the tests ✔️

$ npm test

 PASS  ./index.test.js
   throws invalid number (3ms)
   wait 500 ms (504ms)
   test runs (95ms)

...

Change action.yml

The action.yml contains defines the inputs and output for your action.

Update the action.yml with your name, description, inputs and outputs for your action.

See the documentation

Change the Code

Most toolkit and CI/CD operations involve async operations so the action is run in an async function.

import * as core from '@actions/core';
...

async function run() {
  try { 
      ...
  } 
  catch (error) {
    core.setFailed(error.message);
  }
}

run()

See the toolkit documentation for the various packages.

Publish to a distribution branch

Actions are run from GitHub repos so we will checkin the packed dist folder.

Then run ncc and push the results:

npm run package
git add dist
git commit -a -m "prod dependencies"
git push origin releases/v1

Note: We recommend using the --license option for ncc, which will create a license file for all of the production node modules used in your project.

Your action is now published! 🚀

See the versioning documentation

Validate

You can now validate the action by referencing ./ in a workflow in your repo (see test.yml)

uses: ./
with:
  milliseconds: 1000

See the actions tab for runs of this action! 🚀

Usage

After testing you can create a v1 tag to reference the stable and latest V1 action