Skip to content

[Test] BigQuery DESTINATION change (expect: labeled)#4

Open
Jeremyyang920 wants to merge 5 commits into
deprecate-non-ch-pg-destinationsfrom
deptest-bigquery-dest-positive
Open

[Test] BigQuery DESTINATION change (expect: labeled)#4
Jeremyyang920 wants to merge 5 commits into
deprecate-non-ch-pg-destinationsfrom
deptest-bigquery-dest-positive

Conversation

@Jeremyyang920

Copy link
Copy Markdown
Owner

Automated test of the deprecated-connector labeler/notice workflow.

Jeremyyang920 and others added 5 commits June 22, 2026 14:40
Signal deprecation of the Snowflake, BigQuery, ElasticSearch, Kafka
(incl. Confluent/Redpanda), Azure Event Hubs, and Google Pub/Sub
destination connectors. No code is removed; these remain fully
functional. Actively-maintained paths are Postgres -> ClickHouse,
Postgres -> ClickHouse Cloud, and Postgres -> Postgres.

- README: deprecation notice + connector status matrix
- docs/DEPRECATED_CONNECTORS.md: pin + fork migration guide
- CONTRIBUTING.md: links to the migration guide
- UI: "Deprecated" badge in the peer creation flow
- Issue form with a destination-connector dropdown + deprecation notice
- labeler.yml + workflow: label deprecated-connector PRs/issues and post
  a one-time notice (never auto-closes)

Refs PeerDB-io#4465

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
BigQuery is a supported QRep source, so a blanket "Deprecated" badge is
inaccurate. Model deprecation per role: BigQuery is deprecated only as a
destination and stays a supported source.

- UI: add deprecatedRole to peer-types; badge reads "Deprecated as
  destination" for BigQuery, "Deprecated" for the others
- README: note destination-only scope; add BigQuery as a maintained source
- docs/DEPRECATED_CONNECTORS.md: clarify BigQuery destination-only
- Issue template + workflow notice: same clarification

Refs PeerDB-io#4465

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Move the connector deprecation notice in the README to just after the
  intro (before "Get started") for visibility, linking to the status matrix.
- Peer-creation grid: uniform "Deprecated" badge; mark destination-only
  deprecations (BigQuery) with an asterisk + a footnote.
- Rename docs/DEPRECATED_CONNECTORS.md -> docs/deprecated-connectors.md to
  match the docs/ naming convention; update all references.

Refs PeerDB-io#4465

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- labeler.yml: BigQuery is dual-role (source maintained, destination
  deprecated) and its source/destination code share one directory. Match
  BigQuery paths only when no BigQuery *source* file is in the change
  (source.go, source_schema.go, qrep_object_pull.go, bigquery_source_test.go),
  using the documented all: + all-globs-to-all-files negation. Destination-only
  connectors keep their simple globs.
- deprecated-connector.yml: add `needs: label` + `if: always()` to the notice
  job so on pull_request_target it runs after the labeler applies the label
  (the labeler's GITHUB_TOKEN write does not emit a `labeled` event), fixing
  both the race and the never-posted-notice bug.

Refs PeerDB-io#4465

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Jeremyyang920 Jeremyyang920 reopened this Jun 24, 2026
@github-actions github-actions Bot added the deprecated Deprecated destination connector label Jun 24, 2026
@github-actions

Copy link
Copy Markdown

⚠️ Deprecated destination connector

This issue or pull request touches a deprecated destination connector (Snowflake, BigQuery, ElasticSearch, Kafka, Redpanda, Confluent, Azure Event Hubs, or Google Pub/Sub).

These destinations are no longer actively maintained, but remain functional. We are unlikely to prioritize new work here.

Note: BigQuery is deprecated only as a destination — it remains a supported source.

If you depend on one of these connectors, we recommend:

  • Pin to a known-good PeerDB version so behavior stays stable.
  • Fork the repository if you need to carry your own changes.

See the deprecated connectors documentation for details and migration guidance.

@Jeremyyang920 Jeremyyang920 force-pushed the deprecate-non-ch-pg-destinations branch 2 times, most recently from 58a79ad to 8c02950 Compare June 24, 2026 21:50
@Jeremyyang920 Jeremyyang920 force-pushed the deprecate-non-ch-pg-destinations branch from 8c02950 to 41f25b4 Compare June 24, 2026 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deprecated Deprecated destination connector

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant