Release 0.2.7: bump rake constraint to allow rake 13.x

[00cyre]

Summary

• Bumps cando version from 0.2.6 -> 0.2.7
• Widens runtime rake constraint from >= 10.3.2, < 13.1.0 to >= 10.3.2, < 14 so downstream consumers can use rake 13.x
• Loosens dev Gemfile rake constraint to match (>= 12.3.3, < 14)

Why

soundcloud/sonar#2077 wants to update rake to ~> 13.0, but the currently published cando 0.2.7 — er, 0.2.6 — still pins rake to ~> 10.3.2, which blocks the bump. Releasing 0.2.7 unblocks that PR.

Test plan

• gem build cando.gemspec succeeds (verified locally, rake constraint shows >= 10.3.2, < 14 in built gemspec)
• After merge, run rake release (or gem build + gem push) to publish 0.2.7 to rubygems.org
• Update soundcloud/sonar#2077 to bump cando to ~> 0.2.7 alongside the rake update, then verify sonar's CI passes

Notes

• Gemfile.lock left untouched; bundle install on a modern Ruby fails because of pre-existing dev deps (mysql 2.9.1, json 1.8.1) — unrelated to this change. Lockfile rake (12.3.3) still satisfies the new constraint.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the gem version to 0.2.7 and expands the allowed rake version range to include versions up to 14. Feedback was provided regarding a discrepancy between the rake version constraints in the Gemfile and the gemspec, as the Gemfile's more restrictive lower bound prevents testing against the full range of supported versions defined in the gemspec.

[gemini-code-assist]

The rake constraint in the Gemfile (>= 12.3.3) is more restrictive than the runtime dependency defined in the gemspec (>= 10.3.2). This prevents testing the gem against the full range of supported Rake versions in the development environment. Consider aligning the lower bound with the gemspec to ensure compatibility across all supported versions.

gem "rake", ">= 10.3.2", "< 14"