-
Notifications
You must be signed in to change notification settings - Fork 122
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
Use Semantic Release instead of Grunt #243
Comments
jginsburgn
pushed a commit
to jginsburgn/karma-chrome-launcher
that referenced
this issue
Jan 4, 2022
Except for updating contributors, which remains in Grunt. karma-runner#243
jginsburgn
pushed a commit
to jginsburgn/karma-chrome-launcher
that referenced
this issue
Feb 15, 2022
Except for updating contributors, which remains in Grunt. karma-runner#243
jginsburgn
pushed a commit
to jginsburgn/karma-chrome-launcher
that referenced
this issue
Feb 15, 2022
Except for updating contributors, which remains in Grunt. karma-runner#243
jginsburgn
pushed a commit
that referenced
this issue
Mar 4, 2022
Except for updating contributors, which remains in Grunt. #243
jginsburgn
pushed a commit
that referenced
this issue
Mar 4, 2022
Except for updating contributors, which remains in Grunt. #243
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of the plugins used for Grunt in this repo are dead. We must have a better maintained solution: Semantic Release. Besides, using Semantic Release in this repo will align more with the Karma core one.
The text was updated successfully, but these errors were encountered: