Lint for extensions deprecated in pg17 image

Open
#105 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
postgres
Domain
databases, tooling

Research direction

Start by locating the lint rules or entry point for the pg17 image and checking how extension metadata is represented. Add deprecation warnings for plv8, timescaledb, and adminpack, then run the relevant linter checks to confirm all three are reported.

Written by the indexing model from the issue text.

Description

bug

Add lint warn about extension deprecations in the pg17 image

  • plv8
  • timescaledb
  • adminpack
Dominant language
PLpgSQL
Stars
275
Forks
102
Avg merge
2d 8h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

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 supabase/splinter

All issues in supabase/splinter

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.