-
Notifications
You must be signed in to change notification settings - Fork 124
Comparing changes
Open a pull request
base repository: karma-runner/karma-chrome-launcher
base: v3.1.0
head repository: karma-runner/karma-chrome-launcher
compare: v3.1.1
- 15 commits
- 14 files changed
- 3 contributors
Commits on Mar 4, 2022
-
build: ignore macOS meta files
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 73c839e - Browse repository at this point
Copy the full SHA 73c839eView commit details -
build: track
package-lock.jsonJonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 617b582 - Browse repository at this point
Copy the full SHA 617b582View commit details -
build: use npm instead of Grunt
Except for updating contributors, which remains in Grunt. #243
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for eb0a039 - Browse repository at this point
Copy the full SHA eb0a039View commit details -
Jonathan Ginsburg committed
Mar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 69ba2ea - Browse repository at this point
Copy the full SHA 69ba2eaView commit details -
ci: add the "Test" GitHub Actions workflow
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 2194427 - Browse repository at this point
Copy the full SHA 2194427View commit details -
Jonathan Ginsburg committed
Mar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 80ada9f - Browse repository at this point
Copy the full SHA 80ada9fView commit details -
ci: add the "Release" GitHub Actions workflow
Also: * Remove the "pretest" npm script as it is explicitly called in the "Test" GitHub Actions workflow. * Allow for the "chore" commit type as it is used by the grunt "contributors" task.
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 58c8874 - Browse repository at this point
Copy the full SHA 58c8874View commit details -
build: add the
update-contributorstoolJonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 1d6eb7f - Browse repository at this point
Copy the full SHA 1d6eb7fView commit details -
build: remove unnecessary "set up Chrome" step in "Test" workflow
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 4788113 - Browse repository at this point
Copy the full SHA 4788113View commit details -
Jonathan Ginsburg committed
Mar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 87c59fe - Browse repository at this point
Copy the full SHA 87c59feView commit details -
build: disallow
choretype commitsJonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for d2ad8c6 - Browse repository at this point
Copy the full SHA d2ad8c6View commit details -
docs: explain testing, linting and commit linting
Jonathan Ginsburg committedMar 4, 2022 Configuration menu - View commit details
-
Copy full SHA for 5400b23 - Browse repository at this point
Copy the full SHA 5400b23View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4dc0bd2 - Browse repository at this point
Copy the full SHA 4dc0bd2View commit details
Commits on Mar 9, 2022
-
fix: artificially trigger a release
This will ensure that the recent CI/CD Release workflow with GitHub Actions is working properly.
Jonathan Ginsburg committedMar 9, 2022 Configuration menu - View commit details
-
Copy full SHA for 83fdc3c - Browse repository at this point
Copy the full SHA 83fdc3cView commit details -
chore(release): 3.1.1 [skip ci]
## [3.1.1](v3.1.0...v3.1.1) (2022-03-09) ### Bug Fixes * artificially trigger a release ([83fdc3c](83fdc3c))
Configuration menu - View commit details
-
Copy full SHA for 5f3cbb1 - Browse repository at this point
Copy the full SHA 5f3cbb1View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.1.0...v3.1.1