Skip to content

Repo: Automate version ranges in website's Versioning.md #6389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JoshuaKGoldberg opened this issue Jan 30, 2023 · 1 comment · Fixed by #7367
Closed

Repo: Automate version ranges in website's Versioning.md #6389

JoshuaKGoldberg opened this issue Jan 30, 2023 · 1 comment · Fixed by #7367
Labels
accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website repo maintenance things to do with maintenance of the repo, and not with code/docs

Comments

@JoshuaKGoldberg
Copy link
Member

JoshuaKGoldberg commented Jan 30, 2023

Suggestion

From #6251 (comment): we have hardcoded version ranges in Versioning.md:

> The version range of TypeScript currently supported is `>=3.3.1 <5.0.0`.

Let's use some kind of Docusaurus<>React component shenanigan(s) to automate this. Supported version ranges should be sourced from our package.jsons.

@JoshuaKGoldberg JoshuaKGoldberg added repo maintenance things to do with maintenance of the repo, and not with code/docs accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website labels Jan 30, 2023
@armano2
Copy link
Collaborator

armano2 commented Feb 24, 2023

when we expose those as variables we should update playground to allow only those versions

image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website repo maintenance things to do with maintenance of the repo, and not with code/docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants