merge queue: embarking release-v1.0.0 (31108ce) and #675 together

[mergify]

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch release-v1.0.0 (31108ce) and #675 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #675.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • fix: remove unneeded tracing init in error case #675
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • fix: remove unneeded tracing init in error case #675
• check-success=test-suite-success
• any of [🛡 GitHub repository ruleset rule]:
  • check-success = license/cla
  • check-neutral = license/cla
  • check-skipped = license/cla

Required conditions to stay in the queue:

• #approved-reviews-by >= 1
  • fix: remove unneeded tracing init in error case #675
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • fix: remove unneeded tracing init in error case #675
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • fix: remove unneeded tracing init in error case #675
• check-success=license/cla
  • fix: remove unneeded tracing init in error case #675
• check-success=target-branch-check
  • fix: remove unneeded tracing init in error case #675
• label!=do-not-merge
  • fix: remove unneeded tracing init in error case #675
• any of [🛡 GitHub repository ruleset rule]:
  • check-success = license/cla
    • fix: remove unneeded tracing init in error case #675
  • check-neutral = license/cla
    • fix: remove unneeded tracing init in error case #675
  • check-skipped = license/cla
    • fix: remove unneeded tracing init in error case #675

---
checking_base_sha: 31108ceb8e3c4cb5e5f29c2200b5456a2c2ce60a
previous_failed_batches: []
pull_requests:
  - number: 675
...

[github-actions]

Your PR title doesn't follow the Conventional Commit guidelines.

Example of valid titles:

• feat: add new user login
• fix: correct button size
• docs: update README

Usage:

• feat: Introduces a new feature
• fix: Patches a bug
• chore: General maintenance tasks or updates
• test: Adding new tests or modifying existing tests
• perf: Performance improvements
• refactor: Changes to improve code structure
• docs: Documentation updates
• ci: Changes to CI/CD configurations
• revert: Reverts a previously merged PR

Breaking Changes

Breaking changes are noted by using an exclamation mark. For example:

• feat!: changed the API
• chore(node)!: Removed unused public function

Help

For more information, follow the guidelines here: https://www.conventionalcommits.org/en/v1.0.0/