-
Notifications
You must be signed in to change notification settings - Fork 133
build: Automated release process #297
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
Conversation
| }, | ||
| frameworks: ['mocha', 'chai'], | ||
| files: ['amplitude-snippet.min.js', 'build/snippet-tests.js', 'build/tests.js'], | ||
| // files: ['amplitude-snippet.min.js', 'build/snippet-tests.js', 'build/tests.js'], @TODO: Fix flaky build/snippet-tests.js and re-enable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove this commented code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO leave it as a todo until we can fix then re-enable the flaky snippet tests
kelvin-lu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Summary
Repo collaborators will now be able to do a release by running a workflow from the Actions tab.


Implemented semantic-release for automatic releases (release.yml and release.config.js)
Added test.yml action. Includes testing on multiple LTS node versions
Added deploy_s3.py based off internal deploy script
Updated CONTRIBUTING.md explaining commit conventions and release process
Added pull request template
Added semantic PR bot to check for PR titles (config is here)
Added secrets as env variables
New release workflow tested on personal fork
TODO
masteras development,releaseas release