Repository navigation
docs: drop stale Experimental banners, recommend PG18 - #360
Merged
Merged
Conversation
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
|
Review complete. No issues found — approved ✅. Documentation-only change refreshing package READMEs for the PostgreSQL 18 release: it documents new
Reviewed commit: 186d52c |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only (READMEs). Plan: constructive-io/constructive-planning#2208.
plpgsql-parserandplpgsql-deparser: remove the "pgsql-parser,pgsql-deparser,plpgsql-parser) stay, as plain notes.pgsql-deparser: "Latest Version (PostgreSQL 17)" becomes 18, and PG18 is now the recommendation. PG17 is still supported through@pg17, which is added to the version-specific install list. In the version table, PG14-16 changes from "@pgsql/transform-ast(README +transformers-direct/README.md): the docs still said PG17 was the target, buttransformToLatestalready goes to 18 and thePG*ToPG18Transformer/V17ToV18Transformerclasses ship. Examples and tables now use the PG18 transformers, and the PG17 ones are still listed.pgsql-typeskeeps its Experimental note on purpose. Nothing depends on it yet.Link to Devin session: https://app.devin.ai/sessions/abe99c93b1e24e9c85346420f90d1f36
Open in Devin Desktop: https://app.devin.ai/desktop/session/abe99c93b1e24e9c85346420f90d1f36?variant=devin
Requested by: @pyramation