chore(connectors): bump jira/confluence descriptor versions to publish #1308

[mitasovr]

Why

#1308 (jira/confluence default_concurrency: 1 → 4, the CDK partition-deadlock fix) changed connector.yaml without bumping the descriptor versions — and reconcile republishes a nocode declarative manifest only on descriptor-version drift (descriptor version vs the version stored on the Airbyte definition; equal → noop per ADR-0015).

Verified on virtuozzo after deploying umbrella 0.1.59 (toolbox 2a575de, contains #1308): reconcile ran clean but no-op'd both connectors — the active manifests in Airbyte (declarative_manifest v3 for jira, v2 for confluence) still carry default_concurrency: 1, so the deadlock fix never shipped. (#1283 only got through because an unrelated image-ref bump had already moved jira's descriptor to 1.2.0, creating accidental drift.)

What

• jira descriptor: 1.2.0 → 1.2.1
• confluence descriptor: 1.1.0 → 1.1.1

Patch bump → reconcile classifies it as non-breaking: republish manifest + re-discover catalog, no full-refresh dispatch.

Also encodes the lesson into the /connector skill (deploy prerequisites + validate descriptor checklist): bump descriptor.yaml version in the same PR as any connector.yaml change — a manifest-only PR silently never reaches Airbyte (CI auto-bumps descriptors only for image-ref changes, not manifest edits).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes

  • Updated Jira connector to v1.2.1 and Confluence connector to v1.1.1.

• Documentation

  • Enhanced deployment and validation documentation with clarifications on descriptor version management and republish behavior on reconcile-managed clusters.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a707a2d6-f046-4e03-8995-37774bbb7379

📥 Commits

Reviewing files that changed from the base of the PR and between 3f89af7 and 0cd8415.

📒 Files selected for processing (4)

• cypilot/.core/skills/connector/workflows/deploy.md
• cypilot/.core/skills/connector/workflows/validate.md
• src/ingestion/connectors/task-tracking/jira/descriptor.yaml
• src/ingestion/connectors/wiki/confluence/descriptor.yaml

---

📝 Walkthrough

Walkthrough

This PR documents a descriptor version management policy and applies it to two connector descriptors. Deploy and validation workflows are updated to require version bumps in descriptor.yaml whenever connector.yaml changes, preventing republish failures on reconcile-managed clusters. Jira and Confluence connector descriptors are version-bumped accordingly.

Changes

Descriptor Version Management Policy and Application

Layer / File(s)	Summary
Descriptor Version Policy Documentation cypilot/.core/skills/connector/workflows/deploy.md, cypilot/.core/skills/connector/workflows/validate.md	Deploy workflow and validation checklist are updated to require descriptor version bumps whenever connector.yaml changes, explaining reconcile-managed cluster republish conditions and CI version auto-bump behavior.
Connector Descriptor Version Updates src/ingestion/connectors/task-tracking/jira/descriptor.yaml, src/ingestion/connectors/wiki/confluence/descriptor.yaml	Jira descriptor version bumped from 1.2.0 to 1.2.1; Confluence descriptor version bumped from 1.1.0 to 1.1.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• constructorfabric/insight#1308: Documents and enforces the descriptor version bump requirement whenever connector.yaml changes.

Poem

🐰 A version bump here, a rule penned there,
Descriptors synced with manifests fair!
When connectors change, let versions align—
No drift shall occur in deployment's design. ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}