<!--* Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/issues * For information about documentation content and process, see https://docs.gitlab.com/development/documentation/--> - [x] Start this issue's title with `Docs:` or `Docs feedback:`. ## Problem to solve Currently there is no straight-forward way for folks to lookup the language server version associated with a specific extension by marketplace version, release tag, or commit. The Duo UI and GitLab UI dependencies should also support being updated in this fashion so a YAML manifest of projects mapped to dependencies could be useful. ## Proposal <!--Further specifics for how can we solve the problem.--> * Create a project hosts badge images for each editor extension. * Create git tags based on any alpha/pre-release and stable marketplace versions. * Host each extensions badge at a static URL. * Support linking to the tagged commit asset for the extension's tagged release LSP version badge. * Create a GitLab pages site which shows a table of the latest versions used by each extension on the main branch and the latest stable/pre-release marketplace releases. * Create a CI job file that can be included in all extension projects. * Generate a project token stored in 1Password which extensions maintainers can add as a well-known variable when including the CI/CD template. * CI/CD template should define two jobs: * Commit and push LSP ve * Commit and push LSP version from lockfile on release/pre-release. ## Who can address the issue <!--What if any special expertise is required to resolve this issue?--> ## Other links/references <!--For example, related GitLab issues/MRs-->