-
Notifications
You must be signed in to change notification settings - Fork 913
Comparing changes
Open a pull request
base repository: conventional-changelog/commitlint
base: v19.1.0
head repository: conventional-changelog/commitlint
compare: v19.2.0
- 8 commits
- 31 files changed
- 6 contributors
Commits on Mar 13, 2024
-
fix: update dependency inquirer to v9.2.16 (#3972)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for ea1ab9c - Browse repository at this point
Copy the full SHA ea1ab9cView commit details
Commits on Mar 14, 2024
-
chore: update dependency @swc/core to v1.4.7 (#3973)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 391e8ca - Browse repository at this point
Copy the full SHA 391e8caView commit details -
feat(cli): introduce new --last flag, to stop recommending HEAD~1 (#3916
) * test(cli): add regression test * feat(cli): implement new `--last` CLI flag The upgrade of ES2017 to ES2022 is because of the use of `Object.hasOwn` API which is less ugly than hardcoding `undefined`. * docs(ci): stop recommending HEAD~1 In a single-commit repo, this would lead to this error: ``` Error: fatal: ambiguous argument 'HEAD~1..HEAD': unknown revision or path not in the working tree. ``` Now that we have the `--last` flag, this should work for the case in which we want just to analyze the last commit, not specify a range of commits via `--from` and `--to`. Closes #3892 * fix: use --pretty=format:"%B" instead of --pretty=%B The latter adds unnecessary whitespace at the end of the commit msg. --------- Co-authored-by: Mehrshad <code.rezaei@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 99f4f3f - Browse repository at this point
Copy the full SHA 99f4f3fView commit details -
chore: update dependency @types/node to v18.19.24 (#3974)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 207d2c0 - Browse repository at this point
Copy the full SHA 207d2c0View commit details
Commits on Mar 15, 2024
-
chore: update dependency @swc/core to v1.4.8 (#3975)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 711588d - Browse repository at this point
Copy the full SHA 711588dView commit details -
build(deps): bump follow-redirects from 1.15.4 to 1.15.6 (#3977)
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.4...v1.15.6) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 99cd49d - Browse repository at this point
Copy the full SHA 99cd49dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 94eab40 - Browse repository at this point
Copy the full SHA 94eab40View commit details -
Configuration menu - View commit details
-
Copy full SHA for a64b417 - Browse repository at this point
Copy the full SHA a64b417View 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 v19.1.0...v19.2.0