Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Add CI/CD and semantic release #43

Merged
merged 6 commits into from
Oct 2, 2023

Conversation

rmi22186
Copy link
Collaborator

Instructions

  1. PR target branch should be against development
  2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
  3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

We did not have semantic release on this kit. Since we don't update these kits too often, I wanted to implement this now. Most of this is pulled and adapted from GA4. For reference below:

Testing Plan

  • Was this tested locally? If not, explain why.
    It is not possible to test a github action prior to release. However, if there are any failures, we can debugonce this file is in master.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

@@ -21,7 +21,7 @@

</script>
<!-- change name of XYZ-Kit below to the name of your built kit-->
<script src="../build/DoubleClick-Kit.js"></script>
<script src="../dist/DoubleClick-Kit.iife.js"></script>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're changing the location of this file, shouldn't you also remove the old one?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call.

Copy link
Collaborator

@alexs-mparticle alexs-mparticle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just remove the old build directory and we should be good. Also, Maybe we can introduce a breaking change to verify that tests properly run?

- name: NPM install
uses: actions/setup-node@v3
with:
node-version: 16.x
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Should we update this to a more recent version of node?

Copy link
Collaborator

@alexs-mparticle alexs-mparticle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Copy link
Collaborator

@alexs-mparticle alexs-mparticle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@rmi22186 rmi22186 merged commit ff95e4d into master Oct 2, 2023
@rmi22186 rmi22186 deleted the ci/SQDSDKS-5785-semantic-release branch October 2, 2023 14:09
rmi22186 added a commit that referenced this pull request Oct 2, 2023
ci: Update node version

ci: Add scripts folder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants