Skip to content

chore(deps): bump ytanikin/pr-conventional-commits from 1.4.0 to 1.4.1 #413

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

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 14, 2025

Bumps ytanikin/pr-conventional-commits from 1.4.0 to 1.4.1.

Release notes

Sourced from ytanikin/pr-conventional-commits's releases.

1.4.1

Full Changelog: ytanikin/pr-conventional-commits@1.4.0...1.4.1

Commits
  • 8267db1 docs: update readme, add scope infomration
  • 3ae6b82 docs: update readme, add scope infomration
  • See full diff in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [ytanikin/pr-conventional-commits](https://github.com/ytanikin/pr-conventional-commits) from 1.4.0 to 1.4.1.
- [Release notes](https://github.com/ytanikin/pr-conventional-commits/releases)
- [Commits](ytanikin/pr-conventional-commits@1.4.0...1.4.1)

---
updated-dependencies:
- dependency-name: ytanikin/pr-conventional-commits
  dependency-version: 1.4.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 14, 2025

Labels

The following labels could not be found: dependencies, gh-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@NicolasIRAGNE NicolasIRAGNE requested a review from MickaelCa July 14, 2025 23:51
@filipchristiansen filipchristiansen self-requested a review July 15, 2025 07:30
@filipchristiansen filipchristiansen requested review from MickaelCa and removed request for MickaelCa July 15, 2025 07:30
@NicolasIRAGNE
Copy link
Contributor

not familiar with dependabot, should we do that?

dependencies, gh-actions

or perhaps @MickaelCa you were talking about switching to renovate eventually?

@MickaelCa MickaelCa merged commit 11e2fce into main Jul 15, 2025
30 of 58 checks passed
@MickaelCa MickaelCa deleted the dependabot/github_actions/ytanikin/pr-conventional-commits-1.4.1 branch July 15, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants