build(deps): Bump hashicorp/setup-copywrite from 1.1.2 to 1.1.3

[dependabot[bot]]

Bumps hashicorp/setup-copywrite from 1.1.2 to 1.1.3.

Release notes

Sourced from hashicorp/setup-copywrite's releases.

v1.1.3

What's Changed

• Bump eslint from 8.38.0 to 8.44.0 by @​dependabot in hashicorp/setup-copywrite#52
• Bump @​octokit/rest from 19.0.7 to 19.0.13 by @​dependabot in hashicorp/setup-copywrite#50
• Bump nock from 13.3.0 to 13.3.1 by @​dependabot in hashicorp/setup-copywrite#37
• Bump semver from 6.3.0 to 6.3.1 by @​dependabot in hashicorp/setup-copywrite#54
• Fix and re-enable tets around retries/abuse limits by @​dlaguerta in hashicorp/setup-copywrite#33
• Bump eslint-config-standard from 17.0.0 to 17.1.0 by @​dependabot in hashicorp/setup-copywrite#46
• Update CODEOWNERS to team-pss by @​dlaguerta in hashicorp/setup-copywrite#74
• Maintenance and Testing by @​ksatirli in hashicorp/setup-copywrite#73

New Contributors

• @​ksatirli made their first contribution in hashicorp/setup-copywrite#73

Full Changelog: https://github.com/hashicorp/setup-copywrite/compare/v1.1.2...v1.1.3

What's Changed

• Bump eslint from 8.38.0 to 8.44.0 by @​dependabot in hashicorp/setup-copywrite#52
• Bump @​octokit/rest from 19.0.7 to 19.0.13 by @​dependabot in hashicorp/setup-copywrite#50
• Bump nock from 13.3.0 to 13.3.1 by @​dependabot in hashicorp/setup-copywrite#37
• Bump semver from 6.3.0 to 6.3.1 by @​dependabot in hashicorp/setup-copywrite#54
• Fix and re-enable tets around retries/abuse limits by @​dlaguerta in hashicorp/setup-copywrite#33
• Bump eslint-config-standard from 17.0.0 to 17.1.0 by @​dependabot in hashicorp/setup-copywrite#46
• Update CODEOWNERS to team-pss by @​dlaguerta in hashicorp/setup-copywrite#74
• Maintenance and Testing by @​ksatirli in hashicorp/setup-copywrite#73

New Contributors

• @​ksatirli made their first contribution in hashicorp/setup-copywrite#73

Full Changelog: https://github.com/hashicorp/setup-copywrite/compare/v1.1.2...v1.1.3

Commits

• 32638da Maintenance and Testing (#73)
• b608018 Update CODEOWNERS to team-pss (#74)
• de72466 Bump eslint-config-standard from 17.0.0 to 17.1.0 (#46)
• 8f5324c Fix and reenable tests around retries/abuse limit (#33)
• 70fb486 Bump semver from 6.3.0 to 6.3.1 (#54)
• dccea12 Bump nock from 13.3.0 to 13.3.1 (#37)
• 3b0f2d6 Bump @​octokit/rest from 19.0.7 to 19.0.13 (#50)
• 5e85236 Bump eslint from 8.38.0 to 8.44.0 (#52)
• See full diff 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 show 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)

[github-actions[bot]]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.