Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Prepare a new release after 0.3.20 and establish a regular release cadence

Abierto
  • ¿Algo no está bien?
#821 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
r
Área
release

Línea de trabajo

Start by reviewing the post-0.3.20 changes summarized in the issue and the existing 0.3.20 section in NEWS.md. Then check the project’s release instructions, dependency requirements, CRAN checks and the failed tagbot run. Done means release notes and version details are prepared, release checks pass, and the maintainers agree on a release and cadence.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Proposal

Could we prepare a new CRAN release, for example 0.3.21, to make the improvements since 0.3.20 available to users? CRAN currently has 0.3.20 (published 24 September 2026); the latest GitHub release is still v0.3.19. The summary below covers changes on master through 12f2585 since the 0.3.20 release preparation (#770).

Major changes since CRAN 0.3.20
  • R object intelligence: Static member completion, hover and signature help for chained objects, R6, S4 and S7, including Polars and package objects; R6 method scopes and initializers are better supported. S3 method dispatch is inferred for completion, hover and signatures. (#784, #786, #791, #808, #818)
  • Pipes and signatures: Signature help and parameter-name inlay hints account for native and magrittr pipes and placeholders; quoted arguments and member access have received completion and signature fixes. (#803, #807, #819, #820)
  • Workspace indexing and responsiveness: Background discovery and package-aware indexing prioritize relevant package sources and static source() dependencies; workspace-wide operations can request a full scan when needed. Provider readiness and worker handling have also improved. (#798, #811, #812, #815)
  • Diagnostics and formatting: Backends are selectable independently, with lintr/styler as defaults and optional Jarl diagnostics, Air formatting and custom R adapters. Folderless diagnostics, .lintr handling and terminal-newline fixes are included. (#774, #782, #801, #809)
  • LSP and navigation: LSP 3.18 support adds read-only generated package definitions, linked names for extraction and nullable active signature parameters for supporting clients. Nested outline sections, definitions and chunks are restored. (#816, #817)
  • Compatibility: The minimum R version is now 4.0.0. lintr and styler are optional dependencies and must be installed for their respective default backends; the default lintr backend requires lintr >= 3.3.0-1. (#783, #809, #813)
Release preparation
  • Update the version and date, and separate the post-0.3.20 notes from the existing 0.3.20 section in NEWS.md.
  • Review release checks and CRAN submission requirements, including the changed R and optional-backend dependencies.
  • Check GitHub release publishing: a recent tagbot run failed with Invalid GitHub PAT format; GitHub currently has no v0.3.20 release.
Regular release cadence

Could we aim for a CRAN release roughly every 1–2 months when meaningful changes are ready, with earlier patch releases for critical fixes? The schedule could be adjusted to maintainer availability and skipped when there is nothing substantial to release. A regular check of accumulated changes, open regressions and release readiness would help keep improvements available without long gaps.

Lenguaje dominante
R
Estrellas
679
Forks
119
Merge medio
1 d 11 h
PR fusionados (30 d)
36

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de REditorSupport/languageserver

Todos los issues de REditorSupport/languageserver

Issues similares

Más issues de R

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.