Build(deps): Bump github.com/reugn/go-quartz from 0.7.0 to 0.11.2

[dependabot[bot]]

Bumps github.com/reugn/go-quartz from 0.7.0 to 0.11.2.

Release notes

Sourced from github.com/reugn/go-quartz's releases.

v0.11.2

Fixes

• fix: ensure atomicity of the fetch and reschedule operation (#121)
• fix: export the expired field to allow proper trigger unmarshalling (#120)

Improvements

• refactor(cron): make delimiter runes constant variables (#123)
• refactor: extract retry interval into a separate configuration option (#122)

v0.11.1

Fixes

• fix: parsing compound cron expression fields (#115)
• fix: trim cron expression string (#112)
• fix: potential nil pointer dereference in log (#113)
• fix(job): check response for nil in (*CurlJob).DumpResponse (#117)

Maintenance

• test: improve code coverage (#116)

v0.11.0

Features

• feat: add the ability to pause and resume jobs (#102)
• feat: introduce matchers to filter jobs (#107)
• feat: add Get method to the JobQueue interface (#101)
• feat: classify quartz error messages (#103)

Maintenance

• docs: add package documentation (#108)
• test: enhance assertions in unit tests (#104)
• ci: update versions in workflows (#109)
• ci: update golangci-lint configuration (#105)

v0.10.0

⚠ BREAKING CHANGES

• refactor!: module package structure (#87)
• feat(scheduler)!: introduce JobQueue abstraction (#80)
• feat!: introduce JobDetail and JobKey for job scheduling (#84)
• fix(scheduler)!: reset the queue after deleting a job (#83)
• fix!: reset scheduler after successfully clearing job queue (#86)

Features

• feat(cron): expose validate cron expression function (#95)
• feat(quartz): organize package error types (#94)

Fixes

• fix(logger): call depth for logging events (#97)
• fix(scheduler): rescheduling outdated jobs (#96)
• fix: break statement in execute with retries (#93)
• fix: validate location in NewCronTriggerWithLoc (#90)
• fix: normalize description format for serialization (#89)

... (truncated)

Commits

• eb4b074 refactor(cron): make delimiter runes constant variables (#123)
• 60094f6 refactor: extract retry interval into a separate configuration option (#122)
• 50a769b fix: ensure atomicity of the fetch and reschedule operation (#121)
• 50c609c fix: export the expired field to allow proper trigger unmarshalling (#120)
• a90c2c9 fix(job): check response for nil in (*CurlJob).DumpResponse (#117)
• 45b7905 test: improve code coverage (#116)
• 51879fa fix: parsing compound cron expression fields (#115)
• 8a940a4 fix: potential nil pointer dereference in log (#113)
• ce9418d fix: trim cron expression string (#112)
• 037673d ci: update versions in workflows (#109)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

[coderabbitai[bot]]

[!IMPORTANT]

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

---

Tips

### Chat There are 3 ways to chat with CodeRabbit: - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - The JSON schema for the configuration file is available [here](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json` ### CodeRabbit Discord Community Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback.