Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#821 コメント 5 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
r
領域
release

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
R
スター
679
フォーク
119
平均マージ
1日 11時間
マージ済み PR（30日）
36

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

REditorSupport/languageserver のほかの issue

REditorSupport/languageserver の issue をすべて見る

似ている issue

R の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。