Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add version verification script/workflow

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, postgresql, sql

Research direction

Start by examining META.json, pg_clickhouse.control, doc/pg_clickhouse.md, CHANGELOG.md, the sql directory, and the PG_MODULE_MAGIC definition to identify each version source. Account for CI and semantic version tags through CI and GITHUB_REF_NAME, then verify that every listed incompatibility raises an error or is automated away.

Written by the indexing model from the issue text.

Description

distribution quality

Write a script that examines the version in META.json, pg_clickhouse.control, doc/pg_clickhouse.md, and CHANGELOG.md, and the $GITHUB_REF_NAME environment variable (when $CI is set and it's a version) to ensure they're compatible. Things to check:

  • The version in META.json is canonical. Both instances of it there should be the same
  • The version in pg_clickhouse.control must be the same as the x.y part of the version from META.json
  • Aside from 0.1, the x.y part must always have an upgrade script in the sql directory
  • If a workflow is running for a semantic version tag, the tag must be the same as the full x.y.z version from META.json version
  • PG_MODULE_MAGIC must be the same full x.y.z version from META.json

Any violations should raise an error (or be automated away).

Dominant language
C
Stars
284
Forks
21
Avg merge
1d 3h
Merged PRs (30d)
22

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ClickHouse/pg_clickhouse

All issues in ClickHouse/pg_clickhouse

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.