Allow specific message bundle config ignore for post-install messages

Abierto
#9,808 0 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
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ruby
Área
cli

Línea de trabajo

Comienza rastreando bundle config set ignore_messages.<gem> true y bundle install, centrándote en cómo se seleccionan y suprimen los mensajes posteriores a la instalación. Define cómo se almacena y compara un resumen del mensaje y, después, verifica que un mensaje sin cambios se oculte, mientras que un mensaje modificado o adicional siga apareciendo.

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

Descripción

Bundler
Describe the problem as clearly as you can

bundle config set ignore_messages.<gem> true suppresses all post-install messages from that gem, forever. There's no way to silence one specific message while still seeing a different message the same gem prints later (e.g. a new deprecation notice, or a security warning).

In practice this means teams either live with a message they've already read on every bundle install, or they opt out of that gem's post-install channel entirely and risk missing something that actually matters in the future.

Common real-world examples: readline and httparty both print a post-install message that has stayed identical across many releases. Once you've read it, there's no benefit to seeing it again on every install — but fully ignoring the gem means a genuinely new message (a security notice, a breaking change) would go unseen too.

Did you try upgrading rubygems & bundler?

Yes — reproduced on the latest release.

Post steps to reproduce the problem
  1. Add a gem with a post_install_message to your Gemfile (e.g. httparty).
  2. Run bundle install. Note the message prints every time.
  3. Run bundle config set ignore_messages.httparty true.
  4. Run bundle install again — the message is gone, but so would any future, different message from that gem.
Which command did you run?

bundle install / bundle config set ignore_messages.<gem> true

What were you expecting to happen?

A way to suppress a specific message (e.g. by exact text or a digest of it) so that only that message is silenced — if the gem later changes or adds a different post-install message, it should still show up.

What happened instead?

ignore_messages only accepts a gem name and suppresses every message from that gem indiscriminately, with no content-level granularity.

Proposed API, for discussion:

bundle config set ignore_messages.httparty.<message-digest> true

A digest (e.g. SHA of the message text) matches on the message itself, so it keeps working even if a gem changes its message without bumping the version, and doesn't require Bundler to reason about version ordering.

We considered scoping suppression to the gem version instead (ignore_messages.httparty.<version> true), but ruled it out: gems like readline and httparty keep the same message across many releases, so per-version scoping would force you to re-suppress on every upgrade even though nothing changed — the opposite of "set it once and only hear about it when it's actually new."

Environment
Bundler       4.0.19
  Platforms   ruby, arm64-darwin-23
Ruby          <any>
RubyGems      4.0.19
Lenguaje dominante
Ruby
Estrellas
4k
Forks
2k
Merge medio
1 d 20 h
PR fusionados (30 d)
75

Preparar el entorno

Abrir en Codespaces

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

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 ruby/rubygems

Todos los issues de ruby/rubygems

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.