Fix linearctl 0.8.0 contract regressions#144
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (34)
📝 WalkthroughWalkthroughThis release (v0.8.0) bundles eight interconnected fixes addressing regressions and hardening issues: validation-error routing unification, retry-option consistency across list commands, issue-search default-team scoping, file-redirect cross-host security, name-resolution tie-breaking, Retry-After capping, CLI global-option recognition, and curated command safety classification. ChangesCore v0.8.0 Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Summary
Fixes the 0.8.0 regression batch across search scope, pagination retry plumbing, resolver ambiguity preferences, file redirect safety, leading global flags, curated safety taxonomy, bulk failure envelopes, Retry-After behavior, and envelope-aware validation paths.
Behavior / breaking changes:
issue search <text>without--teamsearches the whole workspace again, even when the active profile has a default team. Use explicit--teamto scope search.errors[]/data.failed[]and derive the process exit code by category priority: auth > rate-limit > not-found > general.issue create --dry-runresolves friendly names before emitting the dry-run payload, so dry-run validates resolvability.Verification
bun run typecheckbun run testbun run buildFixes #133
Fixes #134
Fixes #136
Fixes #137
Fixes #138
Fixes #139
Fixes #140
Fixes #141
Fixes #142
Summary by CodeRabbit
Release Notes v0.8.0
New Features
--teamflag; default team no longer appliedBug Fixes
Retry-Afterheader values properly capped to prevent excessive waits<config-dir>/schemaChanged
--order-by/--order-dirflags with validation error