CircleCI to Github actions migration for Kedro-Viz (Release)

[jitu5]

Description

Resolves #1785

Development notes

The migration from CircleCI to GitHub Actions will have to be done in parts. This PR addresses the Release part, and the test part was already merged.

Workflows:

• deploy-demo.yml:

  • Triggered by push on the demo branch.
  • Sets up the environment, installs AWS CLI, builds a Docker image of the demo project, and pushes it to AWS ECR.
  • The script for building the Docker image and pushing it to AWS ECR is embedded in the Build demo container image step.
  • Creates a new AWS Lightsail deployment using the lightsail.json config file.
  • It deploys the demo project to AWS Lightsail.

• check-release.yml:

  • Triggered by push on main branch.
  • The first job - check-version checks if the version specified on the kedro_viz/__init__.py file is on PyPI already or not. If it isn't, that means a release should be triggered.
  • The script for checking of versions is tools/github_actions/check_version.py
  • The second job - test-kedro-viz runs the test suite with all-checks.yml
  • The third job - prepare-release, extracts release notes from RELEASE.md(using tools/github_actions/extract_release_notes.py) and creates a GitHub release.

• release.yml:

  • Triggered by a GitHub release publish event.
  • The first job - release_to_npm checks out the code, sets up Node.js, installs Node dependencies, builds the React application, and then publishes the package to npm.
  • The second job - release_to_pypi checks out the code, sets up tests, makes a Python package, installs twine, and then publishes the package to PyPI.

Miro board link

Notes

• For demo-project/Dockerfile file, python version updated from 3.8 to 3.9

• CircleCI config files removed.

• Now publishing to PyPi & npm happening in check-release -> tests (lint, unit, e2e, js-lint-test) -> tags the release -> releases

• I successfully ran all the workflow in private repo. For reference:
  For PyPi
  https://github.com/jitu5/kedro-viz/actions/runs/8816265319/job/24200003147
  https://test.pypi.org/project/kedro-vizzz/9.0.0/

  For npm
  https://github.com/jitu5/kedro-viz/actions/runs/8816265319/job/24200002881
  https://www.npmjs.com/package/kedro-vizzz

  For deploy demo
  https://github.com/jitu5/kedro-viz/actions/runs/8805821140/job/24169247490
  https://jitu5-kedro-viz.puqtrjp4c6474.eu-west-2.cs.amazonlightsail.com/

QA notes

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes

[ankatiyar]

overall looks fine to me! Ready for review?

[jitu5]

overall looks fine to me! Ready for review?

Yes!

[ravi-kumar-pilla]

Hi @jitu5 , I have left few comments, but most of the code looks great. I feel the migration work is neat and very well organized. Awesome work !! Thank you

[ankatiyar]

LGTM! Reminder to set up the secrets in repo settings and change "required" test to merge-gatekeeper! @rashidakanchwala might also have to disable CircleCI entirely

[ravi-kumar-pilla]

The demo link does not have experiment tracking, but our demo site should have ET. Apart from this, PR LGTM. Awesome work @jitu5 !! Thank you

[jitu5]

The demo link does not have experiment tracking, but our demo site should have ET. Apart from this, PR LGTM. Awesome work @jitu5 !! Thank you

@ravi-kumar-pilla Yes, we treat it as local and show experiment tracking for the following hosts: 'localhost', '127.0.0.1', and 'demo.kedro.org'.

[rashidakanchwala]

qq - what is this for?

[jitu5]

@rashidakanchwala Ref: #1785 (comment)
Previously We run all the above jobs in parallel which means even if the tests fail for some reason, we still tag our release and publish it to npm, pypi. this change will runs all the required tests (lint, unit, e2e) -> tags the release -> releases it to pypi and npm in a sequence.

[rashidakanchwala]

Amazzzing!!!