chore(deps): bump remarkablemark/commitlint from 1 to 2#9
Conversation
Bumps [remarkablemark/commitlint](https://github.com/remarkablemark/commitlint) from 1 to 2. - [Release notes](https://github.com/remarkablemark/commitlint/releases) - [Changelog](https://github.com/remarkablemark/commitlint/blob/master/CHANGELOG.md) - [Commits](remarkablemark/commitlint@v1...v2) --- updated-dependencies: - dependency-name: remarkablemark/commitlint dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Pull Request ReviewIt looks like the diff is changing the |
ubuntu-latestHere is a summary of the code diff in bullet points:
|
Pull Request ReviewThis is a diff file generated by Git that shows the changes between two versions of a file. The file being reviewed is The changes made to this file are:
|
windows-latestHere's the code diff for a
|
Pull Request ReviewThe diff between the two files shows that there is a change in the "uses" field for the "Commitlint" job. In the original file, it references the version 1 of the commitlint action, while in the updated file, it references the version 2. This means that the workflow is now using the latest version of the commitlint action, which may include new features or bug fixes compared to the previous version. |
macos-latestThe diff between the two files is as follows:
|
remarkablemark
deleted the
dependabot/github_actions/remarkablemark/commitlint-2
branch
1 participant
Bumps remarkablemark/commitlint from 1 to 2.
Release notes
Sourced from remarkablemark/commitlint's releases.
Changelog
Sourced from remarkablemark/commitlint's changelog.
... (truncated)
Commits
0105558Merge pull request #13 from remarkablemark/release-please--branches--master7975b2bchore(master): release 2.0.0ea1d1a5feat(action): bump actions/checkout from 5 to 6 (#12)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)