fix: Bump certifi from 2022.12.7 to 2023.7.22

[dependabot[bot]]

Bumps certifi from 2022.12.7 to 2023.7.22.

Commits

• 8fb96ed 2023.07.22
• afe7722 Bump actions/setup-python from 4.6.1 to 4.7.0 (#230)
• 2038739 Bump dessant/lock-threads from 3.0.0 to 4.0.1 (#229)
• 44df761 Hash pin Actions and enable dependabot (#228)
• 8b3d7ba 2023.05.07
• 53da240 ci: Add Python 3.12-dev to the testing (#224)
• c2fc3b1 Create a Security Policy (#222)
• c211ef4 Set up permissions to github workflows (#218)
• 2087de5 Don't let deprecation warning fail CI (#219)
• e0b9fc5 remove paragraphs about 1024-bit roots from README
• Additional commits viewable in compare view

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 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/ni/nisystemlink-clients-python/network/alerts).

[spanglerco]

@cameronwaterman @mure Should PRs like this be labeled as a fix so it produces a release? Or does build/chore also produce a release?

[cameronwaterman]

@spanglerco good point... "build" isn't even a supported type. Do you know if this is something we have to update manually every time one of these PRs comes in?

[spanglerco]

"build" isn't even a supported type. Do you know if this is something we have to update manually every time one of these PRs comes in?

@cameronwaterman it looks like the library we use does support build as a type, but the documentation doesn't make it obvious what types do what. From that documentation, I'm guessing only feat, fix, and perf do a version bump?

It looks like we can configure dependabot to use whatever prefix we want.

[cameronwaterman]

"build" isn't even a supported type. Do you know if this is something we have to update manually every time one of these PRs comes in?

@cameronwaterman it looks like the library we use does support build as a type, but the documentation doesn't make it obvious what types do what. From that documentation, I'm guessing only feat, fix, and perf do a version bump?

It looks like we can configure dependabot to use whatever prefix we want.

Ah okay. I think you're probably right that the build type wouldn't produce a new release and we'd probably want fix instead.