One App release process

[nellyk]

This outlines the process for releasing One App and adds the functionality using GitHub actions
Please merge this once this is merged #82

Description

The process is documented in Release.md
Please review the file for steps on getting a released started.

An automated pull request is raised every Wednesday and once merged, a tag is created automatically. This kicks off the build of the development and production images which are released to the docker hub. Statics are published to npm added by @infoxicator as part of #82

The last step is to update the release notes and tag it to the release.

Motivation and Context

This allows us to create a manual or automatic releases of One App. Enabling One App users to be able to access One App images to create experiences using it.

How Has This Been Tested?

Yes please review this

• One App docker release action https://github.com/nellyk/one-app/actions/runs/69291362
• Automated pull request One App prerelease #89
• pull request actions https://github.com/americanexpress/one-app/actions/runs/68264293
• Automated tagging https://github.com/nellyk/one-app/actions/runs/69291209
• Automated release drafter https://github.com/nellyk/one-app/actions/runs/68392514, https://github.com/nellyk/one-app/releases/tag/v5.2.3 and a sample release would look like this https://github.com/release-drafter/release-drafter/releases/tag/v5.7.0
• Docker images https://hub.docker.com/r/nkiboi/one-app/tags and https://hub.docker.com/r/nkiboi/one-app-dev/tags

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

This would allow docker images to be published for One App developers to use to create experiences

[oneamexbot]

📊 Bundle Size Report

file name	size on disk	gzip
app.js	112.6KB	31.4KB
runtime.js	15KB	5.3KB
vendors.js	128.1KB	37.9KB
app~vendors.js	405.9KB	106KB
legacy/app.js	119.4KB	33KB
legacy/runtime.js	15KB	5.3KB
legacy/vendors.js	163KB	44.8KB
legacy/app~vendors.js	412KB	107.6KB

Generated by 🚫 dangerJS against 43fb28b

[infoxicator]

Please double check the travis script

[mtomcal]

Do we have in place a way to make sure >= 1 One Amex Admins need to approve the release PR?

[infoxicator]

Well done @nellyk ! 👍

[nellyk]

Well done @nellyk ! 👍

Thank you so much for your help @infoxicator wouldn't be able to get here without you support

[mtomcal]

Fantastic work @nellyk!

[JAdshead]

I think we are there

[JamesSingleton]

Could we do?

env:
  NODE_ENV: development

Not a blocker, but just curious.